- It’s about building the minimal product to start, and getting customers to start using it. Incorporate their feedback, which may take you in a very different direction from the features you had planned. Great example: Twitter.
- “The Curse of Prevention”: When you anticipate a problem too much/try to prematurely solve it, not only do you waste a lot of time by solving a problem that might not arrive, scalability is messy.
- Sales, Marketing & Business -> The Problem Team. What is the problem we are trying to solve? Focused on talking to customers.
- Engineering, Ops & QA -> The Solution Team. Build the minimal viable product. What is the minimal amount of work needed to be done to test the first element of the product?
- Code is not progress. Learning is progress. It’s not just about milestones and deliveries.
- After features are shipped, don’t just move onto the next features. Check that the features you delivered were the right ones. After the code is done, evaluate if that task was worth doing in the first place.
Comments are closed.