Starting a New Job

Not because your employer is careless. Because almost nobody has a real system for this.

Before planning anything, it is worth seeing the shape of the problem. These are the conditions you are actually walking into, and they are remarkably consistent across industries and company sizes.

Read those together and a picture forms. The person responsible for integrating you probably has no training in doing it, was given a template rather than a process, and is busy. That is not a complaint — it is a planning assumption. If you wait to be onboarded, you will spend your most valuable weeks waiting.

It is rarely what the job description said, and it is never written down.

Every organisation has an official set of values and an actual set of behaviours that get people promoted. The gap between them is not hypocrisy — it is just that culture is emergent and slogans are written. Your first month is for finding the second set.

The four questions that reveal it

1. Who gets listened to in meetings, and why? Watch for whether it tracks title, tenure, technical depth, or proximity to revenue. That tells you what currency this place runs on.
2. What gets escalated, and what gets absorbed? The things people quietly fix without telling anyone are the things this organisation does not reward.
3. What was the last thing that went badly, and what happened afterwards? The response to failure tells you more about a culture than any values page.
4. Who left recently, and what is the story people tell about it? The story is more informative than the truth.

You are not being cynical by asking these. You are doing the diagnosis that determines whether your effort lands anywhere.

The pressure to produce something early is real. Resist it for four weeks.

The instinct in month one is to demonstrate value fast. It is the wrong instinct, because you do not yet know which value counts. Month one has exactly three jobs: map the people, find the real problems, and establish that you are someone who asks good questions.

The meeting map

Book fifteen to twenty short conversations in your first three weeks. Not to network — to build a model of how work actually moves. Each conversation has one question that does the work.

Set the success definition in writing

If your manager has not defined what good looks like at 30, 60, and 90 days — and statistically they probably have not — write your version and send it to them. This is not presumptuous. For a manager who has never been trained in this, it is a relief.

Subject: My read on the first 90 days — sanity check?

Hi [name],

Writing down how I'm planning to use the first three months
so you can tell me where I've got it wrong.

Days 1–30: meet [the teams], understand [the systems], no
  major changes.
Days 31–60: take ownership of [area], and aim to have [the
  specific early win] done.
Days 61–90: [the bigger thing].

Two questions:
  1. What's missing or mis-prioritised here?
  2. What would make you say at 90 days that this has gone well?

[name]

One. Chosen for visibility as much as for value.

By day 30 you should have a list of things that are broken. Do not fix all of them. Pick one, and pick it against four criteria.

1. Finishable inside four weeks. An unfinished ambitious thing is worth less than a finished modest one at this stage.
2. Visible to someone outside your immediate team. This is what turns a win into a reputation.
3. Nobody currently owns it. Taking over someone else's problem in month two creates an enemy you do not need.
4. It irritates people. The best early win is a small, chronic annoyance everyone has accepted. Fixing it buys disproportionate goodwill.

That last criterion is the one people underweight. A modest fix to something that annoys twelve people every week will do more for your standing than a technically superior contribution nobody feels.

The check most people skip, and the one that saves jobs.

Around day 60, stop and run an honest audit. You now have enough information to tell whether your read on the job was right, and enough time left to correct it if it was not. Leave it to day 90 and you are correcting under review pressure instead of ahead of it.

Signals you have misread the job

• The work you were hired to do keeps getting deprioritised in favour of something else. That something else is the real job.
• Your manager's attention is consistently on a problem you are not working on.
• You are being invited to fewer meetings than you were in week two, not more.
• The thing you were told was the top priority has not been mentioned since your first week.
• People keep bringing you work that does not resemble your job description — and it is the same kind of work each time.

None of these mean you made a mistake taking the job. They usually mean the role was described accurately at the time and the organisation has since moved. That happens constantly. What matters is whether you move with it or spend six months excellently doing something nobody needs.

I want to check something before I'm too far down a path.

When I started, I understood the priority as [X]. What I'm
actually seeing pull on your attention is [Y].

Which of those should I be organised around? I'd rather
adjust now than at the six-month mark.

Stop being the new person. Start being the person something belongs to.

The last third is about transition of status. Up to now you have been someone being integrated. From here you want to be someone who owns a defined thing, whose judgement is sought on it, and who no longer needs to be checked.

• Take formal ownership of something. Named, in writing, in a place other people can see. Ambiguous ownership at day 90 tends to still be ambiguous at day 300.
• Start saying no to something. The first considered no is what marks the end of the new-hire period. Do it once, with a reason, on something genuinely low value.
• Make one relationship outside your function real. Cross-team relationships built in month three are cheap; built in year two they are work.
• Write the summary before your review, not after the request for one. Three bullets: what you found, what you changed, what you are taking on next.

Subject: 90-day summary

Hi [name],

Three bullets before our check-in.

What I found: [one specific observation about the team or
  system that was not obvious from outside].
What I changed: [the early win, in one sentence, with the
  concrete result].
What I'm taking on next: [the ownership commitment for the
  next quarter].

Two open questions I'd like your read on: [X] and [Y].

[name]

It is normal, it usually fades, and there is a version of it that is worth taking seriously.

The first few weeks of a new job frequently come with a specific kind of low-grade dread — the sense that a mistake is imminent, that you were hired by mistake, that the honeymoon is going to end abruptly and unpleasantly. This is common enough that it counts as part of the experience rather than an anomaly. It usually softens somewhere between weeks four and eight, once you have enough evidence about how the place works to stop having to guess.

The thing that helps most is not a mindset shift. It is the mechanical work of this guide — meetings booked, questions asked, a definition of success written down and confirmed. Concrete evidence quietens the noise faster than any amount of self-talk.