There is a spider web somewhere near you right now. In a corner, under a rail, strung across a window you have been meaning to clean. Most people see a thing to sweep away. I see the most honest organizational chart ever drawn. Every strand is tied to every other strand. No box on top. No box on the bottom. A structure so interconnected that you can tear a piece clean out of it and it will still hold its shape and still do its work.

So ask me to draw how an organization should actually work, and I will not hand you a pyramid. I never have. The pyramid is the shape we were all taught to trust, the neat stack of boxes with one name at the top and everyone else arranged below it in descending order of worth. I have spent a career refusing it. What I draw instead is that web, and I do not mean it as a metaphor I reach for to sound clever. I mean it as the actual architecture I lead by. Everyone is on the same plane. No one is standing above anyone. The only thing that changes as you move toward the center is how much you carry.

Responsibility is not rank. It is weight. In a web, the closer you sit to the center, the more you carry, and carrying more never means standing above.

Here is what a pyramid trains your eye to do. It sends you upward, to the one name that is supposed to answer every question the chart was built to ask. A web trains your eye differently. It pulls you to the center first, and then it does something a pyramid never makes you do. It sends you back outward, to the anchor points, the exact places where the whole structure is tied to the world. Those anchor points are different in every organization, because a spider builds where it lands, and it secures its web to whatever happens to be there. A pyramid hides those anchor points. It also hides the silos it quietly builds between one department and the next, the walls nobody drew on purpose, and nobody will admit are standing. A web hides neither. It shows you where it is anchored and the connections a pyramid works hardest to keep out of sight.

Where it came from

I did not arrive at this metaphor in a boardroom. I arrived at it out of frustration.

I was a young professional with what I believed were good answers to some of the hardest problems my organization had. I had no way to pass a single one of those answers to the people who could act on them, because the organization was built as a strict hierarchy, and there was no channel from where I sat to where the decisions were made. I looked at other systems for a model. I looked at democracy, where a person has a direct line to the people who decide, and I thought, that is a flattened org chart, that is closer. An organization, though, is not going to run as a democracy. So I kept looking for an image that could hold the thing I did not yet have words for: everyone on the same plane, with different levels of responsibility, all of it connected. I had always been fascinated by how a spider builds a web and uses it to communicate. The image was waiting for me the whole time.

I want to tell you where that image actually lives in me, because I will not manufacture an origin that was never true. It comes from childhood, long before I had a single thought about how leadership works. My mom had a beautiful dogwood tree in the front of our house, and almost every morning, spiders built webs in it. One morning, a spider had strung a web between the tree and the porch. There was heavy dew, and you could see the whole thing clear as day. It ran right across the sidewalk we used to reach the driveway. Most people would have swatted it down without a thought. We walked around it. We took the other path to the car, because the web was too beautiful to destroy. I can still see the spider moving across a structure it had built with its own body. That morning taught me nothing about leadership. I did not know then that I would ever need it to. What it gave me was an exact, living picture of a web being built and doing its work, and years later, when I went looking for an image to hold everything I could not yet name, that picture was already there, waiting for me.

There is one more thing that tree taught me, and it points somewhere I cannot fully follow in this chapter. When a spider does not catch anything, it will eat its own web to recover the energy it spent building it. The very structure it uses to run its life also feeds back into it. Nothing is wasted. The thing the spider builds sustains the spider. I have come to believe leadership has to work the same way. If the way you build an organization only ever drains energy from the people inside it, you have not built a web. You have built something that runs on people until they are spent, and then it fails. A structure worth building gives energy back. It sustains the people who hold it up. That is sustainable leadership, and it deserves more room than I can give it here, so I carry it forward into that chapter. For now, hold the image. The web feeds the spider. Leadership, built well, feeds the people who build it.

Why a web, and not something else

I could have reached for other images to explain this. A root system. A constellation. A river delta. The one that comes closest, close enough to be worth taking seriously, is the nervous system, and it is worth seeing exactly where it falls short of a web, because the gap between the two is the whole point.

Every point where the threads intersect is a person. Each of those points carries a single responsibility: when something lands, send the signal. And here is the part almost everyone gets wrong. People assume a web only carries signals inward, to the center, to the spider. It does not. The signal travels across the entire web. The spider does not have to be sitting at the center to know that something has arrived. Wherever it is, the structure tells it, and it goes.

A nervous system does much of what a web does. It carries signals in both directions, from the brain out to the body and from the body back to the brain, which is exactly why it comes so close. Here is where it breaks, and I mean that word literally. Damage a single nerve in the upper arm, and the line goes dead. The brain can no longer reach the hand, and the hand can no longer reach the brain, because there was only ever one pathway between them, and now it is severed. A web does not fail that way. Lose a strand and the web holds its shape, because it is so interconnected that the strands around the gap carry the load, and the signal keeps moving. That is not a small difference. That is the whole reason I lead this way.

How a web actually gets built

I want to slow down on something people skip, because it is the part that turns a metaphor into a method. A spider does not build at random. It builds in a precise order, and the order is instructive.

First comes the bridge. The spider releases a single thread and lets the wind carry it until it catches on something solid. Once it holds, the spider anchors it, and that first line becomes the foundation for everything else. Then come the frame and the spokes. The spider drops a line from the middle of that bridge and anchors it below, forming a Y, and from there it builds the outer frame and runs the radial threads outward from the center like the spokes of a wheel. Then comes the scaffolding, a wide temporary spiral of non-sticky silk that holds the frame steady while the real work happens. And last comes the trap itself, the sticky spiral, laid from the outer edge inward. As the spider lays sticky silk, it eats the temporary scaffolding beneath it because the scaffolding has done its job. Most spiders finish the whole structure in under an hour.

Read that as a leader, and it is a blueprint. You find your anchor points first, the places where the work is tied to something solid, and you secure them before anything else. You build the frame before you build the fine detail. You allow yourself temporary scaffolding, the structures you need to get started, and fully intend to take them down once the real thing holds. And you build all of it on purpose. Intentionally. Not one thread of it is accidental.

What a web knows

A spider senses movement anywhere on the web. I do not love the word "disturbance" for this, because it sounds like something has gone wrong, and most of what moves through a healthy web is simply information. A leader needs to know what is moving, the good and the difficult, both, and needs to be able to go where the action is.

I built a network of people within every organization I led so that I could see a problem before it grew large enough to cause damage, and so that I could catch the good just as quickly. I said it plainly to the people I worked with: a chief title does not mean I do this alone. We all have a job in building a culture where every person knows they belong, and I need your help because I cannot be everywhere at once. Someone would raise a hand somewhere on the web, and the structure would carry it, and I would go. Sometimes it was a real problem. Sometimes it was something worth celebrating, because I told the organization that when something good happens in our culture, we name it and we hold it up. A web that only ever carries problems teaches people to go quiet. We have to move the successes too, so people can see what good looks like and reach for it.

What one strand cannot carry

I once watched a web do the exact thing I now build organizations to do. I was looking at the spiders in my mom's dogwood tree when the wind picked up, and one of the connection points tore loose from the tree. Part of the web dropped. It did not bring the rest of it down. The spider went right to the torn section and began to repair it, and here is the part I have never been able to forget. While the spider was repairing the damage, a fly flew into another part of the web and was caught. The structure was handling a crisis and doing its job at the very same time. One section is under repair. Another section was still catching exactly what the whole thing had been built to catch.

That is what an organization can do when it is built as a web instead of a tower. When one part is in crisis, the rest does not stop. It does not even slow down to watch. It keeps producing, keeps seizing opportunities, keeps carrying the mission forward while the damaged part is rebuilt. A structure that can only do one thing at a time and has to halt everything to deal with a single failure is not resilient. It is brittle. The web is resilient because the work is distributed, and distributed work does not depend on any single strand remaining intact.

This is also why I am careful with the idea of bending without breaking. People say it as though it is a personal virtue, as though the strong leader is the one flexible enough to bend under pressure and spring back on their own. That has never been my experience. On my own, if I bend far enough, I do not spring back. I lose my balance, and I fall. What kept me standing through the hardest seasons was never my own flexibility. It was that the people around me were strong, and we were holding one another, so I could bend far past the point my own balance would ever allow, because everyone else was holding me up. A leader's resilience, in a web, is borrowed from the people. It is not a solo trait. It is a shared one.

Where I actually sit

If you are paying close attention, you are about to catch me in a contradiction. A real spider sits at the center of its web. So when I tell you a web has no hierarchy, you have every right to stop me and ask where I actually sit. Am I at the center, above everyone, quietly running the very hierarchy I claim to reject? It is a fair question, and it deserves a direct answer.

Yes, the spider sits at the center. It does not stay there. It moves. It investigates. Sometimes what landed on the web is not a bug at all; it is a leaf, and the work is to clear away what does not serve. And while the spider is off doing that, if something lands on the far side of the web, it knows, because the web carries the signal even when the spider is nowhere near the middle. That is the freedom of it. The leader does not have to sit at the center to do the job.

I worked in an organization with a fully open floor plan, where even the CEO had no formal office. He sat out on the floor like everyone else because he saw the people around him as equals, and he did not just sit there. He walked the floor constantly, out among people, talking with them, close enough that anyone could reach him. Because he moved that way, everyone always knew where to find him. If you could not see him yourself, the person nearest you had seen him a minute ago and could point you to him. Nobody had to route a question up a chain and wait for it to come back down. That is the web. The signal reaches everyone, and it reaches them without a filter.

The air conditioner

Let me give you the clearest thing the web ever did through me, and notice as I tell it that I held no formal authority over any of it.

I travel to our locations around the country to talk with our frontline staff and learn what is actually happening on the ground, so I can carry it back to the leaders who can act. I was at one of our flagship locations for a routine visit. I was there to ask employees about belonging, about where they knew they belonged and where they did not, about what the organization could do to signal to them that they were wanted. I asked my questions. And the answer came back from nearly every person in the building, the same answer. Christopher, can you get the air conditioner fixed? It is really hot in here.

The air conditioner had been broken for a long time. I told them the truth. I was not sure what I could do about it. However, I was going to ask the questions anyway, because I wanted them to see something. Even when I did not know whether I could fix a thing, I would still choose to act. Deciding to move while unsure was the whole signal.

So I started with the person directly responsible for that building, and I asked why the air conditioner had gone unfixed for so long. They knew why. The work orders had been coming in for months, and they had been sitting on every one of them. What I got was the runaround. I said, plainly, that this was not acceptable. We were asking these employees to help us build a healthy culture. They had sent request after request, and each one had gone nowhere. What they had learned was that nobody was listening. So I did not stop there. I carried the signal up to the leader above that person, someone who could act and would. I had nothing to do with facilities. I was the belonging person. What I had was a place on the web close enough to the center that I knew exactly who to reach when the first node refused to move. The signal was never lost. It was being held shut by the one person whose job was to carry it. So I routed around them and sent it somewhere it would be heard. We had the air conditioner fixed in about two weeks.

I went back a few months later. Before I could ask a single question, the employees came to me. They thanked me for the air conditioner, and they told me what those months had been like: hot, tired, worn down, day after day. And they told me the fix was the first time they had actually known somebody had listened. Let me be careful with the attribution here, because it matters. The idea that a broken air conditioner might not look like a cultural problem is mine, not theirs. What they named was simpler and truer. For a long time, nobody had heard them. Then somebody did. Fixing a machine gave those people their humanity back, because underneath the machine, somebody had finally listened. That is what a web is for. Not the air conditioner. Listening to the air conditioner was made possible.

When the work outran me

I have to show you a time the web did something no top-down structure could have done, and it is not a comfortable story, because it is about the weeks I found out I had cancer.

It moved fast. Weeks from the diagnosis to the surgery, and it landed during one of the busiest stretches of our year. There was almost no time to prepare the organization for my absence. And it held. It held because of how the work had been built. Everyone already knew the plan, their piece of it, and mine. When I handed my responsibilities off, people knew what to do, and I did not even have to say a good deal of it, because they already understood the whole shape of what we were doing. I was pulled out of the center of the plan, and the work kept moving without me. I do not know that it would have, had I built the thing as a pyramid. On an org chart, the only formal line between two teams runs up to a shared boss and back down again. We tell people to follow the hierarchy. Go to your manager. We seldom say go to the person actually doing the work.

I know exactly what that costs, because I have watched it cost. In one organization, a colleague sat across the hall from me on the learning and development team, and the two of us found a real fix for a breakdown in our learning strategy. A good fix. It never happened. Our bosses did not like each other, their egos won, and two people who could have solved a real problem were kept from solving it by a hierarchy that put a personal grievance directly in the path of good work. In a web, we would have built it and then told the whole organization what we had done.

The strand I refused to look at

Now the harder story, the one where I am the problem, because self-implication is the only honest way I know to write about leadership.

You might expect me to confess here to pulling rank. I am going to answer it the other way first, because the truth is stranger. My hardest failure with the web was a decision I kept refusing to make.

I had a person on my team I trusted completely, without question. As the team grew, I handed this person projects I used to run myself, and with them, the relationships those projects were part of. I was so sure of the person that I stopped watching. I went off to carry my own load, and I assumed the strain I could sense building in the organization was coming from other teams. I defended this person. Repeatedly. And the whole time, the web was doing exactly what it was designed to do. It refused to let one weak strand collapse the structure, so it quietly moved the load onto everyone around that strand. That redistribution was the harm. People began to believe that because I allowed it, I condoned it. The relationships I had built with real care started to fray because the person now holding them was not carrying them, and I was not paying attention because I trusted them.

When the signals from the rest of the web finally reached me clearly, I understood that the problem had never been the other teams. It was the one strand I had refused to look at. I had two hard things to do. I had to let the person go, and I did not do it as punishment. I did it as a signal the organization needed to see: this is not acceptable here. And I had to apologize, in person, to the colleagues whose trust I had lost by not paying attention. The repair was not a speech. It was bringing in someone who actually did the job, and then demonstrating, over time and through what I did rather than what I said, that I had heard them. A torn web gets rebuilt one strand at a time. There is no faster way.

There was also a time I did the opposite. I reached for rank when I should have trusted a strand. A manager was leading a project, and decisions made inside it landed on my department in a way I did not want. Instead of using the communication channel our organization had agreed to, I went over her head, to the next layer of leadership, because I was a director and she was a manager. On the org chart, I held more power. On that project, she was the leader, and I undercut her. I tell the full version of that story in the chapter on a just society, where the repair she asked of me does its real work. Here is what it means for the web. The moment I use my place on the chart to reach past a strand that is doing its job, I am telling the entire structure that the chart is the real thing and the web is only decoration. Trust does not survive that message. I had to rebuild what I broke.

You may have noticed that this story rhymes with “air conditioner,” and I would rather name it than hope you slide past it. In both, I went around the person standing in the formal path. In the air conditioner story, I was right too. Here, I was wrong too. That first person had become a dead node. They were sitting on the signal, refusing to carry what it was their job to carry, so I rerouted around the blockage to someone who would move it. The manager was not a dead node. She was a living strand, doing her work and doing it well, and I overrode her anyway, because the org chart told me I could. The first served the mission. The second served me. The difference is the whole point, and it is worth saying plainly.

A web reroutes around a signal that is being blocked. Pulling rank overrides a strand that is carrying the load just fine.

What is genuinely hard about it

People assume this way of leading is slower. It is not. It is faster, and that is exactly the trap. When communication moves quickly, people begin to expect that decisions will move just as quickly, and some decisions need time to sit with the information before they are made well. So you have to say out loud what the system is actually for. It is built for the speed of communication, not for the speed of every decision. You give people a clear frame of freedom: the decisions they are trusted to make on their own, and the decisions that need to move closer to the center, where a higher level of accountability lives.

There is a second hard part. People expect total transparency, every hour of every day, and I do not promise transparency. I promise translucency. Light comes through. The full picture does not, at times. Some information cannot be shared, a personnel matter the law protects, a decision that would do real harm if it traveled before its time. The honesty is in naming that up front, so that no one mistakes translucency for a locked door.

And one more thing, because it is a real misunderstanding. A web does not mean everyone decides everything. It never did. A web means the leader can gather what they need from any point on the structure before they decide. Every junction is a person who holds decisions of their own. A cashier can hand an unhappy customer a discount without calling anyone. When that cashier hits something they cannot solve, they know how to pull the next person in, even a manager at another location, if their own is out for the day, so they are never left stuck. I have stood at a counter and heard that my manager is not available. Some manager is available, maybe not in that building. The web is what lets a person reach them. Some moments call for one clear voice making a fast call, and I have lived plenty of them. The web is not the enemy of that. The web is what puts the full picture in front of the person who has to make the call.

Where the belonging actually happens

I can tell you the exact place a person on a web-led team comes to know they belong, and it is not the moment someone tells them they matter. It is the moment they watch the information they sent to the center change what the organization actually decided. Not their way, every time. That was never the promise. The promise is that their judgment is in the room, shaping the outcome, even an outcome they would not have chosen for themselves. When a person can see their own contribution at work in a decision, they know their value is real, not decorative. That knowing is belonging.

People do not come to know they belong because they are told they matter. They come to know it when they watch what they sent toward the center change what the organization decided.

This is why I think of spider web leadership as inclusion made structural. In the Belonging Formula, inclusion is the behavior that nurtures a culture where every person is empowered to contribute. The web is that behavior built directly into the architecture. We all do different work toward one mission. A web exists to carry a signal to where it needs to go. When every person is tied directly to the mission, each person carries the responsibility to keep everyone else aligned with the organization’s direction. Inclusion stops being a value painted on a wall. It becomes the shape of the thing.

How this chapter connects

I want to be clear about how this chapter sits with the rest of how I lead, because the web makes a demand on its own author. This chapter is not the foundation on which the others are built. It is not the top of a stack, either. A web has no such thing. The moment I place the other chapters underneath this one and call them dependents, I have drawn a pyramid and labeled it a web. So I will not. Mentorship, sponsorship, leading with authenticity, courageous leadership, the way I disrupt on purpose, those are not chapters that answer to this one. They are strands that connect to it. The web is the shape this whole section moves in. It is not the ceiling the section hangs from.

And this is not the same chapter as “Feed NYour network, Feed SYour soul,” even though both feature a picture of a web. That chapter is about the people outside your team, the ones you pour into and who pour back into you when you need it. This chapter is about how to lead the people on your team. One is the network that holds you. The other is the structure you build. Different instruments. Not rivals.

You do not need a title.

You do not need to be anyone's boss to lead like a web. Everyone knows the mission. Everyone has a job. Some of us carry more responsibility for more people. Authority in a web does not come from a supervisory line drawn on a chart. It comes from where you sit relative to the signal. The air conditioner is the whole proof. I held no formal authority over facilities, none at all, and the problem got solved in two weeks, because I sat close enough to the center to know who could act, and I carried the signal to them directly.

I will be honest about the first move, because a reader deserves the truth more than a tidy technique. The hardest part of leading this way is that I hold this philosophy, while most people around me do not. I keep leading like a web inside organizations built as hierarchies, and it creates friction. Operations leaders get uncomfortable when the belonging person shows up talking directly to their frontline, because I keep surfacing what was never traveling up the chain. The air conditioner is only one example of that. So the first move is not a method. It is a decision. You lead this way inside the part of the world you are responsible for, and you accept that it may rub, because your fellow leaders are not wired for it yet. You do it anyway. It is the reason my people went above and beyond, again and again. They were treated as equals with different jobs, never as people beneath me, and they knew the difference.

If you take one thing from this chapter, take this. Treat everyone as a human. You may hold more formal authority than the person beside you. That does not place you above them, nor does it make you better than them. I have held a great deal of formal authority in my career, and I have worked to use every bit of it for good and to treat every single person as a fellow human being. And remember where the brand actually lives. The people on the front lines are not below the C-suite. They may matter more. Remove the executives for a day, and the work still happens. Remove the frontline, and there is nothing left for an executive to lead. The people touching your customers every day are the ones who make or break what you have built. Lead like you know that.

Reflection invitation

Spider web leadership is not a structure you install. It is a way of moving through the people you lead. These questions are here to turn the chapter toward your own web.

Where in your organization does a signal have to climb a ladder before it reaches the person who could act on it?

Find one—a complaint, an idea, a warning, a success that never travels. Then shorten the distance between where it starts and where it can be heard.

Think of two people you lead. If you lead them the same way, one of them is being led wrong. What does each one actually need?

A web is made of individual strands, each anchored to a different point. Name the anchor for each person, and lead to it.

Where have you reached for rank when you should have trusted a strand?

Name the moment plainly. Name the trust it cost. Then name the repair you still owe, and rebuild that strand.

We do not arrive. We evolve.