“In the beginning was the word…”
— John 1:1
Stewardship of organizational meaning
In what now seems a long-forgotten past, Sapient and Razorfish existed separately. Similar, yes, but different propositions. Both had once competed against USWeb/CKS, back when that was still a name that mattered.
When Publicis put them together, we all wondered: what does this mean? What’s our story?
I had colleagues on all sides I’d go to war for.
The cultures aligned. The history did not.
Organizations do not communicate through content alone.
Meaning is received before it’s made—and it’s rarely received the same way twice. It arrives as culture, as cause, as the accumulated identity of the people who built something. But, it lands differently for everyone who encounters it: employees, customers, partners, the market.
Narrative is what organizations do with what’s been received unevenly. It does not resolve it into one fixed account. Instead, it loosely reconciles it by holding different receptions together well enough to function as one story, without pretending they were ever identical.
Narrative does this reconciling through an accumulation of decisions: what an organization says, how it says it, how it organizes information, what it preserves, what it changes, what it lets go. This is how meaning evolves—not toward one settled version, but toward a story wide/capacious enough to hold what everyone actually received. That work is never finished.
Content is what’s left once that work ends. Everything else is implementation.
That work gives rise to the systems organizations rely on. Content is one expression of that system. Technology is one mechanism for enabling it. Governance is a way to nurture it. AI is simply its newest participant.
The larger challenge isn’t producing more content. It’s reconciling meaning that was never received the same way twice, without flattening it into something false. Narratives let organizations act on meaning however it’s received, holding integrity across people, platforms, and time. Meaning evolves for its audiences, even as narratives hold.
It’s stewardship of meaning.
Narrative architecture
Narrative architecture is the intentional design of the structures that hold that work of reconciliation together—so it survives beyond any one entity. It encompasses storytelling, editorial practice, information architecture, semantic systems, governance, content platforms, and AI-enabled operations. Each contributes to a larger narrative ecosystem rather than being an isolated discipline.
Viewed this way, taxonomy isn’t simply classification. It’s the shared vocabulary through which organizations understand themselves and communicate.
Metadata gives meaning the context it needs to persist.
Editorial standards aren’t merely style guides. They preserve voice, intent, and identity—the meaning an organization received, still legible.
Editorial standards aren’t merely style guides. They keep voice, intent, and identity legible, despite the different perceptions of meaning.
Governance isn’t control. It’s stewardship.
AI isn’t replacing authors. It’s becoming another participant in the creation and interpretation of organizational meaning.
The real question
All of that is architecture. And whether or not an organization has that in place, most still ask the wrong questions:
How do we create more content? How do we manage content better?
The real question organizations should ask is this:
How do we reconcile meaning that was never received the same way twice, while maintaining narrative integrity?
This is one of the questions I created Rubicon CX to address.
If you want to learn more about narrative, meanings, and the platform to support them, schedule a free consultation.
