Info |
---|
The guidelines are an evolution of Adrian Agho's excellent Product Management 2.0. |
...
Business KPI | Current level | Current level date | Goal level | Goal date |
---|---|---|---|---|
eg. onboarding flow success rate | eg. 50% | eg. as of July 2024 | eg. 80% | eg. October 2024 |
These KPIs and goals should be agreed by the Business Leader and all team members.
...
A template to help you do that is here.
Info |
---|
Writing HMW questions |
...
Brainstorm ideas for solutions to each 'How Might We' question. Do this with all your team present.
Focus on quantity, not quality here. Generate as many ideas as possible.
Prioritise creativity over immediate feasibility.
...
Start by clustering similar ideas in your prototypes into groups. Talk about the best of the ideas.
Once you’ve got a few ideas for elements, start to combine the best elements of your thinking to form a system.
Now you’re moving to the first solution for testing, which contains a number of new and creative ideas.
...
Keep referring back to the KPI you need to improve. Is this directed towards it? Are there elements missing in your solution? What else can you incorporate to come up with a great solution?
There’s a bit of trial and error here. And creating a concept means you’ll probably create a couple that don’t work out. This process is about learning, not getting it right the first time. Better to test a miserable failure and learn from it, rather than take ages making a beautiful, highly refined prototype.
Get real feedback
Now that you’ve got a prototype to share, get it in front of the people you’re designing for.
Capturing honest feedback is crucial. People may praise your prototype to be nice, so assure them that this is only a tool by which to learn and that you welcome honest, even negative feedback.
Share with lots of people so that you get a variety of reactions.
Write down the feedback you hear and use this opportunity with the people you’re designing for to ask more questions and iterate your ideas further.
Integrate feedback into your prototype, and iterate
Note down and gather all the feedback you gathered in the previous step. Note- wait until a batch of interviews are done and iterate your design based on aggregated comments that you’re hearing over and over again- don’t get sucked into iterating the product based on a single piece of feedback.
Build the next iteration of your prototype, based on this feedback.
Remember that this is a method for refining your idea, not for getting to the ultimate solution the first time. You’ll probably do it a few times to work out the kinks and get to the right answer.
...