Define
We prioritised the problem statements based on their score for added value to the user and business. The total score determined the order of priority. To approach a specific problem or challenge in a creative manner, we use "How Might We" statements. This helps break down the problem into smaller, manageable pieces.
We document all questions, assumptions, and risks per "How Might We" statement to gain a clear understanding from the outset. This allows us to differentiate between what we are certain about and areas where further research is needed. And prioritise these HMWs based on the frequency of occurrence of the problem against the level of user pain experienced.
Example of mapping out the questions, assumptions and risk for the HMW: How might we improve message professionalism for admins with headers and footers?
Before making the various solutions testable, it's wise to understand the ecosystem and the potential impact of this feature. Additionally, it's crucial to identify risks to consider during the design process and, equally importantly, during prioritisation.
Understanding your product's ecosystem
Knowing your product's ecosystem is super important. When you map it out, you can see how everything's connected, figure out what relies on what, spot risks, and find opportunities. This helps make sure your product lines up with what your company wants and what users need.
