Most organizations talk about structure as if it were a blueprint. Think org charts, operating models, governance frameworks, and boxes and lines in a deck that, once approved, are assumed to be more or less fixed until the next reorganization. In this view, structure is something designed, rolled out, and then inhabited.

Static.

But living organizations do not behave that way.

Even when the diagrams do not change, the real pathways shift beneath them. Exceptions become norms, and workarounds become processes. Certain people become gravitational centres for decisions, whether or not the chart names them. A team learns that one director’s “let me think about it” means no, and another’s means yes, and reorganizes its hopes accordingly. Over time, the real structure becomes the pattern of how things actually happen and the pattern of what people stop bothering to ask.

This is closer to how the poet and scientist Johann Wolfgang von Goethe understood form in nature.

For Goethe, form was never static. It was a process of becoming. A plant was not a fixed object but an unfolding movement: seed, shoot, leaf, flower, and fruit. Each stage is different and all an expression of the same underlying gesture. The leaf is not separate from the stem that produced it. The fruit is not separate from the flower. What appears stable is often only the visible edge of something still unfolding.

The form was not the outline.

It was the ongoing formation.

Most people hear the word “narrative” and think of the story we tell, whether it’s a brand story, a campaign, the language on a website, or the latest ESG report. But narrative operates at a deeper level than communication alone. The narratives that hold or destabilize an organization live in the logic that connects belief to behaviour, behaviour to systems, and systems to lived experience. They live in the patterns of what gets rewarded, what gets absorbed, and what quietly disappears from the room.

Narrative, in this sense, is not decorative.

It is structural.

And structure itself is not fixed. It is continuously being made.

The story people learn to live inside

Organizations are always teaching people what is true, whether intentionally or not. Not through slogans, but through repetition.

Which trade-offs leadership makes when pressure rises.

Which behaviours are protected.

Which risks become someone else’s burden.

Which concerns stop feeling worth raising.

Every new decision, every repeated ritual, every story that is told or withheld shifts the pattern, even if only slightly. Over time, those shifts harden into expectation. People learn what is rewarded, what is tolerated, and what must be carried quietly in order for the institution to keep functioning.

That expectation is the narrative.

You can rewrite the language around purpose, culture, sustainability, equity, care, and safety. But if the pattern people experience remains the same, the underlying narrative does not change. The words are absorbed into the existing form and translated back into familiar experience. Someone hears we care about well-being and silently acquiesces unless the quarter is bad. The translation is so automatic that they barely notice themselves doing it.

This is why messaging alone so often fails.

The language changes.

The pattern continues

One scene, four ways of seeing

Imagine it’s Tuesday morning in a mid-sized organization that has spent the last year speaking publicly about psychological safety and care. A well-respected senior employee opens a planning meeting by stating that she will not be able to deliver the launch on the proposed timeline. She has the data to explain why and has done the work to propose an alternative. She has done everything the culture claims to encourage.

What happens next is the form revealing itself.

You can watch it from four distances at once.

What the organization says it believes. The values statement is clear. Care. Trust. Honest communication. The CEO has spoken about it on a podcast. The strategy deck references it repeatedly.

What the organization is structurally organized to do. The launch date is tied to a board commitment. Incentives reward on-time delivery. Her manager’s bonus is connected to the very metric she is asking to renegotiate. Nobody designed this system specifically against her. But every person in the room is sitting inside it.

What the organization actually does under pressure. Her manager nods sympathetically and says all the right things, asking her to “find a way through,” and moves to the next agenda item. No one is unkind. There is no shouting. The meeting ends on time. The form has been preserved without anyone naming what was preserved or at what cost.

What people then come to expect. She walks back to her desk, opens her laptop, and begins, quietly, to find a way through. A colleague who witnessed the exchange decides not to raise the smaller concern she had been planning to mention later that week. Nothing dramatic is said out loud. Still, the organization has taught two people, in one morning, something enduring about what is actually possible here. Neither will describe this moment out loud. But both will carry it into future decisions.

This is the same plant from four angles. The leaf is not a separate thing from the stem. The expectation that forms in her is not a separate thing from the incentive plan that shaped her manager’s nod. What she will tell a friend about her workplace, six months from now, is already being decided in rooms she is not in.

The piece of this that is hardest to sit with is that no individual in the meeting did anything wrong by the standards of the meeting. The form did the work the form was built to do.

Pressure is mostly weather

It is tempting to talk about pressure as a crisis. A legal threat. A collapsing quarter. A public scandal. Those moments matter and certainly reveal a great deal. But most institutions are not primarily shaped by crisis. They are shaped by weather.

The quarterly cycle that never allows long-horizon thinking to fully form before the next reporting deadline. The hiring freeze that extends another six months. The slow accumulation of meetings that begin to fill the time once reserved for thinking. The 9:14 pm email that does not demand a reply but slowly retrains everyone’s nervous system anyway. The colleague who left and was not replaced, whose work has been absorbed into someone else’s calendar without ceremony.

This is the pressure that actually shapes expectations, because it is continuous.

Crisis reveals the form.

Weather grows it.

People do not adjust their understanding of an organization because of a single bad day. They revise it through accumulation, because of hundreds of small adjustments, each one slightly tilted in the same direction.

This is how contradictions become culture. Not suddenly, but gradually enough to feel normal while it is happening. A company may continue speaking the language of care long after the conditions that made care possible have eroded. “Resilience” becomes a way of naming unsupported labour. “Agility” becomes chronic understaffing with better branding. “Innovation” becomes permission for instability to reproduce itself indefinitely.

The language remains sincere enough to survive scrutiny.

Meanwhile, the cost continues moving somewhere else.

The cost is carried somewhere

If form continuously produces itself, then someone is continuously paying for the gap between what is said and what is done. That cost does not vanish. It is metabolized.

It is metabolized into the senior employee who finds a way through, again, while repeatedly postponing the doctor’s appointment she booked three months ago. Into the early-career colleague who learns that raising concerns is technically welcome but practically expensive and adjusts accordingly. Into the team lead who absorbs the impossible math of competing commitments while presenting calm to the team because someone has to. Into the contractor whose agreement is simply not renewed. Into the community downstream of a decision made in a room they will never enter.

The contradiction does not disappear because no one names it. It just relocates into bodies and calendars, relationships, exhaustion, and quiet decisions to leave.

The form is the distribution of the cost. And this is the harder truth organizations often resist seeing:

Many contradictions are not accidental failures of alignment.

They are operationally useful.

Ambiguity allows institutions to appear humane while continuing to extract beyond what their structures could openly justify. The distance between stated values and lived experience often creates flexibility, deniability, and room for performance targets to survive contact with human limitation.

The gap is not always a flaw in the design.

Sometimes the gap is part of the design.

Against the blueprint, including this one

There is another tension worth naming here. The four-layered way of seeing outlined above is itself a kind of framework. So is the language of “small structural shifts.” Any framework, including this one, can become the next thing the organization performs instead of the thing it practices.

A Goethean view does not finally rest in any framework. It rests in attention, sustained over time, to what is actually unfolding. This perhaps explains my recent fascination with Goethe’s work. The four layers are a useful tool because they slow the eye down. They are not useful as a model to install. The moment they are installed, they become another diagram, and the real form will continue to grow underneath them, exactly as it always has.

So the question is not “what should the structure be?”

It is something slower.

“What pattern is already here?”

How do decisions actually move?

Where do people go to get things done?

Which commitments are protected when stress hits, and which ones are quietly dropped?

Many contradictions are not accidental. Organizations are often rewarded for maintaining distance between what they claim and what they operationally require. Ambiguity creates flexibility and allows organizations to appear humane while externalizing costs to employees, communities, or ecosystems with less power to refuse them. The gap is not always a failure of design. Sometimes it is the design.

That tension matters because unacknowledged contradictions eventually become culture, and culture, over time, hardens into expectation.

Seeing is not yet doing

Goethe did not understand plants by reducing them to isolated parts and extrapolating a universal rule. He watched them across time. Through the weather. Through changing conditions and repeated gestures, attending to how each new leaf, bud, and branch expressed the same underlying gesture. He knew that to see a plant truly, you had to spend time with it.

Organizations require the same kind of patience. Working with narrative as a living structure means paying attention to behaviour across fatigue, pressure, incentive, repetition, and recovery. It means noticing where the emerging form aligns with stated commitments and where it bends away.

But here is the honest difficulty.

Seeing the form does not, on its own, change it. Organizations are held together by habits, incentives, dependencies, fears, ambitions, histories, compensation structures, reporting timelines, investor expectations, and the thousands of small accommodations people make in order to keep moving through the day.

A diagnosis is not a treatment. It is entirely possible to map the contradictions with precision and still discover that the organization continues reproducing them tomorrow morning.

Because stories do not operate in abstraction. They survive or fail inside particular conditions.

Particular incentives.
Particular weather.
Particular distributions of who is allowed to be tired.

Where this leaves us

Organizations will always contain a gap between aspiration and capacity. The gap is part of change itself. The questions worth holding are quieter than whether the gap exists.

How conscious is it?

Who is carrying the cost?

What is being done to close it?

And what is being done to keep it open and useful?

For now, in most organizations, employees still absorb the distance between narrative and reality. They translate contradictions, compensating for incoherence, soften the impact of impossible systems, and carry commitments the structure itself does not yet support. For a while, that works. Then, slowly, expectations adjust. People stop raising concerns. Trust becomes procedural rather than lived, and the narrative shifts to match the form.

And once that happens, storytelling alone cannot restore what the structure has taught people to expect.

If narrative is a living form, the real question is not what story do we want to tell.

It is, “What are we willing to keep asking other people to absorb so that the story can continue to sound true.

That is where the next essay begins.

Part of Series II:

Beneath the Story: Essays in Responsible Narrative Infrastructure

Previously in this series:

The Structure Decides the Story

Next Inquiry:

Once we accept that story lives in structure, we stop asking, “What should we say?” and start asking, “What conditions are we asking this story to land in?”

Most organizations do not have a storytelling problem. They have a structure problem.

They keep reaching for better language, sharper campaigns, and new engagement tactics. Meanwhile, something simpler and more difficult sits underneath. What you promise, what you do, and what people actually experience no longer match.

No amount of wordsmithing can carry that for long. Stakeholders are not judging you by the sophistication of your narrative. They are judging you by whether it holds up against their day-to-day experience of you. Your employees, customers, investors, and communities.

If it does not, they do not argue with your story. They stop believing it.

The lag is gone

Organizations used to operate with a narrative lag. You could talk about culture, sustainability, equity, safety, doing the right thing, and it would take years for the outside world to see what was actually happening inside. The gap between the official story and lived reality closed slowly.

That lag is gone.

Employees document their experience in real time. Customers share receipts, not impressions. Public data sits beside your claims. Communities and partners refuse to remain quiet context for a story that does not reflect their reality. Tools now allow investors, regulators, and journalists to compare what you say with what you do in minutes.

The gap between narrative and lived experience is no longer private. It is searchable.

Here is the uncomfortable part. In many organizations, that gap is not a communications failure. It is structural. The system cannot carry the story it is telling.

This is not about messaging. It is about integrity

If you say “safety is our top priority,” or “our people are our greatest asset,” or “we take diversity and inclusion seriously,” the test is not whether those lines resonate. The test is whether your system can sustain them.

Do decisions make those commitments easier or harder to live? Do incentives, processes, and ways of working reinforce them or quietly contradict them? Would the people affected recognize them as true?

If not, the issue is not tone or clarity. Your structure is carrying weight it was never designed to hold. That is where culture starts to fray. Not loudly. Gradually.

Employees absorb the contradiction. They learn the difference between what is said and what is supported. They adjust. They do the work of closing the gap on their own. That adjustment has a cost. Not just in performance, but in trust, in energy, in the quiet erosion of belief that makes everything else harder.

The usual fixes make it worse

The response is familiar. A new campaign. A refreshed brand. A culture initiative. A values cascade. A sustainability narrative rewrite.

Sometimes these moves are necessary. But when they happen before the structure beneath has been examined, they create narrative inflation. The story expands but the support for it does not. Expectations rise, while reality stays where it is.

People feel the stretch. These are the things we hear in nearly every organization we work with:

“We launch a lot of things that do not stick.”

“We are very good at talking about change, not so good at doing it.”

“The messaging feels further away from what it is actually like to work here.”

Externally, the same pattern becomes skepticism. The credibility gap widens. What accumulates is a kind of narrative debt in the systems meant to support the story, surfacing eventually in the culture.

What narrative infrastructure actually is

When we talk about responsible narrative infrastructure, we are not talking about a brand film or a messaging framework. We are talking about the conditions that keep what you say, what you do, and what people experience from drifting apart.

Who owns the commitments. What counts as evidence. How decisions and incentives reinforce or erode what you say matters. What happens when commitments collide with financial pressure. Who is allowed to name that collision without consequence.

Most organizations assume this coherence exists or assign it to a team without the authority to maintain it. Meanwhile, culture absorbs the contradiction. Employees are asked to behave as if commitments are real while navigating systems that treat them as optional. That is where cynicism begins.

Story is not decoration

In a functioning organization, narrative is not a layer on top of strategy. It behaves more like an operating system, defining what you will not do. It shapes how decisions are understood and answers, quietly and consistently, what kind of organization this is.

But no operating system runs on fractured architecture. You cannot ask people to carry a complex purpose narrative on top of structures that contradict it. When that happens, the culture fractures first, and the communications fail after.

The shift

The shift is not better storytelling. It is a better story design.

It means treating commitments as testable. It means designing accountability around narrative integrity rather than leaving coherence to goodwill. It means building the feedback loops that surface drift early, before it becomes the culture, and aligning incentives with stated values, or at a minimum, being honest about where they do not yet align.

This work is slower and less visible. It sits in the space where culture, sustainability, and strategy meet and where accountability is often diffuse. That is the terrain of responsible narrative infrastructure.

Where this leaves you

There is always a gap between what an organization says and what it does. The question is not whether it exists. The question is who is carrying it.

In most organizations, it is carried by employees. In their decisions. In their silence. In their willingness to adapt. For a time, that is enough to keep the system stable. But the gap does not remain static. It widens, or it closes. If nothing in the structure changes, it widens. And when it does, the story adjusts to match it.

Every organization carries a story about what it is, why it matters, and what it is trying to do. Rarely is that story designed. It accumulates. From early wins and inherited language. From the imprint of people who are no longer there. From the things that were said so often they stopped being examined.

At some point, the story begins to shift. Not outwardly, but quietly, the way a foundation settles before the walls show anything. What the organization says and what it shows no longer move in quite the same direction. From the inside, this is hard to name. It feels like drag. Like effort without traction. Like something slightly off in the way things land.

This is where the work begins. Or where it is avoided. Often both at once.

Story as Pattern

A room. A conversation. The sense that everything that can be said has already been said. Another campaign, another articulation, careful work done well. And still, nothing moves.

The instinct is to adjust the story. To find better language, sharper framing, a cleaner line from intention to expression. But if you stay with the feeling long enough, the question changes. Not, What should we say? But, Where is the story already visible?

What people come to believe is not shaped by what is said once. It is shaped by what is repeated, and by what the repetition protects.

If care is named but never given time, the pattern is clear.

If safety is spoken but speed is rewarded, the pattern is clear.

If equity is claimed but decisions remain closed, the pattern is clear.

Story is not only expression. It is expectation. And expectation, once set by practice, is not easily unsettled by language alone.

Where It Shows

A commitment that lives cleanly in language and unevenly in practice. A message that travels further than the conditions that would make it true. A gap that no one intends and no one quite owns.

The work around it continues. People try to close the distance with better phrasing, clearer framing, or more consistency. And occasionally these efforts help. But more often, the friction remains quiet and persistent, because something underneath the story is still teaching something else.

Not by accident. By architecture.

The Quiet Architecture

Most of what shapes belief is not said directly. It sits in how decisions are made and who makes them. In what is measured, and what is left out. In who is present when direction is set, and who learns of it later. In what moves quickly because it serves the centre, and what stalls because it does not.

These are not failures of the story. They are the story, in its most reliable form.

When what is said and what is lived diverge, people follow what holds. Not out of skepticism. Out of attention. They watch what is rewarded and notice what is possible and what, despite all the language to the contrary, is not.

What has changed is not only the complexity of the work, but the speed at which these gaps become visible. What once took months to surface now appears almost in real time. What was once interpreted charitably is now examined more closely. The distance between what is said and what is experienced has shortened. And with it, the time an organization has to live inside its own contradictions without consequence.

The Layer Beneath

This is the layer that usually goes unnamed. Not the message or the machinery, but something in between. The place where what an organization intends, what it can show, and what it says either meet or quietly come apart.

When this layer holds, language carries weight. When it does not, language thins. It reads as intention, not experience. As aspiration performing the work of truth.

People feel this before they name it. The careful worker who begins to hesitate before speaking or the one who still believes in the work but no longer expects the language around it to hold. There is a particular kind of fatigue that comes not from disagreement, but from the effort of staying close to something that is moving away from itself.

Then the question becomes unavoidable: If we say this, what in our way of working makes it true?

And if nothing does, what are we asking language to cover?

Structure

Structure is often treated as fixed. As something given, inherited, already settled by the time anyone thinks to question it.

But it moves.

Goethe described form not as a settled shape but as a process of becoming, something that unfolds, repeats, shifts, and continues. He was writing about plants, about the way a single leaf contains the logic of the whole organism. But what interested him was not only the repetition. It was the variation. The same form, appearing again and again, but never identically. Each iteration shaped by what it meets.

Organizations behave the same way, with one important difference. In a plant, the pattern responds to light, soil, and season. In an organization, the pattern also responds to something else: to what people closest to it are willing to let change and what they are not.

Structure is not only what is written down. It is the pattern that keeps happening. The same decisions. The same priorities. The same distribution of comfort and cost. If the pattern stays the same, the story does too. No matter how often it is rewritten. And patterns do not persist by accident. They persist because someone, somewhere, has a reason to keep them in place.

Seeing

You do not have to look far. One week is enough.

What does the calendar make space for? What moves easily toward the centre? What has to be managed before it can be spoken? What passes without comment? What is noticed? And who benefits from the arrangement as it stands?

The answers are already there. Not hidden. Practiced.

Most organizations do not suffer from a failure to see. They suffer from the distance between seeing and choosing. The gap is well lit. What is missing is not clarity. It is willingness, the willingness to disturb a structure that, for those nearest to its power, still feels like it works.

This Series

The earlier essays stayed close to the human conditions of the work. Courage. Clarity. Agreement. Trust.

This series turns toward form. Not to replace those conditions, but to see what holds them, or fails to. And to ask what it costs to look honestly at structures we also happen to live inside.

Nothing here is offered as conclusion. Only as a way of looking that does not stop where looking becomes uncomfortable.

If something in the story you are part of feels slightly unheld, not wrong but not fully carried, it may not be the language that needs changing. It may be that the structure beneath the story is asking to be seen. And that seeing it clearly, all the way through to who it serves and who it does not, is where the next work begins.

I came to music by ear. Not as a choice, exactly. More as a way of finding my footing.

I was seven, maybe. After school, I would drift down the street to my cousin’s house, drawn by something I couldn’t yet name. In the front room stood a white upright piano. It felt like it had been left there by another life. No one played it. No one knew how. It belonged to the house the way a photograph does: seen, but not touched.

So I did.

I would sit down and press the keys without knowing what I was doing, chasing songs I already carried somewhere inside me. Not from memory exactly. From something closer to instinct. My hands would move until the sound came near enough to what I felt I knew.

Not right. Not wrong. Just reaching.

I stayed longer than anyone expected. Long enough that it became something that needed to be addressed. At some point, his parents called mine. Not harsh. Just firm. This can’t go on like this. And then, without much ceremony, a piano appeared in our house.

I don’t remember the day it arrived. What I remember is where it landed: at the back of the empty living room. Set apart. Away from where the family gathered, where the television filled the air. The only piece of furniture in that long empty room.

No one else was happy about it. To them, it was noise. An interruption. Something slightly out of place.

But to me, it was a door. I could sit down and disappear into it. No questions. No expectations. Just a surface that could hold whatever I brought that day.

I had already been singing for years. Nursery rhymes with my mother. Blues with my grandfather. Broadway tunes with my father. Music moved through the house in layers, shifting the air without warning.

In the morning, my mother would turn on the classical station and send it through the intercom, filling every room before the day had fully begun. The house would settle into it. Held. Ordered. Then my father would come home, and something would open. Sinatra. Streisand. Diana Ross and the Supremes. Harry Belafonte. The same furniture. The same walls. But the room would change its mind.

I didn’t study any of it. I let it enter me. Melody came first. Then phrasing. Then something I couldn’t name then and can only circle now.

The way a voice leans into a word, or pulls back just before it lands. The way a held note can feel like contact. Not explanation. Not agreement. Just contact.

I sang what I heard until it stopped feeling like imitation and began to feel like recognition. Even now, I’m not sure where that line sits.

With the piano came lessons. Classical training. That world asked something different of me: precision, discipline, a willingness to submit to the structure of the piece rather than bend it toward myself.

At first, it felt like constraint. Then something else revealed itself. Form does not limit expression. It exposes it. If you rush, or overreach, or fail to listen, the structure shows it. Not as judgment. As fact.

I am still learning what it means to be seen that way.

Jazz came after. Or alongside. It felt like stepping into a larger room. The same language, but less settled. The edges less fixed. The air between notes more available.

What changed most was not how I played, but how I listened.

In classical music, much of the conversation has already been decided. You enter something that exists before you. Your task is to understand it well enough to carry it forward.

In jazz, the conversation is happening as you play. It is not stable. It depends on whether anyone is actually listening. And you begin to notice what you could once ignore. Not just whether a note is correct, but whether it belongs. Not just whether the timing works, but whether it connects. Not just what is being played, but what it does to the rest of the room.

Sometimes everything aligns. The phrasing. The timing. The attention. The music holds.

Sometimes it doesn’t.

And when it doesn’t, you feel it immediately. The structure is still there. The notes are still there. But something has come apart. No one names it. It’s just… gone.

That was the first time I understood that coherence is not given. It is made. And it is fragile.

Improvisation is often described as freedom. And there is freedom in it. But not the kind that appears without cost. You earn a small range of movement inside something larger than you. You learn the standards, the forms, the patterns, until they settle into your body. And then, in the moment, you respond.

Sometimes what you play fits. It extends the conversation. It creates the sense that something is building, even if no one could say exactly what. Sometimes it doesn’t. It interrupts. It pulls against what was forming. It asks for attention without giving anything back.

And the difference is not always technical. It is relational.

These days, I hear this most clearly in rooms that have nothing to do with music. I’m sitting through a presentation. The language is precise. The slides are polished. Heads nod. Someone scrolls ahead. It all makes sense. And still, something doesn’t settle. There’s a slight hesitation before people respond. A glance that lingers a fraction too long. Questions that begin to surface, then soften into something safer.

The words are moving in one direction. Something underneath them is not. And then, almost quietly, I say,

“I understand it. I’m just not sure I believe it.”

It lands before I’ve fully decided to say it. Not confrontational. Not even complete. Just enough to shift the air. No one answers right away. The room pauses. Not awkward. Not resolved. Just… aware.

It reminds me of playing with someone who is technically precise but not quite present. The notes are correct. The timing is mostly there. But the music doesn’t form. And without that, something essential doesn’t arrive.

Jazz, at least as I have known it, does not prevent this. It just makes it harder to ignore. You are constantly negotiating. When to enter. When to step back. When to support. When to leave space. When to change direction because what you thought was happening is no longer happening.

The space matters more than I once understood. Not as absence, but as the place where alignment either forms or fails.

If jazz has taught me anything, it is this. Not how to speak. Not even how to play. But how to notice, in real time, when something holds and when it doesn’t.

Lately, I keep hearing a sentence that is hard to ignore.

“I know the old way isn’t working anymore… but I don’t know what comes next.”

It’s coming from founders who have stopped believing in the growth-at-all-costs script they once followed. From leaders who can no longer ignore the cracks in the systems they are part of. From people who have climbed the ladder and are beginning to question where it was actually leading.

The details change. The recognition does not.

Something real is shifting. Not all at once, and not always in ways that are easy to name. But enough that many of the assumptions we have been building on are starting to give way. Economic certainties feel less certain. Institutions that once carried authority are being questioned or reshaped. The pace and pressure of work have stretched many people beyond what feels sustainable or even human.

For a while, the instinct was to ask how we might get back to normal. But if we are honest, normal was already under strain. It held together on the surface while quietly eroding underneath.

So we find ourselves here, in the space between stories.

There is nothing firm to hold onto. No clean narrative, no sequence of steps that reassures you that you are moving in the right direction. The markers that once guided you feel less convincing now. The new ones have not yet taken shape.

You feel it in the body before you can name it. A slight unease. A sense of the ground shifting, almost imperceptibly at first. Grief, sometimes, for the version of things you thought would hold. And at times, a sharper feeling. A kind of anger at how much of yourself you gave to something that no longer feels aligned.

I have felt this. Sitting across from a client, helping them shape a strategy I believe in, while sensing that the larger structure we are both standing within has begun to loosen. Doing good, careful work inside frameworks that no longer seem equal to the moment.

There is a kind of vertigo in that. Not dramatic, but persistent. And yet. There is something else here too. Not immediately visible. Not something you can point to or explain. But present.

An opening.

When familiar scaffolding falls away, it leaves space. Not the kind you would choose. But the kind that makes different questions possible. What do I actually want my work to stand for now? What kind of stability am I seeking, not only financially, but emotionally, creatively, relationally? What if growth included integrity and well-being, not just what can be measured on a quarterly report?

These are not abstract questions. They sit just beneath the surface of every conversation that begins with, “something has to change.” They are the questions I hear again and again. The ones I am asking myself.

“Building from the heart” is a phrase that can be misunderstood. It does not mean stepping away from rigour, or becoming less strategic. It asks for something more exacting. To work from alignment rather than inheritance. To be honest about what is shifting and what is no longer sustainable. To allow for the possibility that there are other ways to build, even if they are not yet fully mapped. It looks like pausing long enough to ask whether the thing you are building can actually hold the life you want to live inside it.

It asks for a different kind of attention. The kind that notices when the story you have been telling about your work no longer fits who you have become. That moment is rarely dramatic.

It shows up as a quiet tension.

A sentence you hesitate to say out loud.

A strategy that looks right on paper but feels off in practice.

A version of success that no longer feels like yours.

I think about a conversation I had recently. My friend and colleague had built something impressive by every external measure. The kind of success that made perfect sense on paper and yet didn’t quite hold when lived inside. She sat across from me and said, almost apologetically, “I think I need to take the whole thing apart.” Not because it was failing. Because it was succeeding at something she no longer believed in.

That is what this threshold looks like. Not collapse. Recognition.

If you are standing there, it can feel like you are behind. Like you should already have clarity. Like everyone else has figured something out that you have not.

But that is not what I see. What I see are thoughtful, capable people arriving at the same edge. People who are paying attention closely enough to notice that something is off. People who are no longer willing to keep building in ways that feel misaligned, even when those ways are familiar or rewarded.

That awareness is not a delay. It is a beginning.

And often, the next story does not arrive all at once. It begins in the moment you stop forcing the old one to fit.

This series began, if I’m honest, less as a publishing plan and more as a personal unease. I kept finding myself in conversations about performance, markets, objectives, and key results, and then later hearing the unofficial stories: the ones people told in safer corners about exhaustion, misalignment, unspoken expectations, eroding trust, and the quiet grief of staying too long in shapes that no longer fit.

These essays are, in some sense, me trying to reconcile those two layers: the layer where we talk about decisions as though they’re clean, rational moves on a chessboard, and the layer where those same decisions run through bodies, histories, fears, loyalties, identities, and very real limits. Each piece took one aspect of that dissonance and stayed with it long enough to see what else might be possible.

I haven’t always lived up to the ideas in these pages. I’ve rushed into agreements without clarity, held onto working relationships past the point of honesty, and shown confidence in rooms where uncertainty would have served everyone better. These essays weren’t written from the top of the mountain. They were written from somewhere still along the way.

The path looked something like this:

• What does it mean to lead with courage and curiosity when certainty is easy to perform and hard to justify?

• How do we choose clarity over speed in systems that reward quick moves more than wise ones?

• What changes when we build real agreements instead of running on assumptions and let expectations be spoken instead of silently enforced?

• What becomes possible when we invest in fewer, truer things and allow misaligned work to end, even when it still “works” on paper?

• How does our strategy shift if we treat community and trust as strategic infrastructure, not soft extras? What is the emotional architecture that either carries or cracks our best ideas?

• And finally: how do we prepare for the future without defensively clinging to the past, honouring what brought us here without letting it quietly dictate what must come next?

If there is a throughline, it’s this:

We cannot keep leading as if people are interchangeable parts, time is infinite, and the past is a fixed template for the future.

In the next series, I want to go a layer deeper. I want to explore how the stories we tell about work quietly wire our structures, incentives, and relationships. It’s time to think about how to build a narrative infrastructure that makes honesty and humanity compatible with real results.

If the last six essays were about how we show up, the next six will be about how we design the stories and systems we have to live inside.

What I still don’t know, and have stopped pretending to, is how to hold all of this inside institutions that weren’t designed for it. The ideas here are easier to believe than to operationalize inside a quarterly review cycle, a restructure, or a board that wants a number. I’m unsure whether the gap between what’s possible and what’s incentivized is bridgeable from the inside, or whether something more structural has to shift first. I’m sitting with that. I suspect you might be too.

In the meantime, the work continues in the ordinary places. The meetings, the delayed decisions, the boundaries we honour or don’t, the trust we earn or quietly lose. That’s where all of this either lands or doesn’t.

Thank you for thinking alongside me. I hope you’ll stay.

Every organization carries a history.

There are the obvious things: past strategies and structures, org charts buried in old slide decks, product names that still live on the intranet.

And then there are the quieter layers.

The story about the bold launch in 2014 that “put us on the map.” The founder who used to walk the floor at 7 a.m., coffee in hand. The crisis where a single client kept the lights on.

There is real dignity in honouring what brought us here. There is real danger in letting it quietly decide where we go next.

The work, as I see it, is to prepare thoughtfully for the future rather than nostalgically defend the past. It means honouring what formed us without allowing comfort to set direction. That requires a double movement: gratitude for the people, practices, and ideas that sustained us, and honesty about what must evolve or end if we are to meet the world as it is becoming.

I don’t know how to do this cleanly. I only know it matters.

When History Becomes an Invisible Constraint

Most organizations don’t wake up one day and decide to defend the past. They inherit it. A discount given once in an emergency becomes “our standard pricing.” A workaround created by a clever team in a basement office becomes “our process.” A founder’s personal preference for silence becomes “our culture.”

Over time, decisions settle into defaults. Defaults harden into identity.

You can hear it in everyday phrases: “We’re the kind of company that…” “Our clients expect…” “That’s just how our industry works.”

Many of these stories began as strengths: a bold choice that actually worked, a leadership style that steadied a crisis, a service that once defined the category. But what was adaptive can quietly become prescriptive.

The story shifts from “This worked for us then” to “This is who we are.”

Once a story becomes identity, questioning it no longer feels strategic. It feels personal. Evolution starts to register as a kind of betrayal. Someone hears your proposal for change as a verdict on their earlier effort:

Were we wrong, then?

The risk is not only that we keep doing things the old way. The deeper risk is that we cannot see alternatives at all. The past silently draws the outline of what feels realistic, responsible, or “on brand.”

Preparing for the future means gently surfacing those outlines and asking whether they still serve without shaming the people who drew them.

The Double Move: Gratitude and Honesty

To evolve without tearing ourselves apart, we need a double move.

Gratitude acknowledges the emotional truth: People gave real effort, over the years, to build what exists. They carried stretched roles, worked late, calmed clients, and bent systems to keep things going. They did what made sense with the information and constraints they had.

Honesty acknowledges the strategic truth: What got us here may not get us there. Markets shift. Technology rewrites the cost of coordination. What was once a differentiator becomes table stakes.

If we move straight to critique, people defend the past because they feel erased. They hear: “Everything you built was wrong.”

If we stop at gratitude, we polish the past instead of designing the future.

The double move tries to hold both at once:

• This offering built our reputation and served clients well.

And the market now needs something different.

• Our early leaders made this possible at all

And some of their assumptions no longer git our current scale

But there is a shadow here. The “Double Move” is not a magic spell; it is a negotiation with human resistance. Sometimes, gratitude is used as a stall tactic, a way to stay in the warm bath of nostalgia for one more quarter. Sometimes, the most honest strategy is experienced as a genuine act of violence, no matter how much gratitude precedes it. Integrity means acknowledging that the bridge between what was and what will be is often slippery, and sometimes it collapses entirely under the weight of what we refuse to let go.

Preparing for a Different Kind of Future

The future forming around us is not just a faster version of the present.

Work looks less like a building with desks and more like a shifting network of rooms on a screen. Teams stretch across time zones. New tools appear in the browser every week, quietly redrawing who can do what, from where.

Technology is shifting from a tool to an environment. It’s not just something we “use” for work; it’s the space where work lives. Our chats, our files, our dashboards, and our performance data all exist inside a digital atmosphere that shapes behaviour, visibility, and power.

“We are learning what it means to live inside these “rooms on a screen.” It is a strange, pixelated architecture where the “soul” of an organization is no longer found in the hallway but in the speed of a reply, the transparency of a shared doc, and the invisible permissions that decide who gets to see what. In this digital atmosphere, “the way we’ve always done it” often hides inside an old software setting or a legacy workflow that no one remembers how to change.

Preparing for that future means building more than strategy decks.

It means building:

Trust, feedback, and a strong enough community to carry change. A team that can say hard things early stands a better chance than one that smiles through resentment.

Judgment and adaptability, not only technical skills. Tools will keep changing. The ability to notice patterns, hold conflicting truths, and course-correct will remain valuable.

Relationships capable of weathering experimentation, missteps, and recalibration. If we cannot survive being wrong together, we will avoid the experiments that might teach us what comes next.

Preparing early allows choice. We can decide which parts of our story to carry forward and which to place gently on the shelf.

Waiting leaves mostly reaction.

Sometimes the future isn’t a choice; it’s a collision. We find ourselves reconfiguring the plane mid-flight because the route was changed by someone else long ago, and now the fuel is low and the ground is coming up fast. In that moment, the “Double Move” feels like a luxury we can’t afford, yet it is precisely then that we must pause long enough to ask:

What are we defending here, and why?

Spotting When We Are Defending the Past

Defending the past rarely walks in and introduces itself. It sounds reasonable. It borrows the voice of caution, or experience, or care for the customer.

“Our clients would never go for that.” “Our people couldn’t handle it.” “That’s not how our industry works.”

Sometimes these statements are true. Often, they are inherited assumptions that have not been tested in years.

A simple test is to ask: When did we last check whether this is still accurate?

If the answer is “before the pandemic,” or “I’m not sure we ever have,” we may be protecting history, rather than responding to reality.

Other signals appear:

• We reference a “golden era” and treat any difference as decline.

• We dismiss a new idea with, “That’s not who we are,” without explaining why.

• We confuse consistency with sameness, assuming that staying true to our mission means never changing its expression.

Underneath, a more honest question is often waiting: Are we protecting this because it is essential to our mission, or because it makes us feel safe?

One deserves defence. The other deserves curiosity.

Safety can be emotional: familiar routines, known hierarchies. Or material: roles, status, budgets, influence.

Preparing for the future is therefore not only about mindset. It is also about power and incentives. If career paths, bonuses, and recognition reward guarding the old model, no amount of inspirational storytelling about the future will land.

Allowing for Organizational Grief: A Testimony

Real change includes loss.

Loss of familiar roles and rituals. Loss of a story we’ve told ourselves about who we are. Loss of certainty about what will be rewarded next.

When we ignore that emotional dimension, people cling harder to the past. Not because they hate the future, but because no one has acknowledged what they are losing.

I remember a specific room. The gray carpet, the smell of stale coffee and cigarettes. The florescent hum of the legacy boardroom where a product was being retired. On the spreadsheet, it was the right decision; the margins had thinned to nothing. But in the room, there was a heavy, roughened silence. One man, who had been there since the early days, didn’t look at the slides. He looked at his hands and said, “that product paid for my first house. It paid for my kids’ college. Now it’s just a ‘legacy offering’ on a chart.”

Their attachment isn’t only to the product. It’s to the years of effort, the late nights, the trips away from home, the pride of having built something that mattered.

When we talk only in strategy language, that grief has nowhere to go. It comes back as resistance or quiet cynicism.

Preparing for the future means making room for that grief.

Naming endings out loud. Thanking what served us, specifically. Allowing mixed feelings to exist without rushing to tidy them up.

That might look like:

• Marking the end of a practice with a small ritual, not just an email.

• Publicly telling the story of what a product or process made possible, before explaining why it must change.

• Allowing someone to say, “I know this is right, and I’m still sad,” without treating them as a blocker.

Grief acknowledged becomes energy released. Grief denied becomes a ghost that haunts every new strategy

A Question to Carry Forward

So we circle back to a simple, stubborn question:

What future might we be quietly blocking by holding too tightly to what once worked?

Beside it, another:

What future becomes possible if we honour our history, yet allow curiosity and courage rather than nostalgia to set direction?

The work of this season, for many of us, is simple and difficult at the same time:

• To remember where we came from.

• To see clearly where we stand.

• To notice which parts of our story are truly essential and which are mostly about feeling safe.

• To build enough trust that we can grieve what is ending and still step, together, into a future that cannot yet be fully known.

Because beneath our strategies and structures, there is always another layer at work: the quieter architecture of trust, memory, narrative, and relationship that determines whether change can actually take root.

I am still learning how to navigate that terrain in my own work and life. How to thank what formed me without asking it to decide who I will be next.

Maybe that is the quiet task in front of our organizations, too.

To stay alert.
To stay awake.
And to remember that the work of becoming is never finished.

There was a time when culture lived at the edge of the agenda.

You could feel it in meetings. Revenue first, then operations, followed by product roadmaps, growth plans, and timelines. If there was time left, someone might ask how people were doing. The question carried the tone of hospitality, not necessity.

That arrangement held as long as distance held. When information moved slowly and careers stayed local, organizations could function with a thin relational fabric. Work could be coordinated without much relationship.

That time has passed.

Now a message travels across the company before the meeting ends. People compare notes across teams, locations, and industries in hours. The labour market itself has memory. A single internal experience becomes external knowledge almost immediately.

Under those conditions, community and trust stop being moral aspirations. They become load‑bearing.

Without them, performance flickers.

With them, it holds.

I am beginning to treat them accordingly.

This is not a manifesto. It is a working note to myself. I am trying to understand what it would mean to design work as if psychological safety, honest feedback, and belonging were not by‑products of success, but conditions that make success possible.

We have been talking about agreements, about clarity, about knowing when to let go and where to focus our effort. Each of those depends on something more basic. Before alignment, before strategy holds, there has to be a place where people can tell the truth about what they see.

From “Soft Stuff” to Infrastructure

Most organizations still carry an unspoken hierarchy.

There is real work. And then there is the rest.

You can tell which is which without asking anyone. Watch where the budget goes. Notice which meetings disappear when schedules tighten. Listen to what leaders ask about in reviews.

Revenue is real. Operations are real. Growth is real. Connection is optional.

And yet the pattern repeats.

In a low-trust team, enormous energy goes into positioning, hedging, self-protection, careful wording, and private interpretation. Meetings multiply, decisions slow, and effort leaks sideways.

A high-trust team spends its energy differently. Problems are named early, mistakes surface quickly, and people take risks without rehearsing self-defence in their heads. The work moves because less effort goes into guarding oneself and more into solving together.

Under pressure, the difference becomes unmistakable. Low-trust systems crack. High-trust systems bend and adapt. We often credit that resilience to heroic leadership or exceptional talent. More often, it is quieter than that. Those relationships carry weight.

We use strategy to plan how to win. But it’s trust that determines whether the plan survives contact with reality.

The Emotional Climate

I remember a meeting where a junior team member started to speak, paused, and then said, “Actually, it’s probably fine.” The conversation moved on.

We were reviewing a campaign concept before presenting it to the client. The idea was strong. The room felt energized. The headlines were sharp, the visuals compelling, and the concept clearly scalable across channels. You could feel that familiar lift in the room, the sense that we’d “cracked it.”

Later, in the hallway, the junior copywriter quietly explained what they had almost said.

At the center of the campaign was a single line that hinged on a claim which sounded right, but wasn’t fully supported by what the organization actually did day to day. It wasn’t an outright falsehood. It was subtler than that. It was the kind of message that would look inspiring in a launch video and on a landing page, but would feel off to the employees asked to stand behind it, and fragile under even mild public scrutiny.

They were right. When the issue finally surfaced formally, the cost was real: time, trust, rework, and a delayed launch while we unwound something that could have been questioned in that original room.

Nothing dramatic had happened in the meeting. No one had been harsh. No one said, “Don’t speak up.” But something in the air had made honesty feel expensive. The safest move, in that moment, was to stay quiet and let the momentum carry the room.

Every organization has a climate, whether anyone names it or not. You feel it within minutes of entering a meeting:

How carefully people choose their words.

How quickly someone is willing to admit uncertainty.

Whether a mistake produces curiosity—or a tightening silence.

Most strategy decks map markets, competitors, and channels. Very few map fear. And yet fear alters information flow more reliably than any reporting system. A person who does not feel safe will not share what they know when it matters most.

They will wait.

They will soften.

They will privately adapt instead of publicly challenge.

Then leaders wonder why risks appeared late.

I have begun to suspect that collaboration has a bandwidth, and trust controls it. When trust is low, communication narrows. Only safe information moves. When trust is high, nuance travels, warnings travel, and so do new ideas. Performance follows.

So I find myself asking questions that once sounded like HR and now feel strategic.

Can someone say, “I think we’re wrong,” without calculating personal cost? Where does doubt go inside the organization? Does it go into shared conversations? Private channels?

If truth must travel sideways to be spoken at all, the organization is already working with partial reality.

Designing for Safety

Psychological safety is often mistaken for politeness. It is closer to courage. Not heroic courage, just ordinary courage. The courage it takes to admit a mistake, ask a basic question, or interrupt momentum to say, “I’m not convinced.”

Each of these moments carries interpersonal risk. People make quick calculations: Will I be trusted less? Seen as difficult? Quietly excluded later?

Safety exists when those calculations change.

I have started paying attention to those very small moments. Like how a leader responds to bad news. Or whether uncertainty is spoken aloud. Is someone who raises a concern thanked or merely tolerated?

The system learns quickly. It always does.

If telling the truth costs more than silence, silence will spread. From the outside, everything will look orderly…and inaccurate.

Feedback as Maintenance

Feedback is often framed as evaluation. But it works better as maintenance.

No bridge waits for a crack to widen before inspection. Yet many organizations wait for a conflict to escalate before having a conversation. By then, the issue carries emotion more than information.

We are experimenting with making feedback ordinary. Short reflections after projects. Asking what we are avoiding saying. Speaking to people directly, not about them.

The first attempts feel awkward. People choose their words very carefully. But something changes when leaders accept feedback publicly and act on it. The room relaxes slightly, and information moves earlier the next time.

I am noticing that feedback, done well, is not criticism. It is a continuous calibration. It is a system learning while still in motion.

Belonging

Belonging sounds sentimental until you watch its absence.

In some meetings, only certain voices enter easily. Others wait for an invitation or remain silent. The pattern repeats week after week, and slowly the organization mistakes familiarity for competence.

When people feel peripheral, they contribute carefully. Not out of indifference, but out of self-protection. They measure their words, offer the safest version of their thinking, or stay silent altogether. Why risk an idea if it first has to pass an invisible test of legitimacy?

Belonging changes that calculation. Not forced harmony, but the quiet confidence that participation will not cost dignity.

When that confidence appears, initiative follows. Ideas surface without prompting and ownership spreads. People stop managing impressions and start solving problems.

The work gains the intelligence it had been living without.

Community

Community at work is not events or Slack channels. It is not the offsite, the group photo, or the language we use to describe ourselves.

It is the quiet understanding that we are not facing the work alone.

You recognize it in ordinary moments:

• Someone admits they’re underwater before the deadline passes, and the response is help, not judgment.

• A mistake is spoken plainly, and the first question is “What did we learn?” not “Who did this?”

• A difficult client call ends, and people stay on the line a few minutes longer than necessary, not because they have to, but because no one wants to leave the other person carrying it alone.

You also recognize its absence.

• The meeting where everyone agrees too quickly.

• The careful emails that say less than people know.

• The idea that never makes it to the table because the person holding it can’t quite tell where they stand.

In those environments, the work continues, but it narrows. People do what is asked, not what is possible.

It’s tempting to write these moments off as personality, preference, or mood. But they quietly decide how much of a person actually arrives at work. When community is present, people bring their judgment, their attention, their creativity, and even their doubt. When it is not, they bring only the part that feels safe to offer.

I have watched ordinary teams do improbable things in a strong community. Not because they were unusually gifted, but because they trusted that effort would be shared and mistakes would not harden into identity. And I have seen highly skilled teams stall the moment people began managing exposure, choosing safety over contribution, and protecting small territories instead of a shared outcome.

Community does not replace strategy. It determines whether strategy can be inhabited.

A plan can live on paper. It cannot move without people willing to carry it together.

Trust grows slowly and breaks quickly.

We say this often enough that it almost sounds like a cliché. What we talk about far less is what happens after the break. The work of repair.

Every organization will stumble.

A decision lands badly.

A message is tone‑deaf.

A commitment slips.

The mistake matters, but it is not the whole story. What follows teaches people what is really true here.

If the response is defensiveness and spin, trust thins. The gap between the official story and lived experience widens. People learn that honesty is dangerous, and they act accordingly.

If the response includes ownership and adjustment, something different becomes possible. Trust doesn’t just recover; it can deepen. People learn that reality can be spoken without punishment, and that the relationship can survive the truth.

I’m less interested in whether an organization “gets it right” every time. I’m watching what happens after the error, not the error itself, but the reaction.

Do we close ranks or open conversation? Do we look for someone to blame, or for something to learn?

Infrastructure rarely fails from a single event. It fails from the strain that no one repairs.

Measuring the Invisible

If trust and community really matter, they have to live somewhere besides intuition and hopeful anecdotes. So I’ve started asking a few simple questions, over time:

• Do people feel safe to speak openly, even when their view is unpopular?

• Are difficult topics raised early, or only when they’ve become crises?

• Does information travel through official channels, or mostly through side conversations and back‑channels?

None of these are perfect measures. They’re the signals. Think of them as weather patterns more than metrics that keep one thing in view:

The inner life of the organization is not separate from “the real work.” It is part of the operating system. It is the climate in which every decision, every risk, and every relationship lives inside.

A Working Commitment

I keep returning to a simple thought. We spend enormous effort refining strategy, structure, and measurement. Yet the success of all of it depends on whether people feel safe enough to tell the truth about what is actually happening.

If that is true, then community and trust are not cultural luxuries. They are operating conditions.

I don’t yet know everything this commitment will change. I only know that the quality of our work feels inseparable from the quality of our relationships.

How we are together is already shaping what becomes possible between us.

The room itself may be part of the strategy.

So this is the experiment I want to keep leaning into: to build work that is as honest as the conversations it rests on, and to see how far we can go when people are free to bring their full, unedited selves to the table.

That sentence shows up everywhere once you start listening for it. In organizations. In partnerships. In relationships that seemed aligned until they weren’t.

Every collective effort runs on an invisible web of expectations: what we believe others will do, how we think decisions will be made, and what we assume matters most when trade-offs appear. When those expectations remain unspoken, disappointment and conflict are not anomalies. They are the predictable result.

Assumptions are like silent contracts. Everyone believes there is an agreement, but nothing has actually been said.

“I thought you were handling that.”
“I assumed we were aligned.”
“I figured you knew.”

This year, I am committing to building agreements, not assumptions. Replacing vague hope with explicit, human commitments with my team, with partners, and with clients.

Not because trust is broken, but because trust deserves structure.

The Pitch That Wasn’t an Agreement

This commitment was earned.

Years ago, I spent weeks pitching for what looked like a dream client project. They asked for a detailed deck with strategy, visuals, and sample deliverables. Then another round. Then a few more “exploratory” meetings, each with new stakeholders. Follow-up notes. Revised timelines. Draft language they could “react to.”

Each step felt like momentum. They spoke in the language of partnership.

“We really see you as a collaborator.”
“We’re almost there.”
“Can you bring two or three more options next time?”

So I did. I stayed up late refining concepts. I revised slides. I shaped their story. Somewhere along the way, my language shifted from they to we.

We’ll launch this in Q3.
We’ll navigate the politics.
We’ll make this a flagship project.

By the third or fourth meeting, it felt like we were already in a relationship. Co-creating. Whiteboarding. Exploring possibilities. I let myself believe that the energy in the room was the agreement.

Then the emails slowed. Meetings were “pushed.” A decision that was “days away” stretched into weeks. Eventually, there was a short note saying they were going in a different direction. Or worse, silence.

They walked away with a deck full of my best thinking, a clear internal storyline, and a list of ideas they could reuse with someone cheaper or already on payroll.

They got free ideation.
I got unbillable hours and a lesson.

It hurt, not just financially but emotionally. Because in my mind, we had an understanding. In reality, we had no agreement at all.

There was no shared clarity about what counted as pitching versus paid work. No agreement about how many rounds were reasonable. No agreement about what “moving forward” actually meant, or how a decision would be made.

I had mistaken momentum for commitment.

When Assumptions Become the Operating System

This pattern isn’t unusual. It shows up in client work, internal projects, and early partnerships all the time.

Excitement creates motion. Motion creates the illusion of alignment. And before anyone realizes it, people are operating as if they’re already in relationship while the other side is still collecting options.

No one is necessarily acting in bad faith, but power matters. The party with more leverage often benefits from ambiguity. The party eager to belong or prove value fills in the gaps with effort, generosity, and unspoken hope.

Assumptions quietly become the operating system.

You can hear them in everyday frustration:

“I thought you were responsible for that.”
“I assumed this was a priority.”
“I figured you knew.”

Over time, these assumptions harden into cultural rules no one remembers agreeing to:

Around here, speed matters more than thoughtfulness.
Real decisions happen in side conversations.
Questioning direction is risky.

No one wrote these rules down. No one consented to them. Yet they determine what feels safe, possible, or worth investing in.

When things break, we blame people. Rarely do we name the real issue: there was never a shared agreement to begin with.

Agreements as Quiet Infrastructure

An agreement is not just a contract or a policy. It is a shared understanding that lives in relationship.

It answers a few simple but consequential questions:

• What are we doing together?

• Why does it matter?

• How will we behave along the way?

• What will we do when things get difficult?

Real agreement exists when everyone involved can describe it in their own words, revisit it without defensiveness, and understands what happens if it isn’t met.

Assumptions live in the gaps. Agreements live in the open.

Each explicit agreement is a small act of care. It says: I respect you enough to name what matters to me, and to hear what matters to you.

In a moment marked by mistrust and fragmentation, agreements are quiet infrastructure. They don’t remove uncertainty, but they give us something solid to stand on together.

What Strong Agreements Actually Require

Building agreements can feel slow because it asks us to speak out loud about things we often treat as obvious: boundaries, definitions of “done,” decision rights, and timelines. What values actually look like in practice.

When urgency is high, this kind of conversation can feel like friction.

“Do we really need to spell this out?”
“Can’t we just get started?”

But skipping agreement-building doesn’t remove friction. It pushes it downstream, into moments when the stakes are higher, and repair is harder.

When I try to turn assumptions into agreements now, I return to a few practices.

I make the work concrete. I move from fuzzy labels to a visible scope. I name what is included, what is not, and how completion will be recognized.

I name the purpose clearly enough to guide trade-offs. A shared reason for the work becomes a compass when conditions change.

I translate values into observable behaviour. Not “respect,” but response times. Not “collaboration,” but how disagreement is handled.

And I decide in advance how strain will be addressed. Deadlines slip. Capacity changes. Feelings get bruised. Strong agreements do not pretend otherwise. They name the response before it is needed.

None of this prevents difficulty. It prevents confusion when difficulty arrives.

Choosing Care Over Drift

Let’s be honest. There is no way to eliminate assumptions. But we can decide what to do with them. We can let them run quietly in the background, shaping our work through projection and guesswork, or we can bring them into the open and do the slower, braver work of turning them into agreements. That work carries risk. Agreements ask us to name needs before we know if they will be met. Assumptions protect us from that exposure.

Still, I am choosing clarity over confusion. Care over assumption. Responsibility over drift.

In a time when so many working relationships are strained, agreement-building is not bureaucracy. It is a discipline of leadership.

Every clear agreement is a small refusal to operate on wishful thinking.
A small act of respect for the people you work with.
1And a step away from silent contracts toward shared, deliberate choice.

Share

The unspoken belief is that faster is always better. Speed is a proxy for relevance, ambition, and competence. But in environments shaped by complexity and uncertainty, speed without clarity is not a strength. It is a liability. The organizations that will actually thrive in the next decade will not be the ones that simply move fastest. They will be the ones that move at the speed of clarity. Fast where it is safe to be fast, deliberate where it is essential to be deliberate.

Choosing clarity over speed is not an argument for slowness. It is an argument for disciplined pace. It is the willingness to slow down at the right moments so that when we do move, we are aligned, coherent, and able to sustain momentum.

This is not just an operational question. It is a leadership choice. And increasingly, it is an ethical one.

The Cult of Speed and What It Costs Us

Many of us were shaped inside a familiar business logic:

· Launch first and you win.

· Respond fastest, and you win.

· If we show up with an answer immediately, we look competent, even if the answer is shallow

That logic made more sense in stable environments, where problems were contained and consequences were easier to predict. In today’s reality, marked by social volatility, technological acceleration, and overlapping crises, speed without clarity amplifies risk. We see the pattern everywhere:

· Products launched before implications are understood.

· Campaigns that generate attention but quietly fragment trust.

· Decisions enforced quickly, then publicly walked back.

· Teams sprinting toward subtly different interpretations of the same goal.

From the outside, this looks like productivity. Underneath, it is friction, rework, confusion, and erosion of trust.When clarity is missing, people fill in the gaps themselves. Rumor, assumption, and anxiety become the real operating system of the organization. Once that happens, it matters very little how quickly you move. The system begins to counter-move against you.

What We Actually Mean by Clarity

Clarity is not having all the answers. In complex environments, that is neither realistic nor desirable. Clarity is more precise than that.

It is clarity of intent.

Why are we doing this? What problem are we actually trying to solve, and for whom? What are we explicitly not trying to do?

It is clarity of narrative.

What is the story that holds this together? Can people explain it in their own words and act on it without constant translation?

It is clarity of responsibility.

Who is accountable? Who is consulted? Who decides when trade-offs arise?

And it is clarity of boundaries.

What are the constraints? What are the time, budget, risk tolerance, and ethical lines we will not cross? What are we not willing to compromise, even under pressure?

Choosing clarity over speed means answering these questions explicitly, together, before we press go. That front-loaded discipline rarely takes as long as people fear. Often it is the first 10 to 15 percent of the work. But it radically changes the quality of everything that follows.

Why Clarity Feels Slower

Leaders resist this move because it feels slower.

· It feels slower to pause a meeting and ask, “What decision are we actually making here?”

· It feels slower to say, “Before solutions, can we agree on the problem?”

· It feels slower to acknowledge, “We have multiple definitions of success circulating.”

In cultures trained to equate pace with performance, these questions can look like hesitation or obstruction.

Zoom out beyond the next twenty-four hours, and the math becomes obvious.

Ten minutes of alignment now often saves weeks or months of misdirected work. A single shared narrative can prevent dozens of micro-conflicts across teams. One explicit conversation about trade-offs can prevent months of quiet resistance. Clarity does not slow you down. It removes hidden drag. What we often call speed inside organizations is actually churn. Activity without alignment. Urgency without direction. True speed emerges when people are clear enough to act without constant oversight. It translates into understanding not only what to do, but why, and within what bounds.

Clarity as a Leadership Responsibility

Choosing clarity over speed is not a communication tactic added at the end of the process. It is a leadership posture. It asks leaders to do several uncomfortable things:

1. Name the real stakes. Not only the KPI version, but the human and reputational stakes. What breaks if we get this wrong? For whom? What does that mean for trust?

2. Surface competing truths. Clarity does not require a single dominant voice. It requires that reality is fully seen before decisions are made.

3. Tolerate a brief period of constructive ambiguity. There is a phase where complexity has been acknowledged but not yet simplified. Many leaders rush past this phase out of anxiety. The discipline is staying just long enough to integrate what matters.

4. Decide in the open. Explain not only what was decided, but why. What was considered, what was deprioritized, and what principles guided the choice.

This is slower in the moment. It is much faster over time.

Making Clarity Operational

Clarity only matters if it can be practiced under pressure. A few simple moves help make it real. Start with a one-page Clarity Brief before greenlighting work. What problem are we solving? For whom? What does success look like? What are the constraints? Who decides when trade-offs arise? Is there anything we think we agree on that hasn’t actually been said out loud? This is not bureaucracy. It is a clarity artifact. Writing it surfaces fuzziness early, when it is still cheap to fix.

Build a clarity check into key meetings. What exactly are we deciding? Is any critical context missing? Can someone summarize the decision and the why in two sentences?

Anchor on a clear narrative, not a pile of messages. Before emails, decks, or town halls, ask what story holds this together. How does it connect to values, strategy, and the world people are actually living in?

And make trade-offs explicit. If speed and thoroughness conflict here, which wins? Which risks are acceptable, and which are not? Ambiguity around trade-offs doesn’t protect you. It just pushes the burden of impossible choices down the hierarchy.

The Emotional Dimension of Clarity

Clarity is not only cognitive, it is also deeply emotional. When people have clarity, they experience psychological safety. They understand the boundaries and the why. They no longer need to scan for hidden agendas. They experience agency and can make decisions without fear of stepping wrong. Most of all, they experience trust. They can see that speed is not being used to bypass scrutiny or responsibility.

Moving fast without clarity reliably produces the opposite: anxiety, cynicism, quiet disengagement. Over time, this pattern doesn’t just frustrate people; it burns them out. Not because they’re doing too much, but because they’re doing it in the dark. That’s why choosing clarity over speed is not just about performance. It is about the social contract between leaders and the people they ask to build the future with them.

When Speed Truly Matters

There are moments when speed is non-negotiable: crisis response, customer harm, operational incidents. But the paradox is this: the stronger your baseline clarity, the safer and more effective your speed becomes. Teams with shared intent, a coherent narrative, and clear decision rights can move quickly without creating downstream chaos. Clarity is not a substitute for speed. It is the precondition for meaningful speed.

Choosing Clarity Is Choosing Responsibility

In a world where actions and narratives ripple far beyond org charts, choosing clarity over speed is a form of responsibility.

· It is the decision to understand implications before launching.

· To tell stories that can withstand stress.

· To ask people to move quickly only when they have the context to do so wisely.

Urgency will always be seductive. Approving the deck. Signing off on the strategy. Greenlighting the campaign can feel like progress. But leadership is not about feeding the urgency machine. It is about creating conditions for work that is coherent, sustainable, and worthy of trust.

Choosing clarity over speed is one of those conditions. And it is a choice we make, moment by moment, meeting by meeting, narrative by narrative.

Every January, leaders are encouraged to set goals that sound reassuringly measurable. Revenue targets. Hiring plans. Expansion roadmaps. I’ve made lists like that for most of my career. They have their place. They help us steer the ship.

But as I enter 2026, I find myself less preoccupied with what we will achieve and more concerned with how we will move toward it and who we are becoming in the process.

The world around us is increasingly defined by volatility and acceleration: AI systems that move faster than our norms and laws, social feeds that reward outrage over understanding, and economic and ecological pressures that expose every weak seam in our institutions. In this environment, leadership is less about having the right answers and more about developing the inner and collective conditions that allow better questions, better choices, and better relationships to emerge.

This year, I’m setting a different kind of resolution for myself, less like a checklist and more like a compass.

They are not promises of perfection. They are directions I want to face, again and again, especially when it would be easier to look away.I’m sharing them here in case they serve as a point of reflection for you, too.

The first direction I want to face is courage and curiosity.

There is always a moment, just before an important decision, when fear offers the easiest path: retreat into skepticism, stay on the sidelines, and critique from a safe distance. As leaders, we can become very skilled at using our intelligence to justify inaction.

This year, I’m committing to leading with courage and curiosity: to stay open, constructive, and possibility-focused, even when it’s more comfortable to close down.

Courage, in this sense, is not the absence of fear. It is the choice to keep our hearts and minds available to what is unfolding, to step into conversations we cannot fully control, and to admit when we don’t yet know. Curiosity is its twin: it is the willingness to ask, What else might be true here? What am I not seeing? Whose perspective is missing?

In a culture that often confuses leadership with certainty, choosing curiosity can feel like a risk. Yet, without it, organizations slowly harden around their own assumptions. Innovation becomes cosmetic. Strategy becomes theatre.

So I’m asking myself:

• When tension arises, do I default to shutting it down or leaning in?

• When someone challenges my approach, can I stay with the discomfort long enough to learn from it?

• Can I let my questions be as visible as my convictions?

Leading with courage and curiosity is how I want to meet challenges and opportunities this year. Not with bravado, but with a willingness to stay open.

Over the coming weeks, I’ll spend time with each of the new directions on my list, not as conclusions but as ongoing inquiries. If one of them meets you where you are, you’re welcome to sit with it here. And if it raises questions of your own, I’d be glad to hear them.