The First 90 Days in a New Job: A Practical Plan

The first 90 days are for learning the role, building dependable relationships and beginning to deliver—not proving that every previous practice was wrong.

Before joining

Confirm reporting details, role, location and first-day plan. Review public information and your interview notes. Prepare questions, but do not design a strategy without internal context.

Days 1–30: understand

Clarify responsibilities, priorities, success measures, decision rights and immediate deadlines. Map stakeholders and recurring work. Learn systems, customer context, policies and team norms. Agree one-to-one frequency with your manager.

Keep a learning log of terms, decisions and open questions. Look for the real workflow, including hand-offs not shown in the organisation chart.

Days 31–60: contribute

Take ownership of defined work and deliver small reliable results. Confirm priorities in writing, ask for feedback and correct errors early. Build relationships through useful follow-through rather than scheduling introductory meetings with everyone.

Days 61–90: improve responsibly

Use evidence from the first two months to propose improvements. Explain the problem, affected users, options and risk. Start with a manageable change rather than a broad transformation.

Example

A new HR manager notices late payroll inputs. In month one they map owners and cut-offs; in month two they stabilise the exception list; in month three they propose a manager reminder and escalation rule. They avoid replacing the system before understanding why delays occur.

Manager alignment

At each monthly review, discuss outcomes, learning, stakeholders, workload, support and next priorities. Ask what should stop as new work begins. Do not wait until day 90 to discover a different expectation.

Common mistakes

• Promising change before understanding constraints
• Confusing long hours with useful progress
• Avoiding questions to appear experienced
• Building only upward relationships
• Ignoring routine operational work

Create a working stakeholder map

For each important relationship, note what they need from your role, what you need from them, current commitments and the best communication rhythm. Include peers, operational partners and people affected by the work—not only senior leaders. Update the map as you learn where decisions and expertise actually sit.

Separate learning, delivery and improvement

Maintain three short lists. The learning list contains unanswered questions; the delivery list contains commitments with dates; the improvement list contains observations that need evidence. This prevents every unfamiliar practice becoming an immediate change proposal and keeps routine responsibilities visible.

Define a useful 90-day review

Bring your manager a concise account of delivered outcomes, unresolved risks, stakeholder feedback, capability gaps and priorities for the next quarter. Compare progress with the agreed role expectations, not an internet checklist. Where expectations changed after joining, document the new priority and what was deprioritised.

By day 90, aim to be trusted for accurate work, clear communication and sound questions. Mastery of a complex role will take longer; the plan creates a credible foundation.