Instead of collecting human panel responses, Project Brainstorm runs structured interviews, group discussions, and synthesis studies across grounded synthetic populations and organizes the results into a deterministic, repeatable workflow.
Project Brainstorm is not a prediction engine. It is a system for understanding reasoning, uncertainty, and decision-shaping factors. Its role is to help users explore questions, assumptions, tensions, and decision dynamics before they commit significant resources to validation, experimentation, or execution.
Teams today are having to make critical decisions without truly understanding how people in the market are thinking – whether that’s potential customers evaluating something new, stakeholders interpreting a narrative, or employees reacting to a change inside the organization.
Markets move quickly, ideas get developed before they’re tested, and research is often too slow to keep up or too shallow to reveal what truly matters. Even when data exists, it rarely explains how people interpret something unfamiliar and ambiguous. As a result, assumptions go untested, early signs get misread, and uncertainty is hidden rather than explored.
The problem isn’t usually a lack of demand – it’s a lack of clarity. Teams often don’t know which assumptions are wrong, what drives or weakens interest, where confusion or tension exists, or what is still unknown. Traditional research Is slow or shallow, while pure generative AI is fast but ungrounded. Project Brainstorm solves this by letting teams explicitly test assumptions, validate structured decisions, and surface uncertainty before committing to action.
At its core, Project Brainstorm separates understanding how people think from testing a decision. Teams can use it in two complementary ways:
1. Standalone Grounded Simulations - In-Depth Interviews, Focus Groups, and Synthesis Studies
This mode is for teams who want deep, grounded understanding without running a full weekly cycle.
1) Ground the population
Before any simulation, the system builds a grounded view of the market using external context.
It retrieves signals across demographics, geography, socio-economic conditions, and local narratives to establish:
- who exists in the market
- how different segments behave and live
- what constraints, habits, and environments shape them
This grounding is explicitly tracked and kept separate from the outputs that follow.
2) Generate personas within that population
Personas are not generated arbitrarily, and they are not designed around your product or concept.
They emerge from the grounded population and represent statistically-plausible individuals defined by:
- lifestyle and habits
- cultural and socio-economic context
- environmental constraints
At this stage personas are independent of your product, idea, or decision. This ensures the system starts from who exists, not from what you want to test. Personas created in a lineage can be reused across studies, allowing reasoning to accumulate rather than reset.
3) Apply context during execution
Only after personas are defined does the system introduce your specific context, concept, positioning, or decision.
It then runs:
- interviews => to explore individual reasoning
- discussions => to observe social reasoning
- synthesis => to identify patterns, tensions, and variation
External sources may be used at this stage to improve realism but are explicitly labelled as context, not validation.
4) Produce structured insight
The output is not a single answer. It also reveals:
- how people reason about a situation
- where perspectives diverge or conflict
- what drives or weakens interest and decisions
- where confusion or tension exists
- what remains uncertain
This helps teams understand why something might work or fail before proceeding with it.
Lineages and Synthesis Studies
All standalone simulations belong to a lineage -- the ongoing record of everything you’ve explored about a specific market or problem. A lineage accumulates your interviews and focus groups over time, building a grounded base of evidence.
Synthesis Studies are only unlocked once a lineage contains enough prior grounded work (a minimum of three IDIs and FGs, although more is better, in this case). This ensures synthesis is based on a sufficiently rich and diverse set of perspectives, not on a small or biased sample.
A lineage makes standalone simulations cumulative: each interview or discussion strengthens the foundation for deeper reasoning, and eventually enables synthesis.
A Synthesis Study tests which patterns from your earlier IDIs and Focus Groups actually hold when applied across many simulated persona contexts. It doesn’t measure real‑world prevalence or survey opinions -- it evaluates pattern stability. Synthesis operates at the lineage level, summarizing patterns across all prior studies tied to the same Decision To Support.
It shows:
- which signals remain consistent across contexts
- where tensions, contradictions, or barriers persist
- how strongly one direction leads over others
- whether the pattern is stable enough to act on
- what still needs validation
IDIs and FGs surface signals; Synthesis tests which signals hold; decisions act on those stable signals.
The other way to use Project Brainstorm is the Reasoning Cycle.
2. Reasoning Cycle (or the weekly loop)
The Reasoning Cycle is a powerful, deterministic loop that tests assumptions and validates decisions, transforming isolated studies into cumulative understanding.
Teams running Project Brainstorm week-to-week use a structured five-step cycle:
Step 1 – Test Assumptions
You define assumptions about how people might think about something.
The system tests them through grounded interviews and discussions.
Each assumption receives a structured outcome: supported / partially supported / none.
Step 2 – Run Simulations
Personas are generated from the grounded population.
Simulations explore individual reasoning and group interactions.
Step 3 – Extract Insights
The system identifies reasoning patterns such as interest triggers, weakening conditions, cultural alignment signals, credibility cues, habit barriers, and contradictions.
These patterns form the frozen evidence base. Frozen evidence informs the anchors; frozen anchors define the decision context. Keeping these separate prevents drift and ensures each week’s refinement is grounded in stable insight.
Step 4 – Refine Anchors
Anchors (Problem, Decision To Support, Product Concept, Target Audience, Market) are refined using frozen evidence.
Evidence is snapshotted and frozen – no live reads are allowed.
Step 5 – Commit & Align
Teams review the frozen evidence and structured decision using a guided workflow:
- stance (Confirm / Challenge)
- frozen reference
- lineage specific template
- editable scaffold
- examples
- validation indicators
Archive blockers ensure correctness.
Archiving creates a successor baseline for the next week’s cycle – the authoritative record of what was accepted this week. That successor baseline becomes the starting point for next week’s cycle, which carries forward:
- the frozen anchors (Problem, Decision, Product/Concept, Market, Target Audience)
- the frozen evidence snapshot
- the structured decision you just committed
- the required Step 1 assumptions to retest
- the alignment responses
- the successor baseline itself
Each week’s archive becomes the baseline for the next week’s reasoning.
You don’t restart the decision -- you continue it, testing what didn’t hold, refining what did, and aligning again with updated evidence.
This is how Project Brainstorm creates cumulative reasoning instead of isolated studies.
Project Brainstorm is not a conventional research tool, and it is not designed to predict outcomes from the start.
Most tools are built to answer questions like:
- How many people prefer this?
- Which option performs better?
Those are important questions, but we believe they depend on understanding something more basic first.
Project Brainstorm starts from how people make sense of the world -- their constraints, motivations, interpretations, and trade‑offs -- and how those thought processes shape their decisions.
This leads to a different kind of output:
- patterns, not percentages
- reasoning, not just responses
- tensions, not just consensus
Over time, that foundation can support more traditional questions around demand, preference, and pricing. But instead of jumping straight to measurement, Project Brainstorm focuses on building understanding first.
Project Brainstorm uses grounding to make simulations realistic, and evidence to show how personas reason. These are different things, and neither is meant to prove that a conclusion is true in the real world.
Grounding happens before any study begins. The system builds a picture of the market using real‑world context, so personas reflect the kinds of people who actually exist. This step shapes the environment in which personas think.
During execution, personas may encounter contextual material -- everyday examples, cultural references, or local narratives. These help them interpret situations more realistically, but they are not treated as proof and do not become evidence.
Evidence comes from the simulation itself: how personas react, how they weigh trade‑offs, how they revise their thinking, and how social context reshapes their views. Reports organize this reasoning into patterns and tensions that help you understand how people think something.
In Reasoning Cycles, evidence is frozen to preserve what was learned and keep the lineage consistent over time. Frozen evidence is authoritative inside the lineage, but it remains structured reasoning, not external validation.
The core idea is simple: grounding improves realism, simulation reveals reasoning, and frozen evidence preserves insight.
Why Project Brainstorm is Useful
Project Brainstorm is most useful when the problem is still forming and the answer isn’t obvious yet. Many important decisions begin in situations where the context is shifting, the assumptions are unclear, and you don’t yet know which questions matter.
Traditional research struggles in those early‑stage situations because it needs the problem to be well‑defined before it can measure anything. Surveys, experiments, and even focus groups require clear questions, stable concepts, and known variables. When the context is still shifting and you’re not yet sure what matters, those methods can’t operate effectively -- not because they’re flawed, but because they’re built for a different stage of the decision.
Project Brainstorm helps you explore how people make sense of a situation before measurement is even possible. It shows how different audiences interpret a concept, which assumptions break under real‑world constraints, where reasoning diverges, and why a promising idea might fail once context is applied. This makes it especially valuable when entering new markets, testing early‑stage ideas, or evaluating decisions where small misunderstandings can become expensive mistakes.
In short, Project Brainstorm is useful when you need understanding before you need measurement -- when you don’t yet know what you don’t know.
Use Project Brainstorm when you’re still shaping the problem, not validating the answer. Start with IDIs to explore individual reasoning. Add Focus Groups to see which views hold up socially. Run Synthesis when you want to test which patterns actually hold across perspectives. Then use Reasoning Cycles to refine your assumptions week by week, freezing evidence as you go so your understanding becomes cumulative rather than circular.
Project Brainstorm doesn’t replace judgment or downstream research. It strengthens both by helping you see the reasoning behind people’s decisions before you commit resources, time, or brand reputation.
We’ll continue publishing guides and FAQs on interpretation, validation, and how to get the most value out of each study type. Sign up to be notified when new articles are released.
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, you can reach us at contact@projectbrainstorm.xyz