The First 90 Days After a Move — What Gets Decided Before Performance Does

Introduction
1. What the Ninety Days Actually Decides Is Classification
2. The First Two Weeks — The Kind of Questions You Ask Defines You
3. The First Month — Three Maps
4. Trust Is Built from Small Promises, Not Large Results
5. When Are You Allowed to Change Things
6. An Internal Move Is a Different Game
7. What You Do Not Have to Do in the First Ninety Days
8. The Ninety-Day Check
9. One Thing You Can Do Today
Where This Advice Does Not Apply
Closing
Further Reading

Introduction

This blog already has one post about a ninety-day onboarding. The First 90 Days as an FDE was written on the premise of a role that goes out to the customer site. It deals with two layers of unfamiliar environment at once, your own company and the customer, and it is built around a week-by-week checklist and a technical map.

This post is different. There is only one unfamiliar environment, and in exchange it deals with the problems inside the organization. Not a checklist but three axes. What you have to learn first, what trust is built out of, and when you are allowed to start changing things. And it includes one case the FDE post does not cover: not changing companies but moving departments inside the same company. That side actually holds more traps.

One basic premise differs too. The ninety days in the FDE post is designed as the process of opening a trust account. The ninety days here overlaps with that, but something sits in front of it. Before the account can be opened, classification happens first.

1. What the Ninety Days Actually Decides Is Classification

People do not observe a newcomer for long. There is no time to observe. Instead they classify quickly off a few contacts, set that classification as the default, and fill in the rest to match.

The boxes differ by organization but are broadly similar. Someone you can hand things to and trust. Someone who needs looking after. Someone who talks a lot. Someone who quietly does well. Someone you cannot tell about yet. And once a box is set it is hard to change, because information arriving afterward gets interpreted to fit it.

What matters here is that the input to the classification is not performance. In a first quarter there is not yet any performance to judge. Something else gets used instead.

What kind of questions you ask
Whether you do the thing you said you would do by the time you said it
How you handle the first time you disagree
Whether you say you do not know, or act as though you do

All four are observable from the first week. Which is why the classification finishes long before any results appear.

This may sound uncomfortable, but it is actually favorable news. Performance is hard to produce in a first quarter, and those four are available to you starting today.

2. The First Two Weeks — The Kind of Questions You Ask Defines You

A newcomer has a question budget. For the first several weeks nothing you ask is strange, and that period does not come back. Ask the same question three months later and it means something different.

So the budget is not to be saved but to be spent well. Two mistakes are common here. One is not asking out of fear of being a nuisance, and the other is asking things you could have looked up.

What separates a good question from a bad one is not difficulty. It is three things.

First, could you have looked it up. Asking something that sits in a document is buying your own time with someone else's time. One qualifier attaches here, though. If you look for ten minutes and cannot find it, asking is correct. Two hours of searching is the larger waste.

Second, are you asking the same question twice. This is what changes an impression the most. The moment you ask twice, the other person starts wondering where the first answer went.

Third, where do you store the answer. Write down what you hear, and when that content later comes back as a document, the question stops being a cost and becomes a contribution. It is also a contribution only a newcomer can make. The people already there do not know what has gone undocumented.

And there is one more kind of good question. The question of why it is set up this way. What to do and how to do it is in the documents; why it is done that way usually is not. And without the reason, when you later propose changing it you end up repeating a discussion that has already concluded.

3. The First Month — Three Maps

The goal of the first month is not contribution but maps. You draw three.

The decision map. What gets decided where. Some decisions end inside the team, some need another team to agree, some go upward. And in Korean organizations there is one more layer here. The gyeoljae line is the formal approval chain a document travels up, signatory by signatory, and the path it prescribes is often different from the place where the decision actually gets made. On paper three people have to approve; in practice one person objecting ends it. Miss this gap and you will repeatedly experience getting every formality right while nothing moves.

The people map. The common misreading here is putting people on a single axis. In reality three kinds differ. People who have information, people who decide, and people who can block. The third is especially often omitted. Every organization has a seat with no formal authority whose objection stops the work. Someone who has been there a long time, or who is the only one who knows that area.

The norm map. The rules that are in no document. Is it acceptable to disagree in a meeting? Where does your own judgment end and asking begin? How fast do you have to answer a message? At what level of completeness do you show a draft? How do you address people?

That last item deserves particular attention in Korean organizations. Hoching, the form of address used between colleagues, is not settled across the country: some organizations use rank titles, some attach the honorific nim to a given name, some use English names, and the meaning packed into that choice differs from organization to organization. Read the address rules wrong and the first impression goes off regardless of what you actually said. This is something a day of observation will tell you, so there is no reason to get it wrong.

Drawing the norm map is eight parts observation. One item is better asked outright, though. Where does my own judgment end. Read this wrong and you become either high-handed or exasperating, and both stick for a long time when they attach early.

4. Trust Is Built from Small Promises, Not Large Results

What a newcomer most wants is an impressive result. But that does not work well early on. There are three reasons.

First, a large result takes time to verify. An output that takes months to judge as genuinely good contributes nothing to the impression formed in a first quarter.

Second, attribution is unclear. Large work is mostly done by several people, and a newcomer's share looks especially blurry.

Third, a large output made without context has a high chance of being wrong. An improvement designed without knowing why things are the way they are now is usually a proposal that was already considered and discarded.

Keeping a small promise, by contrast, is immediately observable, clearly attributed, and leaves no room to be wrong. Saying you will write it up and send it by Thursday, and sending it on Thursday. That is the actual currency of a first quarter.

So set the early goal like this. To land in the classification of someone whose word arrives when they said it would. That classification becomes the route to being handed large work later. Conversely, if you do not land in it, large work does not come, so the opportunity to produce a result never arises in the first place.

There is one practical trick. Early on, make your promises short. Rather than showing a two-week piece of work once after two weeks, it is better to show an intermediate state once after three days. Shrink the size of the promise and the number of times you keep one goes up, and trust accumulates by count, not by size.

5. When Are You Allowed to Change Things

A newcomer sees strange things. And they are mostly genuinely strange. What becomes invisible after a long time is visible to a new pair of eyes.

The problem is timing. Too early and it is a criticism without context; too late and those eyes are gone. Judging by conditions rather than by date is more accurate. There are three.

First, can you explain why it is set up this way now. If you do not know the reason, the reason may still be valid. And proposing without knowing it sounds, to the people who lived through that discussion, like a repeat of the same conversation.

Second, do you know who this change inconveniences. Every change has someone for whom the current way is convenient. Propose without knowing who that is and you run into unexpected opposition, and you mistake that opposition for something personal.

Third, is it reversible. A reversible change has a low discussion cost, because you can try it and go back if it turns out wrong. An irreversible change is hard to propose early.

If all three are yes, thirty days is fine; if even one is no, ninety days is still early.

And what matters in a first proposal is not size but kind. It is better to start with something that does not touch anyone else's territory, is reversible, and that you can execute yourself. The experience of a first proposal passing is what creates the weight of the next one.

Here one of the most expensive early mistakes has to be named. When the way that worked at your previous job does not work here, interpreting that as this place is broken. That interpretation is often correct. But being correct and being able to act on it right now are different problems. A newcomer at day ninety has no trust balance to push that judgment through, and pushing without a balance only worsens the classification, regardless of whether the judgment was right.

6. An Internal Move Is a Different Game

An internal move looks easier than changing companies. You know the company, you know the systems, you know a few of the people. So you prepare less. That is the trap.

The core asymmetry is this. Reputation follows you and context does not.

Reputation following you cuts both ways. A good reputation makes the start easier, but it also sets expectations high from the beginning. And a reputation built in your previous team was built to that team's standards, which may differ from what the new team values.

That context does not follow you is the more important half. Even inside the same company, teams differ in how they decide, in documentation culture, in pace, and in quality bar. But because an internal mover is assumed to already know, nobody explains any of it. The onboarding a new hire receives, an internal mover does not.

So in an internal move you have to request onboarding explicitly. Say that you know the company but not this team, and ask for the time to draw the three maps above. Without that request, two months go by with nobody having recognized there was a problem.

The second trap is using your previous team's way as the default. It happens unconsciously. And the better that way worked in the previous team, the more it happens. The sentence that comes out of this is dangerous. On the team I was on before, we did it like this. That sentence comes from a good-faith intention to supply information, but on the receiving end it sounds like a comparison.

The third is your relationships with people from the previous team. They are an asset. Information comes in, and cooperation is easy to ask for. They are also a burden. If your time keeps flowing toward the previous team before any sense of belonging has formed on the new one, the new team sees you as someone who has not arrived yet. For the first few months it is better to tilt your time deliberately toward the new team.

7. What You Do Not Have to Do in the First Ninety Days

There are things anxiety tells you to do. Three are especially common.

Getting close to everyone. Try to build a relationship with the whole organization and the quarter ends without your knowing anyone deeply. Early on, five or six people your work directly touches is enough. The rest grows naturally as you work.

Reading all of it. The attempt to read every document, all the code, and all the meeting minutes mostly fails, and what remains after the failure is self-reproach. It is better to draw a map so you can find things when you need them. Knowing where something is and knowing what it says are different, and what you need early is the former.

Producing a result immediately. For the reasons in section 4, a large early result is worth little. And rushing a result means moving without having drawn the three maps, so the speed of the second month comes back as the accidents of the third.

8. The Ninety-Day Check

At the three-month mark, ask yourself three things.

First, can you say in one sentence what your work is evaluated on. If you cannot, you still know nothing. And this is something you can find out by asking, so there is no reason to leave it unknown.

Second, can you answer where to go when you are stuck, for three kinds of stuck. Stuck technically, stuck because you lack the authority, stuck because another team is not moving. The answers are all different, and all three need to have one.

Third, is there a promise you made here that you have not kept. If there is, deal with that first. An unfulfilled promise from a first quarter is billed far more expensively later.

If even one answer is blurry, pick that area alone and go back to the section above that covers it. Ninety days is not a deadline; it is a checkpoint.

9. One Thing You Can Do Today

Whatever week you are in, make one page. On the left, write down the things in this organization whose reason you still do not know. Why this procedure exists, why that tool is used, why that meeting happens.

On the right, write down who to ask about each item.

Then cross off two a week. Spending the list while the question budget is still there is the whole purpose of it.

Where This Advice Does Not Apply

If you were brought in during a crisis, there is no observation period. Right after a restructuring, a team in the middle of an ongoing outage, a seat a predecessor left suddenly. In these cases, following the order above is too slow. The order there is different. Grab the one thing that is collapsing right now, and draw the maps while holding on to it. Even then, though, the small promises in section 4 still hold. They hold more, if anything.

If you joined as a leader or a senior, the expectations are different. Observing only can read as incompetence rather than as modesty. In these seats you are asked for judgment in the first month, and deferring judgment is itself assessed. The three conditions in section 5 still apply, though. Reach the judgment quickly, but you still have to know first why things are the way they are.

If your employment arrangement puts the evaluation point earlier than ninety days, the frame has to be moved to that point. If the probation review falls in the second month, or a contract renewal decision is made before the quarter is out, the ninety-day frame does not fit. Confirming the real evaluation point and counting backward from it comes first.

If the organization is already coming apart, judgment comes before adaptation. Sometimes you get in and the situation is not what you were told it was. Continuing to try to adapt can become a way of deferring the judgment. It is better to read How to Evaluate a Company and When to Leave and When to Stay alongside this.

And the question budget and the first disagreement in this post work very differently depending on how strongly hierarchical the organization is. What is a good strategy where questions are encouraged works in reverse where a question reads as insufficient preparation. This is why you have to draw the norm map from section 3 before using the methods in this post. Reverse the order and a good method produces a bad outcome.

Finally, one honest note. Spending the first ninety days well does not guarantee what comes after. A favorable early classification only means more opportunities arrive, and what you do inside those opportunities is a separate matter. What this post covers is the position of the starting line, not the finish.

Closing

The goal of a first quarter, in one sentence, is this. Not to produce a result, but to be placed where producing one is possible.

That position is made of three things. Knowing what gets decided where, becoming someone whose word arrives when they said it would, and knowing why things are the way they are before saying they should change.

All three point in the opposite direction from haste. And a failure in the first ninety days almost always comes from haste, not from laziness.