Remove Acquisition Remove Agile Remove Customer Development Remove Retention
article thumbnail

Why Build, Measure, Learn – isn’t just throwing things against the wall to see if they work

Steve Blank

Best practices in software development started to move to agile development in the early 2000’s. This methodology improved on waterfall by building software iteratively and involving the customer. With Agile you could end up satisfying every feature a customer asked for and still go out of business.

Lean 120
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. The AARRR model (hence pirates, get it?)

Insiders

Sign Up for our Newsletter

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

article thumbnail

Why Companies are Not Startups

Steve Blank

These groups are adapting or adopting the practices of startups and accelerators – disruption and innovation rather than direct competition, customer development versus more product features, agility and speed versus lowest cost. existing enterprises are establishing corporate innovation groups. This is a big idea.

IRR 335
article thumbnail

Lessons Learned: Validated learning about customers

Startup Lessons Learned

Some products have relatively obvious monetization mechanisms, and the real risks are in customer adoption. Products can find sources of validation with impressive stats along a number of dimensions, such as high engagement, viral coefficient, or long-term retention. Go on an agile diet quickly. April 15, 2009 4:06 PM Eric said.

Customer 167
article thumbnail

Lessons Learned: The App Store after the gold rush

Startup Lessons Learned

The App Store is a channel for customer acquisition. I think its helpful to think about two kinds of competition for distribution: acquisition competition and retention competition. Acqusition competition is how new apps get new customers. Retention competition is how you get people to come back to your app.

article thumbnail

Product design debt versus Technical debt

andrewchenblog.com

Coupled with A/B testing, customer development, and thinking through business problems in a scientific, hypothesis-driven way, you end up with a powerful cocktail of techniques to build a modern startup in the most iterative way possible. We’ll call this general category of debt Type I. You can also find more essays here.

article thumbnail

Lessons Learned: The metrics and levers of engagement.

Startup Lessons Learned

At IMVU , we would routinely find retention effects that would stem from registration changes and have impact days or weeks later. Why, we just unified acquisition and engagement! I do think the concept allows us to unify acquisition and engagement, and is important for that reason. helping you balance engagement vs acquisition.

Metrics 88