The Language You Think In
This is the third in a four-part series exploring the ideas behind Pattern and Flow's complexity practice. Each post stands alone. Together, they build a foundation for working differently with organizational challenges that resist planning.
In the previous post, I described the most common failure mode in organizational work: treating complex situations as merely complicated. Bringing analysis and planning to situations that require presence and responsiveness.
But this raises a question. If we can sense that mechanistic methods don't fit — and most experienced practitioners can feel this mismatch — why do we keep defaulting to them?
Part of the answer is ontological. It lives in the words we use to think.
Words Carry Worlds
We don't just describe reality with language. Language shapes what we can perceive as real.
The vocabulary we inherit in organizational life assumes a particular ontology — a theory about what exists and how it works. Consider phrases you probably use or hear regularly:
"Stakeholder" assumes discrete entities holding claims to something you own.
"Human resources" assumes people are raw material for extraction.
"Drive change" assumes change is a vehicle you control.
"Implement solutions" assumes problems hold still while you install fixes.
"Deliverables" assumes work moves down a production line.
This is mechanistic language. It came from an era when the dominant metaphor for organizations was the machine — separable parts, linear causation, controllable outcomes.
Not Wrong. Partial.
The mechanistic model isn't wrong. It's partial. There are genuine mechanisms in organizational life — payroll systems, compliance processes, production schedules — where this language accurately describes what's happening and these methods genuinely serve.
But when we bring mechanistic language to living systems — to organizations made of relationships, to communities constituted through interaction, to culture that emerges from connection — we literally cannot see what's happening. The language doesn't have the capacity to name it.
If all you have are words for parts, you can't perceive the whole. If all you have are words for control, you can't perceive emergence. If all you have are words for extraction, you can't perceive reciprocity.
The Ontological Claim
Here's the deeper point, and it's a strong claim: reality isn't made of separate things that interact. It's made of relationships that differentiate. Connection comes first. Entities emerge from patterns of relation.
This isn't poetry. It's a description that matters practically. When you look at a team through the lens of "separate individuals with different skill sets who need to be aligned," you see one thing. When you look at the same team through the lens of "a pattern of relationships from which distinct contributions emerge," you see something different — and different possibilities for action become available.
The language you think in determines which of these you can see.
A Practical Exercise
Try this: think of a phrase you use regularly in your work. Something ordinary — "align the team," "implement the strategy," "drive adoption." Say it to yourself.
Now ask: What does this language assume about how reality works? What can it see? What must it miss?
"Align the team" assumes the team is a set of separate vectors that need to point the same direction. It can see coordination. It can't see the creative tension that comes from maintained difference. It can't see coherence — which is alive and relational — because it only has a word for alignment, which is imposed.
"Drive adoption" assumes adoption is a destination you can force people toward. It can see compliance. It can't see the conditions under which something takes root on its own. It can't name the difference between people using a tool because they were told to and people using a tool because it genuinely serves their work.
These aren't just semantic differences. They're perceptual ones. The language constrains what you can notice, and what you can notice constrains what you can do.
Why This Matters for Practice
If you read the first post in this series, you encountered the idea that plans fail when there's a mismatch between the situation and the engagement. If you read the second, you learned a framework for sensing what domain a situation lives in.
This post names a reason that sensing is so difficult: the language we think in pre-filters what we can perceive. If you're trying to sense whether a situation is complex or complicated, but the only vocabulary you have assumes everything is a machine, the complex domain is literally invisible to you. Not because you lack intelligence, but because you lack words.
The final post in this series offers something practical: a vocabulary adequate to living systems. Not as a replacement for mechanistic language — you still need that where mechanisms are actually at play — but as an expansion of perceptual range. A second language for the situations that the first one can't reach.
Continue Exploring
Previous:Sensing Before Solving: A Different Way to Read the Room — A framework for sensing what kind of engagement a situation invites.
Next:An Ecological Vocabulary for Living Systems — Words adequate to the living systems we actually work in.
Also in this series:
Why Your Plan Didn't Survive Contact with Reality — The felt experience of bringing the wrong mode of engagement to a living situation.
Pattern and Flow works with practitioners and organizations operating at the limits of what planning can accomplish. If this resonates with something you're experiencing, we'd welcome a conversation.
