Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 17, 2008

Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. Conference streaming, sponsors, discounted tickets. for Harvard Business Revie.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

NOVEMBER 13, 2008

Its why, at my previous job, we were able to get a new engineer completely productive on their first day. We had a great on-boarding process, complete with a mentoring program and a syllabus of key ideas to be covered. Most engineers would ship code to production on their first day. for Harvard Business Revie.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

MARCH 22, 2010

In the past two decades, they have accounted for nearly all the net job growth in our country. In the past two decades, they have accounted for nearly all the net job growth in our country. Part of this is due to their determination to overtake us, but part is due to structural changes in the nature of entrepreneurship.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

NOVEMBER 14, 2013

We’ve posted the full program for The Lean Startup Conference , and it includes more than three days of events for Gold pass holders and six days of events for VIP pass holders. It can’t work if developers have the attitude that they’re done once their code works on their machine and it’s checked into version control.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

Startup Lessons Learned

SEPTEMBER 13, 2008

We ran ad campaigns against every single product we could think of in an adjacent market space to ours. Since we were only paying per click, it didnt cost us anything to cast a wide net. We would pretty much bid on any phrase that was "[name of competitive product] chat" and variations like that. for Harvard Business Revie.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

JULY 2, 2009

These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules. I pick that example on purpose, for two reasons: 1) most of the companies I work with deal with this problem and yet 2) almost none of them have any kind of training program in place for new employees.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

AUGUST 8, 2009

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. Firmness: A program should not have any bugs that inhibit its function. We owe a lot to this seminal document.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

MARCH 27, 2009

Even if it helps optimize one stage, if it slows you down somewhere else, it might not be a net win. Customer Development : a disciplined approach to finding out if there is a market for your product before its too late. Customer Development Engineering : techniques for accelerating your product development.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

OCTOBER 26, 2009

In previous posts, I’ve mentioned quite a few of these, including these most important ones: having engineers post on the forums in their own name when they make a change routinely split-testing new changes routinely conducting in-person usability tests and interviews Net Promoter Score Each of these techniques is fundamentally bottoms-up.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

SEPTEMBER 14, 2008

Some techniques that Ive found especially helpful: Build your own tracking survey, using a methodology like Net Promoter Score (NPS) to identify and get a regular check-up from promoters (and to screen out detractors). Thoughts on scientific product development Lo, my 5 subscribers, who are you? for Harvard Business Revie.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

NOVEMBER 18, 2008

I believe its important that product teams be cross-functional, no matter what other job function the product champion does. Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. Its even more critical in lean startups when they need to manage growth. Amazon PostRank

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JANUARY 12, 2009

Lessons Learned by Eric Ries Monday, January 12, 2009 Why PHP won When I first learned to program on the web, Perl + CGI was the dominant platform. Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. Thats simply impossible on most platforms.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

NOVEMBER 17, 2008

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

NOVEMBER 5, 2008

Obama understood the two concepts that are essential for building a high-performance, highly adaptable, agile organization: 1) rapid iteration and 2) clear values-based objectives. Mission synchronization If an organization is changing on a daily basis how is it that it doesnt look "erratic" yet feels "agile."

Campaign 84

Campaign San Francisco Lean Agile 84

Startup Lessons Learned

JANUARY 18, 2010

My transition to Continuous Deployment Prior to adopting continuous deployment, I used to release software on a weekly schedule (come rain or shine) which I viewed as pretty agile, disciplined, and aggressive. With staged releases, time provides a (somewhat illusory) safety net. On the other hand, it is scary as hell.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

SEPTEMBER 29, 2008

Revenue is always my preferred measure, but you can use anything that is important to your business: retention, activation, viral invites, or even customer satisfaction in the form of something like net promoter score. Thoughts on scientific product development Lo, my 5 subscribers, who are you? 1 comments: Andrew Meyer said.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

MARCH 4, 2009

Thanks to those of you who were willing to fill out the survey, I learned my net promoter score (about 25) as well as some clear other segmentation insights: about 80% of you are founders of or work at a startup, you read many of the same other blogs, and many of you would like to engage with Lessons Learned in formats and venues beyond this blog.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

NOVEMBER 5, 2008

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

Startup Lessons Learned

NOVEMBER 19, 2008

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60

Startup Lessons Learned

NOVEMBER 11, 2008

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa.

Silicon Valley 68

Silicon Valley San Francisco Lean Continuous Deployment 68

Startup Lessons Learned

DECEMBER 16, 2008

But if your new positioning message improves your engagement loop by more than the cost to your viral loop , you have a net win on your hands. Since your viral ratio is still above one, its still getting your message out, albeit a little slower. Conference streaming, sponsors, discounted tickets. for Harvard Business Revie. Amazon PostRank

Viral 140

Viral San Francisco Lean Continuous Deployment 140

Startup Lessons Learned

JULY 9, 2009

Of course, those were the days when 12 year old, 80% market share, $200mm, 30% net profit companies were the ones going public. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94