Build Structures That Hold Under Weight:Arches' Stone Spans

Your team isn't breaking because they're weak.

They're breaking because the structure underneath them was never designed for the weight it's carrying.

Here's what most leaders believe:

So you carry more.

You absorb more.

You become the single point holding everything together.

And when things crack... you blame them.

Or worse... you blame yourself.

But the team was never the problem.

The architecture was.

There are landscapes that make you question physics.

Arches National Park is one of them.

You walk beneath these massive stone structures and your brain can't make sense of them.

Delicate Arch towering alone on a ridge.

Landscape Arch stretching impossibly thin.

Double Arch intersecting layers of gravity and geometry.

Balanced rocks that look like they should have fallen centuries ago.

And they're still standing.

Not because they're lucky.

Not because they're light.

Not because they avoid pressure.

The weight is part of what holds them together.

Scientists who tested sandstone found that rock under load wears away more slowly, because the weight locks the grains together. The rock carrying nothing crumbles first.

The arch isn't designed. It's what's left after everything that wasn't carrying weight wore away.

Even then, it doesn't last forever. Every arch out here will fall someday. Wall Arch, one of the largest in the park, came down one night in 2008.

But while they stand, they stand because the weight is shared across the curve.

I stood under Double Arch, neck craned back, staring at how much stone was overhead.

Tons of rock, overhead.

And the structure made it look... effortless.

No tension.

Just balance.

And a thought hit me harder than I expected.

Straight up. Linear. Everything depending on one central point.

Me.

I looked at that arch and thought...

“

What if the answer was never about carrying more weight? What if it was about building something that distributes it?

How much of the pressure I feel as a leader is because I'm trying to be a single pillar instead of building an arch?

You've been the pillar.

The meeting where everyone looked at you for the answer and you gave one... even though three people in the room could've handled it.

The project you took back because delegating felt riskier than just doing it yourself at 10 PM.

The decision you made alone because asking for input felt like admitting you didn't know.

Absorbed someone else's stress because you didn't want to add to theirs.

Held the tension between two team members instead of building a system that addressed it.

Said yes to the extra responsibility because saying no felt like failing.

And then sat in the parking lot after work wondering how much longer you can do this.

Your kids got the leftovers of your energy.

Your partner got the version of you that had nothing left.

Your health got whatever you could squeeze between the meetings and the fires.

And then wondered why you're the one cracking.

You're not overwhelmed because you're incapable.

You're overwhelmed because the architecture of your leadership was never built for what it's carrying.

This is the part that rewired how I think about leadership.

An arch doesn't fight pressure.

It distributes it.

The weight that would crush a straight beam becomes manageable when it spreads across the curve.

The stone isn't stronger than a pillar. The shape is smarter.

Most leaders spend years trying to be stronger.

Working longer. Pushing harder. Absorbing more.

Thinking that if they could just handle more weight, everything would hold.

It doesn't.

Because strength without structure is just delayed collapse.

Your team member who keeps missing deadlines?

He's not lazy. He's operating inside a structure that has no clear expectations, no defined handoffs, and no accountability rhythm.

He's standing under a single pillar waiting for you to tell him what to do.

“

That's a design problem. Not a people problem.

Think about your last team meeting.

How many decisions were waiting for you that someone else could have owned?

How many questions came to you that should've had answers built into the system?

That's not a team problem. That's architecture without a playbook.

When did you stop designing the structure... and start just holding up the weight?

This one hurts.

I know.

Because it's easier to believe the team is the issue.

Easier to think: if they just cared more, tried harder, stepped up...

But they're not fragile.

Your systems are.

Picture an executive director who's doing everyone's job plus her own.

Exhausted. Resentful. Convinced her team can't handle anything.

The team isn't the problem.

The architecture is.

No clear roles. No defined expectations. No playbook for how decisions get made.

Everything runs through her. Every question. Every approval. Every next step.

She's the pillar.

And the pillar is cracking.

Now picture her building a playbook with clear expectations and strengths-based roles...

Her team starts owning the work.

Not because they suddenly got motivated.

Because the architecture finally supports them.

Arches don't hold weight by being tougher.

They hold weight by spreading it across the entire curve.

“

Every part of the curve carries a piece. No single point carries it all.

Your quiet employee who stopped volunteering for projects?

She didn't lose her drive. She lost faith in the structure.

She watched the last three initiatives collapse because everything depended on one person.

What would your team look like if the architecture actually held?

This is the shift.

You don't need to be a stronger pillar.

You need to stop being the only thing holding it up.

The arch at Arches doesn't try harder.

It doesn't grit its way through the pressure.

It doesn't absorb more than its shape can hold.

The architecture does the work.

The curve. The distribution. The shape.

That's what a playbook does for your leadership.

Clear decision pathways so everything doesn't funnel through you.

Shared ownership so the weight spreads across the team.

Defined expectations so people know what success looks like without asking you.

Repeatable rhythms so your culture doesn't reset every Monday.

A lot of leaders learn this the hard way.

They're the approval bottleneck. The emotional absorber. The one holding it all.

And they call that leadership.

It isn't.

It's architecture failure.

The moment they start building the playbook... defining who owns what, how decisions get made, what success actually looks like...

The weight doesn't disappear.

It distributes.

Across the team. Across the system. Across the curve.

And for the first time in years, they can breathe.

Your strongest performer... the one who always delivers?

She's carrying weight that should be distributed across the whole team.

And she's one bad week away from walking out the door.

“

What if the most powerful thing you could build... isn't your endurance, but your architecture?

Your best people start looking for teams with better architecture.

Your decisions get bottlenecked because everything runs through one point.

Your culture stays inconsistent because the systems depend on your mood and energy.

Your team stays dependent because the structure taught them to wait for you.

Your body keeps the score of every ounce of weight you're carrying alone.

And you end each week more exhausted... wondering why nothing changes.

But when you build the arch?

When the weight distributes across the team?

When the architecture holds instead of one person holding?

Everything shifts.

You wanted to build something.

Something that lasts. Something that develops people. Something bigger than one person holding it all together.

And somewhere along the way... carrying became the identity.

The weight became the proof that you mattered.

And the breaking became normal.

It doesn't have to be.

Arches reminded me of something I need to keep relearning:

“

The strongest structures aren't the ones that carry the most weight. They're the ones shaped to distribute it.

Your team isn't the problem.

The absence of a playbook is.

And that's actually good news... because architecture can be redesigned.

Think about one place where your leadership feels heavy or fragile right now.

Now ask yourself:

“

Is this a people problem... or an architecture problem?

Identify one system, one rhythm, or one expectation you can redesign this week so the weight gets distributed instead of absorbed.

Write it down. The system. The change. The date.

Because if the architecture only lives in your head... you're still the pillar.