Your First 90 Days: Starting Strong at a New Company

Careers are often decided at transitions. The first few weeks in a new role are the first one you'll face, and the one most people rush.

You got the job. You want to prove they made the right call. So you show up with ideas, fill your calendar, and start fixing things by Thursday.

That instinct is understandable. It's also how a lot of good people burn credibility they haven't earned yet.

The best start I ever had at a company began with doing something simple but difficult.

I listened.

My leader and peers told me to take the first couple of days to meet people, have coffees, and get a lay of the land. My calendar filled quickly with recurring meetings and onboarding calls with HR, IT and so on. I protected my time anyway and declined almost all of them (except the HR one).

Two things happened. First, I showed I take advice seriously, especially from my boss. Second, I learned more in two days of listening than I could have learned in weeks of acting. I took detailed notes, asked follow-up questions, and didn't try to impress anyone. Only after that did I build a 30-day plan, which then shaped my 60 and 90.

This module gives you that playbook: how to listen on purpose, how to turn it into a plan, and how to pick the first wins that actually count.

The short version

• Listen before you launch. Your first two weeks are for context, not output. Context gives you credibility.
• Don't over-engineer your start. A 30-60-90 plan written before Day One is mostly guesswork. Write it after you've listened.
• Get close to the customer and the frontline fast. That's where you learn which problems are real and which are just loud.
• Respect what came before. Most "obviously broken" systems exist because of constraints you can't see yet.
• Don't judge the company by Day One. A rough first day says very little about the job.

Listen first: the LISTEN framework

Even a great interview process won't show you the real power dynamics, the unwritten rules, why things are done the way they are, or which problems are real versus just loud. You only learn those by being there and paying attention.

Here's the framework I use.

1. Learn the unwritten rules. Who actually makes decisions? Does this team prefer Slack or email? Are meetings for debate or for confirming decisions already made? Watch before you assume.
2. Invest in relationships early. Book 20-minute coffees with your teammates, the people your work feeds into, and the people whose work feeds you. Ask, don't pitch.
3. Sit with customers and frontline teams. Whatever your role, get close to the people doing the real work. Sit in on sales calls. Read support tickets. Watch how work actually happens.
4. Take advice seriously. If your manager tells you to spend week one meeting people, do exactly that. Following early advice is the fastest trust signal you can send.
5. Earn trust before change. Early in my career I thought many things obviously needed to change. Over time I learned most systems exist for reasons you don't see yet. Respecting what came before builds trust with the people who are still there.
6. Never judge the company by Day One. One of the best companies I ever worked for had one of the worst first days. The entire team was on holiday in another country. Nobody answered emails or calls. Instead of reacting, I used the quiet to read, explore systems, and understand customers. It became one of the best experiences of my career.

Key idea: Listening first gives you context. Context gives you credibility. Credibility is what lets you change things later.

The three questions to ask everyone

You don't need a fancy script. In every early conversation, ask some version of:

1. "What's working well here that I should be careful not to break?"
2. "What's one thing that slows you down every week?"
3. "Who else should I talk to?"

The third question is the one people skip. It builds your map of the organization for you, one name at a time.

Turn listening into a 30-60-90 plan

Unless your manager explicitly asks for a 30-60-90 plan before you start, don't build one yet. Build it at the end of week two, when you actually know something.

A 30-60-90 plan is just a simple document that says what you'll focus on in your first 30, 60 and 90 days. Keep each phase to three or four outcomes.

Then take it to your manager and ask one question: "Is this what success looks like to you?" Their edits are the most valuable thing on the page. You're aligning on expectations before anyone writes your first review.

Pick the right early wins

You'll feel pressure to show value fast. That's fair. Just pick the right kind of win.

Good early wins are small, useful to someone else, and come straight out of your listening. If three people mentioned the same annoying weekly report, fixing that report beats any big strategy deck. It shows you heard them.

Bad early wins are the ones that rewrite something a respected teammate built, before you understand why they built it that way.

What it looks like in practice

A composite example. Say Priya just started as an operations coordinator at a regional logistics company. Her old job was at a bigger firm, and on day two she can already see three processes she'd "fix."

Instead, she spends her first two weeks running the listening tour. She books twelve coffees, sits with the dispatch team for two mornings, and reads a week of customer complaint emails. She asks everyone the same three questions and keeps notes in one doc.

A pattern shows up fast. Dispatchers re-enter the same delivery data into two systems every afternoon. Nobody likes it, but nobody owns fixing it. And one of the processes Priya wanted to change on day two? It exists because of a contract with their largest customer. Good thing she didn't touch it.

At the end of week two she writes a one-page 30-60-90 plan. Her 60-day goal: cut the double entry with a simple shared template. She shows the plan to her manager, who moves one priority up and adds a relationship she'd missed.

By day 60 the dispatch team saves about 30 minutes a day, and they tell people Priya was the one who listened. That reputation is worth more than the time saved.

Common traps

• Arriving with the answers. "At my last company we..." is the fastest way to lose a room. Fix: ask how things work here first, then offer the comparison only when asked.
• Letting the calendar run you. Onboarding meetings expand to fill your week. Fix: protect blocks for coffees and frontline time, the same way you'd protect a client meeting.
• Writing the plan too early. A plan built on interview impressions points you at the wrong problems. Fix: listen for two weeks, then write it.
• Only meeting up. New hires court their boss and skip the frontline. Fix: at least half of your early conversations should be with peers and the people closest to customers.
• Panicking over a rough start. Bad laptop, no desk, everyone on holiday. Fix: use the quiet to read, explore systems, and learn the customer.

Do this this week

If you're starting a new job soon, or you started in the last few months, run a mini listening tour.

1. List eight people: your manager, three teammates, two people in teams you work with, and two people closest to customers.
2. Book 20 minutes with each. Ask the three questions above and write down exact phrases they use.
3. Highlight anything that came up three or more times. That's your shortlist of real problems.
4. Draft a one-page 30-60-90 plan from that list and ask your manager, "Is this what success looks like to you?"

Your tool

CopyFIRST 90 DAYS: LISTENING TOUR + PLAN

PART 1: LISTENING TOUR (Days 1-14)
Who to meet (aim for 8-12):
[ ] My manager
[ ] 3 teammates
[ ] 2 people in teams my work feeds into
[ ] 2 people whose work feeds me
[ ] 2 people closest to customers (support, sales, frontline)
[ ] Anyone else I get referred to

Questions for every conversation:
1. What's working well here that I should be careful not to break?
2. What's one thing that slows you down every week?
3. What do you wish the person in my role did more (or less) of?
4. Who else should I talk to?

Notes template (one line per person):
Name | Role | What's working | What slows them | Who to meet next

Unwritten rules I've noticed:
- How decisions actually get made:
- Preferred channel (Slack / email / in person):
- What meetings are for here:
- What "good" looks like to my manager:

PART 2: PATTERNS (end of week 2)
Problems mentioned 3+ times:
1.
2.
3.
Things that look broken but exist for a reason:
-

PART 3: 30-60-90 PLAN (one page)
Days 1-30, LEARN. Outcomes:
1.
2.
3.
Days 31-60, CONTRIBUTE. Early win(s) from my patterns list:
1.
2.
Days 61-90, OWN. The lane I want to be known for:
1.

PART 4: ALIGN
Question for my manager: "Is this what success looks like to you?"
Their edits:
Next check-in date:

Talk about it

1. Think of a time you (or someone you watched) changed something too early at a new job. What context were they missing?
2. Which of the six LISTEN steps comes least naturally to you, and why?
3. What's the difference between an early win that earns trust and one that spends it?

— Evan