Core Workflows
Use Insights, Solutions, Hypotheses, and Gaps correctly
Insights should read the richest strategic analysis available and turn it into usable downstream direction.
What this helps with: Help teams understand what each strategic area means and how it should behave.
What Insights is for
Insights surfaces the synthesized patterns the system believes matter most right now.
Insights summarize evidence-backed observations.
Solutions convert those observations into candidate moves.
Hypotheses expose what still needs validation.
Gaps show where evidence is still missing.
What should feed it
Insights should be downstream of the best strategic analysis the system has, not a stale or partial copy.
The richest canonical strategic analysis should drive the view.
The page should never degrade because it read the thinner branch of data.
Method suggestions in gaps should only point to supported research paths.
How to use it
Treat this as a strategic synthesis layer, not a raw research log.
Use Insights to see the strongest current signals.
Use Solutions to discuss what to do next.
Use Hypotheses and Gaps to decide what still needs evidence.