Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting. October 13, 2008 6:47 PM Luke G said. Eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

JUNE 2, 2010

As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Techniques from lean manufacturing can be part of a startups innovation culture. Speed up or slow down?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

AUGUST 2, 2008

Its to everyones advantage to let the world think the founders thought of everything. I say this as a founder: the contribution of founders is always overestimated. The danger here is that new founders, looking at existing founders, will think that theyre supermen that one couldnt possibly equal oneself.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 15, 2008

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. The designers might be telling you that the new design looks much better than the old one, and thats probably true.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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

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. They are on-schedule and on-budget, but their gross metrics are way off. They are on-schedule and on-budget, but their gross metrics are way off.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

SEPTEMBER 15, 2008

Mark Montgomery Founder Kyield Initium VC September 12, 2009 4:21 AM Mark Montgomery said. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Otherwise it's a great idea.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

JULY 3, 2009

If your practice is not designed to cope with uncertainty, it has no place in a startup - even if your startup is located in government or enterprise. Now, I dont think even most dot-com era founders were bad people, I just think traditional startup methods make it too easy to become confused about whether were creating real progress or not.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

SEPTEMBER 2, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned - the Conference (April 23.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JULY 5, 2010

I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. 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.

Customer Development 166

Customer Development Developer San Francisco Customer 166

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. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

AUGUST 26, 2009

Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. 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. Revisiting the Software Design Manifesto (and what.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

SEPTEMBER 10, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned - the Conference (April 23.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 8, 2008

This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Instead, we do everything possible to validate the founders belief. Most people cant sustain more than a few of these iterations, and the founders rarely get to be involved in the later tries. Heres the catch.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

FEBRUARY 8, 2010

Lessons Learned by Eric Ries Monday, February 8, 2010 Beware of Vanity Metrics (for Harvard Business Review) The next article in my series on entrepreneurship for Harvard Business Review is live today. Once again, we revisit the topic of Actionable metrics and their nemesis: Vanity metrics. Remember "metrics are people, too."

Metrics 121

Metrics San Francisco Lean Continuous Deployment 121

Startup Lessons Learned

JANUARY 7, 2010

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned - the Conference (April 23.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

JANUARY 2, 2009

The core of the article is my first attempt to articulate the key metrics (in graph form) that I believe demonstrate customer value. My son is planning a software product that will take the mystery out of wikis and make the technology easier for consumers to use. You can read the article to find out why. Bring your questions.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. Every board meeting, the metrics of success change. These founders have not managed, to borrow a phrase from Steve Blank , to create a scalable and repeatable sales process.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 12, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned - the Conference (April 23.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. April 23, 2010 in San Francisco.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

SEPTEMBER 7, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned - the Conference (April 23.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Your CTO might be a great architect, evangelist, interface designer or incredible debugger. Great piece!

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JANUARY 18, 2010

Ash Maurya is the founder of WiredReach , a bootstrapped startup that he has been running for seven years. 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. This case presents a further complication: desktop software.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

SEPTEMBER 2, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned - the Conference (April 23.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

MARCH 25, 2009

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned - the Conference (April 23.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

JULY 6, 2009

Its also frustrating how some founders see ANY form of struture/approach as limiting and go to the total reverse of waterfall by just doing what they were told by "their wifes friend" This is great and practical stuff.will make sure I pass it on and use in my discussions (giving credit to you!) April 23, 2010 in San Francisco.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

JULY 9, 2010

Lessons Learned by Eric Ries Friday, July 9, 2010 Founder personalities and the “first-class man&# theory of management At any given time, something like four percent of the US population is engaged in some form of new-company-creation. Are we solving the right problem? We can do better by focusing on process instead of personality.

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

JULY 30, 2009

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned - the Conference (April 23.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

NOVEMBER 17, 2008

Growth - when you have existing customers, the pressure is on to grow your key metrics day-in day-out. Some companies and founders refuse to serve existing customers, and are always lurching from one great idea to the next. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

MARCH 17, 2009

Eric- I am an industrial design student at Virginia Tech. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Tried it with multiple browsers. March 19, 2009 9:34 PM Chris Morgan said.

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

MARCH 16, 2009

Thats why I prefer to think of them as two co-equals: the problem team and the solution team. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. April 23, 2010 in San Francisco.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

MARCH 29, 2010

Weve gone from total obscurity to something people are beginning to misunderstand and even co-opt. If you just throw a minimum viable product out the door to see what sticks, wont that necessarily be ugly and badly designed? Is design important to lean startups? Is design important to lean startups? Congratulations.

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

JULY 28, 2010

Andy Mathieson, a founder and managing member at Fairview Capital , was particularly supportive. Andy Mathieson, a founder and managing member at Fairview Capital , was particularly supportive. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. The response was surprisingly positive.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

SEPTEMBER 14, 2008

Today, when I talk to startup founders, the most common answer I get to the question "do you talk to your customers?" ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Bring your questions.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

JUNE 8, 2009

That’s because many of our reports feed us vanity metrics: numbers that make us look good but don’t really help make decisions. Yet even among those who have access to good actionable metrics, I’ve noticed a phenomenon that prevents taking maximum advantage of data. Too much of this data is non- actionable.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84