Project Brainstorm is designed to help you learn about a market in service of a decision. The quality of that learning depends heavily on how well you frame two anchors:
*Business Problem (or Opportunity)
*Decision To Support
These are not administrative fields. They are the foundation of a lineage and determine whether studies compound into useful insight, or fragment into disconnected outputs.
Why anchors matter
Every study in Project Brainstorm exists to inform a Decision To Support. As you run multiple studies tied to the same decision, those studies form a lineage -- the structure that later enables Synthesis.
Poorly framed anchors lead to:
- vague or drifting studies
- outputs that are hard to interpret together
- synthesis that feels disconnected or inconclusive
Well‑framed anchors:
- keep exploration coherent across iterations
- make it clear why studies belong together
- allow learning to accumulate meaningfully over time
Don’t worry about lineages when you’re starting
In the beginning, your goal is not to “build a lineage”. Your goal is to get the anchors right through trial and error. The fastest way to do that is to run one or two quick IDIs, read the reasoning, then tighten your Business Problem and Decision based on what you learned. If your anchors still make sense after a few IDIs, a lineage will naturally emerge later, without you forcing it.
The two anchors (and how they differ)
1. The Business Problem (or Opportunity)
The Business Problem captures what you don’t yet understand.
A good Business Problem:
- is open‑ended and exploratory
- describes uncertainty, not a solution
- focuses on the market, not the company
Good examples
- “We don’t yet understand how people perceive rabbits as pets, or what shapes acceptance.”
- “We lack clarity on what makes a subscription service feel ‘worth it’ to first‑time users.”
Weak examples
- “We need to prove demand for promoting rabbits as pets.”
- “How big is the market for rabbits as pets?”
- “People don’t understand the value proposition of our subscription service.”
A simple test: If your Business Problem already sounds like an answer, it’s too narrow.
2. Decision To Support
The Decision To Support defines what this research will help you decide.
A good Decision To Support:
- is concrete and actionable
- does not assume an outcome
- can clearly be supported or not supported
Good examples
- “Whether to invest in promoting rabbits as companion pets for pre‑teens.”
- “Whether to prioritize [a certain market or segment] in our next expansion.”
Weak examples
- “What features should we put on the landing page?”
- “How to convince parents to let teens keep rabbits.”
- “Whether we should pursue a subscription service.”
A simple test: Could two reasonable teams read the results and still disagree? If yes, it’s probably framed at the right level. Disagreement isn’t a flaw, it’s a feature that supports continued exploration.
How the two anchors work together
Think of the anchors as a pair:
- The Business Problem defines what you’re trying to learn
- The Decision To Support defines why that learning matters
Neither should imply the other’s answer.
Most productive lineages start with:
- a broad, honest Business Problem
- paired with a specific, bounded decision
Common mistakes to avoid
Over‑specifying too early
Strong anchors leave room for discovery. You can narrow later.
Embedding assumptions
- “Why people don’t want…”
- “How to convince users…”
These pre‑decide the story.
Chasing novelty instead of coherence
If you change the decision every study, you’re not building a lineage -- you’re starting over.
Practical guidance
If you’re unsure how to phrase your anchors:
- Start rough. Precision comes through iteration
- Read the examples and tooltips
- Use Mark (Problem Framing Helper) to pressure‑test clarity and bias
A useful rule of thumb: If your anchors can still make sense after 3-4 IDI studies, they’re probably good enough to support a lineage.
Why this matters for Synthesis
Synthesis doesn’t summarize a study. It summarizes what a lineage has learned in service of a decision.
Clear anchors ensure that:
- IDI and FG results accumulate rather than diverge
- Synthesis reflects real progression, not forced aggregation
- Decision Signals feel grounded rather than arbitrary
Anchors are not just the start of a study. They are the thread that holds learning together.
In Project Brainstorm, insight compounds only when decisions are framed clearly enough to be revisited, tested, and stressed over time. That starts with writing good anchors.
---------
SHORT CHECKLIST: “Is my anchor ready?”
This checklist is intentionally fast (a user can answer in 30 seconds). It’s derived from your internal “what good looks like” framing and the “avoid tactics/features” guardrails.
(1) Is my Business Problem ready?
- It states an uncertainty, not a task. (“We don’t yet understand…”)
- It describes what’s unclear or risky, not what we plan to do
- It avoids tactics / features / pricing / campaigns
- It’s specific enough that someone can tell what changed and what’s unknown (not just “pricing problems”)
- It would still make sense if you ran 3-4 IDIs and learned new things (ie, it’s not over‑narrow)
(2) Is my Decision To Support ready?
- It is a real choice, not a research question (“Whether to invest / pause / focus / defer…”)
- It is blocked by the uncertainty in the Business Problem (they clearly pair)
- It avoids solution‑decisions like “build Feature X” or tactical decisions like “which price point in ads”
- It is actionable: if you got directional clarity, you could decide one way or the other
One last check: If you remove your Product / Concept entirely, does the Problem and Decision still make sense as a market uncertainty and a real choice? If yes, your anchors are probably ready.
---------
We’ll continue publishing additional guides and FAQs on lineages, synthesis, personas, and interpretation to help you get the most out of the platform. Use the platform to explore, iterate, and let the market population surprise you -- before committing to action.
Remember: Project Brainstorm is an experimental beta. It is designed to help you see the market more clearly -- not to replace judgement or downstream validation.
If you’d like to learn more about Project Brainstorm or share feedback on the beta, you can reach us at contact@projectbrainstorm.xyz