On Second Thought
The One System You Never Stop to Examine
You don’t perform to the level of your talent, your intentions, or your goals. You perform to the level of your systems — and the one system you never stop to examine is the one running you.
Key Takeaways
Every leader runs on a system, whether they designed it or not.
The visible one — your calendar, your routines, how you run a week. And the inner one: how you react under pressure, the decisions you make on autopilot, where your attention drifts when no one is directing it. Together they are your leadership operating system, and they produce your results far more faithfully than any goal you’ll ever set.
Here’s the uncomfortable part. You’ve almost certainly never reviewed it.
You review your metrics, your team’s output, the quarterly numbers. But the system generating all of it runs unexamined in the background — until it fails. The burnout. The decision you wish you could take back. Failure becomes the only thing that prompts you to examine how you work, and any fix you make under that pressure will likely be reactive, incomplete, and unsustainable. It tends to be a band-aid, not the fuller, calmer change you could have made before the urgeny arose.
Your results aren’t set by your ambitions. They’re set by a system you’ve never stopped to inspect.
So inspect it — with the discipline a process engineer brings to a workflow, turned inward. Here’s the loop I teach.
The Loop
THREE MOVES, TURNED INWARD
Name the GapWhere what you say and what you do diverge
Start where the system leaks: the gap between what you say matters and what you actually do.
My priority is X — but I keep doing Y.
My priority is developing my people — but I keep solving their problems for them.
My priority is strategy — but I keep living in my inbox.
Look at the evidence, not your memory. Memory is a flattering narrator. And the clearest evidence is your budgets — not the money and calendar you manage, but the attention and energy you spend all day without once checking the balance. Where they were allocated last week is your real priority, regardless of your intentions. The Y you keep doing is often not a choice but a reflex — and the reaction you never catch is the one that runs you.
Design One Experiment — and Say WhenSmall, specific, and wired to a trigger
Choose one practice to test against that gap. Not ten. One — because changing many things at once is the fastest route to changing none of them.
Make it Minimal Viable Effort — so small it almost feels like it doesn’t count. (If you’re wired type A, that flicker of this is too small to matter is the sign you’ve sized it right.) Then don’t leave it to willpower; willpower is a mood, not a method.
Wire it to a moment that already exists: when X happens, I will do Y.
When a report brings me a problem, I will ask one question before I offer one answer.
When I sit down after lunch, I will close every tab but one.
The trigger does the work your motivation won’t. And hold it as an experiment, not a verdict on your character — you’re testing a system, not engaging in self-criticism.
Measure on Two Levels — Along a ContinuumDid you run it — and did it change anything?
Most people score a habit pass/fail: did I do it or not. That’s only half the picture, and the less important half.
Activity: Am I practicing the behavior consistently?
Impact: Is it changing anything — in my results, and in how it feels to lead?
A practice you execute consistently with no impact is information: the experiment may be wrong, not you. Adjust, and try again. Track progress as movement, not a grade — am I further along than last month? Then close the loop: begin your next review by evaluating the last experiment, not by making a fresh resolution.
Measure both the activity and the impact. A practice that changes nothing is still telling you something.
Start with Yourself — Then Enlist the Team
The team you lead works exactly the same way: buried in operating demands, improving only when something breaks. A team takes its cue on improvement from the person leading it. An unexamined leader builds an unexamined system — the same lind spot repeats at every level.
But the connection is more direct than that. The system your team runs on is, in large part, one you've built — out of what you repeatedly do. When you step in to solve their problems, they learn to bring you problems, not solutions; when you hold decisions close, they stop making them. Your behavior doesn't just run you — over time it becomes the conditions they work within.
So don’t start with the team.
You can’t install in your team a discipline you don’t practice yourself. Require it anyway, and you’ll get compliance, not change.
Run the loop on your own system first, until it visibly changes how you lead. Then bring it to the team — not another weekly meeting no one has room for, but a quarterly rhythm realistic enough to survive a hard quarter.
The Order That Works
Model it before you mandate it.
Take fifteen minutes, alone, and write down the gap — my priority is X, but I keep doing Y.
Design one experiment to address it, wired to a specific trigger, with one activity measure and one impact measure.
One gap. One experiment. Not ten. One.
You are already performing to the level of your systems. The only question is whether you’re designing them — or still waiting for them to break before you give yourself permission to examine them.
If this named something you recognize, I’d like to hear it. Email me here.