Your First 30/60/90 Days as a New HRBP

You signed the offer expecting strategic partnership. By day 4, your VP has forwarded an active employee relations case, an engagement survey nobody acted on from two quarters ago, and a comp question they need answered "by end of week, just give me a number." Welcome.

Most new HRBPs walk into team morale that nobody warned them about and 2-3 live ER cases sitting in their inbox before they've finished filling out their I-9. The job is not what the JD said. It's not what your hiring manager described in the interview either. The sooner you stop expecting the version they sold you and start working the version you got, the faster the job becomes survivable.

This is a 90-day plan written for the person walking in, not the person who hired them. It assumes you're an IC HRBP at a B2B SaaS company, supporting one or two business units, and that nobody is going to hand you a runbook.

Why The First 90 Days Set Your Ceiling

HRBPs who don't earn business credibility in the first quarter spend the next two years stuck running engagement surveys and approving PTO. That's the deal. The window to be seen as a partner, not a service desk, closes around day 90, and once it closes it stays closed for a long time. People form their model of "what HR is for" inside the first few interactions, and after that, they call you for what they decided HR is for.

What you do in weeks 1-4 decides whether your VP brings you into the room for the layoff conversation in month 5, or whether they tell you about it after the fact and ask you to handle the comms. Both paths exist. You're picking now.

The signal that you're winning: leaders interrupt their own meetings to text you a question. The signal that you're losing: every interaction starts with someone explaining their role to you because they assume you don't know what they do.

Days 1-30: Listen, Audit, Do Not Fix Anything

The biggest mistake new HRBPs make is trying to ship value in week 2. You don't have value to ship yet. You don't know who's good, who's fragile, where the comp lands, or which manager is one bad week from quitting. Anything you "fix" right now will be the wrong thing.

The job for the first 30 days is to listen at scale and write everything down.

10 manager 1:1s in the first 3 weeks

Every people manager in your scope. No exceptions, including the ones who are "too busy" or "fine, they don't need anything." The fine ones are the most informative.

Same five questions every time. Take notes by hand, not on your laptop. Do not promise anything. Do not solve anything in the room.

The list:

What does success look like for your team in the next 90 days?
Who on your team would you be devastated to lose?
Who is one person you're worried about (performance or flight risk)?
What does HR currently get wrong here?
If I could fix one thing in the next 60 days, what would help you most?

Question 4 is the one that separates good HRBPs from forgettable ones. Most managers will not have been asked this directly before. They'll either give you a polite nothing-answer in the first 90 seconds, or they'll talk for fifteen minutes and you'll learn more about your function than your last three jobs combined. You're listening for the second one.

By the end of week 3 you should have a single document: ten manager interviews, the five answers each, and a "common threads" page on top. The common threads page is the start of your 90-day diagnostic.

Audit the last engagement survey

Open rates by team. eNPS by team. The free-text comments tab that nobody opened. Identify the two teams with the worst scores and the one team with surprisingly good ones.

The good team is your case study. You will reference it for the next two years. What does that manager do that the others don't? Why is psychological safety higher in their org? Who did they hire last and how? You don't need an answer in week 4. You need the question to be sitting in your notebook.

The two worst teams are your near-term risk. Pull regrettable attrition for the last 12 months on those teams and overlay it on the eNPS scores. If the trend lines match, that's a flight-risk pattern, not a survey artifact.

Anti-pattern to avoid here: do not walk into the worst-scoring team's manager and tell them their score in week 4. You don't know enough yet. They will read it as judgment from a stranger. Wait until day 45 minimum, after you've sat in their meetings and heard the context.

Sit on 5 cross-functional meetings

Your VP's staff meeting. A sales pipeline review. A product roadmap review. An engineering retro. A customer escalation call.

You are not there to talk. You are there to learn how the business actually decides things: what gets escalated, what gets shipped, who interrupts whom, where the unspoken hierarchy sits. The org chart will tell you one story. Five meetings will tell you the real one.

If you only get to pick one: the customer escalation call. That's where you find out which team is on fire, which manager is overextended, and what your VP actually values when the stakes are real.

Learn the comp bands

Every level, every function, where the band breaks happen, who is currently below band and why. This is the single fastest way to stop sounding like a generalist.

When a manager asks you a comp question (and they will, in week 2), the difference between "let me get back to you" and "your senior is at the 40th percentile of band, here's what a counter would cost" is the difference between being a partner and being a help desk.

Read the last 2 quarters of board decks if you can get them. The People slide tells you what your CHRO is being asked to defend. If retention is on the slide, retention is the priority. If it's not on the slide, it's not the priority, even if everyone says it is.

Days 31-60: Pick Three Small Wins, Ship Them

By day 31 you've heard enough to act. The temptation now is to act on everything. Don't.

Pick three things. Ship them. Nothing else.

Run 1 manager coaching circle

Five or six managers, 60 minutes, one real situation each. Not training. Peer coaching. You run it, you don't teach.

Pick managers who already trust each other, or who at least won't actively undercut each other. Skip the ones who will dominate. The format is simple: each manager brings one current situation they're stuck on, gets 8 minutes of questions from the group, and walks out with one thing to try.

This is how managers start asking for you by name. After one good circle, your calendar fills with people requesting "the same thing but for my team." That's the goal. Coaching scales the way training never does.

Anti-pattern: do not make this a workshop. The minute you put up slides, you're a trainer, not a partner. Show up with one printed copy of the agenda and a list of follow-up questions. That's it.

Fix 1 broken policy

The one every manager named in your 1:1s. Not the biggest. The most-mentioned.

Common candidates from real HRBP scopes:

A PTO approval flow that takes 9 days to get through three approvers
An internal transfer policy that nobody understands, so nobody uses it
A promotion calibration deck that hasn't been updated in 18 months, so managers are calibrating against ghosts
A probation period rule that's contradicted by the offer letter template

Pick one. Fix it. Send a 4-line note announcing the fix, with credit to the managers who flagged it. The note matters as much as the fix. People need to see that flagging something to you produces a result, otherwise they stop flagging.

Deliver 1 internal mobility recommendation

A real person who should move teams or get promoted, with a written case. One page: who, current role, target role, why now, what the receiving team gets, what the losing team needs to backfill.

This is the move that gets you invited to talent reviews. Most HRBPs in their first year never write one of these unprompted. The ones who do get the calendar invite.

The candidate should be obvious from your 1:1s. If three managers told you about the same person ("she's wasted in that seat"), that's your recommendation. If no name has come up three times, wait another two weeks before forcing it.

What you do not do in days 31-60

You do not redesign the performance review system. You do not propose a new engagement survey vendor. You do not rewrite the EVP. You do not write a manager training curriculum.

New HRBPs who try to fix big things in month 2 lose the room. The visible pattern is: they spend three months on a strategic initiative, present it at a leadership offsite, and watch it get tabled. After that, they spend the rest of their tenure being the person who "had a lot of ideas." Don't be that person. Save the big proposals for the H2 plan in days 61-90, when you've earned the standing to be heard.

Days 61-90: Own A Number, Present A Diagnostic, Propose H2

This is the phase where you stop being the new HRBP and become "our HRBP." Three deliverables. Each one is a public artifact.

Own one engagement metric

eNPS for your BU. Regrettable attrition. Manager effectiveness score. Internal mobility rate. Pick one. Put it on the wall. Report it weekly to your VP.

The choice matters less than the consistency. The metric you own becomes the thing your VP thinks about when they think about you. If you pick eNPS, you're the engagement person. If you pick regrettable attrition, you're the retention person. If you pick internal mobility rate, you're the talent person. There is no wrong answer, only the answer you're willing to defend in front of a finance partner.

The trap to avoid: owning a metric you can't actually move. If your eNPS is currently 18 and the company-wide average is 22, you can probably get to 22 in two quarters with focused work. If your eNPS is currently 18 and your company is in the middle of layoffs, picking eNPS is volunteering to lose. Read the room.

Present a 90-day People diagnostic

Five slides max, presented to your business leader (your VP, not their staff).

The format:

Slide 1: Top 3 risks. Named teams, named issues, evidence (data or pattern from your 1:1s), what you recommend
Slide 2: Top 3 strengths to protect. Team, why it works, what would break it (the high-eNPS team is one of these)
Slide 3: Manager effectiveness. Score by manager, gaps, who needs coaching now (privately, this slide is your political document)
Slide 4: Comp band exposure. Count of below-band ICs, retention risk, cost to fix
Slide 5: Your H2 ask. 3 priorities, 1 metric each, what you need from them

Bring data, not vibes. Every claim on slide 1 needs an evidence column. "Sarah's team has trust issues" is a vibe. "Sarah's team has 41% eNPS, 3 of 8 ICs flagged in 1:1s as flight risk, and one open ER case from October" is a diagnostic.

The slide nobody else will give them is slide 3. CHROs see manager effectiveness in aggregate. VPs see their managers individually. Nobody but you can hand them the version that maps both.

Propose an H2 People plan

Three priorities. One metric per priority. What you need from them.

Keep it short. Three priorities is the maximum a VP can hold in their head between meetings. Five priorities means you have no priorities.

The proposal is the artifact that converts you from "the new HRBP" to "our HRBP." Once it's signed off, you have a mandate, a budget conversation, and a quarterly check-in built in. Without it, you'll spend H2 doing whatever lands in your inbox.

The Hard-News Reality

Somewhere between months 3 and 9, you will deliver hard news. A layoff list. A PIP outcome the employee didn't see coming. A leader exit. A reorg that erases someone's team.

You are not a real partner until you've delivered hard news and the business still trusts you. That's the actual test. Everything before is preamble.

The layoff signal

When leadership starts asking about "performance distribution" or "ratio of ICs to managers" or "what does our cost per head look like compared to peers," that's the prep conversation, not a thought experiment. The numbers always come before the decision. By the time the decision is announced, your CFO has been running the model for six weeks.

If you hear those phrases, your job changes that day. You start tracking who has the most institutional knowledge, who's on a visa, who's on parental leave, who has a comp arrangement that complicates a severance package. You don't volunteer the list. You have it ready when it's asked for.

When your VP asks you to draft the comms before the decision is made

This will happen. The framing is usually casual: "Can you put together a rough script for the all-hands, just so we have something?" The decision is described as still open.

Two things to know. First, the decision is rarely as open as the framing suggests. Drafting the script is part of how leadership commits to a path. Second, you draft it anyway. Refusing on principle is performative; the comms still get written, just by someone with less skill. You draft it, and you flag (in writing, in the document) what's not yet decided and what changes if the decision shifts. That's the protective layer for both of you.

The rule

Never deliver someone else's bad news as if it were yours. Never deliver your own bad news as if it weren't.

The first half: when a VP fires someone, the VP should be in the room. You are there to handle the process and the human moment, not to be the person whose name the employee remembers as "the one who fired me." If you find yourself delivering exits the leader hasn't shown up for, that's a pattern, and the pattern is that the leader is using you as a shield. Push back, in private, every time.

The second half: when you cut a benefit, restructure a policy, or kill a program, name it. Don't hide behind "the company decided" if the decision was yours or your team's. The credibility you build by owning hard calls outweighs the discomfort of the conversation by a factor that will surprise you the first time you do it.

What "Done" Looks Like At Day 90

Run this checklist on day 88. If most of it is true, you've earned the next quarter.

Every manager in scope has had two real conversations with you, not three rescheduled 30-minute slots.
You can name the flight risks in your BU by name, without looking at a doc.
You own one metric your VP cares about, and it's reported weekly without anyone reminding you.
You've shipped one visible policy fix, and at least three managers reference it unprompted.
You've delivered one internal mobility recommendation that landed, meaning the move actually happened, not that the deck was approved.
Your business leader has seen one diagnostic that didn't sound like a generalist wrote it.

If half of this is true, you're on track. If less than half is true, look at where the gap is. It's almost always one of two things: you spent too much time on tickets and not enough on 1:1s, or you tried to ship a strategic initiative before you had the standing for it.

The first 90 days don't make you a great HRBP. They earn you the right to spend the next 12 months becoming one.

HR Business Partner Playbooks