91: How to sharpen up your vision and strategy
You can help your company to sharpen up its vision and strategy with these straightforward questions and worked examples.
You can help your company to sharpen up its vision and strategy with these straightforward questions and worked examples.
» Every decision is a trade-off — deciding what not to do is just as important as deciding what to do
» A good product vision captures customer, user, value proposition and links to organisational objectives
» Interrogate your goals: “For this to happen, what must be true?”, then mark which are facts or assumptions
» Avoid jumping on the first idea — check what problem we think it solves, then ask, “How else could we do this?”
When your stakeholders each have their own interpretations of the product strategy, this lack of stakeholder alignment will cause you no end of problems. Here’s what you can do about it.
» What happens when words and deeds don’t align
» More than office decoration: taking a stand on core values
» When our values are aligned to the things we create, work doesn’t feel like work
» What is meant by the word “brand”
I gave a talk recently about how I’ve been using data and analytics to guide my decisions in product management. I’ve edited the transcript a little and split it into bite-size parts for your entertainment. This final bit tells the secret behind meaningful product roadmaps.
Here’s another question I was asked recently:
If you’re concerned about buyer needs and their objectives, how closely aligned do you suggest product organisations be with marketing and with the persona development to ensure they are creating a solution that does meet those needs in the market?
Here’s my answer:
The interview covers things like:
thinking about outcomes, not outputs; alignment with broader goals; finding and measuring leading indicators; and the 5 most important metrics for product managers.
Your developers may be happiest when they’re hacking gnarly code, leaving you to get on with engaging with the market, but this doesn’t mean you can ignore their need for context – the ‘why’ of their project.