Years ago, I started a new job with a company that was about to change the legal services industry for good. Before I could consult on a single project, before I was allowed to talk to a single client, I was handed two books and told to read them before my first day.
The first was Eliyahu Goldratt’s The Goal. The second was Raving Fans. Nobody told me these were optional. I was told this was how the company worked, and that if I didn’t understand the books, I wouldn’t understand the job.
I thought that was the whole onboarding. It wasn’t even the beginning.
The company I joined had built one of the most respected managed services operations in a part of the legal industry most people outside it have probably never heard of; the unglamorous hardware and software that sits behind every major litigation, the people who handle the data nobody sees, but everyone depends on. I came in as a solutions consultant, the person standing between what clients needed and what the company could deliver.
And before they let me do that job, not only was I to read those books before Day 1, but when I got there, they made me sit in on every other job first. Ten weeks, split across IT, the team that processed the data, project management, application development, and the team that implemented the contracts once they were signed. All of this, before I was trusted to do the thing I was hired to do.
I was living in Charlotte, North Carolina, at the time. The company was based in a small town in Kansas. For the better part of a year, I flew back and forth every single week, Charlotte to Kansas and back, just to physically sit inside each one of these teams long enough to understand how the work moved. Eventually, my family and I packed up and moved to Kansas, because you cannot fake your way through that kind of understanding from a distance.
At the time, I thought this was just an unusually thorough onboarding. I know better now.
What that company did to me before I ever touched a client was teach me systems thinking as a lived discipline. They understood something most leaders never learn. You cannot find what’s broken in a system you’ve only ever seen from one seat.
That’s what we’re talking about today. Not motivation. Not mindset. A discipline. How to see the system you’re standing inside of, and how to tell the difference between what feels broken and what’s constraining you.
I want to be upfront about something before we go further. Forty episodes ago, in Episode 26, I asked, “Should you quit?” That episode was a personal diagnostic test for you. Mission, energy, impact, team, gut. It was about accurately reading your own exhaustion.
This episode is not that. This episode asks a harder, earlier question. Before you ask whether you should quit, have you diagnosed what’s broken? Because most leaders never get that far. They feel the friction and react to it. They never find the real constraint.
Let’s fix that.
Why Changing Elements (People) is Your Weakest Lever
I want to slow down here because most leadership content skips this part entirely, and that omission is exactly why most leaders never find the real constraint.
A system is not just a bunch of stuff. A system has three parts, and only three parts, according to Donella Meadows, who wrote the book, Thinking in Systems: 1) Elements; 2) Interconnections; and 3) Purpose.
Elements are the parts you can see and touch. People. Departments. Headcount. Line items on an org chart. Interconnections are the rules and relationships between those elements, the things that determine how they behave toward each other. Purpose is the deepest layer of all, the thing the whole system is organized to produce.
The mistake almost every leader makes is automatically defaulting to managing elements, since they are the easiest part of a system to see. When something feels broken, our instinct is to change an element. Fire the slow manager. Hire a new VP. Reorganize the team.
But changing elements is usually the weakest lever you have. Donella Meadows, who spent her career studying how systems behave, makes this point using football. Swap out every player on a football team, and you still have a football team. It might play better, it or worse, but it’s still recognizably football. Now keep the exact same players, but change the rules from football to basketball. Same people, same field, entirely different game. That’s the power of interconnections. They determine how elements behave toward each other, and changing them changes everything, even when the people stay exactly the same.
Purpose is the one almost nobody touches, because almost nobody can see it clearly. Purpose is not what’s written in your mission statement. Purpose is deduced from behavior. You don’t find a system’s purpose by reading what it claims about itself. You find it by watching what it rewards and what it punishes.
Way back in Episode 7, “Systems, Discipline, and the Soul of Leadership,” I told a story about an employee who found a faster, smarter way to solve a client’s problem using the software more efficiently. The work was done well. The client was happy. And that employee got chastised, because they hadn’t logged enough billable hours. Come review season, someone who moved more slowly and delivered less got the bigger bonus, because they billed more time doing it.
The element was the employee. The interconnection was a compensation rule that tied rewards to hours logged rather than to value delivered. The purpose, the one revealed by what got rewarded, was never “serve the client well.” It was “protect billable hours.” The firm’s mission statement likely mentioned client service. The system’s behavior said something else entirely. That gap is where almost every leadership failure I’ve ever watched up close lives.
Measuring What Matters: Deducing Purpose from Behavior
Let’s make this concrete.
Here’s a scenario almost anyone in professional services will recognize immediately. Your team wants to bring in a new tool, a new process, a new way of doing the work that everyone on the ground agrees would make things faster and better. And it dies. Not because anyone said no outright, but because it has to clear sixteen different layers of internal approval, and at every layer, someone finds a reason to slow it down or send it back.
Legal wants more time to review it. Risk wants another round of questions answered. IT wants a security assessment that takes three months. Nobody says no. Everybody just adds friction, and the friction compounds, and the initiative dies a slow death, and everyone privately blames the last department to slow it down.
Most leaders stop their analysis right there. They’ve found the loudest department, and they assume that’s the problem.
Run it through the three layers instead. The elements are the functions involved: Legal, Risk, IT, and the business unit asking for the change. The interconnections are the unwritten rule running underneath it all, the rule nobody wrote down anywhere, which is that nobody in any of those functions wants to be the name attached to the bad outcome if something goes wrong later. So everyone defers. Everyone asks for one more review. Everyone protects themselves by slowing things down, because slow is safe and fast is risky, and nobody gets fired for slow.
And the purpose, deduced from behavior rather than from whatever the strategic plan says about innovation and growth? The system isn’t organized to enable new ideas. It’s organized to prevent the next bad outcome. That’s not a flaw hiding somewhere in the process. That’s the system working exactly as designed, just not designed for what leadership claims it’s designed for.
I want to give you a tool for finding this, because “deduce purpose from behavior” can sound like a nice phrase that’s hard to use. I talked about this in Episode 39, “The Leadership Flywheel,” borrowing from the organizational psychologist Edgar Schein. Schein distinguished what he called artifacts, the visible stuff, the mission statement on the lobby wall, and what he called basic underlying assumptions. These unwritten rules govern behavior. The artifacts are the paint. The assumptions are the foundation. If you don’t manage the foundation, it manages you.
Schein gave us three places to look. What does the organization measure and control, not what it says it values? How did leadership react the last time something went wrong? Did the first question sound like “whose fault is this” or “what can we learn?” And who got the last promotion, because rewarding the wrong person is louder than any mission statement you will ever write.
Two completely different disciplines land on the same conclusion here. Systems theory tells you purpose is revealed by behavior, not rhetoric. Organizational psychology tells you culture is revealed by what gets measured, what gets punished, and who gets promoted, not by what gets said in a town hall. When two different fields of study independently arrive at the same answer, that’s usually a sign you’ve found something true.
Stop Strengthening the Wrong Links
Now we get to the tricky part, even if you’ve correctly identified that something is broken.
Eliyahu Goldratt, in his book The Goal, built his entire body of work, The Theory of Constraints, around one observation. Every system has exactly one constraint, the single weakest link that limits everything else. A chain is only as strong as its weakest link, and strengthening any of the other links does nothing for the chain’s overall strength. It can make things worse, because you’ve added weight and cost to a part of the chain that was never the problem in the first place.
Think about what that means for the sixteen-layer approval example. The instinct, once leadership notices the friction, is usually to fix the loudest department. Send Legal for more training. Add headcount to Risk. All of that strengthens a link that was never the weakest. The function that looks the most inefficient is very often not the one limiting what the whole system can produce. The constraint is usually quieter than the loudest complaint in the room.
Goldratt built a discipline around finding and working a constraint correctly, in strict order: identify it, get more out of what you already have before spending anything, align everything else around it, and only then invest money to expand it. Almost every leader skips straight to spending, because spending feels like leadership. It feels decisive. But the earlier steps, when done fully, typically expose a huge amount of hidden capacity that had been sitting there the entire time, completely free. The sixteen-layer approval process probably isn’t underfunded. It’s probably underused, full of capacity nobody’s bothered to find, because everyone jumped straight to “we need more people” before they ever asked, “are we using what we have?”
The ‘Seat’ Problem: When You Have Influence, But No Structural Power
Let’s say you’ve found the constraint. You understand the system underneath it, elements, interconnections, and purpose. Now comes the question almost nobody asks, and it’s the question this entire episode has been building toward.
Do you have the authority to move it?
Not whether you should try. Not whether you care enough. Whether you, in the seat you currently sit in, have the power to change the layer where the constraint lives.
This is where I need to draw a distinction that most leadership conversations blur together, between authority and influence, because they are not the same thing, and confusing them costs people years of their careers.
Authority is structural. It’s the right to move an interconnection or a purpose. It usually comes with a title, control over the budget, the power to hire and fire, and a seat on the board. Influence is relational. People listen to you. They defer to your judgment. They change their behavior because you asked them to, even though you hold no formal lever that requires them to.
Influence is real, and it matters, but it is not a stable, permanent state the way authority is. It’s closer to a balance; you’re spending down every time you use it. Every time you name a constraint and nothing moves, you haven’t just failed to fix the problem. You’ve spent some of the trust people had in your reading of the situation. Do that enough times, and the deference that used to follow your judgment stops following it.
I’ve watched this happen to people, more than once, in more than one organization. Someone takes a senior seat with real influence and no authority over the layer where the constraint sits. For a while, that influence is enough to move small things. But every time the bigger constraint gets named, and nothing happens, a little more of that influence erodes. What I’ve noticed, watching this pattern repeat itself, is that it’s rarely about the person. When you see two different people, in succession, sitting in the same seat, independently arriving at the same complaint, that’s not two leaders who weren’t good enough. That’s a seat that was built, by design or by neglect, to have influence and nothing else. The problem was never the person. It was the chair.
There’s an old idea, the one about two roads diverging in a yellow wood, that gets quoted at moments exactly like this one, usually to romanticize the uncertainty of the choice. I don’t think that’s useful here. The poem is about not knowing where either road leads. This diagnostic exists specifically to remove that not-knowing. You can find out, before you commit to anything, whether you hold real authority over the constraint you’ve identified.
The Identity Shift: Admitting Where the Constraint Truly Lives
So here’s the test that I have for you: once you’ve found your constraint, elements, interconnections, purpose, all of it diagnosed, ask yourself one question. Do I hold authority over the layer where this constraint lives, or do I only hold influence?
There are only two answers, and each one tells you which sequence of work comes next.
If you have authority, the sequence is Resilience first. You hold your center long enough to work the constraint correctly before you spend a dollar expanding it, because most leaders with authority still skip straight to spending. Then, empowerment, because moving an interconnection or a purpose almost never happens through your effort alone. It requires other people, across functions you don’t fully control, choosing to act differently because you’ve made the case clearly enough. What comes out the other side, if you’ve done that work, is Reinvention. Not your own personal reinvention. The system itself now operates differently because you used real authority correctly.
If you don’t have authority, only influence that’s been depreciating every time you’ve named the problem and watched nothing change, the sequence runs differently. The Reinvention doesn’t happen when you leave. It happens the moment you admit the diagnosis. That tenure, loyalty, and political capital, all the things you’ve spent years accumulating, do not automatically convert into authority over a purpose-level constraint. That admission is the identity shift. It’s harder than leaving, because it means giving up a story you’ve probably been telling yourself for years, that staying long enough and working hard enough eventually buys you the power to fix what’s broken.
Once you’ve made that admission, Resilience is the discipline of leaving well. Intact relationships. You have documentation of what you tried, what worked, and what didn’t, so the people staying behind aren’t stranded. No scorched earth on the way out, because how you leave is itself a leadership act, maybe the last one you get to perform in that seat.
And Empowerment shows up twice on the other side of that door. Once for the team you’re leaving, give them what you hand them before you go. And once again, somewhere new, specifically because the organization is willing to bring you in, it has already run this same diagnostic on itself. They already know they have a constraint they cannot fix from inside, because everyone currently inside their interconnections is, by definition, part of what’s holding that constraint in place. They need someone whose authority isn’t compromised by relationships and history they were never part of. That’s not failure walking out one door. That’s a correctly diagnosed system meeting a leader equipped to move it.
Recall that episode 26 was a personal test. Mission, energy, impact, team health, gut. It asked how you’re doing, and it ended in a binary about your own state, whether to prepare an exit or refocus on what you control.
This is a structural test. It asks where the constraint lives, and whether you, specifically, in this specific seat, hold the authority to move it. A leader can pass Episode 26’s test completely. Energized. Mission clear. Team is healthy and engaged. And still fail this one, because no amount of personal wellness, no amount of mission clarity, buys you authority you were never granted.
If you’re someone who calls yourself a leader, this test isn’t something you run once, in a crisis, when things finally get bad enough to force the question. It’s something you run continuously, as a discipline. Tolerating a constraint indefinitely without ever checking whether you have authority over it isn’t resilience. It just feels like resilience from the inside. From the outside, it’s absorbing damage and calling it grit, year after year, in a seat that was never built to let you fix what you correctly identified as broken.
Ten weeks of onboarding taught me something very powerful: you cannot diagnose a system from a single seat. You have to see the whole thing, elements, interconnections, purpose, before you can say where the real constraint lives, and before you can say whether you’re the person with the authority to move it.
That’s the work. Go find your constraint.
Takeaways:
One. A system has three parts: elements, interconnections, and purpose. Most leaders manage only the first one, the weakest lever they have.
Two. Purpose is deduced from behavior, never from a mission statement. Watch what gets measured, how the last crisis got handled, and who got the last promotion.
Three. Once you’ve found the constraint, work it in order. Identify it. Get more out of what you have before spending. Align everything else around it. Only then invest money. Most leaders skip straight to spending and miss the capacity that was sitting there for free.
Four. Authority and influence are not the same thing. Authority is structural. Influence is relational, and it depreciates every time you name a problem and nothing moves.
Five. Run the test honestly. If you hold authority, the work is Resilience, then Empowerment, then Reinvention. If you don’t, the Reinvention happens the moment you admit it, not the moment you walk out the door.
