A senior executive arrives at a new company with a history
Most plans for a senior executive's first 90 days in a new job rest on one assumption: the executive does not know the company, so the first task is to learn it. The assumption is half right. A managing director, a CFO or a sales director hired from outside genuinely does not know the new company. But they do not arrive empty. They sit down at the table with a history, and that history is also the answer to why they were hired.
The story told in the interviews tends to be the same. At the previous company a division was turned around, a market was opened, a scattered team was brought into shape over a few years. The CEO or the board doing the hiring listened to that story and wanted one like it. The executive knows this from the first day: here, too, they are expected to do it again.
The sentence about the last company
In the first weeks that expectation surfaces in a small sentence. In a meeting, with good intentions, the executive describes how the same problem was solved at the previous company. Once said, the sentence gets easier, and by the end of the first month it can be heard in almost every meeting. For the executive it is the most natural way to share what they have learned. Yet the real risk in a senior executive's first ninety days is not ignorance but the assumption that what they knew somewhere else still holds here.
We wrote earlier about how a new manager spends the right not to know in the first months. For a senior executive hired from outside, the problem runs the other way. Admitting what they do not know is rarely hard for them; seeing where what they know came from is.
The previous success was partly the previous company's
The success story told in an interview is told in the first person singular. That is natural, since it was told to get hired. But in that form the story leaves out most of the conditions that made the success possible. The executive is not hiding them; most likely they no longer see them. Over the years those conditions faded into the background, and only the work remained.
What the story leaves out
When we retell the story with the executives we work with, the missing conditions usually fall under four headings:
- A CEO or a board that stood behind them when things got difficult.
- A team they had built or chosen themselves over several years.
- An organisation that knew their shorthand and finished their half-sentences.
- A store of accumulated trust that let their mistakes be tolerated.
None of the four moves to the new company. When the executive takes the same step with the same resolve, it is now taken without that backing, with an unfamiliar team, on ground where no trust has built up yet. When the result comes out differently, the executive often reads it as a flaw in the new company.
Reputation earns a hearing, not compliance
The fourth condition misleads the most. A senior executive arrives with a reputation, and in the first weeks it does real work: meetings open up, people listen, proposals are taken seriously. The executive takes this for a continuation of the trust they had before. But a reputation brought from outside earns a hearing, not the standing to have things carried out. The trust people need before they act on a proposal builds as they watch the person making it read this place correctly, and that build starts from zero.
A reputation earns a hearing. The standing to act is earned here, from zero.
The team hears the comparison as a verdict
When the executive talks about the previous company, they believe they are sharing experience. The team hears the same sentence differently. Each time the old company's method comes up, they conclude that the current method has been found wanting. The people who built the current method are usually in the room. Nobody objects, but small reasons for keeping things as they are start to surface more often in meetings.
Resistance looks like confirmation
The executive reads those reasons as proof of the problem described to them during hiring. They were told the company resists change and that old habits run deep, and there it is. So the resistance produced by their own sentence gets filed as a finding that proves them right. By the third month the executive and the team have each built a story about the other, and both stories confirm themselves.
The inside of this period does not show from outside. The CEO who listened admiringly to the story in the interview begins to ask why it has not yet been repeated here. The executive feels the pressure and goes back to what they trust most: the method that once proved them right. Holding tighter to the last company as the pressure rises is the loop senior outside hires fall into most often in the first quarter. They are alone in that loop, because no one at the new company is yet close enough to tell them why the old method is not taking hold here.
The method is to sort the past into what travels and what was local
Setting the past aside is neither possible nor right; the executive was hired for it. The method we use is not to drop the past but to sort it. The executive rewrites their most important success at the previous company on a single page, this time putting one question beside each element: would this have been there without me, or did it arrive with me?
Two columns
The result almost always falls the same way. The solutions themselves, the structure that was built, the people they worked with and the timing all go in the local column. What remains in the portable column is smaller and more abstract: a way of reading a situation, the questions they ask, a sense of what matters. What moves to the new company is not the executive's solutions but their questions. With that split written down, an executive about to cite the old company in a meeting can first ask what exactly they are bringing.
A ninety-day rule
The practical rule that follows is simple. For the first ninety days, the previous company is not named in meetings. The experience is not discarded; it is turned into a question about this place. Asking who makes this decision here, rather than saying that sales made it there, puts the same experience on the table as curiosity instead of as a verdict. Some executives add a step. In the first months they openly choose one practice they found at the new company and will keep unchanged, and they say so. That small choice tells the team the executive reads before ruling, more clearly than any speech could.
The same page has one more reader: the person who did the hiring. The CEO or the board also heard the first-person version of the story and set their expectations by it. When the executive shares the two columns with them at the end of the first month, they say in advance which result will take longer here, and why. The conversation does not lower the expectation; it ties it to a realistic timetable. When it does not happen, the same gap is discussed in the sixth month as a disappointment, and by then the executive has no page to explain it with.
From the field
Senior executives hired from outside usually come to us in the second or third month. Their first sentence tends to be the same: why is everything so slow here. Then come the new company's habits, its decision processes, the caution of the team. Most of what they describe is accurate. But somewhere in the conversation the previous company returns, in almost every paragraph, as the yardstick.
The story we ask for first
So in the first conversation we ask the executive to tell their previous success once more, this time naming everyone in it. The story gets longer. A CEO's backing appears, a deputy hired years earlier, a board decision nobody else remembers. As they tell this second version, the executive starts to see what is actually missing at the new company: not the method, but the conditions that carried it. If the seat they have joined is the CEO's, the same period carries another weight, which we covered in a CEO's first 90 days are spent being read. A senior executive's first ninety days work when they are spent not carrying the past but sorting out what in it actually travels.
How we work begins with that second story. Our other pieces sit on the Perspective page.