Should I try to make a big impact in my first month?

No — learn first. Ask the questions a newcomer is allowed to ask, meet everyone your role touches, and deliver small things quickly to establish reliability. Sweeping proposals in week two usually misfire because you don't yet know why things are as they are.

How do I make my work visible without bragging?

A short written weekly update to your manager — what you did, what's next, where you're blocked — makes effort legible without self-promotion. Frame outcomes in terms of what your manager is measured on.

When should I ask about promotion criteria?

Around day ninety, in a conversation you schedule yourself. Bring your record of delivery and ask what the next level requires. That turns an informal probation into a documented development plan.

Your first 90 days: turn a new job into a promotion track

July 9, 2026 · 4 min read

Nobody remembers your fourth month in a new job. Everybody remembers your first three. The impressions formed then — reliable or flaky, curious or passive, someone who makes things easier or harder — become the reputation you carry, and reputations are slow to change. The goal for the first ninety days is not to impress with hours or to ship something heroic. It is to build, deliberately, the reputation you want to be stuck with.

The 30 / 60 / 90 shape

Days 1–30: learn loudly. Ask the questions a new person is allowed to ask — how decisions get made, where the real information lives, what has been tried before and why it failed. Write down what you learn. Meet everyone your role touches, not just your team. Deliver small things fast: a document cleaned up, a meeting summarized, a bug fixed. You are establishing that you follow through.

Days 31–60: contribute visibly. Take ownership of one meaningful piece of work with a clear finish line and finish it. Start offering opinions in meetings, grounded in what you learned in the first month. Begin the habit of a short written weekly update to your manager — what you did, what is next, where you are blocked.

Days 61–90: shape something. Propose one improvement to how the team works and carry it through. Ask your manager directly what "exceeding expectations" looks like in this role and what the path to the next level involves. By day ninety you want a written record of delivery and a stated understanding of what promotion requires.

Understand the scoreboard

Every manager is measured on something — a revenue number, a delivery date, a quality metric, a stakeholder's satisfaction. Find out what yours is measured on in your first two weeks and frame your work in those terms. "I finished the migration" is a fact; "the migration is done, which takes the risk off your Q3 date" is a contribution to their scoreboard. People who help their manager hit their number get advocated for.

Keep a wins file from day one

Open a document and, every Friday, add two or three lines: what you delivered, with a number where possible, and who benefited. Six months later this file is your performance review, your promotion case and your updated resume. Memory is unreliable and flattering in the wrong ways; the file is neither.

Build relationships before you need them

Promotions are decided in rooms you are not in, by people comparing notes. Make sure several of those people have a direct, positive experience of working with you. Offer help across teams when it costs you little. Learn the names and roles of the people your manager listens to. A quiet, useful presence in three or four teams is worth more than brilliance visible to one.

Ask for feedback early and specifically

"How am I doing?" gets "fine." "What's one thing I could do differently in how I run our stand-up?" gets a real answer. Ask your manager at thirty days and sixty days, and ask a peer or two as well. Then visibly act on it. Being seen to take feedback is one of the strongest early signals of someone who will grow.

Avoid the common early mistakes

Proposing sweeping changes in week two. You do not yet know why things are the way they are. Learn first; change later.
Working invisibly. Long hours nobody knows about build nothing. Short, written updates make effort legible.
Saying yes to everything. Overcommitting and slipping erases the reliability you are trying to establish. Agree to what you can finish.
Criticizing predecessors. Some of the people who built the mess are still in the room.
Skipping the boring onboarding. Compliance, tooling, documentation — finishing it promptly is itself a signal.

The day-ninety conversation

Schedule it yourself. Bring your wins file and three questions: what has gone well from your manager's view, what they would like to see more of, and what the criteria for the next level are. Write down the answers and send a short recap afterward. You have now converted an informal probation into a documented development plan — and you have done it in a way that marks you as someone who manages their own career, which is exactly what people at the next level do.