You are the beam
The team holds because of you. That's the design flaw.
Sunday night. 9:23 pm.
She’s at the kitchen table. The laptop is open. Tomorrow’s calendar is on the screen, though she’s not really reading it. The mug next to her has gone cold. Somewhere down the hall, someone she loves is asleep. The dishwasher has stopped. The house is quiet. It has been for a while.
Her cursor is hovering over a 30-minute slot. Weekly 1-on-1 with her senior team member. She extended it by 15 minutes this morning, in case her team member needs the time. Her team member usually does.
She’s done that for four people this week.
Somewhere in the last two years, her week turned into this. The project she’s leading is going fine. Last quarter’s review said “high performer.” Her own 1-on-1 with her manager was cut from 30 minutes to 15 minutes a month ago, and she hasn’t found a way to mention it without sounding like she’s complaining. She’s the person who rewrote the onboarding document on a weekend because it was broken. She’s the person who checked on the junior team member when their partner moved out. She’s the person who organised the team dinner because someone had to.
She’s the person this team runs on.
Last quarter’s review went like this. Her skip-level asked the simple question that gets asked in all these conversations. What did she deliver this quarter? She named the project. She named the metrics. She named the thing that shipped.
She didn’t name the Tuesday afternoon she spent unblocking a designer who was stuck because two product managers had given her conflicting specs. She didn’t name the Thursday morning coffee where she realised her team lead was about to resign, and spent 40 minutes talking him through it instead of writing the brief she had promised her manager. She didn’t name the weekly direct message she has been running with the new hire, who is struggling and will not say so in the team meeting.
Those conversations were the air the project was breathing.
Her manager does not measure air.
In 1961, a journalist named Jane Jacobs walked a block in New York and made an observation that would eventually change urban planning.
Jacobs had no credentials in the field. She lived in Greenwich Village, walked her daughter to school, and bought bread from the shop on her corner. What she noticed was this. The city blocks that worked shared one ingredient: the most uncounted human maintenance.
The shopkeeper who watched the kids cross the road. The old man at his stoop who nodded at strangers. The woman who swept the footpath in front of her building because that was what people did.
None of it was a job. None of it was in anyone’s brief. All of it was what held the block together.
Jacobs called it “eyes on the street.” She wrote The Death and Life of Great American Cities to argue something the planners of her era refused to believe. Demolish the casual infrastructure of a place, and the neighbourhood fails quickly. The maintenance was real. It was just invisible.
The same physics runs through her team. Sixty years after Jacobs, an engineer named Tanya Reilly gave the workplace version a name: glue work. Same shape, different building.
Load-bearing work doesn’t announce itself. The shopkeeper held the block together, uncounted, until she retired, and the crime rate on that block climbed. The senior team member holds the team together, uncounted, until she burns out and two projects stall in a month.
The evidence that a piece of work is structural is what breaks when it stops.
She’s doing load-bearing work in a system architected as if the load did not exist.
Here is the question I want you to carry into Monday morning.
If I stopped doing the work that sits outside my review, what would collapse first?
Don’t filter. Don’t be fair. Write down the first 5 things that come to mind, on paper, in 10 minutes. That list is the audit. You will know by the fifth item how load-bearing you actually are.
The list usually looks like this. The onboarding process only works because one person keeps maintaining it by hand. The junior engineer who keeps their job because someone is coaching them out of hours. The skip-level trust that only holds because someone is doing quiet hallway diplomacy between two teams that don’t like each other. The cross-team decision that gets made because someone walks the notes from one meeting to the next, before the next one starts.
You absorbed this work slowly, over the years, because the alternative was watching something break, and you are the kind of person who cannot watch something break.
That is the story of how you got here.
Three moves. Pick the one you’ll actually run.
Move one. Make it visible.
Write down what you did last quarter that does not appear on your deliverables list. Time-cost each item, honestly. Dollar-cost the items you can. Put the list in your next performance review document using the same font size as the project work. Send it to your manager a week before the conversation so they have time to read it before the conversation.
The point is to make the work countable. A manager cannot defend work they cannot see. Your skip-level cannot fight for resources for a role they cannot describe. Visibility is the prerequisite for protection.
Move two. Make it someone else’s.
Pick the two pieces of glue work that are costing you the most time each week. Pick a specific person who should own each one. Transfer them cleanly, in a single 20-minute meeting for each handover. Then walk away.
Don’t hover. Don’t rescue. Don’t send the follow-up message that says, “just wanted to check in, let me know if you need anything.” The handover is the work. If the new owner does the job at 60% of how you did it, the system is still better off than it would be if you continue to burn out doing it at 100%.
Move three. Redesign the beam.
If the work is genuinely structural, and nobody on your team can carry it, and you cannot hand it off, then the structure is wrong. You are the diagnostic. The fix is architectural.
Hal Moore, the American battalion commander at Ia Drang, wrote one line about command that is worth borrowing here.
“If you discover subordinates who are uniquely talented, give them the tough jobs and mentor them. It’s your duty to help them develop their skills and to learn.”
A system that depends on any one person for its continuity is a fragile system. A single point of failure will eventually fail. This is a structural property. The person at the point of failure makes the design flaw visible. The glue work is your single point of failure. The team is the system. And the system is fragile in exactly the shape of you.
You’ve probably told this to your direct reports. You’ve probably coached them to delegate, to build bench strength, to develop their own successors. You’ve probably written it into their development plans.
You haven’t applied it to yourself.
The glue work is the tough job Moore was describing: hard, unstructured, judgment-heavy, with an invisible pay-off. You’ve been holding it because you’re good at it. That is exactly why it is the work you should be handing to the next person under you, with coaching, with air cover, and with the authority to do it their way. Hand it off because building people who can carry work like that is what a leader is actually for.
Redesigning the beam is building the team you’ve been telling your reports to build.
This is also a conversation your manager’s manager needs to be in. That conversation is about whether a team should depend on one person to absorb uncounted load. It has nothing to do with whether you are coping or whether you should see the employee assistance psychologist. A team that depends on a single person to absorb uncounted load is a team with a design flaw. The fix is a role design, a process change, or a headcount decision, depending on where the load is concentrated.
That conversation is the only one that ends it.
Glue work costs you more than hours. It costs you by disguising itself as a character trait.
Your manager calls you generous. Your peers call you a team player. Someone told you, probably years ago, that you were “good at people.” The compliments are sincere. They are describing the load you are carrying with words that make it sound like a gift.
The work is real. The load is real. Calling it generosity doesn’t change what it costs.
Load that isn’t measured still weighs what it weighs.
You’ve been holding up a building that was never planned to be held up by one person. The exhaustion you’re feeling at the kitchen table on a Sunday night has a physics to it. It’s the sound of a load-bearing beam under sustained stress. The beam is real. The weight is real. The design is wrong.
Jacobs’ block held until the shopkeeper retired. Then it didn’t.
The building stands.
The blueprint is the problem.
I built The Still Architect’s Energy Diagnostic for the person at the kitchen table at 9:23 on a Sunday night. A 5-minute structural assessment of the load that falls outside your review. It shows you the beam. Take the Diagnostic.
If you’ve already taken it and you know which beam is breaking, The Refactor is the 6-week walk-through of Move 3. Redesigning the beam, with an AI partner that holds the work in place between Sunday nights. Explore The Refactor.