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

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.

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: Validated learning about customers

Startup Lessons Learned

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. Case Study: Continuous deployment makes releases n.

Customer 167
article thumbnail

The Principles of Product Development Flow

Startup Lessons Learned

Reinertsen weaves together ideas from lean manufacturing, maneuver warfare, queuing theory, and even the architecture of computer operating systems and the Internet. If we showed the Toyota Production System to an Internet protocol engineer, it is likely that he would remark, "That is a tail-dropping FIFO queue.

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

What would you want to tell Washington DC about startups?

Startup Lessons Learned

Of course, the real thanks should go to a startup - Gogo Inflight Internet - that I was lucky enough to meet at a recent workshop. 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. Thanks guys!)

DC 90
article thumbnail

Lessons Learned: The metrics and levers of engagement.

Startup Lessons Learned

The solution for app developers caught in this vicious cycle is to develop competency in positioning. I would bet (although I don't have the data) that for normal (non-hyper-addict) Facebook users, the time between logins is strongly correlated with the number of high-quality notifications they receive. So, in summary: 1.

Metrics 88