How the problem statement is created and used
The problem statement is generated from discovery and evidence, then carried across the strategy system.
What this helps with: Understand how the problem statement anchors downstream work.
Where it comes from
The problem statement should come from the project foundation and system evidence, not from arbitrary method defaults.
Discovery provides the starting context.
Research and evidence strengthen or clarify the framing.
The system uses the grounded statement as a strategic anchor.
Where it shows up
Once set, the problem statement influences the rest of the platform.
It supports the strategy surface and final document sections.
It helps methods stay aligned with the real project objective.
It should not be overridden by hardcoded category assumptions.
What to do if it feels wrong
If the problem statement does not reflect reality, the right fix is stronger context, not forcing the system to work around it.
Strengthen discovery and evidence first.
Then regenerate or refresh the strategic surfaces that depend on it.