Your First 90 Days Back: A Gentle, No-Panic Roadmap

Your first day back is disorienting. Everything is different. The software is different. The people are different. Your brain screams you don't know what you're doing. This is normal. This is temporary. This is what the first 90 days are for.

Week 1-2: Orienting (Your Job: Feel Less Lost)

Monday: The Systems Blitz
Get your laptop working. Get access credentials. Get email running. Get basic infrastructure so you can actually work. At day's end: you should have basic access and one person who can answer questions.

Tuesday-Thursday: Context Collection
Read documentation. Sit in meetings. Ask questions. You're not expected to contribute meaningfully yet. You're collecting information about company priorities, technology changes, reporting structure, what your role should deliver.

Ask your manager: "What are the three most important things I should know in my first week?" Focus on those.

Friday: Small Wins
Do one small meaningful thing. Fix a small bug. Answer a question. Update a document. This is for your confidence. You need to feel you can still do this job.

Meet with your manager 30 minutes. Debrief: What did you learn? What's clear? What's confusing? What do you need?

Week 3-4: Contributing (Your Job: Do Small Things Well)

Identify 1-2 Small, Scoped Projects
Find something completable in one to two weeks. Clearly defined, low complexity, meaningful (not busywork), achievable (you will finish it). Examples: Update documentation. Fix a known issue. Create a process guide. Analyze a dataset.

Develop Your "Landing Narrative"
You'll get asked: "What did you work on while away?" Have a clear answer: "I took time for [reason]. I stayed connected through [specific examples]. I'm excited to be back and bring that perspective to [area]."

Start Building Relationships
Have 1-2 people you check in with. "How's [project] going?" "What's been most challenging?" People like talking about their work. Listen. Remember.

By end of Week 4: Complete one small project successfully. This matters for your confidence.

Month 2: Building Visibility (Your Job: Be Known as Capable)

Speak Up in Meetings
At least once in every meeting, say something. Not brilliant. Just something: "That's a good point." "Have you considered [perspective]?" "I can help with that." You go from "woman who's been away" to "one of the people on this team."

Take On a Cross-Functional Thing
Volunteer for something involving another team. You meet more people, prove you work across teams, build broader network.

Update Your External Presence
Update LinkedIn. Post about being excited to be back. Engage with your network. Signal that you're actively employed and engaged.

By end of Month 2: People should know you're back and capable. You should have completed 2-3 real projects.

Month 3: Owning Your Role (Your Job: Move From Transition to Full Responsibility)

Take On Real Ownership
By month three, you should own something fully. A project. An initiative. A portfolio. Something where you're the decision-maker.

Get Specific Feedback
"I've been back three months now. How am I doing? What's working? What needs to improve? Are we on track with expectations?" You need honest feedback.

Assess Your Confidence
Do you feel like you can do this job? If yes, you're done with onboarding. If no, flag it. "I feel like I'm still in transition mode. What's not clicking? What do I need?"

Three months is reasonable. If you're not there, something needs to change.

Managing Imposter Syndrome

You will feel like you don't know anything. Everyone else seems confident. Everyone else seems to belong. This feeling is normal. It's also not true.

You know how to do this job. You've forgotten specifics. But the core ability is still there. When imposter syndrome creeps in, ask: What evidence do I have that I can't do this? Usually: "I don't know where the documentation is." That's not evidence you can't do the job. That's evidence you need five minutes with Google.

You're not starting over. You're continuing. Trust that.