The Discovery Intelligence Series: A Reading Guide by Role
By Rich Garcia, Co-founder of Mayetik · June 28, 2026 · 3 min read
Every organization generates qualitative intelligence continuously — in customer interviews, discovery calls, health checks, retrospectives, and alignment sessions. Almost none of it compounds. It lives in notes, briefs, and the memory of whoever ran the conversation. When that person moves on, the intelligence moves on with them.
The series below covers seven versions of this problem, each written for the function that experiences it most directly. The underlying argument is the same across all of them. The failure mode, the vocabulary, and the specific cost differ by role.
Start with the article written for your role. They can be read in any order.
For the Head of Customer Success
The Customer Knowledge That Leaves With the CSM
Customer Success is the only function with a longitudinal relationship with the customer. Every call should compound into a body of knowledge that survives the life of the account. Instead, it lives with the CSM — and when the CSM leaves, the customer starts over with a vendor who doesn't know them.
For the VP of Marketing
The Buyer Intelligence That Doesn't Survive the Brief
Every ICP research cycle produces two things: the quotes that make it into the messaging doc, and the reasoning behind them that doesn't. The reasoning is what positioning strategy actually runs on. Most marketing teams discard it with every cycle — and rediscover it in the next one.
For the VP of Sales or CRO
What the Buyer Said That Isn't in the CRM
Discovery is when buyers are most honest — before they've committed to a vendor, before they've shaped their answers to what the rep wants to hear. That conversation becomes a CRM note. By the time it reaches the pipeline review, the buyer's reasoning has been through three compressions and the mechanism is gone.
For the CFO or VP of Finance
The Revenue Assumptions Nobody Has Checked
The revenue forecast requires assumptions about buyer behavior: conversion rates, churn rates, expansion triggers. Those numbers come from historical performance. Why they are what they are — the buyer reasoning behind the rates — was never captured. When a number changes, the only explanations available are theories from the teams that own it.
For the Engineering or Programme Lead
The Gap Between What You Said You'd Do and What You Did
The retrospective asks what happened. The futurespective, three months earlier, recorded what the team predicted would happen. Almost no one puts both documents in the same room. The gap between them is where the pattern lives — and it's the only thing that makes a planning cycle self-improving.
For the HR Leader or Chief People Officer
Why Health Check Data Sits in a Deck and Changes Nothing
The health check results come back. Leadership reviews the deck, acknowledges the scores, commits to following up. Six months later, the same scores come back. This isn't a follow-through problem. It's a diagnosis problem — and the score, by itself, can never provide one.
For the CEO or Chief of Staff
The Meeting Where Everyone Realized They Were Working on Different Things
Four departments attended the same all-hands, read the same deck, and heard the same executive describe the H2 priorities. Six weeks later, a structured alignment check revealed four different beliefs about what H2 actually required. None of them were wrong. All of them were building in different directions.
The Common Thread
Each article describes a different function losing a different kind of intelligence in a different kind of conversation. The mechanism is the same in every case: the conversation generates something — buyer reasoning, customer context, planning assumptions, organizational signal — that gets compressed into a note, a score, or a summary, and the compression discards what mattered.
The fix isn't better notes. It's a system that captures what conversations produce in a form that accumulates rather than resets — and makes it queryable by the people who need it, including the ones who weren't there.
That's what Mayetik is built for. Start your free trial.
Start capturing knowledge today
Mayetik helps teams design better questions, capture structured conversations, and synthesize intelligence that compounds over time.
Found this useful? Share it.
Next in Part 5
The System in Practice: What Structured Qualitative Intelligence Actually Looks Like
The argument for building infrastructure around qualitative intelligence is straightforward. What's less obvious is what that infrastructure looks like when it's running — and what it changes about the way a team actually works.