According to Brown (2016), teams that have a well-built problem statement can align efforts towards solving a problem, define the goal of the solution being designed and make the team care about solving that problem and consequently achieve the goal (Fig. 1). For a problem statement to work, it needs to be recognised by the whole team as a focus point and align everybody involved towards the same direction.

As discussed previously, MyFitnessPal’s users demonstrated that over time their knowledge of the app was not improving over time. Features were lost in a complicated Information Architecture. To solve the issues detected, our problem statement became:
“Users concerned about health and nutrition need to input data about their food intake but face a complicated interface that discourages learnability.”
References
Brown, D. (2016, November 11). How to Build a Problem Statement. [https://medium.com/eightshapes-llc/how-to-build-a-problem-statement-d1f21713720b]. Accessed 25 February 2018.