A few controversial things I believe about PM and growth:
1) Customer outcomes over business metrics
Pursuing only business results is a silly goal.
Because users are too often forgotten.
Customer outcomes are a better pursuit in the long term: 🧵
• Delighted customers impact your business > $$$
• Happy customers stay with you longer > lower churn
• They can't stop talking about the product they love > growth
Contrary to popular belief, OKRs are not "the most important" tasks.
Their goal is to create focus on what's not urgent yet critical for the long-term growth of the business (strategy). You should select only one OKR. You can sequence them if needed.
Selecting many OKRs is a fast-track to multitasking. As a result, many things are being done, but nothing is ever finished.
I'm not saying you shouldn't coach individual employees.
I’m just saying you should take care of the team first. Eliminate internal competition, egos, and conflicts. Align everyone around shared values and goals.
Also, never hire an a**shole, no matter how brilliant he or she is.
Instead, focus on understanding their problems, needs, and desires in-depth. @ttorres has a great framework for discovering what to build, without falling into the Product Death Cycle Trap:
• As a PM, work with the Designer and Engineer
• Interview customers regularly
• Map opportunities (opportunity solution tree)
• Ideate possible solutions
• Identify hidden assumptions
• Test the riskiest assumptions by running experiments
Bill Gates, Elon Musk, and Barack Obama. There is a common principle followed by highly successful people. They all spent at least five hours a week reading, or rather, on self-improvement.
You can start with the biggest collection of PM learning resources (free):
Take the MVP test results as proof and execute your plan in a waterfall style. Without regular inspection and adaptation, your plan will fall apart like a house of cards.
Shot to the moon.
2. Agile
Pick an Agile framework like Scrum. Start without validating your business model. Came up with ideas and deliver them in iterations.
Most ideas are not going to work. And your product probably never had a chance to achieve the Product-Market fit.
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.
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."