First 90 Days at a New Job

The critical onboarding window where new employees build relationships, demonstrate competence, and establish the reputation that defines the rest of their tenure — with a framework for doing it intentionally.

The first 90 days at a new job are disproportionately important. Research on organizational behavior, popularized by Michael Watkins in 'The First 90 Days,' shows that the impressions formed during this period — how you ask questions, whom you build relationships with, what you prioritize, and how you handle your first visible assignments — are sticky and persistent. The reputation you establish in month one shapes how colleagues interpret your behavior for years. Conversely, false starts — misreading the culture, making premature recommendations, alienating key stakeholders — are hard to recover from because they create negative priors that color all subsequent interactions.

The most common mistake new employees make is trying to prove their value through immediate contributions before they've built the understanding, relationships, and credibility that make contributions land well. This is especially tempting for experienced hires who know exactly what they'd do — but organizations don't just run on competence, they run on trust, context, and relationships. A recommendation from someone who's been there three months and understands the landscape is far more persuasive than the same recommendation from someone who's been there three weeks and is perceived as not yet understanding how things work here. The first 90 days are primarily an investment in the social capital and organizational understanding that makes subsequent work more effective.

Structuring the first 90 days intentionally — rather than letting the calendar fill with whatever comes — dramatically improves both the experience and the outcomes. The common 30-60-90 framework provides a useful scaffold: the first 30 days are for learning and listening (understanding the organization, the team, the role, and the unwritten rules); days 31–60 are for contributing cautiously (taking on real work, proposing improvements in areas where you have context, building cross-functional relationships); days 61–90 are for establishing impact (leading something, making visible progress on a priority, demonstrating the value that justified the hire). The specific milestones vary by role and level — an individual contributor's 90-day plan looks different from a VP's — but the underlying logic applies across levels.

A 30-60-90 Day Framework

  • Days 1–30 — Learn and listen: absorb organizational context, ask questions, meet everyone relevant, understand how decisions are made. Resist the urge to propose changes. Build relationships with your manager, key peers, and important stakeholders.
  • Days 31–60 — Contribute and validate: take on substantive work, make your first visible contributions, start proposing ideas grounded in what you've learned. Get feedback on how you're doing. Clarify your manager's expectations explicitly.
  • Days 61–90 — Establish impact: lead something, deliver a result, make a recommendation that gets implemented. By day 90, your team should be able to articulate what you've contributed.
  • Throughout: over-communicate with your manager. The most common early-tenure failure is under-communicating progress and blockers. A brief weekly email or 1:1 agenda item is the simplest insurance.
  • Request explicit feedback at day 30 and 60: 'I'm at the one-month mark — what am I doing well and where should I adjust?' is one of the highest-value conversations you can initiate.

What New Employees Underestimate

Most new employees underestimate how much the informal social infrastructure — who trusts whom, which relationships matter, what's not in the org chart — affects how work actually gets done. In the first 90 days, time spent having lunch with a peer, joining an informal working group, or asking a senior colleague for a 30-minute knowledge-sharing call creates social capital that makes every subsequent piece of work land more effectively. New employees also underestimate the importance of psychological safety with their manager: if you don't establish a pattern of honest communication early (including sharing where you're struggling or what you don't understand), you make the first failure much more consequential. The managers who most consistently report success with new hires cite 'they weren't afraid to say they didn't know something' as a top factor.

Example

A new director of engineering joins a company that had been struggling with on-call reliability. In her first 30 days she interviews every team member, sits in on incident reviews, and reads the last 12 months of post-mortems — listening only. At day 45 she proposes a structured on-call rotation change grounded in specific data from those post-mortems. The recommendation is implemented within two weeks because she built the credibility and context to be believed. The same recommendation made on day 3 would have been received as premature.