Remove Continuous Deployment Remove Metrics Remove Non-Compete
article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage.

article thumbnail

Lessons Learned: The metrics and levers of engagement.

Startup Lessons Learned

Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. Unfortunately, its easy to lose track of positioning effects when optimizing for a single metric.

Metrics 88
Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

Lessons Learned: A hierarchy of pitches

Startup Lessons Learned

Its different from selling a product, because it is not part of our regular business practice, is not something that relates to our core competence, and tends not to happen in a repeatable and scalable way. Ill exclude those non- lean startups who basically exist for the purpose of raising bigger and bigger sums of money.

article thumbnail

Lessons Learned: Validated learning about customers

Startup Lessons Learned

Every board meeting, the metrics of success change. This approach is fundamentally non-scalable. This is why companies often get out-competed by former employees (Palm vs Handspring to name just one), even though the upstart lacks all of the familiar resources, tools, processes, and support they used to have.

Customer 167
article thumbnail

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

Startup Lessons Learned

Worse of all, the plaintext codes we were used to sending were considered non-authoritative, since they could be pulled off a third-party network. There's lots of information about performance and metrics out there, as well as a peer expectation that being concerned about those things is an important part of being a competent engineer.

article thumbnail

What would you want to tell Washington DC about startups?

Startup Lessons Learned

I'm a bit late, and this one might be controversial to some, but long-duration non-competes hurt the development of startups by adding friction to the entrepreneurial economy. Case Study: Continuous deployment makes releases n. Truth be told, we've got defense contractors here just like California does too.

DC 90
article thumbnail

The Principles of Product Development Flow

Startup Lessons Learned

Many of the startups I talk to - and their boards - seem to equate ability to "hit the schedule" with competence and productivity. Even worse, and unlike their established counterparts, startups often experience a non-quantifiable cost of delay. Case Study: Continuous deployment makes releases n. Does this sound familiar?