Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

Steve Blank

JUNE 25, 2009

Computer hardware companies were faced with their customers asking for low-cost (relatively) desktop computers they had no experience in building. They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. The result wasn’t what I expected. Help them?!!

Technology 143

Technology Silicon Valley Fractional VPE Part-Time VPE 143

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down? This is the first post that moves into making specific process recommendations for product development. Hence, cutting corners often paid huge dividends.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

YoungUpstarts

OCTOBER 24, 2012

He was building a better enterprise software product, and to get the word out, he organized ‘City Tour’ events and neighborhood ‘street teams.’ The City Tour events would bring his customers together with prospects and a few other interesting people for presentations and group discussion. Build strong customer communities.

Marketing 234

Marketing Software Review Technical Review Social Network 234

Startup Lessons Learned

NOVEMBER 7, 2008

We spent weeks working on this new product, racing the clock so it would be done in time for the real presidential debates. We had endless arguments internally about what features it should include, how the avatars should look, and how much it should cost. Just load them all in and choose a low cost-per-click. I used to use $.05,

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. Seth Godin: How often should you publish?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

YoungUpstarts

SEPTEMBER 12, 2012

by Bill Lee, author of “ The Hidden Wealth of Customers: Realizing the Untapped Value of Your Most Important Asset “ The old paradigm works like this: Your company produces goods and services that help customers get a job done. In return, the customers pay you money. Why would customers make such an effort?

Customer 168

Customer Social Media Retention Canada 168

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. Although it costs to pay down the principal, we gain by reduced interest payments in the future. Instead, we balance lots of unknowns.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 30, 2008

If the CEO wants to completely change the product in order to serve a new customer segment, you need someone in the room who can digest the needs of the new (proposed) business, and lay out the costs of each possible approach. In my mind, theyre racking up costs (one month for that part, two months for that other part, uh oh).

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Steve Blank

AUGUST 29, 2016

The end result is often that change can happen but it is going to come at the cost of disruption and difficulty.”. The process starts by collecting agency-wide ideas and/or customer problems, collecting a group insight, and sorts which problems are important enough to pursue.

Lean 182

Lean Silicon Valley Government Acquisition 182

Steve Blank

AUGUST 29, 2016

The end result is often that change can happen but it is going to come at the cost of disruption and difficulty.”. The process starts by collecting agency-wide ideas and/or customer problems, collecting a group insight, and sorts which problems are important enough to pursue.

Lean 182

Lean Silicon Valley Government Acquisition 182

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. He wrote it in 2000, and as far as I know has never updated it.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Steve Blank

AUGUST 27, 2009

This series of posts is a brief explanation of how we’ve evolved from Product Development to Customer Development to the Lean Startup. The Product Development Diagram Emerging early in the twentieth century, this product-centric model described a process that evolved in manufacturing industries.

Silicon Valley 269

Silicon Valley Product Startup Product Development 269

Steve Blank

JULY 30, 2009

Some are r esegmenting an existing market– directed at a niche that an incumbent isn’t satisfying (like Dell and Compaq when they were startups) or providing a low cost alternative to an existing supplier (like Southwest Airlines when it first started.) Whenever he did that most vendors would ignore him in the meeting.

Silicon Valley 143

Silicon Valley RSS California Customer Development 143

Startup Lessons Learned

AUGUST 2, 2008

It costs not just the time of the actual meeting, but the time getting there and back, and the time preparing for it beforehand and thinking about it afterward. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. Thats why we need continuous integration and test-driven development.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

FEBRUARY 20, 2009

Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Labels: five whys root cause analysis , product development 11comments: Peter Severin said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Interesting post.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 8, 2008

It cost us a few hundred thousand dollars to get our app up and running, but none of that was dollars spent on software licenses or professional services. We just had our app support a few tens of thousands of customers, and it did well. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

MARCH 29, 2010

Heres a tiny sample: "Case studies, case studies, case studies presented by real people. Then, well talk case studies in each area, presented by practicing entrepreneurs who have actually grappled with the topic at hand. Heres a tiny sample: "Case studies, case studies, case studies presented by real people.

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: Expo San Francisco 2009 The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. It uses principles of agile software development, open source and web 2.0,

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

JULY 3, 2009

davemcclure : amazing concepts on Continuous Development => "Cluster Immune System" @EricRies #LeanStartup @fbFund [link] dalelarson : Because most features take longer to argue and prioritize than to build. Although there is cost and overhead associated with continuous deployment, the benefits are immense. Now for the feedback.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

MAY 27, 2009

Heres their description of the event: The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Steve Blank

MARCH 15, 2011

The Nine Teams Present. Each week every team presented a 10 minute summary of what they had done and what they learned that week. As each team presented, the teaching team would ask questions and give suggestions (at times pointed ones) for things the students missed or might want to consider next week. in Control Systems.

Business Model 238

Business Model Nebraska Peru Germany 238

Startup Lessons Learned

SEPTEMBER 2, 2008

In an eyeballs business, you just cant seem to acquire or activate that next step-up of customers. Or your cost of customer acquisition just magically floats up to match your customer lifetime value. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Steve Blank

MARCH 1, 2010

While most investors don’t actually read your business plan for a first meeting, a summary of your competitive analysis usually ends up as a slide or two in your PowerPoint presentation. Get to work and add all of these for first customer ship.”. Product development salutes and gets to work building the product.

Customer Development 263

Customer Development Metrics Differentiation Engineer 263

Startup Lessons Learned

APRIL 18, 2010

Truth: The Lean Startup method is not about cost, it is about speed. Lean Startups waste less money, because they use a disciplined approach to testing new products and ideas. Lean, when used in the context of lean startup, refers to a process of building companies and products using lean manufacturing principles applied to innovation.

Lean 167

Lean San Francisco Continuous Deployment Startup 167

Startup Lessons Learned

JUNE 15, 2009

In practice, how developers respond to this dilemma is determined by their incentives, which are driven by the culture of their team. Who will ultimately bear the cost of their mistakes? One of the distinctions that has helped at the executive level is to stress that you're reducing the COST of failure, rather then its PROBABILITY.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

JUNE 5, 2009

If it costs $0.10 to acquire an early adopter, how much should it cost to acquire a mainstream customer? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? But proving your assumptions with early adopters is an essential first step. But $10.00?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

AUGUST 24, 2009

So let’s turn our attention from what may happen in the future to what is definitely happening in the present. As the costs of production fall, it’s getting easier and easier to send in a proposal or even a complete work. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JUNE 17, 2010

And lastly, it removes the engineering team’s ability to find breakthrough solutions that might deliver most of the value at a fraction of the cost. And lastly, it removes the engineering team’s ability to find breakthrough solutions that might deliver most of the value at a fraction of the cost.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

OCTOBER 5, 2010

It is the ultimate product development get-started guide to Lean Startup. Also included is the incredible Venture Hacks Bible, which is worth the price of admission on its own, and The Entrepreneurs Guide to Customer Development (which I previously reviewed here). And theres so much more. Phew, Im exhausted.

Lean 153

Lean San Francisco Startup Continuous Deployment 153

Steve Blank

NOVEMBER 2, 2009

For those of you who have been following the discussion, a Lean Startup is Eric Ries ’s description of the intersection of Customer Development , Agile Development and if available, open platforms and open source. The Customer Development process (and the Lean Startup) is one way to do that.

Lean 260

Lean Silicon Valley Startup RSS 260

Startup Lessons Learned

SEPTEMBER 19, 2009

In my presentation this morning, I emphasized three key areas: reducing the personal cost of failure for entrepreneurs, innovation-friendly legal reforms, and access to the digital means of production (slides from my White House presentation are available at the end of this post). The Geeks are doing their part.

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

OCTOBER 19, 2009

"We do not develop a product until we get a paying customer," says Orit Pennington , who co-founded the six-employee company with her husband in 2002. Development time is typically no more than two to three weeks, and it generally takes just a few orders to cover development costs. Read the rest.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137