First 90 Days at New Job: What to Do and Avoid
Published by StepUpCareer ·
Make your first 90 days at a new job count. Use our 30-60-90 plan, week-by-week checklist, one-on-one agenda, feedback prompts, and probation review template. India-aware guidance with cited sources.
Read this first
Your first 90 days set expectations, trust, and working rhythms. Focus on four tracks from day one:
- Learn: systems, processes, customers, success criteria
- People: manager, teammates, cross‑functional partners
- Performance: a few meaningful early wins
- Ways of working: communication, prioritization, and feedback loops
This guide gives you a ready-to-use 30‑60‑90 plan, week-by-week checklist, meeting scripts, feedback prompts, and a probation review template. Claims about “the exact process everywhere” don’t exist; adapt to your team and company. For clarifying expectations and role goals, see guidance from Indeed India source. For why you should avoid big changes before understanding context, see Cisco Talent Bridge source.
What success looks like by day 90
By the end of your third month, aim to be able to:
- Explain your team’s goals, how your work contributes, and key stakeholders
- Demonstrate a few concrete wins that matter to your manager and customers
- Run effective one‑on‑ones and communicate updates without prompting
- Prioritize confidently using your team’s criteria and trade‑offs
- Ask for and integrate feedback regularly
Your 30‑60‑90 day plan (copy, adapt, and use)
Create a living document with four sections. Keep it simple and visible to your manager.
30 days (orient and learn)
- Learn
- Map systems, tools, core processes; note unknowns
- Shadow a teammate; read playbooks and prior project docs
- People
- Schedule intro 1:1s with manager, teammates, key partners
- Ask each person: what “great” looks like from this role
- Performance
- Identify 1–2 small, low‑risk tasks you can complete end‑to‑end
- Ways of working
- Confirm update cadence, preferred channels, and decision norms
60 days (contribute and refine)
- Learn
- Close knowledge gaps; document what you learn for the team wiki
- People
- Co‑own a cross‑functional task; clarify handoffs and SLAs
- Performance
- Deliver one medium‑scope improvement or project milestone
- Ways of working
- Share a weekly summary: progress, risks, asks for help
90 days (own and improve)
- Learn
- Propose a focused learning plan for next quarter
- People
- Mentor a newer teammate on one workflow you now own
- Performance
- Ship a meaningful deliverable; report impact using agreed metrics
- Ways of working
- Run a short retro: what to start/stop/continue next quarter
Tip: Walk through a draft of this plan with your manager in week 1–2 to align expectations Indeed India.
Week-by-week checklist (first 12 weeks)
Week 1
- Access: tools, accounts, trackers, project boards
- Ask your manager: top three outcomes that matter in the next month
- Schedule 1:1s with immediate team and key partners
Weeks 2–4
- Document how work gets planned, prioritized, and reviewed
- Complete at least one contained task; share what you learned
- Start a weekly update to your manager (bullets: done, next, risks)
Weeks 5–8
- Take ownership of a small project/workstream; confirm definition of done
- Run a midpoint check‑in: are we on track for your 60‑day goals?
- Capture recurring questions and propose one improvement to reduce them
Weeks 9–12
- Deliver a visible outcome and a brief readout: context, actions, results, lessons
- Collect feedback from manager and 2–3 partners
- Draft your probation review notes and next‑quarter focus
One‑on‑one agenda you can reuse
Use this 30‑minute outline for regular 1:1s.
- 5 min: Quick wins/updates since last time
- 10 min: Current priorities (progress, blockers, decisions needed)
- 10 min: Feedback both ways (what to do more/less/differently)
- 5 min: Next steps and confirmations
Message template to book first 1:1s “Hi [Name], I’m new to [team]. I’d love 20 minutes to learn how our work connects and how I can make collaboration easy for you. Would [two time options] work?”
Stakeholder map template
List your key collaborators. Capture their goals and how your work helps.
- Name / Role
- What success looks like for them
- How our work connects (inputs/outputs)
- Preferred channel and response time
- Current asks / commitments
Feedback prompts that get useful answers
Ask specific questions to reduce vague advice Indeed India.
- “What’s one thing I should do more of this week?”
- “What’s one thing I should stop doing to be more effective?”
- “If this project slips, where is it most likely to happen?”
- “How do you prefer to receive updates: format, timing, detail?”
How to ask by message “Could I get 10 minutes of candid feedback this week on [task]? One thing I did well and one thing to improve would be very helpful.”
Early‑win ideas (pick one that fits your team)
- Reduce a recurring manual task by documenting steps and pitfalls
- Fix a small but visible pain point in a dashboard, template, or handoff
- Close an unowned ticket/bug/queue item end‑to‑end and write the SOP
- Draft FAQs for new teammates based on questions you asked in month 1
Why small wins first? They build credibility and reveal real constraints before you suggest bigger changes—avoid proposing sweeping changes until you understand context Cisco Talent Bridge.
What to avoid (and what to do instead)
- Don’t propose large process changes immediately
- Do: map current workflows, pain points, and constraints first Cisco Talent Bridge
- Don’t overcommit across too many streams
- Do: confirm priorities and definition of done with your manager
- Don’t assume unspoken norms
- Do: ask about decision rights, review cadence, and communication styles
- Don’t work in isolation
- Do: schedule regular syncs; share progress and risks early
Remote or hybrid? Adjust these three things
- Visibility: share concise weekly updates in the agreed channel (link artifacts)
- Relationship building: book short virtual coffees with key partners in weeks 1–3
- Meeting hygiene: send agendas, keep notes, confirm owners and due dates
Probation review prep checklist (save this)
Two weeks before your review:
- Collect: your 30‑60‑90 plan, shipped work, messages that show stakeholder value
- Summarize wins: what changed, how you measured success, what you learned
- Share lessons: what didn’t work and how you adjusted
- Propose next‑quarter focus: outcomes, dependencies, support needed
Self‑review template
- Role outcomes I focused on:
- Deliverables shipped (with links):
- Feedback themes and actions I took:
- Biggest lesson and how I’ll apply it:
- Proposed goals for the next quarter:
Useful mini‑tools you can copy today
- Weekly update skeleton
- Done:
- Next:
- Risks/Asks:
- Decision log
- Date / Decision / Why / Alternatives / Owner
- Meeting notes
- Purpose / Key points / Decisions / Owners & dates
Light StepUpCareer tie‑ins (optional)
- Resume upkeep: As you complete wins, keep a running list of results you could turn into resume bullets later. If you decide to refresh your resume, you can draft quickly with our Builder at stepupcareer.in/builder.
- When targeting internal roles or future applications, learn how to mirror role language thoughtfully: see our guide on matching job‑description keywords at stepupcareer.in/blog/job-description-keywords-how-to-match-your-resume.
FAQs
- How detailed should my 30‑60‑90 plan be?
- One page is usually enough to align on direction; add details as you learn.
- What if my manager doesn’t give clear goals?
- Propose a draft based on team priorities, ask “what would you change?” and confirm definition of done for the next two weeks Indeed India.
- How soon should I suggest improvements?
- After you can describe the current workflow, constraints, and trade‑offs. Start with reversible, low‑risk tweaks Cisco Talent Bridge.
AI assistance disclosure: Draft developed with AI support for structure and wording. It provides general guidance and templates, not legal or HR advice. Always follow your company’s policies and your manager’s direction.