The first 90 days in a new role, without the consulting-speak

Most published 90-day-plan frameworks were written for people walking into a leadership role with a mandate to change things. Applied literally to a mid-level individual contributor's first three months, that advice produces the wrong behavior: showing up trying to change things before understanding why they are the way they are.

Days 1 to 30: build the map, do not touch anything

The goal is not output yet, it is understanding who actually makes which decisions, what has already been tried and failed, and where the real constraints are versus the ones that are just habit. Ship something small and low-risk if the opportunity is there, but treat this month as primarily diagnostic.

Days 31 to 60: take the first real swing

By now the map should be reliable enough to pick one clearly-scoped piece of work and execute it well, visibly, with the people who matter watching. This is less about the size of the win and more about demonstrating judgment: that you picked something worth doing and did it competently.

Days 61 to 90: widen out

With one credible result behind you, this is the window to start contributing opinions on things beyond your immediate task, in code review, in planning discussions, without it reading as overstepping, because context has now been earned to back the opinion up.

The mistake this framework prevents

Arriving with strong opinions formed at the last job and applying them immediately, before learning why this team's version of the problem might be different. Most bad first impressions in a new role trace back to that, not to a lack of skill.