Remove Continuous Deployment Remove Design Remove Early Stage Remove Framework
article thumbnail

Revisiting the Software Design Manifesto (and what's changed since.

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The argument itself got me thinking a lot about design and its role in building products.

article thumbnail

Lessons Learned: Validated learning about customers

Startup Lessons Learned

In an early-stage startup especially, revenue is not an important goal in and of itself. Let’s start with a simple question: why do early-stage startups want revenue? And yet their numbers continue to grow, month after month. But all things are never equal. And yet revenue alone is not a sufficient goal.

Customer 167
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: Don't launch

Startup Lessons Learned

Lessons Learned by Eric Ries Friday, March 13, 2009 Dont launch Heres a common question I get from startups, especially in the early stages: when should we launch? This is the usual reason given for a marketing launch, but for most early stage startups, its a failure. Case Study: Continuous deployment makes releases n.

article thumbnail

A Different Kind of Entrepreneurship Conference

Startup Lessons Learned

The difference matters, because while there are more than enough conferences aimed at startups—more of them every year it seems—so many of them look the same: a succession of speakers who are on the conference circuit, and a series of fast pitches and demos from early-stage startups. The fine art of experimentation.

Lean 166