The Organizational Gravity Podcast — Episode 1: The Ones Holding It Together
You saw it coming before anyone else did. You said so. And by the end of the meeting, somehow you were the problem, not the thing you pointed at.
This first episode is for you. For the people who hold organizations together without the authority to run them, and get taught, one meeting at a time, to go quiet.
It's about why that happens. It gives you two names for what you've been up against all these years, Organizational Gravity and Human Middleware. And it introduces a guy named Dave, whose spreadsheet turned out to be running his whole company, right up until leadership decided to automate it. Dave's story is really a story about how the work survives AI, and how the people who understand it survive too.
If you've ever been the one who saw it coming, press play.
A quick note: I added the full audio, but the whole transcript is below too, so you can read it if that's easier or more accessible for you.
If this sounds like you, or like someone on your team, forward it to them.
And here's the standing invitation for this show. If you're the Dave in your building, or you're fighting a gravity nobody around you will name, I want to hear about it. Just reply to this email. I'll protect you, no company names, first names or none, and nothing goes out without your okay.
Subscribe to get every episode and essay, written for the people holding it together.
— Gabe
Transcript
You've been in the meeting where the date was set before anyone asked how long the work would actually take.
Where the estimate got sharpened until it won the deal, and then you were the one held to a number you never agreed to. Where the status stayed green because green was the only color anyone upstairs wanted to see. You're the project manager, the planner, the estimator, the one in supply chain who can see the lead time coming months before it lands. You're the director who put it in the risk report, and the VP who said it out loud in the room, and watched it change nothing.
You saw it. You said so. And somehow, by the end of the meeting, you weren't the person who caught the problem. You'd become the problem.
I've watched this meeting for twenty years, and here's what I keep seeing. The person who speaks up is rarely making it up. They've usually caught something real, just a little before anyone else is ready to hear it. And that's the whole trap. Early and difficult look the same from across a conference table.
So here's how it tends to go. The thing you flagged comes true, more or less on schedule. And by then, nobody remembers that you called it. What they remember is that you were hard to work with that day. So the next time you see something coming, you think twice about saying it out loud.
And here's what really gets me. You did all of it without the authority to make any of it easier. No title that made people listen, no power to overrule a bad call. You had to talk a skeptical manager into it, and move a team you couldn't give a single order to.
And you did it anyway. Because you actually care about the work.
If that's you, then welcome to the Organizational Gravity podcast. I'm Gabe Rybicki, your host, and your confidant in a fight you've mostly been having alone.
Those meetings train you to go quiet. I want to do the opposite. Give you the language for what you're actually up against, the stories of people who found a way through it, and a reason to keep speaking up.
Stay with me.
Let me be specific about who I'm talking to.
Not only the person at the top of the org chart. The person a level or two down who has to make things better anyway. You're asked to align stakeholders you have no authority over. To fix a process, but not allowed to touch the thing that's actually broken. To own the outcome with none of the control.
I've sat in the leader's chair too, so let me tell you a secret from it. A lot of the real work of change doesn't happen there. It happens with you. The seat you're in is where organizations actually turn, and it's the seat almost nobody makes a show for.
So I am.
There's a subtle power in naming things, and I want to give you that power. Because once you can name a thing, it stops being your fault and starts being a problem you can point at. So here are two names for things you've felt for years, and maybe never had the words for.
The first one is Organizational Gravity.
It's the reason your company is harder to change every year. Organizations pull weight toward themselves. A little at a time. A new process here, an exception there, another system, another approval, another report someone needs. Nobody decides to make it heavier. It just accumulates faster than anyone stops to question it. That's gravity. It's constant, it's cumulative, and there's no villain anywhere in it. Which is exactly why willpower can't fix it. You cannot try hard enough to escape a force that never stops pulling.
The second one is the one I really want you to hear. Human Middleware.
Middleware is the software that sits between two systems that were never designed to talk to each other, quietly translating so they can work. And in most companies, that software is a person. It's you. You're the one reconciling the numbers from two tools that don't connect. Rebuilding the context that got dropped in a handoff. Remembering the rule nobody wrote down. Translating the same thing between two departments for the tenth time.
That work is invisible, it's exhausting, and it builds nothing, because it only exists to cover for a design that's broken underneath you. You are the connective tissue holding a disconnected organization together by hand. And nobody put that on your job description.
I'm not telling you this to make you feel stuck. I'm telling you because there's a way through it, and it starts with seeing it clearly. Let me show you what I mean, with one person.
So there's this guy. I'll call him Dave.
Every morning, before he opened anything else, Dave opened one file. A model he'd built himself. It had too many tabs, because his process had too many exceptions. It had formulas buried inside other formulas, because the answer was never in just one place. Vendor notes. Cost flags. Margin warnings. Little bits of logic he'd added over the years, every time he watched the same mistake get expensive.
People called it Dave's model. A little with affection, a little with judgment. Like it was just a quirk of his. But that file was doing something nobody ever said out loud. It was protecting the company's margins from scope creep. It was catching the assumptions nobody would admit they were making. Really, it was the operating system the whole business ran on, and nobody had ever admitted it existed.
Then leadership decided to automate more of the work. And Dave pushed back.
Now, you already know this story. The veteran with the spreadsheet who won't let go. The blocker. Arms crossed in the doorway of the future. That's what the room saw. And honestly, for a few days, that's about what Dave gave them. Every time someone asked if a step could be automated, he explained the exception that made it harder than it looked. And the more he explained, the more he sounded like a guy defending the past.
But here's the thing. Dave was right about the work. He was just standing in the wrong place.
He was defending the file, like the file was the point. It wasn't. That model was never sacred. It was evidence. Every tab in it marked a spot where the official process had quietly failed, and somebody had to cover for it by hand. Every workaround was a confession the company had never read out loud.
And the day Dave understood that, everything changed. He stopped trying to prove automation would fail. He started telling them what the new system would have to understand to actually work. Where the requests really came from, which was never where the workflow said. Which numbers were real, and which ones were guesses everybody had started treating as facts. How a project could slide into the red while everyone swore they were just moving money around.
The room got less comfortable. And a lot more useful. Because Dave wasn't fighting automation anymore. He was making sure it didn't just inherit all the old confusion and run it faster.
He didn't get through that change by caring less about the work. He got through it by getting more precise about what the work actually was. He stopped being the guy guarding an old file, and became the guy holding the only honest map of how the business really ran.
I tell you about Dave because Dave is you. And Dave isn't a level on the org chart. He's the analyst holding the numbers together, and he's the director holding the strategy together. He's anyone, anywhere in the building, who actually understands how the work fits, and gets treated like a blocker for saying what they see.
And there's a fear running underneath all of this right now, so let me say it plainly. A lot of you are afraid that AI is coming for exactly the work you do. The reconciling, the translating, the remembering, the cleaning up. And you're not wrong to notice it. That is the work that's easiest to automate.
But here's what Dave figured out. The task is not the value. Anyone can see the task. The value is that you know why the task exists. What it protects. Where it's fragile. What breaks if someone automates the visible steps and ignores the hidden ones. A machine can do the reconciling. It cannot tell you why the reconciling was ever necessary, or what quietly falls apart when it stops.
So the move, when the work starts coming for you, isn't to defend the task. It's to explain what the task has been holding together. Make the real work legible. Where it starts, what it protects, where the judgment lives, where the risk hides. Because the more clearly you can explain the real work, the harder it becomes for anyone to automate a bad version of your expertise.
You don't want to be Human Middleware forever. Nobody should. The goal was never to keep you doing the translating by hand. The goal is to turn what you know into the design of something better, so you stop being the duct tape and start being the person who decides what gets built. That's not surviving the change. That's leading it, from a seat that never gave you permission to.
So here's where I'm going with this show.
I'm going to keep telling these stories. The people who fight gravity without the authority to command it. The ones who refuse to quietly become middleware. The ones staring down AI and figuring out how to stay indispensable in a way that's actually about their judgment, not their job title.
And eventually, I don't want to just tell these stories. I want to sit down with the people living them. With you.
If something in this hit close, if you're the Dave in your building, or you're fighting a gravity nobody around you will name, I want to hear about it. You can reach me at the newsletter, and I'll leave a way in the show notes. And here's my promise. I will protect you. No company names. First names or no names. You'll hear anything before it ever goes out, and you can pull any of it. This show is on your side, on the record, and it will stay that way.
Because you've spent enough of your career being unseen. Not here.
I'm Gabe Rybicki. This has been the Organizational Gravity podcast.
If you've ever been the person who saw it coming and got called the problem for saying so, come back next time. I've got more of your story to tell.
Get full access to Organizational Gravity at organizationalgravity.substack.com/subscribe
