Have you built a prototype of your idea?
The purpose of a prototype is to gather feedback from users and stakeholders and identify areas for improvement.
Once you understand the purpose of your prototype, it’s time to choose the right type of prototype for your needs. There are many different types of prototypes, such as paper, digital, or physical prototypes.
Give your idea/concept a name. Then name the stakeholders who would benefit from it (this should include your persona segment). Now articulate the main problem your concept solves (this should be related to your problem statement/HMW) and describe the idea as a whole.
Illustrate the flow of your solution. Remember this should be as low-fidelity as possible. We don’t want to be looking at aesthetics at this stage, but rather functionality and the user journey.
Suggest reasons why you think your solution might fail – this helps anticipate areas for testing and understanding. Decide what areas you may want to test with users (it may be a specific part of your solution (eg. login). Finally, articulate some ideas around how you would measure the success of your idea.
Map out the steps required to take this idea from this low-fidelity version to mid or high fidelity, through to a beta or live pilot in the real world.