Keep going back to the main problem you are solving
As designers or developers, when we start analysing a product, we can easily think of all the things that might be wrong with it or what can be improved on the product. Then the next thing you know, you are at the point of saying “Let’s just scrap the whole thing and start from scratch”. Even though that might sound super exciting to some people or maybe it seems that it will make it easier to solve, it could also lead to a lot of other problems.
Some of the issues you might run to are:
- There might not be enough time to “redo” everything and then the main problem that needed to be solved actually never gets solved.
- If you don’t go back to that main problem you might spread yourself or your team too thin and have nothing valuable to show at the end of the project.
- By not focussing on the main problem, you could end up creating more problems than solving them.
- Your team might not have the budget to solve more than the main problem at this point in time.
- Lastly, there could have been a very good reason why something was there in the first place.
It is always important to find what the main problem is by doing research and prioritising the problems you find in your research.