Most advice for a new leader’s first ninety days is about establishing presence and making an early mark. All of that comes second. The real first job is reading the standard that’s already there — accurately — before you touch anything.
Most advice for a new leader’s first ninety days is about establishing presence — setting a vision, making an early mark, showing the organization who is now in charge. I think all of that comes second, and treating it as first is where a lot of promising new leaders do real, avoidable damage in their opening quarter.
The claim, against a real comparator
Michael Watkins’ The First 90 Days is, deservedly, one of the standard references for executive transitions, and it gets a great deal right about the mechanics of onboarding — stakeholder mapping, early wins, aligning expectations with the board. What I want to add, from having taken over organizations at several different scales, is a priority ordering the standard advice tends to underweight: before you can responsibly do any of that, you have to accurately diagnose what the organization currently tolerates and what it currently enforces. Acting before that diagnosis is complete means you risk one of two mistakes — preserving a bad standard by accident, because you didn’t see it clearly enough to know it needed to change, or destroying a good one by accident, because it looked, from the outside and on a short timeline, like something that needed fixing.
What accurate reading actually requires
The method is not complicated, but it is uncomfortable, because it asks a new leader to delay the thing everyone is expecting them to do. Watch what actually happens at the operating layer before reading a single strategy document — documents describe intentions, and the operating layer describes what is actually true. Identify the specific gap between the standard the organization states about itself and the standard it actually practices day to day; that gap, wherever it exists, is more informative than either version alone. And resist the pull toward early, visible action before the diagnosis is genuinely complete, even when waiting feels, to everyone watching, like the new leader hasn’t started yet.
I felt the weight of this most directly at the largest scale I ever operated at, moving into a role with responsibility for roughly 680,000 people after having run an organization a fraction of that size. At that scale, there was no possibility of learning the standard by walking around and seeing it myself — the organization was simply too large for that method to reach more than a rounding error of it. The diagnosis had to run through what the organization’s own reporting, inspection, and reward structures revealed about what was actually being tolerated and enforced, because personal observation, which had worked at smaller scale, could not scale with me.
The trap of early action
New leaders default to early, visible action because it is what the organization and the board expect to see, and because waiting genuinely looks like inaction even when it is the correct move. The specific cost of getting this wrong is real: changing a standard that was actually working, because on a ninety-day clock, from an incomplete diagnosis, it looked like it wasn’t.
A structure that respects both pressures
The compromise that has worked for me: the first thirty days are diagnosis only, with no changes announced, however uncomfortable that silence feels to a board expecting immediate action. The next thirty are a small number of deliberately chosen, well-tested changes — not a comprehensive plan, a short list you are confident in because the diagnosis actually supports it. The last thirty are reinforcement, watched closely for reversion, because a change that looks like it took in month two and quietly unwinds in month three was never really adopted.
You cannot enforce a standard you have not correctly identified yet. Trust what’s tested. Not what’s told — and in your first ninety days, the organization will tell you a great deal about itself. Most of it will need to be tested before you act on it.
Scott Pleus is an operating executive who has built his career on a single conviction: an organization’s confidence in its own readiness is only as good as the last time someone actually tested it. If nobody told you your numbers were good, would you still believe them? That conviction was forged over three decades of command in the United States Air Force, retiring as a Lieutenant General and the longest-serving Acting Vice Chief of Staff in the role’s 79-year history. His command experience is the civilian equivalent of running large, high-consequence operations at every level of scale — from a single division, to a joint international operation, to the number-two position in a 680,000-person global organization. In every one of those roles, the product was readiness, and there was no such thing as a plausible excuse for being wrong about it. His standard, in his own words: accountable, not responsible. That is the experience most executive backgrounds don’t have, and it is what any organization needs when it wants to know — not hope — that it can perform under pressure. Early in his career, he noticed something worth learning from: a self-assessment that had never once produced a failure. Rather than take that as good news, he treated it as a signal that the test itself needed to evolve. He built a new version of the check — one that measured real readiness instead of rehearsed readiness — and kept refining it, even when the organization pushed back, because he was committed to the standard underneath it, not just the version of it that was easiest to pass. That same instinct shaped how he led. He made a habit of showing up unannounced, not to catch anyone, but to see the organization as it actually ran day to day — and to ask the one question a prepared briefing never answers. That habit paid off when he inherited a struggling unit: he gave its two senior leaders a clear deadline and clear ownership of the turnaround, and in sixty days, the unit had rebuilt the standard for itself. The stakes in his operating environment left no room for a wrong answer — there was no version of a readiness failure that was merely inconvenient. That is precisely why the discipline transfers: an executive who has enforced a verification standard with zero margin for error brings a rigor to operating risk that most executive backgrounds never have to develop. Trust what’s tested. Not what’s told.
