Startup Lessons Learned

APRIL 29, 2013

Not to mention $200,000 in staff time and hard costs. Generously, it might cost you $20,000. In other words, you could test ten book ideas for the cost of publishing one. Last year, the co -founders of B ack to the Roots talked about their innovation accounting and how they were ignoring sales metrics in order to grow.

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

JUNE 15, 2009

In practice, how developers respond to this dilemma is determined by their incentives, which are driven by the culture of their team. Who will ultimately bear the cost of their mistakes? So developers stuck in this world tend to think the other developers on their team are either, deep in their souls, plodding pedants or sloppy coders.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

FEBRUARY 28, 2009

I used to think that investments in metrics were a form of waste. Customers dont care if you have good metrics, only if you have a good product. The only reason we learned the art of metrics-based decision making at IMVU was out of necessity. But code written that doesnt help the company succeed is a sunk cost.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

ConversionXL

FEBRUARY 9, 2016

In the article, Andrew describes growth hackers as a cross between marketers and coders. Without metrics or data, a growth hacker can feel out of place and uncomfortably exposed. This strong bias towards data drives a growth hacker away from vanity metrics towards metrics that will make or break the business.”

Retention 48

Retention Metrics Acquisition Conversion 48

maplebutter.com

JANUARY 8, 2013

Written By Dan Martell on February 2nd, 2012 | Category: Hiring LeanStartup Marketing Metrics Startup Life | 6 Comments. Building Product 2. Building Metrics / Usage Reports / KPI 3. Product/Metrics (70%/30% time) * Get your product activation (sign-up + meaningful action) to 60% * then, Get your product retention to 20% weekly.

Technical Review 44

Technical Review Startup Cofounder Software Review 44

Startup Lessons Learned

SEPTEMBER 11, 2009

This single decision wound up costing the company significant revenue and over the course of several months sent its customer growth into decline. In the end, we managed to repair the damage, but only after losing a lot of time and at significant opportunity cost. We were totally unprepared for the magnitude of what happened.

Community 158

Community Management Lean Software Review 158