Knowledge management

In the context of this work, “knowledge management” (or KM) is the general discipline of capturing, organizing, and maintaining an organization’s intellectual assets.

But that’s the conventional view, and it has some serious flaws. Traditional KM systems tend to focus on managing episteme (which is theoretical knowledge, or facts) and techne (which is technical skill, or procedures). The big problem is that these systems almost always fail to capture the critical elements of meaning and context.

We’ve all seen the issues this creates:

1. People resist it. Conventional KM systems are often seen as top-down mandates, so employees find ways to work around them.
2. It captures the “what,” not the “why.” Traditional style guides and brand books preserve the outcomes of communication (what was decided). They don’t capture the cognitive process or the reasoning behind those decisions.
3. It hides the real costs. These systems suffer from what we call “cost-attribution blindness.” This is where the expense of duplicating knowledge just disappears into the background. When a new agency or new hire has to spend 40 hours re-deriving the same brand context, that cost is scattered and invisible. It adds up to thousands of hours and dollars spent reconstructing intelligence that should have been portable.
4. It can’t preserve judgment. Traditional KM is pretty good at handling episteme (facts, data, RAG systems) and techne (automation, processes). Its biggest failure point is phronēsis (practical wisdom and contextual judgment).

So, for this work, you can think of traditional knowledge management as the baseline function of organizing information. It’s a flawed baseline because it completely misses the interpretive layer that’s necessary for any effective cross-cultural or human-AI communication. That missing layer is what we call Context Intelligence.

---

 

How new approaches expand on traditional KM

 

New approaches like Context Intelligence and hermeneutics (the theory of interpretation) completely change the game. They transform KM from a passive system of document storage into a discipline of interpretive stewardship. The new focus is on capturing and scaling organizational judgment.

 

1. Context intelligence adds the “phronēsis architecture”

 

Context Intelligence is the work of building systems that capture the deep, situation-specific knowledge architecture of an organization. This goes way beyond just storing documents. It fundamentally expands KM by building what we call the Phronēsis Layer.

• It focuses on reasoning. A Context Intelligence Portal (CIP) turns a traditional, static style guide into a living knowledge system. It’s built to record reasoning (the why, the logic, the tone) rather than just the final decisions.
• It captures judgment (phronēsis). The whole point of Context Intelligence is to build an infrastructure for organizational phronēsis. This is the practical, “in-the-room” wisdom that, for centuries, people like Aristotle considered non-transferable. It was just “experience” that “died” with the expert. This approach finally gives that wisdom an infrastructure.
• It’s the discipline, not the tool. This is a key distinction. Traditional KM might use a retrieval tool (like a RAG system). Context Intelligence is the overarching discipline of building the “why” that makes those tools valuable in the first place.
• It makes interpretation systematic. A good CIP ensures that everyone (internal teams, new hires, external partners) is working from the same coherent map of tone, audience, and intent. This drastically reduces the ambiguity and guesswork that plague conventional, fragmented KM systems.

 

2. Hermeneutics adds the interpretive method

 

So, if Context Intelligence is the goal (building that phronēsis architecture), then hermeneutics is the methodology for how we get there.

Hermeneutics provides the discipline for building Context Intelligence. It transforms KM from a passive archive into an active, disciplined process focused on clarifying meaning. We call this the Hermeneutic Workflow Methodology (HWM).

Here’s how HWM is different:

• The Goal: It’s designed to capture reasoning, intent, and nuance through a process of interpretation.
• The Methodology: It uses Interpretive Iteration. This is a cyclical process of review and reflection where meaning gets clearer as the context and intention are revisited. (This is the “hermeneutic circle” in practice).
• The Pace: It requires a Temporal Investment and Productive Friction upfront. You can’t rush it. This contrasts with traditional KM, which often prizes speed above all, leading to context loss.
• The Human Role: The human is the Semantic Apprentice Trainer and Interpretive Steward. The human actively teaches the system their judgment and maintains Human Primacy at all times.

The HWM dictates an intensive, time-consuming process called the Semantic Apprenticeship. This is the 150-200 hours of structured, iterative dialogue with an AI. This is the work required to build a genuine context intelligence infrastructure. This sustained investment is what teaches the system the organization’s reasoning, its tone, and its audience logic, making that interpretation systematic and transferable.

With this approach, even frustration becomes productive. When an AI falters or gives you “workslop,” the hermeneutic method sees it as a signal. It’s a sign that you need to articulate an assumption you’ve been holding. That’s how you externalize the tacit, “in-your-head” intelligence that traditional KM could never touch.

By putting these two pieces together, this new approach repositions KM as a strategic layer. It becomes a system focused on scaling practical wisdom and ensuring human judgment stays central in an age of fast automation.