This is issue one hundred. Two years of showing up in your inbox every week with the same commitment: name the pattern honestly, even when it's uncomfortable, and trust that clarity serves you better than comfort does. If you've been reading since the early issues or found this one first, thank you for spending part of your week here.

You got the role. The one you spent the better part of two years positioning for, interviewing for, waiting for.

For a few weeks, it feels like the hard part is finally over. Then the actual job starts, and you realize the thing that got you here and the thing that's required of you now are not the same thing, and nobody warned you about the gap between them.

You are exactly as capable as the people who hired you believe you are. What nobody told you is that the first ninety days run on a completely different clock than the eighteen months that got you here, and that clock started the moment you said yes.

I have watched this exact derailment happen to new CIOs, VPs, and Directors across companies of every size, more often in the first ninety days than at any other point in their careers. Not because they lacked the ability to do the job. Because nobody told them the first ninety days are a different job than the one they just spent eighteen months proving they could do.

Anthony took over as VP of Engineering at a mid-size logistics company after a search that lasted most of a year. Technically sharp, well liked in his interviews. In his first month, he moved fast the way he always had: rewrote a roadmap in his second week and personally overrode a technical decision his new director had made.

By week six, two of his strongest directors had gone quiet in meetings. Not because his ideas were wrong. Because nobody had asked for his opinion on the roadmap yet, and overriding a decision before understanding why it was made read as something other than confidence to the people who'd made it.

A new executive walks in with more formal authority than they will have at any other point in their tenure, and less credibility than they will have at any other point too. Most people spend that gap acting on the authority. The ones who land well spend it building the credibility first.

This doesn't get easier with time. The opinions people form about you in weeks two through four are the opinions that follow you for the next eighteen months, whether or not they turn out to be accurate.

By the time Anthony realized what was happening, three months in, some of what he needed to undo had already hardened into how his team quietly described him to each other. Reversing an early impression takes far longer than making a good one would have.

Nobody schedules a meeting to tell a new executive their credibility clock is running. It just runs, and by month four or five, the leaders who spent their first ninety days proving they could execute are often still explaining themselves, while the ones who spent that window building trust are already being handed the next mandate.

There's a useful distinction for the first ninety days: are you spending your authority, or are you building your credibility? They are not the same currency, and most new executives are unknowingly spending one while believing they're building the other.

Spending authority looks like using the title to move fast, override, and decide. Building credibility looks like understanding before acting, even when the room is watching to see what you'll do.

Three questions worth sitting with honestly:

What have you already decided or changed in this role that you made before you fully understood why things were the way they were?

Who are the three or four people whose read on you will most shape how the rest of the organization sees you, and how much deliberate time have you actually spent with them?

If your first ninety days ended today, what would people say established you, and what would they say you rushed?

Most new executives can answer the first question uncomfortably fast. The third question is usually where the real work begins.

Smart, capable new executives still fall into this, even when they've read every piece of advice about the first ninety days.

Slowing down when you've just been hired to make things happen feels like the opposite of what you were brought in to do. Boards and CEOs use words like urgency and momentum when they make the offer. Nobody tells the new executive that urgency applied to the wrong thing in week three can cost them the very trust that urgency was supposed to build.

There's a deeper pull too. The instinct to prove yourself technically, to show the room you already understand the business, comes from exactly the same place that got you promoted in the first place. It worked for eighteen months. Turning it off, even temporarily, while you build context feels like abandoning the thing that made you valuable in the first place.

None of this makes the instinct wrong. It makes it miscalibrated for this specific window. Anthony wasn't a bad leader. He was applying a proven playbook to a phase of his career the playbook was never designed for, and by the time he noticed, he was already spending real energy rebuilding trust he hadn't needed to spend in the first place.

The hardest part is that nobody around a new executive is incentivized to say any of this out loud. Direct reports are still forming their own opinion. Peers are watching to see how the new person handles pressure. The boss who hired you wants to see the urgency they promised the board, not a plan that looks, on paper, like patience.

There's a version of this that's specific to technology leaders in particular. You were very likely hired, at least in part, because you could speak credibly about the technical direction of the organization. That credibility is real. It's also the exact credibility most likely to tempt you into acting before you've earned the broader kind, the kind that comes from understanding the political landscape, the informal relationships, and the history behind decisions that look, from the outside, like they were simply wrong. Anthony's roadmap wasn't a bad roadmap. It solved a problem the previous director had already spent four months building consensus to solve differently, for reasons Anthony didn't yet know existed.

If you're heading into a new executive role, or you're already a few weeks into one and starting to feel the gap between how it looked from the outside and how it feels from the inside, a longer to-do list won't close that gap. What actually closes it is an outside, structured look at what your first ninety days need to build, specifically for the organization and the people you just inherited, before more of that window closes without anyone telling you it's closing.

That kind of look is difficult to get from inside your own reporting line, where almost everyone around you has a reason, conscious or not, to tell you what you want to hear rather than what you need to know. Your new boss wants to see confidence. Your new team is still deciding whether to trust you with the truth. Neither of them is positioned to tell you, plainly, which of your early moves are building credibility and which ones are quietly spending it.

It's easier to see clearly from someone with no stake in whether you slow down or keep moving fast, who has watched this exact transition succeed and stall across thirty years and every size of organization, and who can usually see the specific pattern within the first conversation.

That's a single conversation, not a program pitch. Book time here: https://meeting.techleadership.net/

The authority came with the title on day one. The credibility is still being decided, in rooms you're not in, based on what you do this week.

Ninety days from now, you will have either spent that gap closing it, or you'll still be wondering why it never seemed to close, and quietly explaining a first impression you didn't mean to make. A hundred issues in, that's still the whole job here: naming the gap early enough that you get to choose which one happens, instead of finding out which one happened after the fact.

Robert