The first three months in a new job are when your reputation gets set, often for good. Managers form lasting impressions early, and a scattershot start — jumping between tasks without a clear sense of priority — is hard to undo later. A 30-60-90 day plan gives you a simple structure to work from, whether or not your manager hands you one.

Days 1-30: Learn before you act

The first month is for absorbing, not proving. Map out who actually makes decisions versus who is listed on the org chart. Sit in on meetings even when you're not required to contribute, and keep a running list of tools, acronyms, and unwritten rules nobody explains but everyone assumes you know. Resist the urge to suggest fixes this early — you don't yet have the context to know why things are the way they are. Instead, ask questions that signal curiosity rather than judgment: "What's the history behind this process?" lands better than "Why do we still do it this way?"

By the end of month one, you should be able to explain your team's goals, your manager's priorities, and how your role fits into both — in your own words, not copied from the job description.

Days 31-60: Take on real, visible work

The second month is where you start contributing independently. Pick one or two problems you can solve without needing to overhaul anything, and deliver them well. Visibility matters here: a solid piece of work that nobody notices does less for you than a smaller win your manager can point to in a review. This is also the point to start building relationships outside your immediate team — a quick introductory chat with someone in an adjacent function pays off later when you need their help fast.

Days 61-90: Show a pattern, not just a result

By the third month, one good deliverable isn't enough — you want a pattern of reliability. Revisit the goals you identified in month one and check whether your work is actually moving them, or just keeping you busy. This is also a natural point to raise your first substantive idea for improvement, now backed by enough firsthand experience that it lands as informed rather than presumptuous.

Close the quarter with a short, honest self-review: what worked, what you'd do differently, and what you still don't understand. Bring that list to your manager rather than waiting for them to ask. It shows self-awareness, and it gives them an opening to tell you things they might otherwise have held back.

What derails this plan

• Trying to fix everything you notice is wrong in week one — most of it is there for reasons you haven't learned yet.
• Going quiet because you don't want to seem like you need help — early questions read as diligence; the same questions three months in read as a gap.
• Measuring your first quarter by how busy you were rather than by what actually moved forward.

None of this requires a formal document or your manager's buy-in. It works as a private checklist just as well as a shared one — the value is in the discipline of pacing yourself, not the paperwork.