article thumbnail

Lessons Learned: Customer Development Engineering

Startup Lessons Learned

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Its a nice complement on the product engineering side to his customer development methodology.

article thumbnail

Lessons Learned: The three drivers of growth for your business.

Startup Lessons Learned

I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." Paid - if your product monetizes customers better than your competitors, you have the opportunity to use your lifetime value advantage to drive growth.

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 lean startup

Startup Lessons Learned

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168
article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

So I initially gravitated to the CTO title, and not VP of Engineering. But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. I want to add one last idea, even though I recognize it is controversial, bordering on the boundary between the CTO and VP Engineering. Heres my take.

CTO 168
article thumbnail

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

Startup Lessons Learned

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. why couldnt the engineer see the problem in their sandbox?

article thumbnail

Lessons Learned: Just-In-Time Scalability

Startup Lessons Learned

Thoughts on scientific product development Lo, my 5 subscribers, who are you? SEM on five dollars a day Andrew Chen: Growing renewable audiences Marc Prensky's Weblog: Cell Phones in Class A new version of the Joel Test (draft) Smarticus — 10 things you could be doing to your c.

article thumbnail

Lessons Learned: Ideas. Code. Data. Implement. Measure. Learn

Startup Lessons Learned

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. Thoughts on scientific product development Lo, my 5 subscribers, who are you?