Remove Continuous Deployment Remove Customer Development Remove Engineer Remove Framework
article thumbnail

The Entrepreneur's Guide to Customer Development

Startup Lessons Learned

I believe it is the best introduction to Customer Development you can buy. As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. You can imagine how well that worked. On the minus side, that has made it a wee bit hard to understand.

article thumbnail

Lessons Learned: What is customer development?

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? But too often when its time to think about customers, marketing, positioning, or PR, we delegate it to "marketroids" or "suits." Many of us are not accustomed to thinking about markets or customers in a disciplined way.

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: The three drivers of growth for your business.

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. Daily builds are giving way to true continuous integration, in which every checkin to the source control system is automatically run against the full battery of automated tests. Do you make daily builds?

article thumbnail

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

Startup Lessons Learned

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. Great engineers see it and smile. This is called set-based concurrent engineering (SBCE). [1]

article thumbnail

New conference website, speakers, agenda

Startup Lessons Learned

Tactics were discussed out of context, and there wasnt an overarching framework for figuring out what works for what kinds of companies, industries, and stages of growth. Doesnt the communication overhead of a large team lead to chaos of overlapping experiments and continuously-deployed bugs?" "If Is design important to lean startups?

article thumbnail

Two Ways to Hold Entrepreneurs Accountable (for Harvard Business.

Startup Lessons Learned

This whole framework breaks down when teams confront entrepreneurial situations in which theyre trying to build something new under conditions of extreme uncertainty. This whole framework breaks down when teams confront entrepreneurial situations in which theyre trying to build something new under conditions of extreme uncertainty.