The Art of the Question: Why Asking Well Is a Competitive Skill
June 16, 2026 · 8 min read
By Ric Garcia, Co-founder of Mayetik
Many organizations spend millions making decisions and almost nothing improving the quality of the questions those decisions are based on.
Think about what that means. Every strategy, every product, every hire, every go-to-market move is downstream of information. And that information came from somewhere — from conversations, from interviews, from discovery calls, from listening sessions. The quality of those inputs determines the quality of everything that follows.
And yet: little investment. Few systems. Rarely any discipline. Just the assumption that smart people ask good questions — and that if the interview happened, something useful was captured.
That assumption is costing organizations more than they realize. Not because individuals are poor interviewers, but because few have built the infrastructure to make questioning a durable, compounding organizational capability. There's a difference between asking good questions once and building a system that makes good questions the organizational default. In our experience, many organizations don't have the latter — and many don't know they're missing it.
The Skill Nobody Operationalizes
Somewhere along the way, we decided that intelligence was about having the right answers.
We hire for it, promote for it, and reward it in meetings. The person who speaks with confidence, who arrives with a position, who doesn't need to ask — that's the person we assume knows what they're doing.
But there's a quieter capability that drives more value, in more contexts, than almost anything else in organizational life: knowing how to ask.
Socrates is remembered less for delivering answers than for asking questions — precisely and relentlessly, until the person across from him arrived somewhere they couldn't have reached alone. The insight wasn't just that questions unlock thinking — it's that the right question, in the right sequence, turns latent knowledge into usable knowledge.
Organizations understand this at the level of the individual — the good interviewer, the curious PM, the consultant who listens before proposing. What they almost never do is build it into the organization itself. They treat questioning as a personal attribute rather than an organizational capability. And that distinction is where most of the value leaks out.
A conversation that isn't structured to produce comparable, synthesizable knowledge too often becomes a one-time event. It might produce insight for the person who ran it. It rarely produces learning for the organization.
What Bad Questions Actually Cost
Bad questions aren't just inefficient. They're structurally expensive — because they corrupt the inputs that decisions are built on.
When a consultant enters a client engagement with assumptions already formed and asks questions designed to confirm them, they leave with a polished version of what they already believed. The real problem — the one the client couldn't quite articulate — stays buried. The engagement produces a sophisticated answer to the wrong question.
When an HR leader runs exit interviews with a standard checklist, they collect data. They don't collect truth. The departing employee answers the questions asked, not the ones that matter. Attrition patterns stay invisible for another quarter.
When a founder does customer discovery but frames every question around validating their solution, they hear what they want to hear. They build what they planned to build. They wonder later why it didn't land.
In each case, the failure isn't a bad conversation. The conversation happened. Notes were taken. Something was captured. The failure is structural: questions weren't designed to surface what the organization actually needed to know, and there was no system to catch the gap.
The Organizational Failure Nobody Talks About
Many organizations think they have a discovery process. What they actually have is a collection of individual interviewing styles.
Every conversation starts from scratch. Every interviewer improvises. Every insight lives in someone's notes, or their memory, or nowhere at all. And because there's no shared structure, there's no way to compare what one person learned against what someone else learned. There's no synthesis. There's no compounding.
The result is that insight quality becomes entirely dependent on whoever is in the room. It varies by interviewer. It doesn't transfer across teams. It doesn't survive turnover. This quarter's customer discovery doesn't make next quarter's smarter — because everything the organization learned is stuck in formats that can't be compared or queried.
No shared frameworks for what good questions look like in your context. No structure that ensures consistency across interviewers. No way to transform individual conversations into organizational knowledge.
This is what we mean when we say organizations underinvest in inquiry. It's not that they don't run interviews. It's that they've never built questioning into a repeatable system — something that can be designed, standardized, improved, and compounded over time.
Some organizations have methodologies — structured frameworks for how discovery should work. That's better than nothing. But a methodology standardizes process. It doesn't automatically create institutional memory. A team can follow the same interview framework on every engagement and still lose everything they learned the moment the person who ran those interviews moves on. Process and memory are not the same thing. What's missing in most organizations is the layer between them: structured capture, synthesis, and the ability to query what was learned across time.
What Organizational Amnesia Actually Looks Like
The following is a composite scenario drawn from patterns we see repeatedly across organizations.
A mid-size software company spent three months doing customer discovery before a major product redesign. Their head of product personally ran 40 interviews. The findings were rich: customers didn't want more features — they wanted the existing ones to work together. The core insight was clear. It went into a slide deck, presented to leadership, and shaped the roadmap.
Eighteen months later, a new product leader joined. The previous head of product had moved on. The slide deck existed somewhere, but no one could find the version that mattered, and no one remembered which customers had said what or why certain decisions had been made. So the new leader did what any reasonable person would do: she ran her own discovery process. Another round of interviews. Another synthesis. Another slide deck.
The insight was almost identical.
The organization spent roughly six months and significant leadership bandwidth rediscovering what it already knew. Not because anyone was careless. Because the knowledge had never been structured in a way that survived the people who held it.
This pattern — running discovery, capturing findings in formats that don't transfer, watching the knowledge evaporate — repeats itself constantly across product teams, consulting firms, HR departments, and strategy functions. We've seen versions of it in customer research initiatives, stakeholder listening programs, expert interview projects, and post-project retrospectives. The interviews happen. The conversations are good. The learning dies with the notes.
It happens in consulting too, in a slightly different form. A firm completes a market-entry engagement for a client in a specific sector. The partner who ran the stakeholder interviews leaves two years later. A new team wins a similar engagement in the same sector. The institutional knowledge from the first project — what questions surfaced the real blockers, which stakeholder concerns turned out to matter, what the client didn't say but clearly meant — is gone. The new team starts fresh. They're competent. But they're not compounding. Every engagement is year one.
Why Existing Tools Don't Solve This
When organizations recognize this problem, they reach for something familiar.
Surveys are scalable and comparable — but they sacrifice the nuance that makes qualitative intelligence valuable. You learn what the options you offered were chosen. You don't learn what the respondent actually meant, or what they would have said if you'd asked differently.
Notes and documents capture what happened in a conversation — but are rarely in formats that make it easy to compare across interviewers, query across time, or synthesize into patterns. They're archives, not intelligence.
Meeting recordings and transcripts are richer — but preserving a conversation isn't the same as understanding it. A folder of transcripts is not an organizational memory. It's a pile of raw material that often no one has time to process, in a format that was never designed to be compared, synthesized, or queried.
The gap between these tools and what organizations actually need isn't a feature gap. It's a category gap. What's missing is something that combines the comparability of surveys, the depth of conversation, and the ability to synthesize and query across both — at the same time. Structured qualitative intelligence: knowledge that is designed to be captured, comparable by design, synthesized automatically, and queryable over time.
That's not a workflow improvement. It's a different kind of organizational asset.
From Individual Craft to Organizational Capability
Organizations don't suffer from a lack of conversations. They suffer from a lack of memory.
The discovery call happened. The exit interview was conducted. The customer research ran for six weeks. But when a new PM joins six months later, or a leadership team faces the same strategic question in a different quarter, the knowledge is gone — locked in one person's notes, lost to turnover, or simply never structured in a way that made it findable. Every effort starts from scratch. Every team rediscovers what the last team already learned.
This is the compounding cost nobody tracks: not the failed interview, but the organizational amnesia that follows it.
Here's the distinction that matters: a well-designed question asked consistently across twenty interviews becomes organizational intelligence. The same question asked twenty different ways by twenty different people becomes noise. The difference between those two outcomes isn't interviewer talent. It's infrastructure.
That infrastructure has four stages. Design: questions built intentionally before the conversation starts, with shared frameworks that hold across interviewers and over time. Capture: structured responses that preserve not just what was said, but what it means. Synthesize: patterns surfaced automatically across responses, so each round of interviews builds on the last. Query: the ability to ask questions of your accumulated knowledge later — not just at the moment of collection, but whenever the organization needs it.
Design. Capture. Synthesize. Query. Each stage depends on the one before it. Most organizations do the first two inconsistently and skip the last two entirely.
The goal isn't scripted conversations. It's creating enough consistency that learning compounds across conversations — so each interview makes the next one smarter, and the organization retains what it learns rather than starting over.
The organizations that will outlearn their competitors aren't the ones that gather more feedback. They're the ones that learn faster from the feedback they already gather. That requires a system — one that accumulates, transfers, and compounds over time rather than resetting with every new project, every new hire, every new quarter.
The art of the question is ancient. The infrastructure to practice it at scale is new.
In our experience, most organizations believe they are learning from their conversations. What they're often doing is generating qualitative exhaust — raw material that evaporates before it can compound. The issue isn't that they fail to collect knowledge. It's that they fail to make knowledge survive. The competitive edge isn't running more interviews. It's building the system that turns every conversation into something the whole organization can learn from, long after the conversation ends.
Organizations that compound what they learn will increasingly outperform organizations that repeatedly relearn the same lessons. The gap between those two kinds of organizations is not talent. It's infrastructure.
Mayetik helps teams design better questions, capture structured conversations, and synthesize intelligence that compounds over time. If your team keeps rediscovering the same lessons — in customer research, stakeholder interviews, or organizational listening — we'd love to talk.
Start capturing knowledge today
Mayetik helps teams design better questions, capture structured conversations, and synthesize intelligence that compounds over time.
Next in Part 2
The Question Is the Product: Why Most Organizations Get Discovery Backwards
Organizations invest heavily in analytics platforms, dashboards, and AI synthesis layers. Then they wonder why the output still feels shallow. The problem isn't downstream. It's upstream. It's the question.