Startup Lessons Learned

MARCH 25, 2010

(for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Similar results apply in product management, design, testing, and even operations. Take the example of a design team prepping mock-ups for their development team.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

APRIL 4, 2010

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 22, 2008

For Neopets, its simply a side-effect of their game-like product design. Either way, you can use any marketing channel thats available to bring in new customers, including word of traditional advertising, SEO, SEM - wherever you can find prospects who are going to find your product addicting. April 23, 2010 in San Francisco.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Platform selection and technical design - if your business strategy is to create a low-burn, highly iterative lean startup, youd better be using foundational tools that make that easy rather than hard.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own. Bring your questions.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 15, 2008

This kind of result is typical when you ship a redesign of some part of your product. The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 2, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

NOVEMBER 6, 2008

They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Anyway, thanks Stevey for your thoughtful post. . April 23, 2010 in San Francisco. Bring your questions.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

JANUARY 18, 2010

If youre interested in contributing a case study for publication here, consider getting started by adding it to the Lean Startup Wiki case study section. Prior to starting any maker activity, I clearly identify what needs to get done (the goal) and sketch out how it needs to get done (the design).

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

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. Good luck, engineering manager. It was painful for a lot of people.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 2, 2008

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 10, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

JUNE 2, 2010

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 12, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries. April 23, 2010 in San Francisco.

Agile 111

Agile Customer Development Developer San Francisco 111

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

Startup Lessons Learned

JANUARY 2, 2009

My son is planning a software product that will take the mystery out of wikis and make the technology easier for consumers to use. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. You can read the article to find out why. 3comments: Charles Crawford said. Thank you for this excellent article.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0 Expo to explain the lean startup concept to a larger audience.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

JULY 30, 2009

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

Lean 68

Lean San Francisco Continuous Deployment DC 68

bizthoughts.mikelee.org

MARCH 8, 2012

Categories Blogs (35) Book Summaries (5) Business (76) Business Travel (7) Design (27) Entrepreneurship (89) Environmentalism (9) Finance (13) Friday Fun (33) Globalization (6) Ideas (42) Innovation (20) Investing (23) Leadership (10) Management (50) Marketing (82) Media (27) Mobile (18) Organizational Behavior (34) Product Development (7) Psychology (..)

Technical Cofounder 40

Technical Cofounder Cofounder Technical Review Software Review 40

Startup Lessons Learned

AUGUST 26, 2009

And one last specific practice that came up at this session: feverishaaron : UI, design and programmers are all in the same department, all have the same title, and all are evaluated the same. That meant getting designers, programmers, and QA folks to cross-train and work together as peers. April 23, 2010 in San Francisco.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

JULY 6, 2009

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

JANUARY 15, 2010

Behind this analysis is a spreadsheet model, complete with detailed metrics for a set of customer behaviors that show just how valuable the new product will be. Behind this analysis is a spreadsheet model, complete with detailed metrics for a set of customer behaviors that show just how valuable the new product will be.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

JULY 5, 2010

While maintaining persistence and willpower is certainly good advice, Customer Development methodologies are designed to give you data and feedback you may not want to hear. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. It is incumbent upon you to listen. April 23, 2010 in San Francisco.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

NOVEMBER 4, 2008

Eric, Any thoughts on how forum feedback fits into customer development and agile product development? Youve probably addressed this in the past, but I continue to be blown away by how fast Blizzard reacts to noise in their forums and rapidly makes fixes to the product. . =) November 4, 2008 10:58 PM IMVU said.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JANUARY 7, 2010

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 2, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

NOVEMBER 8, 2008

You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Our goal in product development is to find the minimum feature set required to get early customers.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

DECEMBER 28, 2009

Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. Its likely that the new release will contain new bugs.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

SEPTEMBER 14, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

SEPTEMBER 1, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68