1. Stakeholders decide on the high-level roadmap 2. PM refines the details and creates User Stories ("WHAT") 3. Work is waterfalled to the DEVs, who only decide "HOW" 4. Designer tries to make it prettier. It's like lipsticking a pig
You know what I think? Waterfall and stage gates. Even if you use an Agile framework, don't lie to yourself. That's a project mindset.
How to clean up this mess?
1. Company defines goals (e.g., OKRs)
It's essential to realize that OKRs are not a list of tasks. Their goal is to create focus on what's not urgent yet critical for the business's long-term growth. Select only one OKR for every team. You can sequence them if needed.
In addition, ask the team to define Key Results. This helps build a stronger commitment and sense of ownership and results in better decisions.
Learning by delivering is expensive. According to @cagan, at least half of your ideas are simply not going to work. We need Product Discovery, which answers the question "WHAT to build."
Instead of building silos with stage gates, embrace a collaborative approach. PM, Designer, and at least one Engineer work together to identify opportunities related to the goal, ideate solutions, and test assumptions. Product Discovery results in a validated Product Backlog.
Tips:
- It's a Designer's job, not the Product Manager's, to create user prototypes. She is the expert responsible for Usability.
- The best ideas often come from Engineers. They are the experts who know technology by heart and can tell WHAT's possible.
While the goal of Product Discovery is to answer the question "WHAT to build," the purpose of Product Delivery is to build it. Those streams should run in parallel.
Working with individuals is not enough. To achieve great outcomes, you need to work with the entire team. Eliminate internal competition, egos, and conflicts. Make sure everyone is aligned around shared values and goals.
2. Leadership can only be earned
Your top priority is coaching people and helping them grow. Listen and pay attention. Carry about their well-being and support them when they need it.
"If 'you're a great manager, your people will make you a leader. They acclaim that, not you"
Ask yourself: What are their problems, needs, and desires? What's truly important to them? What jobs do they want to perform? By which outcomes will they evaluate your product's value?
A common mistake is to focus too much on a particular solution. Theodore Levitt famously said, "Customers don't want a drill, they want a hole in the wall."
Sometimes there might be some UI guy who takes care of selecting stock photos or modifying the CSS styles. But in reality, the usability of the product is not taken seriously by anyone.
So the usability sucks.
2. The Designer is engaged too late.
The Designer is asked for help when low-fidelity prototypes are ready, or worse, once the application is built. Their only job is to "make it prettier."
No matter how much they try, it's like lipsticking a pig.
• The number one book for all Product Managers.
• Most of your ideas are not going to work.
• Principles of product discovery, which results in a validated product backlog.
• You need to be very specific when identifying the most important business problems.
• Your role as a leader is to help everyone on the team achieve the competence necessary to solve those problems.
The biggest collection of PM learning resources: books, podcasts, videos, internships, free courses, conferences, frameworks, and much more (October 2022): 🧵