No individual has full visibility into a knowledge system. Everything you “know” is a localized view, shaped by position, perspective, timing, and access.
Understanding that your view is limited, and impacted by your experience, and requires learning with others is called epistemic humility.
Like an NFL quarterback, you are always running the plan and reading the field. You can’t see the whole. You can’t know whether a receiver will arrive where you expect. Despite that uncertainty, you still have to decide.
In the relationships between people who each see something different, there is the potential for knowledge. In healthy systems, knowledge flows across a network of people’s thinking, insight, choices, and experiences.
Every situation relies on some version of this network—a knowledge infrastructure. Wherever it is fragmented, knowledge is fumbled. Wherever it is connected, outcomes become possible that couldn’t happen otherwise.
A completed pass might look effortless, but that convergence is a practiced art. It happens in systems where knowledge can move, integrate, and evolve—flowing over infrastructure that lets a group approximate the whole.
Knowledge flow is a team sport.
Epistemic humility
Epistemic humility is what enables you to change your mind, update your thinking, learn from others, synthesize, and improvise.
This is not a virtue or personality trait. It is acceptance of reality—and a prerequisite for knowledge architecture.
Architecture, then, is the integration of different perspectives through systemic reasoning—also known as argumentation. Argumentation is not arguing or negotiating conflict. Argumentation is the process of reaching a conclusion when there is no single right answer. By synthesizing enough perspectives to understand, as best you can, the situation.
Understanding is the goal, and each person contributes something necessary.
Not all disagreement is argumentation.
Sometimes, it is something else entirely.
Epistemic dominance
Epistemic dominance is a “change my mind” situation.
A pattern where someone controls the frame of the discussion in a way that prevents shared understanding or resolution.
The difference can be subtle. But you can feel it when it’s happening.
- Questions get reframed into smaller, safer scopes.
- New ideas must justify themselves within existing constraints.
- The conversation loops—circling the same points, never quite landing.
- The challenges that get attention exist only within that frame.
Understanding is not the goal. Control of the frame is.
The pattern is rarely overtly derisive and is often mixed with sincerity. Which is why so many people miss it—each individual move seems reasonable. You find yourself deep in the pattern before realizing you’re stuck.
What not to do
When faced with this pattern, most people respond by trying harder.
You often feel like more explanation will help. Others reinforce this: “be clearer,” “more precise,” “more concrete.” Say it differently, you are told, and once they understand you, the blocker will resolve.
But it doesn’t resolve.
This works in good-faith disagreement, where everyone is operating with epistemic humility. It may take time, but as ideas become clearer, understanding follows.
This does not work under epistemic dominance.
Because this is not an understanding problem. It’s a feedback loop, and that loop tends to advantage whoever is maintaining control of the frame.
When people are crafting knowledge together, they are shaping something that exists between them—ideas, systems, possibilities that neither could fully produce alone. The outcome is both shared and emergent.
Epistemic dominance disrupts this by collapsing ideas into identity.
You are trying to change minds or generate insights with better reasoning. They are protecting identity and control. The more you work to integrate perspectives, the more you reinforce the structure that resists integration.
So what do you do?
Reframing
The first step is to stop participating in the conversation as if it were argumentation.
This is a subtle but important shift: non-cooperation with the frame.
Instead, identify the dominating constraint shaping the discussion. At its core, epistemic dominance looks like “change my mind,” but operates as “I decide.”
Make that structure visible. What assumption of ownership is underlying the conversation?
Then adjust your stance. Redefine the conditions under which meaningful work can happen.
Here is a common example. The frame is: you must deliver something that satisfies requirements in one month.
“This feature, as described, needs to be delivered in one month.”
(After a day of solutioning and estimation) “The work required includes capabilities we don’t have. It will take at least four months.”
“Then what can I have in a month? This is a must-have priority.”
“We could build X, since it relies on the current capabilities.”
“That won’t work. We also need Y and Z.”
You respond … and the loop continues.
This framing excludes information required for shared understanding:
- Why this work wasn’t discussed earlier
- Why Y and Z are required
- What “required” actually means
- Who decides when to say no
- Why this is higher priority than current work
- How the impact of a rushed solution will be addressed (and when the necessary capabilities will be built)
- How this integrates with existing variations
A different framing sounds like this:
“We have a big event coming up. It’s an opportunity to create an experience our users want, and it aligns with our goals. We don’t yet know what’s technically feasible in this timeframe. Let’s work together to find something both meaningful and achievable.”
That’s a frame you can enter.
Non-cooperation with the frame means stepping out of the loop as early as possible.
A simple heuristic helps. When you find yourself repeating the same explanation, answering increasingly narrow objections, and circling without resolution, pause and ask:
Am I being asked to explain, or to conform?
If the answer is conform, you are no longer in argumentation.
You are in a boundary-setting situation.
What to do
To set those boundaries and shift toward knowledge flow:
- Name the pattern without personalizing it
“We’re evaluating this within predefined constraints, which is shaping the outcome.” - Refuse the frame when necessary
“That question assumes we’re staying within the current system. I’m not.” - Re-anchor the conversation
“What experience are we actually trying to create, and why?” - Surface what’s implicit
“Right now, we’re separating what’s wanted from what’s possible. Is that intentional?” - Require symmetry
“If we’re evaluating this approach, we need alternatives—not just objections.” - Clarify decision rights
“Who owns this decision?”
“Who owns the impact on the system?” - Exit the loop when necessary
“I’m not going to continue evaluating this within that frame.”
These are not social techniques. They are structural adjustments. They shift the conversation out of an unproductive loop and back into a space where thinking together is possible.
The goal is no longer to win the argument.
It is to restore the conditions under which real system design—and real thinking—can happen.