Prove the point. Bring it to life.
Quantitative research proves. Qualitative research brings to life. An insight that has both is the only kind that can leave the room it was found in — into a plan, into a measurement system, into an AI brain.
Whether an insight is proven
Whether an insight is understood
Insight needs both. A number nobody understands and a story nobody can size are the two ways research fails.
Q × Q = SI(a, t) — the ScaleQ2 equation
Q × Q— Quantitative × Qualitative. Multiplication, not addition: either at zero and there is no insight.
SI(a, t)— Scalable Insight, as a function of its actionability and its transferability.
a— Actionability. How comprehensively, versus narrowly, the insight can be activated.
t— Transferability. How far the insight travels beyond where it was found.
Two lenses.
One insight.
Quantitative asks whether an insight is proven. Qualitative asks whether it is understood. Insight needs both.
The question it asks
Whether an insight is proven.
Its own signal
Confidence
The question it asks
Whether an insight is understood.
Its own signal
Meaning
The four corners
| Actionability | Low t | High t |
|---|---|---|
| High a | Narrow insight | Scalable insight |
| Low a | Observation | Platitude |
A platitude transfers everywhere and changes nothing. A narrow insight works once, in one place. An observation is a number on its own. Q2 is the upper right.
Capture / Protect filter. Every insight in the table is also tagged Capture (upside to take) or Protect (downside to prevent), so a Scalable insight reads as "scalable capture" or "scalable protect". Observations and Platitudes are discarded in Assessment; only Narrow and Scalable insights proceed to Strategy.
Three phases.
One loop.
Q² does not float free. It runs inside a three-phase process. Each phase hands exactly one noun to the next. The process is a loop, not a funnel.
Delivers
Opportunity
Capture (upside to take) and Protect (downside to prevent).
Delivers
Idea
Position × Target × Intended Outcome.
Delivers
Plan and Impact
POET applied to the target groups chosen in Strategy; Impact measured on the same instrument.
Opportunity → Idea → Plan → Impact → (next) Opportunity.
Read the process→Three families.
Nineteen sources.
Every source gets a Quantitative read and a Qualitative read. There is no quant-only or qual-only source; only sources read with one eye.
Asked
01SurveyQuant Frequencies, scales, cell comparisonsQual Open-ends- 02InterviewQuant Theme frequency per cellQual Meaning, verbatims
- 03Focus groupQuant In-room concept scoresQual Group language, dynamics
- 04Message / concept testQuant Preference, credibility ratingsQual Why it lands, or feels defensive
- 05Internal expert perspectivesQuant Structured internal polls, Delphi roundsQual SME interviews, institutional memory
Observed
06Media monitoringQuant Volume, share of voice, sentimentQual How the story is told, by whom- 07Social listeningQuant Volume, reach, sentimentQual Actual language; the say-do gap
- 08SearchQuant Query volume, trendsQual What people are actually asking
- 09LLM auditQuant Citation share, positionQual What models say, and cite
- 10Owned / webQuant Traffic, engagementQual Paths, behaviour
- 11Paid performanceQuant Reach, CPM, conversionQual Creative resonance by segment
- 12Customer serviceQuant Contact volume, CSAT, resolutionQual Transcripts, complaint language
- 13RegulatoryQuant Filings, comment counts, approval timelinesQual Comment content, decision language, testimony
- 14Financial performanceQuant Results, share price, multiples vs peersQual Earnings-call language, analyst questions
Assembled
15Secondary / literatureQuant Published dataQual Prior findings, gaps- 16Syndicated trackersQuant BenchmarksQual Category narrative
- 17Expert analysis & ratingsQuant Ratings, rankings, scores, awardsQual The reasoning in the reports
- 18Competitive / peerQuant Every row above, on peersQual Their story vs yours
Build.
Prove.
Research serves two purposes. They run on the same grid, may run at similar sample sizes, and are integrated by AI into one system. They are not two passes over the same questions; they are two different jobs. Build runs in Assessment and Strategy; Prove runs in Execution and feeds the next Assessment.
Build
- Job
- Train, test, build
- Question
- Who are they, what moves them, what should we make
- Weight
- Qual-heavy: voice per cell
- Sources
- Fewer, deeper — the Asked family plus targeted Observed and Assembled
- Sample
- Enough voice per cell to build a person
- Output
- Personas with personality, tested ideas, written hypotheses, a baseline
- Cadence
- Before and during; repeat when the audience or the idea changes
- Non-negotiable
- Segmentation, and hypotheses written down before fielding
Prove
- Job
- Connect, attribute, showcase
- Question
- What moved, how much, because of what
- Weight
- Quant-heavy: every signal available
- Sources
- As many as exist — the whole grid, and usually many more rows than Build used
- Sample
- Enough coverage per cell to detect change
- Output
- An impact chain, attributed, across tiers and over time
- Cadence
- Continuous; reported in phases
- Non-negotiable
- A baseline, and a measurement architecture agreed before activity starts
Research in the probability era.
Traditional research counted things. A census counted people. A completed interview was a person who answered. A sale was a sale. The move from traditional to digital research and measurement changed the unit: almost every digital number is an estimate of an event that probably happened, not a record of one that did. The impression is the clearest example, and it is one of many.
What the digital KPIs actually are
| KPI | Reported as | What it really is |
|---|---|---|
| Impression | Times your ad was seen | Probability a screen had the ad on it |
| Viewable impression | Times it could be seen | ≥50% of pixels for ≥1s (2s video); opportunity, not attention |
| Reach / unique users | People | Cookies, devices and panel models standing in for people |
| Attribution | Which touch caused the sale | A model's allocation, from last-click to probabilistic MMM |
| Sentiment | Share positive / negative | A classifier's confidence, above a threshold someone chose |
| Share of voice | Your share of the conversation | Share of what the monitoring captured, times relevance |
| Search volume | Times people searched | Sampled, rounded, bucketed estimates |
| LLM citation | Whether the model cites you | Changes on the next run; a rate, never a fact |
| AI-coded open-ends | Theme counts | Classification probabilities summed |
Reported as counts, every one of them is a probability with a width the report rarely shows.
What the probability era demands
- 01
Report the width, not just the point. Every number in a research report is a probability; the report's job is to say how wide.
- 02
Treat digital KPIs as opportunities and estimates, and buy attention and outcome measures separately when the decision needs them.
- 03
Put a voice behind the probability. The probability says how often the event happened; only the qual says what happened when it did. Interview thirty of the people reached and you learn what a 1.5-second fixation left behind, which is the only thing the million was for.
Prove it. Then bring it to life.
Three tests for confidence, two for meaning. Pass all five and the insight can leave the room.
Contact→Objektive Working Papers (2026). ScaleQ2: Quantitative × Qualitative. Working Paper No. 4, 2026 edition. https://scaleq2.com
Markdown edition: the Q2 Grid template