1. Creating products is complex. It can't be planned in detail.
When working on products, you must run small experiments, inspect, and adapt as you go.
"In complex environments, what will happen is unknown." - Scrum Guide 2020
2. Most of your ideas are just not going to work.
- The customers do not desire it
- Users won't know how to use it
- Ideas are not viable for your business
- Technology doesn't allow it
"The first truth is that at least half of your ideas are just not going to work" - @cagan
3. You won't do it right the first time.
"(...) even with the ideas that do prove to have potential, it typically takes several iterations to get the implementation of this idea to the point where it actually delivers the necessary business value." - @cagan, Inspired.
4. Roadmaps will only slow you down.
They won't make you deliver more value or make your work more predictable. Instead, they may shift your focus from outcomes to outputs.
"typical roadmaps are the root cause of most waste and failed efforts in product organizations" @cagan
5. Customers do not know what they need. Your stakeholders either.
An interview with a customer resembles a visit to a doctor. Some people can tell you what hurts them, but they rarely can make a diagnosis, let alone propose treatment.
The only logical conclusion is:
- Give up control
- Empower your teams
- Encourage experimentation
- Inspect and adapt as you go
- Focus on the outcomes
Why is it so hard to understand?
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1. Sometimes, you get specific requirements (outputs) from powerful stakeholders or the company's founders. Reverse-engineer them by asking: "how do you measure the success"? And then, "If I do it differently, would that be ok?"
After a few questions, you have your outcomes.
2. If strategy 1 doesn't work, wait one day and say: "We'd like to use OKRs as Google does." Then reverse-engineer the requirements and start the discussion about OKRs.
Define objectives as outcomes. You have your outcomes.