I approach the first 90 days in a new job as three overlapping phases: learn the system, earn trust, and begin contributing. I resist the urge to prove myself by changing processes before I understand why they exist.
Days 1–30: I build context
I clarify responsibilities, success measures, meeting rhythms, decision rights, and immediate risks. I map the people who provide information, approve work, use the output, and feel the consequences when something fails.
I keep a running glossary of terms, systems, names, and unanswered questions. I ask how work really moves, not only how the process is documented.
Days 31–60: I take ownership
I begin handling recurring work with less support and look for one contained improvement. I choose something useful but reversible, such as a clearer tracker, handoff note, or reporting check. I involve the people affected before changing it.
Days 61–90: I show reliable judgment
I aim to deliver a visible result, explain what I learned, and propose next priorities. I ask my manager where my view is still incomplete and what greater ownership should look like.
I create regular feedback points
I do not wait for a formal review. I ask brief questions such as: “What should I continue, change, or understand better?” Specific feedback is easier to use than “How am I doing?”
My 90-day document
- Role outcomes and current priorities
- Key stakeholders and preferred communication
- Recurring deadlines and risks
- Questions and assumptions
- Early wins and lessons
- Next-quarter development goals
I want the first 90 days to establish that I learn carefully, communicate early, and deliver what I promise. Speed matters, but informed reliability matters more.