Project Weeknotes Part 4 Hypothesis and Validations
Ideations is the stage where I can formulate different methods from the context to help me find a solution. Remaining at a conceptual level helps to look into the problem further and reveal the most straightforward answer with the most value to be delivered to the user.
Hypothesis
This is the starting point of a proposition, what a solution could look like at the top level. I see it as the key to intuitive and effective design and implementation here. I know it is worth building if I can get to where 1 to 2 flows solve many problems and pain points. Big, bloated monoliths come from deploying UI after UI for every problem rather than one concise method for as much as possible.
The template for this is simple:
If we/I [build something], then [some condition to met], therefore [some value to user and benefit to creator].
But from trying to write this, it is often that the Vision, Problem, and Goals may need adjusting or more insight has to be gathered.
For Project Weeknotes, the Hypothesis is:
If I build a web app where I can summarise my week, plan for the next, and share that with others, then I will have to take the time to reflect on the week. Therefore, those I share with will hold me accountable and take away the insights from my journey.
Validations
With everything I have written so far, a crucial step must be taken to ask how true these statements are. Now, this does not mean whether you do it or not, but more how you approach the problem. Identifying how many assumptions you have determines how much work you put into it and how experimental it is. In other words, I see the amount of assumption as a linear relationship to the amount of time spent building it.
High assumption, low build, high experimentation, i.e. MVP
Medium assumption, medium build, medium experimentation, i.e. iteration
Low assumption, high build, low experimentation, i.e. full feature work
Therefore, the aim is to move from high-low in assumptions, using each build to test and validate; everything is an experiment.
For Project Weeknotes:
Weeknotes has been working great and delivering value to myself and others already. Therefore, moving out of Heroku (due to their pricing change) is a valid approach.
End of Part 4
It is easy to fall into solutionising, that being just thinking of solutions and not entirely of the problem. Having a concept born out of context that needs to be proven true will lead to successful products.
