Why Your Team Falls Apart: The Load Path Principle from J.E. Gordon
J.E. Gordon wrote Structures: Or Why Things Don't Fall Down for engineers, but he buried an insight in those pages that applies directly to your career, your team, and every system you touch. It's not about formulas. It's about seeing failure before it happens.
The insight is this: things don't fall down because forces have a path to travel. When that path breaks, collapses are inevitable. Not mysterious. Not bad luck. Predictable.
Most people ignore this principle when they leave the construction site. They shouldn't.
The Single Biggest Lesson: Load Paths Determine Survival
Gordon's central thesis is deceptively simple: every structure—from a medieval arch to a human bone to an airline operation—survives because forces that land on it find an ordered route toward a stable foundation. When that route is interrupted, blocked, or undersized, failure follows.
Here's the part nobody talks about: the weakest point in the load path is where everything breaks, regardless of how strong everything else is.
A bridge with massive steel cables but a single corroded bolt at the joint fails at the bolt. A team with talented people but a single overwhelmed manager who can't distribute responsibility fails when that manager breaks. An organization with excellent processes but no clear decision authority fails when decisions get stuck in ambiguity.
Gordon called this principle the "weakest link," but he meant something precise: not the weakest person or component in absolute terms, but the weakest point in the continuous path where all the force has to flow.
This changes everything about how you diagnose problems.
Why Your Current Diagnosis Is Probably Wrong
When a system fails—a project derails, a team burns out, revenue drops—the first instinct is to attack the most obvious symptom or strengthen the most visible component.
Gordon teaches a different approach: trace the load.
If a team is failing, don't immediately hire better people or mandate longer hours. Ask: What pressure is this system supposed to handle? (Revenue targets, customer deadlines, quality standards—identify the actual load.) Where does that pressure travel once it enters the organization? (Through which people, which processes, which junctures?) And critically: where does the entire load have to pass through a single, narrow point?
That narrow point is your structure's load path. If it's a single executive bottleneck, the system fails when that executive can't keep up. If it's a single database that everyone queries, the system fails when that database slows down. If it's one person who knows how to do something critical, the system fails if that person gets sick.
The system doesn't fail because the load is too big. It fails because there's only one route for the load to take, and that route is too narrow.
How to Apply This to Your Week: A Three-Step Protocol
Step 1: Draw Your Load Map (Today, 20 minutes)
Take a piece of paper and sketch your team, project, or organization as a system. Write down:
- The load: What pressure does this system bear? (customer demand, project deadlines, operational output, decision volume)
- The path: Draw arrows showing where that pressure flows. Who or what does it hit first? Where does it travel next? Where does it concentrate?
- The junction: Circle every point where multiple loads converge into a single channel. These are your potential failure points.
Be honest. Most teams have one person where everything funnels—decisions, approvals, knowledge, accountability. If you can't find one, you're probably in denial about how your system actually works, not that it doesn't exist.
Step 2: Measure the Actual Load on Your Narrowest Point (Tomorrow, 30 minutes)
Take the load path with the smallest cross-section (the person or process handling the most compressed work) and quantify what they actually carry:
- How many decisions per day do they approve?
- How many people report to them or depend on their output?
- How many hours per week do they spend on that particular function?
- What happens if they're absent for one week?
Now ask: is this person designed, equipped, or authorized to handle this volume? Be specific. "I think they're overwhelmed" is not a diagnosis. "They're handling approvals for 47 people in 4 hours per week" is a diagnosis.
Step 3: Redesign That Single Bottleneck (This Week, specific action)
Don't add more capacity. Redesign the path. Gordon's structural principle is that changing geometry and distribution matters more than adding more material.
Your options:
- Widen the path: Distribute the decision authority to three people instead of one. Add parallel processes instead of a serial bottleneck.
- Reduce the load hitting that point: Filter decisions before they reach the bottleneck. Pre-approve whole categories. Delegate authority down.
- Add intermediate support: Don't go from zero to full load path redesign. Add a junior person or process that handles 30% of the load, directing it around the bottleneck.
- Change the material: Sometimes the bottleneck isn't the person, it's the tool they use. Better software, better templates, better information access can increase the throughput that a single person can handle.
Pick one. Commit to it this week. Not next quarter. This week.
The Elasticity Principle: Breathing Room Is Structural Strength
Gordon made another observation that most leaders miss: solid materials don't actually hold things up through rigidity. They hold things up through elasticity—the ability to deform slightly under load and then recover.
A beam that bends a little under weight is safer than one that seems rigid but has no give. The slight deformation distributes the stress. Rigidity concentrates it.
Apply this to your team: a system that operates at 100% capacity with zero margin breaks catastrophically when load increases by 10%. A system with 20-30% breathing room can absorb shocks, redistribute stress, and recover.
When you reduce the bottleneck load from crushing to manageable, you're not just solving this week's problem. You're building in the elasticity that lets your structure survive the unexpected.
Why This Matters Right Now
Most people understand that systems can fail. Few understand that failures are not accidents—they're consequences of specific, visible design flaws that you can diagnose and fix without reorganizing everything.
Gordon spent his career teaching engineers to see that difference. He showed them that medieval cathedrals didn't collapse by mystery—they collapsed because someone didn't understand how forces travel. Modern airplanes don't stay in the air because they're made of strong materials; they stay up because every force has a clear path to the fuselage and wings, down through the landing gear to the ground.
The same is true for your organization. Your people don't burn out because they lack resilience. They burn out because you've designed a structure where all the load funnels through one person, one decision point, one process that has no capacity to handle it.
You can see it. You can measure it. You can fix it. Not in six months. This week.
Start with the drawing. Trace the load. Find where it narrows. That's where you'll find the reason things are falling apart. That's where you redesign.
Download BOOKOS and listen to the full audio summary: https://bookosapp.com