Set goals and let the team discover how to best achieve them. Hold them accountable only for the outcomes.
In the case of OKRs, ask your teams to propose KRs. This will build a stronger commitment and a sense of ownership.
2. Show trust instead of exercising control
This may seem difficult at first. As a rule of thumb, you should delegate and trust more than you feel comfortable with.
Make sure you provide people with context to enable better, informed decisions.
3. Let others work however they need to
The people closest to the problem and the technology know what they need to do their work.
Do everything possible to let them use any tools, frameworks, or methods they need.
No Jira, no Scrum, or no Git?
No problem.
4. Encourage experimentation and learning from mistakes
It's impossible to construct detailed plans in complex environments. Accept that sometimes goals will not be achieved.
Embrace taking calculated risks. Encourage experimentation and learning from mistakes
5. Become a product evangelist
Communicate vision and strategy regularly so that others can believe in the mission and trust they are going in the right direction. You can do it on every occasion.
This may seem excessive at times, but from my experience, it is essential.
6. Show vulnerability and listen
Feel good about not being the smartest person in the room. Listen carefully. Make sure people feel valued by being in the room with you.
Acknowledge your weaknesses and limitations. Being yourself is one of the best ways to build trust.
Other recommended books, videos, podcasts, newsletters, internships, free courses, videos, and much more (all free): huryn.substack.com/p/the-biggest-…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
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.
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."