Ecological Vocabulary
This is the fourth 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 made the case that mechanistic language — the vocabulary most organizations run on — isn't just imprecise. It's ontological. It carries assumptions about what's real, and those assumptions prevent us from perceiving what's actually happening in living systems.
This post offers something practical: a vocabulary that can see what mechanistic language can't.
Not Replacement. Expansion.
The goal isn't to abandon mechanistic language. You need it. Budget spreadsheets are mechanistic, and they should be. Compliance processes have right answers, and the language of procedure serves them well.
The goal is to be bilingual — fluent in mechanistic language when that serves, and fluent in ecological language when that's what's alive. The practice is discernment: which ontology does this situation invite? Am I working with a mechanism or participating in a living process?
Most organizational challenges live in both. The budget spreadsheet is mechanistic. The team relationships that make the budget meaningful are ecological. You need both languages to work with the whole situation.
A Glossary of Living Systems
What follows is a set of terms drawn from ecology, systems science, and relational philosophy. Each names something that organizational life is full of but that mechanistic vocabulary can't reach.
Tending
Caring for conditions without controlling outcomes. What you do in a garden. Different from managing, which assumes you can direct results. You can't manage trust into existence. You can tend the conditions where trust becomes possible.
Entanglement
Mutual constitution through relationship. Nothing exists independently — everything is partially made by its connections. Applies to mycelial networks and leadership teams equally. When a team member leaves, the team isn't the same team minus one person. It's a different team. The relationships constituted everyone differently.
Porosity
Boundaries that maintain distinction while allowing exchange. Cell membranes. Riverbanks. The edge between departments. Not walls, not dissolution — selective responsiveness. An organization needs porosity between teams: enough boundary to maintain distinct function, enough exchange to remain a living whole.
Emergence
Patterns that arise from interaction and can't be predicted from parts alone. Not mystical — precise. Culture emerges. Trust emerges. Strategy emerges from participation. You can't build emergence. You can create conditions where it's more likely and notice it when it arrives.
Composting
Generative transformation of what's finished into conditions for new growth. Applies to outdated processes, organizational grief, letting go of strategies that once served. Not deletion — metamorphosis. The old initiative didn't fail. It's becoming soil for what comes next.
Attunement
Fine-grained responsiveness to subtle shifts. What a musician brings to their instrument. What a facilitator reads in the room. Different from alignment, which is imposed. Attunement is relational — you attune to something, which means you're changed by the encounter.
Coherence
Relational integrity without uniformity. Jazz musicians creating something together while maintaining their distinct voices. Different from alignment, which erases difference. A coherent team doesn't agree on everything. It holds together across genuine differences because the relationships are alive enough to sustain the tension.
Vitality
The quality of aliveness and responsiveness. Not just functioning — thriving. A vital team versus a compliant one. You can feel the difference when you walk into a room. Vitality isn't something you can mandate or measure on a dashboard. But its presence or absence shapes everything.
Reading the Grain
Perceiving the inherent patterns in a living system and working with them rather than against them. A woodworking metaphor that applies to organizational change. Every living system has grain — tendencies, histories, relational patterns. You can cut against the grain, but the wood will splinter.
Sympoiesis
Making-with. Nothing makes itself alone. All creation is collaborative, even when it doesn't feel that way. The strategy didn't come from the executive team. It came from the entire system of relationships, constraints, histories, and possibilities that the executive team participated in. Naming this changes who gets credit and who gets consulted.
Translation as Practice
Having the vocabulary is a start. Using it changes what you can see. Here's what translation looks like in practice:
"We need to drive adoption" becomes "What conditions would let this take root?"
"Let's align the team" becomes "How might we cultivate coherence while maintaining necessary difference?"
"We need buy-in from leadership" becomes "How do we invite leadership into this relationship?"
These aren't just nicer ways to say the same thing. They open different possibilities for action. "Driving adoption" leads to rollout plans and compliance metrics. "What conditions would let this take root?" leads to asking people what they actually need, noticing where resistance carries information, and designing for organic uptake rather than forced compliance.
What This Doesn't Mean
To be clear about what bilingual fluency is not:
It's not using ecological language to sound nice while still thinking mechanistically. Calling people "partners" while treating them as resources changes nothing except the branding.
It's not replacing all nouns with metaphors. "The garden of our synergistic stakeholder ecosystem" is worse than plain mechanistic language because it obscures what you're actually doing.
It's not abandoning measurement or accountability. Living systems have patterns. Those patterns can be noticed, documented, and responded to. Ecological thinking is rigorous — just rigorous about different things than mechanistic thinking.
What It Does Mean
It means expanding your perceptual range. Matching your methods to what's actually happening. Recognizing that how you speak shapes what you can see — and choosing your language with that awareness.
Here's an invitation: choose one term from the glossary above. One that names something you've been sensing but didn't have words for. For the next two weeks, watch for moments when it applies. Don't force it — just notice. And when it feels right, try speaking it aloud. See what happens.
The language you use shapes what you can perceive. Choose it with care.
The Full Series
This is the final post in a four-part series on the foundations of complexity practice. Here's the complete arc:
Why Your Plan Didn't Survive Contact with Reality — The felt experience of bringing the wrong mode of engagement to a living situation.
Sensing Before Solving: A Different Way to Read the Room — A framework for sensing what kind of engagement a situation invites.
The Language You Think In Shapes What You Can See — Why we keep defaulting to mechanistic engagement even when we sense it doesn't fit.
An Ecological Vocabulary for Living Systems — Words adequate to the living systems we actually work in. (You are here.)
Pattern and Flow works with practitioners and organizations operating at the limits of what planning can accomplish. Our workshops offer experiential practice with these ideas — not as theory, but as lived skill. If this resonates with something you're experiencing, we'd welcome a conversation.
