Startup Lessons Learned

MAY 9, 2012

From Lean Startup Machine , Lean LA and San Diego Tech Founders , to countless speeches and workshops, I have seen the impact that their leadership has had first hand. There continues to be an incredible demand out there for actionable, practical lessons in how to apply this emerging set of ideas. It was a fairly organic thing.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

Startup Lessons Learned

SEPTEMBER 15, 2008

This slinging of whatever against the wall to see what sticks does not a market make, is to me a sign of too much capital in the wrong hands, and it's already the most over invested area in recent years- in both human and financial capital- particularly relative to revenue. Case Study: Continuous deployment makes releases n.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? All things being equal, of course, you’d rather have more revenue rather than less. And yet revenue alone is not a sufficient goal. More on that in a moment.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. At IMVU it’s a core part of our culture to ship.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

SEPTEMBER 22, 2008

is an elegant way to model any service-oriented business: Acquisition Activation Retention Referral Revenue We used a very similar scheme at IMVU, although we werent lucky enough to have started with this framework, and so had to derive a lot of it ourselves via trial and error. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

AUGUST 24, 2009

One is explaining the world as it used to work: the importance of gatekeepers, the scarcity implied by limited distribution, and the resulting quality bar that the industry is so proud of. Mostly it is the time and expense required to create the means of distribution for that industry. What is the right revenue model?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

SEPTEMBER 13, 2008

And one day a remarkable thing happened: we started making more than five dollars a day in revenue. ► 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.

SEM 164

SEM San Francisco Lean Continuous Deployment 164