The first month of a new IT role is about orientation, not heroics. Your goal isn't to fix the hardest ticket — it's to understand how this place works, who to ask, and where the landmines are. Do that and competence follows naturally.
Week 1 — Learn the lay of the land
- Map the environment: what OS, what directory service (Active Directory / Entra), what ticketing system, what remote-access tools.
- Get your accounts and access sorted, and write down exactly what you have and don't.
- Find the documentation — the wiki, the runbooks, the shared drive. If there's none, that's useful to know too.
- Identify the two or three people who actually know how things work. Be friendly and take notes.
Week 2 — Shadow and absorb
- Watch how tickets flow from open to closed, and match the team's tone in your own.
- Learn the top ten recurring issues — password resets, VPN, printers, onboarding. Most tickets are a handful of repeats.
- Ask "what's the right way to do X here?" freely. Asking early reads as diligence; asking late reads as guessing.
Weeks 3–4 — Start owning work
- Take real tickets end to end, and document what you did so the next person benefits.
- Under-promise and over-deliver on timelines; a clear "I'll have this by 3pm" builds more trust than speed.
- When you're stuck, show your work: "here's what I tried, here's where it broke" — that's how seniors want to be asked.
The mindset that gets you kept
New hires who last aren't the ones who knew the most — they're the ones who were reliable, honest about what they didn't know, and easy to hand a task to. Curiosity plus follow-through beats raw knowledge in month one, every time.
Walk in with the whole checklist done for you
The First 30 Days in a New IT Job Checklist turns this into a day-by-day, printable plan — exactly what to learn, ask, and document each week so you ramp faster and stand out early. Instant download.
Get the checklist →