Useful things to remember
Index
Do you need a test plan?
Do you want to add a new practice?
Suggest a practice01
Do you need a test plan?
Not all the projects needs a test plan: for more linear / optmisation project you can go directly to the implementation step (see next practice). If you are following a project which scope is broad, high risk or involve a lot of users, testing your action plan before moving forward is necessary.
Read less
02
Define the critical hypothesis
Prioritizing hypothesis is fundamental to keep the innovation manageable and don't go crazy following too many things. You should validate your solution starting from the assumptions that are critical to the success of the solution itself.
To define a critical hypothesis, think about:
1- how much are you sure this assumption is correct? Are you pretty sure? Is it an educated guess? Is it a wild guess?
2- what is the impact on your solution if the assumption is falsified? Is it catastrophic? Is it problematic?
Read more
03
Producing a Test Plan
Once you have identified the critical hypothesis, you can move on the testing phase. A Test plan is a formal step necessary to ensure the gathering of critical information for your innovation project. It's a simple tool that can be done either in Mural, Excel or hand-written. Here's a video to deep dive in the test plan structure.
Warning: pilot a solution is not the only way
There are different ways to test your idea or hypothesis: as an example you can do service simulation or roleplay, additional field research, rough protoype session. Piloting a solution is often really complex and not always the best solution. Look at this link if you need more inspirations! 🙂
https://servicedesigntools.org/tools
https://www.strategyzer.com/blog/testing-business-ideas-4-most-common-tests-to-get-you-started
Read more
04
Fixing Lessons Learnt
Don't wait too long to fix your lessons. Anytime you discover something, update your A3 with the lessons you have learnt along with the testing.
Read more
