Do you know this dream? You are standing in front of a room of people with something important to say. Life or death. Or something magical. But no one can understand you. You are speaking gibberish. The thing you need to say is growing in intensity within you, but the audience is shifting from confusion to concern. Then you begin to recede. The audience turns away. Something feels like it's dying.

Or what about this dream? You are trying to reach a place on the horizon. Beautiful, shimmering, just beyond grasp. You run toward it, but the horizon doesn’t close. You run harder, and it stays forever just out of reach. You run until you wake up or you don't, and the place you were trying to reach is exactly as far away as when you started.

Both dreams are about the same distance. And most leaders I know are living inside one of them right now, awake.

- - -

I am known inside my organization as the Integrator. It’s not a title I chose, but one earned through the observations of others: people who named what they saw in me before I had.

What they saw was someone who moved between disciplines on complex projects, carrying meaning from one specialist to another without losing too much of it along the way. What they didn't see was the mechanism underneath. The thing I had subconsciously built that made the whole operation run.

I shape things. I mean that I am constitutionally, almost compulsively, inclined to guide every conversation, every team assignment, every framing of a problem toward a solution I can catch. The side conversations before a meeting. The questions I ask that aren't quite neutral. The encouragements that carry a direction. The body language I offer when someone's thinking drifts toward territory I can't rescue. I was shaping the universe of every project toward something within my reach, and doing it so naturally I had mistaken it for talent. I became a safety net.

In the model where I was the safety net, I could compensate for weakness by working harder. A struggling partner, a missed deadline, a gap in the work. Whatever it was, nights and weekends could cover it. Most people who have led anything know this feeling. It is control dressed as reliability. And it works, up to a point.

The point is 3+3=6.

You can reach six by doubling your effort on three. It costs you, but it's available. What no amount of additional effort can accomplish is getting from six to nine. Nine requires something different entirely. Because while 3+3 and 3×3 use the same resources, the relationship between them is different—not incremental, but categorical.

- - -

Consider two expressions of the same force.

A battery produces electricity. It is a casing around a chemical reaction. It stores energy converted to current through a process that generates heat, produces waste, and degrades over time. It’s reliable. Portable. Controllable. Effective. But it is not what electricity is.

A lightning bolt is what electricity is. Unmediated. Elemental. It moves at one third the speed of light and heats the air around it to five times the surface temperature of the sun. In certain atmospheric conditions, it does something the battery cannot approach: it splits nitrogen and oxygen molecules, recombining them in ways that eventually feed the soil that grows the food. The lightning bolt is not just more powerful. It is participating in something that sustains life.

The battery, to its credit, is very reliable.

Most organizations are built on battery logic: predictable inputs, measurable outputs, controllable processes. This is not wrong. Reliability is not nothing. You need the battery.

But there are results the battery cannot reach. It’s not a matter of a bigger battery, greater effort, or more output. It’s a different category of output, requiring different relationships between the forces involved. That’s how you capture lightning.

Put another way: when two waves on open water meet and their relationship is right, they don't simply add. They amplify. The resulting wave carries more than either wave contained alone. When the relationship is wrong, the waves collide. Ships have been torn apart by seas that were the product of that collision. The waves themselves were not exceptional. Their relationship was catastrophic.

The same forces. A different relationship. A categorically different result.

- - -

Several years ago, I walked into a room that was larger than anything I had been the safety net for before.

A military construction project for a special warfare unit training facility. The table was surrounded by specialists from different companies, different disciplines, different professional cultures with different languages and different operating assumptions. Architects. Business strategists. Military training specialists. Technologists. Communications experts. Each of them excellent. Each of them carrying the particular jadedness of the seasoned professional—the imaginative zeal of their training now surfacing only in sparks, quickly extinguished by the accumulated weight of projects that had taught them to expect compromise. They had extended their hands before. They knew what usually happened next.

I looked at that room and saw what was coming before it arrived. Powerful people about to engage in a sophisticated tug of war, each pulling the solution toward the boundary of their own specialty. Not from selfishness. From competence. A specialist solves to the fullest extent of what they know and stops. That is what mastery looks like from inside a boundary. Multiply it across a room and you get a collection of correct answers that don't fit together. Everyone building something true, nothing cohering.

I knew I could not save it. The room was too large, the disciplines too far apart, the gaps too wide. I didn't have enough hours, enough reach, enough talent. The safety net I had always carried wasn't big enough for this room, and for the first time I knew it before the project started rather than after.

So I stood up and went to the whiteboard.

What happened next is difficult to describe accurately. I was not executing a plan. The marker moved before I fully understood what I was drawing. A diagram of dependencies surfaced. A way of designing the relationships between the specialists so that meaning could move between them without being lost. I was acting before I realized what I was doing. It felt less like confidence and more like being conducted by something outside me.

What I remember most is the facing away. The whiteboard gave me a small, strange shelter. The room was behind me, out of sight. My hand moved. My thinking ran on a current I hadn't generated. And for those few seconds, facing the wall, I had a space of safety I didn't deserve and needed completely. My fear hadn't caught up yet. It was running toward me from somewhere behind the room.

Eventually I had to turn around.

Thankfully, the project succeeded beyond what any individual at that table could have produced. Not because we worked harder. Because we worked different.

- - -

Here is what working different actually looked like, from the inside.

The specialists in that room had learned, over long careers, to translate. To stop speaking in the language of their discipline and start teaching it. They simplified, contextualized, and repeated. But every translation costs something. The idea that arrives is a copy of the one that left, carrying less of what made it true. The specialist loses something in the explaining. Something alive in the original formulation goes flat in the transfer. Multiply that loss across every handoff in a complex project and what reaches the end is a diminished version of what started. Meaning degrades. This is not a communication failure; it is a structural reality of how knowledge moves between people who have spent years becoming fluent in different things.

The integrator's job is to close that distance. Not by being the smartest person in the room but by becoming fluent enough in every specialist's language to carry meaning across the gaps without dropping it. To move between rooms without losing what you're holding. When that works, something shifts that is difficult to manufacture and unmistakable when it arrives. Specialists stop translating. They operate in their native language at the height of what they know. The spark that had been going out for years begins, cautiously, to return. Slowly, the way someone extends a hand that has been slapped before. Not yet sure what this room will do with it. Ideas arrive at other specialists fresh rather than filtered. Those ideas meet other ideas. The energy in the room changes from obligation to inspiration, and when it does, you can feel it. It is palpable. Clients have walked into our office and said they felt something without being able to name it. I know what they felt. I have watched it accumulate, over time, in rooms that had forgotten what was possible.

Additive or siloed teams operate to the lowest common denominator. Integrated teams operate toward the highest order of meaning.

What I mean by meaning is not sentiment. I mean the power a thing has when it is operating closest to its own nature. The lightning bolt is not more powerful than the battery because it is larger. It is more powerful because electricity is unmediated, doing what it was always designed to do, without conversion loss standing between the power and its expression. Integration does not add power to a team. It removes the distance between what the team contains and what the work can become.

Meaning is what remains when nothing essential has been lost in translation.

- - -

For a long time, the ability I have been describing served me well enough that I never examined what was governing it.

At a small scale, designing projects toward solutions I could rescue looked like leadership. It produced results. People were grateful. I was useful, and I knew it, and knowing it felt good in ways I didn't scrutinize. But the scale of the work kept growing, and somewhere in that growth the thing that had made me valuable began to make me a ceiling. I was designing teams toward my own limitations and calling it stewardship. I was arranging the conditions under which I would be needed and confirmed, and telling myself I was reducing risk for the client.

When I finally saw that clearly, I couldn't unknow it. The conviction that arrived was not gentle. It was the specific discomfort of recognizing that something you have been proud of has been doing work you didn't authorize it to do. I am still not entirely sure how guilty I am. I don't believe manipulation was my primary motive. But I am not guiltless, and the distance between those two things is not a place I get to resolve quickly or cleanly.

What I know is that the ability needed to be laid down. Not destroyed, but put on the table and left there long enough to scrutinize what had been governing it. Fear? The need for confirmation? The comfort of a ceiling I had built myself and could therefore always touch? Those things had to be faced before the ability could be picked up again. Whether or not it should be picked up again was not something I knew in advance.

What came back was the same capacity, returned from a different direction. Governed now by a different question.

Not: how do I design this toward what I can catch?

But: how do I design this toward what it must become?

The integrator, properly understood, is a servant. A steward. Not the person who holds the antidote but the person who learns every language in the room so that meaning can move freely between people who would otherwise be shouting across a distance neither of them can measure. The integrator does not produce the energy. They design the conditions under which it can appear. That is a different kind of power. Less visible. Harder to take credit for.

It is also the only kind that gets to nine.

- - -

You may never run an integrated project team. The model requires specific conditions, specific roles, specific investment. It is not the right operating system for every organization or every moment.

The lightning bolt is only needed for a moment. The battery serves faithfully the rest of the time. The trap lies in assuming the battery, applied with sufficient dedication, will eventually do what only the lightning bolt can do.

Look at the goals that matter most to you. The ones on the horizon. Beautiful, real, or close enough to real that you keep running toward them. Now ask honestly: how many of them are sitting at a distance that a work-harder pace will never actually close?

What would it mean to work different instead?

You may not be able to see what different looks like from inside the operating assumptions you already carry. The kind of different that closes the distance effort cannot close is often invisible from where you are standing. That is not a weakness. But it does mean that you may need new people, new voices, outside perspectives. Not because you lack ability, but because the horizon you are trying to reach is outside the boundary of what your current fluency can conceive.

Put down the thing that has always saved you. Go to the whiteboard. Draw something true before you know if you can deliver it.

Eventually you will have to turn around. But not yet. For now, the marker is in your hand, the room is behind you, and something is moving through you that didn't originate with you.

That is the distance effort cannot close. And that is exactly where you are standing.

Dave Ortega is Chief Creative Officer at McKee Wallwork.