Oaks Co. · Playbook Series

Talent Acquisition
Playbook

From hire to perform — a complete guide for hiring managers, recruiters, and HR leaders. From planning the role, to landing the person, to making sure they actually perform.

Position · Person · Performance 11 Sections End-to-End Interactive
01 · Why This Playbook Exists

Most hiring playbooks end at the offer letter. This one doesn't.

Because a signed contract isn't a successful hire. A performing, motivated employee at month 12 is.

If you've been in HR or hiring long enough, you've seen it. The offer gets signed, the req closes, everyone celebrates — and six months later the new hire quietly resigns. Or worse, they stay but never click. The role is filled on paper, but the hire failed.

Most of the time, the failure didn't happen during probation. It happened much earlier — at hiring. Fuzzy role clarity. Rushed interviews. A gut-feel offer. A weak handoff to onboarding. By the time probation issues surface, the real damage was done months before.

This playbook treats talent acquisition as what it actually is: a 12-month discipline, not a 4-week process. It starts before the req is opened and ends when the person is performing, engaged, and embedded.

The real cost of a bad hire

Recruitment fees and salary are only the visible costs. The full cost is steeper than most leaders realize — and the research is consistent across sources.

Direct cost
30%

Minimum cost of a bad hire as a share of first-year salary. For managerial or specialized roles, this can climb to 50% or more.

Source: U.S. Department of Labor

Replacement cost
50–200%

Cost to replace an employee, expressed as a percentage of their annual salary. Senior roles tend toward the upper end.

Source: SHRM

Team cost
85%

Share of hiring professionals who report that a bad hire negatively affected the entire team, not just the company's balance sheet.

Source: LinkedIn hiring survey

A separate Gallup study finds that a new hire typically takes around 12 months to reach full performance potential — meaning a hire that fails at month 5 represents nearly half a year of paid ramp-up with no return.

The framework that holds this playbook together

Every decision in this playbook traces back to a single triangle. Before you hire anyone, you need clarity on three things — and each one is defined at a different stage.

The Core Framework
Defined Before Hire

Position

Scope, competencies, success indicators, and salary range. This is the job scorecard — written before the req opens.

Assessed During Hire

Person

Can-do and will-do attitude. Tested through CBI, hypothetical scenarios, and the 4-Fits calibration.

Proven After Hire

Performance

Only visible once they're in the seat. Why onboarding & probation are TA's responsibility, not a separate team's.

→ Clarity upstream
→ Rigor during
→ Accountability after

If the Position isn't clear before you open the req, everything downstream is guesswork. If the Person assessment is sloppy, you're gambling on gut feel. And if no one owns the Performance horizon, hiring becomes a transaction instead of a relationship.

The point of view

Talent acquisition doesn't end at a signed offer. It ends at a performing, motivated employee at month 12. If probation fails, TA failed too — not just the leader.

Who this playbook is for

If you do any of these things, this is for you: write job descriptions, screen candidates, interview, decide who to hire, make offers, or own the handoff to onboarding. That means hiring managers, team leads, recruiters, HR business partners, and founders doing their own hiring.

How to use it

Read it cover to cover once, to internalize the framework. Then use it as a working reference — the toolkits are the real product. Every section ends with a template or canvas you can copy and adapt.

02 · Before You Hire

Before you open any req, ask: should we develop someone instead?

Hiring is the default answer. It shouldn't be.

When a role opens up, the instinct is to post it externally. But the best hire isn't always an external hire. Sometimes the right answer is to promote someone who's already earned it, stretch someone who's ready, or develop a high-potential into the role over 3–6 months.

Developing is slower upfront but cheaper overall. It builds loyalty, compresses onboarding (they already know the culture), and sends a signal to the rest of the team that growth is real here. Hiring is faster but requires rigor to not fail — and as the cost data in Section 01 shows, a failed hire is expensive.

The decision depends on two things: is the skill gap trainable in a reasonable timeframe, and do you have a leader with coaching capacity to bridge it?

Toolkit · Interactive

Hire vs. Develop Decision Tree

Answer three questions. Get a recommendation.

Question 01
Is the core skill gap trainable within 3–6 months?
Recommendation

Develop internally

You have all three ingredients: a trainable gap, a motivated internal candidate, and a leader who can coach. Developing is the higher-ROI move here.

Next steps: Write a 90-day development plan. Define stretch assignments. Set biweekly check-ins with the leader. Promote with clear expectations, not as a reward.

Recommendation

Hire externally

The skill gap isn't quickly trainable, or you don't have the internal conditions to develop. Hire — but hire with full rigor using the rest of this playbook.

Next steps: Start at Position (tab 04) — Defining the Ideal Candidate. Write the job scorecard before you post anything.

Recommendation

Hire — but stop and check first

You have a trainable gap and a candidate, but the leader doesn't have coaching capacity. Developing without coaching usually fails. Two options:

  • Option A: Hire externally, but plan to invest in leader coaching skills in parallel.
  • Option B: Develop internally with explicit external coaching support (mentor, external coach, or buddy-leader).

A note on hire-to-develop

Sometimes you'll hire at a lower level intending to develop the person into a bigger role. This is valid — but only if the hiring leader is genuinely ready to coach, and the role has time to grow into. Hiring "cheap to develop" without coaching capacity is one of the most common hiring failures in startups.

Reminder

Developing doesn't mean lowering your standards. It means raising someone into a standard — with the right support in place.

03 · End-to-End View

The Talent Acquisition funnel — eight stages, one discipline.

Good hiring isn't one big decision. It's a sequence of smaller decisions, each with its own purpose, owner, and standard.

This section maps the full funnel at a glance. Later pages go deep on interviewing, offering, and the handoff. For each stage below, you'll find purpose, owner, and a preview of the tips and toolkits you'll get later.

01
Talent Planning

Manpower plan. Target candidate profile. Position clarity. The "Position" corner of P-P-P gets defined here.

Leader + HR
02
Talent Marketing

Job portals, ATS setup, employer branding. Where will the right people actually see this role?

Recruiter
03
Sourcing

Active outreach, referrals, passive channels. The funnel gets wide here — or it doesn't.

Recruiter
04
Screening

CV review, portfolio review, phone screen. First meaningful filter against the scorecard.

Recruiter
05
Interviewing

Can-do & will-do. CBI, hypothetical scenarios, 4-Fits. The heart of the playbook.

Hiring Mgr + Panel
06
Offering

Salary band logic, negotiation protocol, offer conversation. The fairest offer you can defend.

HR + Leader
07
Pre-Employment

Reference check, background check, contract. Legal and logistical readiness before Day 1.

HR
08
Onboarding Handoff

The 5C's bridge: Compliance, Clarification, Confidence, Connection, Culture. TA's last job.

HR + Leader
"If your funnel breaks at stage 05, the fix usually lives at stage 01. Fuzzy planning leaks downstream."
— The Rule of Upstream Clarity

A few patterns worth naming before we go deep:

The funnel leaks at the top, not the bottom. Most hiring failures are traced to weak planning (stage 01) and weak marketing (stage 02), not weak interviewing. If your interview panel keeps rejecting candidates, the problem is probably upstream.

Each stage has a single accountable owner. Shared accountability is no accountability. If both the recruiter and the hiring manager "own" screening, neither does.

Speed and rigor aren't opposites. The fastest hiring processes are the most rigorous ones — because they don't waste cycles on unclear roles, misaligned panels, or re-interviews. Rigor at stage 01 saves weeks at stage 05.

04 · Defining the Ideal Candidate

Position clarity is the highest-leverage work in the entire funnel.

If you can't write a job scorecard, you're not ready to open the req.

This is the Position corner of the P-P-P triangle. Everything downstream — the job post, the sourcing strategy, the interview questions, the offer, the onboarding plan — depends on getting this right. Fuzzy position clarity is the single biggest reason hires fail.

A well-defined position answers four questions: what outcomes the role must deliver, what competencies are required, which are must-have on day one, and what "fit" looks like for this specific role, team, leader, and company.

Below, two things you can use today. First, a worked example showing what a finished Job Scorecard looks like. Then, a visual model for the 4 Fits — interactive, so you can score a candidate and see the shape of their fit profile.

Worked Example · What "Good" Looks Like

Senior Product Manager — B2C Growth

Drafted by hiring leader · Reviewed by HR · Approved before req opens
Sample
Role Basics
Title
Senior Product Manager, Growth
Grade / Level
5B — Senior IC, IDR 45–58M/mo band
Reports to
Head of Product (Adi)
Team
Growth squad · 1 PM, 4 ENG, 1 DS, 1 Design
Why this role exists
To own the activation funnel end-to-end and lift activation rate from 38% to 55% within 12 months — unlocking the next stage of revenue growth without expanding paid acquisition spend.
Outcomes — Measurable, Not Activities
90 days
Onboarded fully. Diagnosed the top 3 drop-off points in the activation funnel using SQL + product analytics. Shipped one quick-win experiment with measurable lift.
6 mo
Owns full activation roadmap. Shipped 2 major releases tied to activation. Activation rate up at least 5 percentage points. Weekly cadence established with data + design.
12 mo
Activation reaches 55% target. Growth product team grown to 2 PMs. Selected and onboarded the second PM. Recognized internally as the growth product authority.
Competencies — Knowledge · Skill · Attitude
Knowledge
  • B2C growth product experience (3+ yrs)
  • Experimentation frameworks (A/B testing)
  • SQL literacy — can self-serve queries
  • Indonesia market familiarity
Skill
  • Writes crisp PRDs (will request a sample)
  • Runs experiments end-to-end
  • Leads cross-functional squads
  • Communicates with execs in their language
Attitude
  • Ownership mindset — "the buck stops here"
  • Intellectual honesty about data
  • Comfortable with ambiguity
  • Coaches teammates, not just delivers
Must-have vs. Nice-to-have
⚠ Must-have on Day 1
  • · B2C growth product experience (non-negotiable)
  • · SQL literacy
  • · Ownership mindset
  • · Experimentation experience
✓ Nice-to-have (developable)
  • · Indonesia market familiarity
  • · People management experience
  • · Direct exec communication exposure

The 4 Fits — and why they need their own model

Position clarity goes beyond competencies. Two candidates with identical skills can land in completely different places: one thrives, one washes out. The difference is usually fit — and fit isn't one thing, it's four.

Most hiring teams treat "culture fit" as a single yes/no. That's why hires fail in surprising ways: someone aligned to the company values can still flame out under the wrong leader, or in a team whose dynamic doesn't match them. We need a sharper tool.

Visual Model · Interactive

The Fit Compass

Score a candidate across the four fits. Watch the shape change. A balanced diamond means strong all-around fit. A lopsided shape is a warning sign worth investigating before the offer.

50 100 Company Values · Mission Leader Style · Feedback Job Daily Work · Motivation Team Dynamic · Rhythm
Company fit
75
Alignment with values, mission, way the company operates
Leader fit
75
Match with direct leader's style, expectations, feedback rhythm
Job fit
75
Motivational fit with the actual day-to-day work itself
Team fit
75
Compatibility with team's rhythm, norms, and unspoken dynamics
Reading the shape
Balanced fit — investigate before offering
Move the sliders to see how the shape changes. A symmetrical diamond at high values means strong all-around fit. Asymmetry is a signal that one corner deserves deeper interview attention.

How to read the compass

The Fit Compass turns a fuzzy concept ("culture fit") into a concrete, debatable picture. In hiring debriefs, instead of arguing "is this person a fit?" — interviewers each plot their compass, and the team discusses where the shapes disagree. Disagreement on the Leader axis means the next interview should probe how the candidate works under a leader like yours. Disagreement on Team means the team meet should be longer.

The shape is more important than the area. A small but balanced diamond can be a developable hire. A large but lopsided one is the kind of hire that fails in surprising ways at month 4.

Toolkit · Fillable Canvas

Job Scorecard — Your Turn

Now fill one out for your role. Export when done. If you can't fill it under 90 minutes, the role isn't ready.

Not "to do product management." What specific business problem does this role solve?
Outcomes are measurable results, not activities. "Launch X" is an outcome. "Manage the roadmap" is an activity.
Must-have (Day 1)
Nice-to-have (developable)
The 90-minute test

If you can't write the Job Scorecard in under 90 minutes, the role isn't ready to hire. Go back to talent planning.

05 · Testing Can-Do Attitude

A candidate's past behavior is the closest thing you'll get to predicting their future.

Credentials tell you what they were exposed to. Behavior tells you who they actually are at work.

The Can-do question is simple: can this person actually do the job? Not "do they look qualified on paper," but "do they have the knowledge, skill, and behavior pattern to deliver the outcomes in the scorecard?"

Traditional interviews answer this badly. They lean on credentials, opinions, and chemistry — all of which are unreliable predictors. Competency-Based Interviewing (CBI) answers it better, because it asks the candidate to walk through what they actually did, in a real situation, in their recent past. Near-past behavior is the strongest single signal we have about near-future behavior.

The CAR concept — anatomy of a real story

Every behavioral answer should have three parts. If even one is missing, the answer isn't a story — it's a claim. And claims aren't evidence.

The CAR Framework

Context → Action → Result

C

Context

The specific situation. When, where, who was involved, what was at stake. Vague context = vague story.

"In Q3 last year, my team missed our enrollment target by 28%. The board meeting was three weeks away and the CEO asked me to own the recovery plan."
A

Action

What they personally did. Not "we." Listen for the difference between "the team did X" and "I did X."

"I ran a 2-day diagnostic with marketing and ops, identified that 60% of the gap was in lead routing, and rebuilt the routing logic that week with the engineering lead."
R

Result

What measurably changed. Numbers, outcomes, consequences. If the result is fuzzy, the story is fuzzy.

"Within 6 weeks, enrollment recovered to 94% of target. The routing fix is still in production today. I was asked to lead the next year's planning."
Worked Example · A CBI in Real Time

What it actually sounds like

Three dialogues showing the full range. A Complete CAR — clean and tagged. A Partial CAR where one piece is missing, with the dig that uncovers it. And a hypothetical question — where the follow-ups are where the real thinking shows up.

Example 1 · Complete CAR
I
Interviewer
Tell me about a specific time you took ownership of a problem that wasn't technically yours.
C
Candidate

C · ContextIn Q3 last year, my product team was on track, but the support team was drowning. Ticket backlog had grown 4x in two months and the support lead had just resigned. It wasn't my function — but it was hurting customer retention, which our growth depended on.

A · ActionI sat down with the interim support lead and our head of CX. I built a triage system that auto-categorized tickets, then negotiated with engineering to ship three top-volume bug fixes in the next sprint. I also spent two evenings personally answering tickets — to understand the patterns from the ground up.

R · ResultWithin six weeks, backlog dropped 70%. The triage system is still in use. The interim lead stayed and was promoted. And I learned more about our actual users in those weeks than the previous year.

I
Interviewer · Probe
How did your own team react to you spending time outside your function for six weeks?
Example 2 · Partial CAR · Result is Missing
I
Interviewer
Tell me about a project you led that didn't go the way you planned. What happened, and what did you do?
C
Candidate · Partial CAR ⚠

CLast year we launched a new mobile feature — push notifications for our top users. We projected 30% adoption based on benchmarks, but week-one adoption was around 8%. I owned the launch from the product side.

AI called an emergency review with our analytics and design leads. We pulled a cohort breakdown, found that iOS users were converting fine but Android users were hitting a permission prompt that was confusing. We redesigned the flow and re-launched two weeks later, this time with in-app context.

…that's basically what happened.

⚠ Strong Context, strong Action — but where's the Result? Did the redesign actually work? We don't know if the candidate is good at closing loops, or just good at starting things. Missing-R is the most common Partial CAR pattern. Dig for the measurable outcome and the second-order effects.
I
Interviewer · Digging for R
What happened to adoption after the re-launch? And were there any second-order effects — on the team, on how you approach launches now?
C
Candidate · Now with the Result

RAfter the re-launch, Android adoption jumped to 24% within three weeks — close to iOS, and within the range we'd considered acceptable. We never hit the original 30% benchmark on Android, but internally the launch was treated as a recovery.

The bigger second-order effect was the post-mortem. We made permission-flow review a standing item in our launch checklist, and I wrote a short write-up that the broader product org adopted as a template. The next two launches I led used it.

Example 3 · Hypothetical Question · Digging into Thought Process
I
Interviewer · Hypothetical
Imagine our largest customer just told us they're switching to a competitor at end of quarter. You have one week before the renewal conversation. Walk me through how you'd approach this.
C
Candidate · First Take
I'd start by gathering data. Talk to the account team to understand the relationship, pull usage data to see if there were any warning signs we missed. Then I'd want to understand what the competitor is offering — pricing, features, anything specific. After that I'd put together a counter-proposal and align with leadership before the meeting.
✦ A reasonable answer — but generic. It tells us this person has a sensible playbook. It doesn't yet tell us how they actually think under pressure, what they'd prioritize, where they'd push back. Hypotheticals get their power from the follow-ups — that's where real thinking shows up.
I
Interviewer · Pin Down Day 1
Walk me through Day 1 specifically. You wake up that morning — what's the first conversation you have, and what do you want to know by end of day?
C
Candidate · Thinking Specifically
Day 1 I'd start with the account exec — but I'd want to understand the customer's actual decision-maker, not just our relationship contact. By end of day I want to know three things: who initiated this — the buyer or someone higher up; what the real reason is — price, feature, or support; and what the actual deadline is. "End of quarter" is often more flexible than it sounds, but only if I ask. I'd deliberately avoid pulling usage data on Day 1 — it makes me anchor on what I think the problem is before I've heard the human story.
I
Interviewer · Test the Assumption
What if the account exec disagrees with your read — they're convinced it's purely about price?
C
Candidate · Under Tension
I'd take their read seriously — they know the relationship. But I'd triangulate: check with a mid-level user on the customer side we have a relationship with, or pull any objective signal from support tickets. If two of those three sources point to something other than price, I'd push back on the account exec — but using their data, not against it. Coming in with "I think you're wrong" breaks the trust I need from them in the renewal meeting itself.

Three types of CAR — and what to do with each

Real interviews rarely produce a textbook Complete CAR on the first ask. Most of the work is recognizing what kind of CAR the candidate just gave you, and responding with the right follow-up.

Best case

Complete CAR

Specific context, personal action, measurable result. Sounds grounded, specific, and time-bound. You can almost picture the situation.

"Last quarter, when our churn jumped to 9%, I ran a 5-day cohort analysis, identified the 3 highest-churn segments, and shipped a save-flow that recovered churn to 5.2% in 8 weeks."
→ Score the behavior against the competency and move on.
Watch out

False CAR

Vague, opinion-based, theoretical, or future-tense. "I usually..." "I would..." "I always try to..." These aren't stories — they're claims wearing story clothes.

"I always take time to find out what the customer wants, and I've made a lot of customers happy that way."
→ Paraphrase and re-ask for a specific past example.
Most common

Partial CAR

Story is there, but one or two pieces are missing — usually the personal Action or the measurable Result. The candidate skipped, you need to dig.

"We were missing the deadline, so the team contributed and we got it done on time."
→ Dig deeper. What did you specifically do? What was the result?
The 70:30 Rule

The candidate should talk roughly 70% of the time. You talk 30. If you're talking more than that, you're either oversharing or asking closed questions. Listen for facts, not opinions. Watch for what's missing, not just what's said.

Behavioral vs. Hypothetical — two question types, two purposes

CBI lives mostly in behavioral territory ("tell me about a time when..."), because past behavior predicts future behavior. But hypothetical questions ("how would you approach...") have their place when the candidate is moving into a meaningfully new context — a new industry, a new function, or a much bigger scope. There, you're testing thought process, not pattern.

The rule of thumb: behavioral first, hypothetical only where the candidate genuinely has no analog past experience. And even then, watch out — hypothetical answers are easy to over-rehearse. They tell you how someone talks about problems, not necessarily how they'd solve them.

Toolkit · Question Library

Can-Do Question Bank

Starter behavioral & hypothetical questions across four commonly-tested attributes. Adapt the language; keep the structure.

Ownership & Accountability
Behavioral
Tell me about a time you took ownership of a problem that wasn't technically yours. What did you do, and what happened?
Follow-ups: What made you decide to step in? How did your manager react? Looking back, would you do it again?
Behavioral
Walk me through the most recent time something you owned didn't go well. What was the situation, what did you do, and what was the outcome?
Follow-ups: What did you tell your team or your manager? What did you change in your approach afterward?
Analytical Thinking & Problem Solving
Behavioral
Tell me about a recent decision you made with incomplete data. How did you think through it, what did you decide, and how did it turn out?
Follow-ups: What did you not know that you wished you knew? How would you make the same decision now?
Hypothetical
Imagine our largest customer just told us they're switching to a competitor. You have one week before the contract renewal. Walk me through how you'd approach this.
Follow-ups: What's the first thing you'd want to know? Who would you involve? What would you do if your CEO disagreed with your recommendation?
Cross-Functional Collaboration
Behavioral
Tell me about a time you had to deliver something that depended heavily on a team you don't manage. How did you make it work?
Follow-ups: What was the hardest part of the dependency? Was there a moment of friction? How did you resolve it?
Behavioral
Describe a time you disagreed strongly with a peer's approach on something that mattered. What did you do?
Follow-ups: How did the conversation start? What did each of you concede? What was the final call and how did you feel about it?
Leadership & Coaching
Behavioral
Tell me about the most difficult feedback you've ever given to someone on your team. What was the situation, what did you say, and what happened next?
Follow-ups: How did you prepare? Looking back, would you change anything? Where is that person now?
Behavioral
Walk me through a time you developed a team member who started underperforming and ended up doing strong work. What did you actually do?
Follow-ups: What was your hypothesis about the underperformance? What was the turning point? How long did it take?

What to listen for — and what to ignore

Inside a CBI answer, your job is to filter signal from noise. Listen for: specific verbs ("I built," "I decided," "I told"), time markers ("last quarter," "in Q3"), concrete numbers, and uncomfortable details (real stories have uncomfortable details — perfect stories often don't). Ignore or probe: hedge words ("we kind of," "I would usually," "generally I try to"), theory ("I believe leadership is about..."), and self-praise without evidence.

The best CBI interviewers ask three or four questions in 45 minutes. They don't rush. They probe. They get specific. And they take notes — not to remember everything, but to score against the scorecard later without their feelings doing the work for them.

The Discipline

Behavioral interviewing isn't about being clever. It's about being patient. Most useful interview moments are the ones where you wait a few seconds longer than feels comfortable.

06 · Testing Will-Do Attitude

Can-do gets you a qualified candidate. Will-do tells you if they'll stay and thrive.

Skills don't quit. Motivation does.

The most expensive hires aren't the ones who can't do the job. They're the ones who can — but quietly check out at month 5, never get embedded, and resign at month 9. They had the can-do. They never had the will-do.

Will-do is the motivational-fit question: given who this candidate is, will the work, the leader, the team, and the company keep them engaged and effective? This is what the 4 Fits framework actually measures. We met the Fit Compass in Section 04 as a visual tool. Here, we go deeper — what each fit actually means, what to probe, and what to ask.

Fit 01 · Values & Mission

Company Fit

Alignment between the candidate's values and how the company actually operates — not the wall-poster version of values, but the lived ones. The way meetings run, decisions get made, conflict gets handled, customers get treated.

Probe with behavioral questions against your core values
"Tell me about a time you had to make a tough call where doing the right thing cost you something."
"Describe a workplace value that mattered deeply to you in a past role — and what happened when it was violated."
Fit 02 · Style & Feedback

Leader Fit

Match between the candidate's working preferences and the direct leader's actual style — how they give feedback, how much autonomy they grant, what they need to see, how often they meet. Mismatch here kills hires fast.

Probe with what the candidate needs from a leader
"Describe the best leader you've worked with. What specifically did they do that worked for you?"
"What kind of leader would you struggle most under, and why?"
Fit 03 · Dynamic & Rhythm

Team Fit

Match between the candidate and the team's actual rhythm — pace, directness, conflict tolerance, social style. A high-energy candidate in a quiet, async team fails differently than a reflective candidate in a high-velocity sales team. Both fail.

Probe with how they describe past teams
"Describe the team you've been happiest on. What made it work for you?"
"When have you struggled to fit into a team? What was going on?"
Fit 04 · Daily Work & Motivation

Job Fit

Match between the candidate's natural motivators and the actual day-to-day work. Not what's on the job description, but what fills the calendar most weeks. Someone who loves building can wash out fast in a role that's 80% maintenance.

Probe with what they liked and disliked about past work
"When in your career have you felt most energized? What specifically were you doing?"
"What aspects of past jobs have drained you, even when you were good at them?"

The job fit probe — when, what, why

Job fit is the easiest of the four fits to get wrong, because candidates rarely talk honestly about what they don't like. A good probe has three parts. When: ask them to identify a time they felt satisfied or dissatisfied with job-related activities. What: drill into what specifically they liked or disliked about that activity. Why: ask why the situation was satisfying or dissatisfying — what was underneath it.

The "why" matters most. Two candidates can both say "I didn't like the reporting work." For one, it's because reporting felt like surveillance. For the other, it's because they hated context-switching from creative work. Same surface answer, very different will-do implications.

Toolkit · Question Library

Will-Do Question Bank

Motivational-fit questions you can rotate through across the 4 fits. Each one has a follow-up that pushes past the rehearsed answer.

Company & Values Fit
Motivational
What kind of company would you not be happy at — even if the role and the pay were great?
Follow-up: Have you ever been somewhere like that? What did you do?
Motivational
When you've stayed somewhere for a long time, what kept you there? When you've left quickly, what pushed you out?
Follow-up: How would you know, six months in, that the place isn't right for you?
Leader Fit
Motivational
How do you like to receive feedback? Walk me through the best feedback conversation you've had.
Follow-up: What about it worked? What would you have wanted differently?
Motivational
How much direction do you want from a leader on a typical week? Where on the spectrum from "tell me what to do" to "leave me alone" do you sit?
Follow-up: When does that preference flip for you?
Team Fit
Motivational
Describe a team that brought out your best. What was the team culture like — pace, directness, how they handled disagreement?
Follow-up: How would you know early in this team if the dynamic was off for you?
Motivational
What's a team behavior — something specific that teammates do or don't do — that quietly drains you over time?
Follow-up: Have you raised it before? How did that go?
Job Fit
Motivational
If I followed you through a great work week, what would I see you spending most of your time on?
Follow-up: And what was the last week that looked like that? What about a draining week — what was on the calendar then?
Motivational
Three months in, what would tell you this role is the right job for you? And what would tell you it's wrong?
Follow-up: What would you do if you noticed the "wrong" signals at month 3?
"Skill predicts whether they can do the work. Fit predicts whether they'll still be doing it next year."
— The Will-Do Premise

How to weight the 4 Fits in your decision

Not every role weighs the fits equally. A senior IC role with high autonomy weighs Job Fit and Leader Fit higher (because there's no team-immersion to lean on). A junior role on a tight pod weighs Team Fit and Leader Fit higher (because the team will absorb a lot of the learning). A founding-team role weighs Company Fit very highly (because they're building the culture, not joining it).

Before the interview panel meets, decide together: for this specific role, which two fits matter most? Then design the interview rotation so the two heavy fits get the most airtime. A panel that interviews every candidate the same way regardless of role isn't running a process — it's running a script.

Reading the Compass Honestly

A lopsided fit profile is more dangerous than a small one. The strong corners create excitement that masks the weak corner. The single most common hiring failure isn't a weak candidate — it's a strong candidate whose weak corner nobody investigated.

07 · Running the Interview

The interview is a relationship — built in sixty minutes, judged for the rest of someone's career.

Candidates being interviewed are vulnerable. Warmth doesn't compromise rigor — it enables it.

A great interview isn't a great list of questions. It's a great conversation that happens to be structured. The structure protects both sides — the candidate from a chaotic, anxiety-spiking ordeal, and you from a charming-but-empty 60 minutes that produces no real data.

This page is about the mechanics. How to set up before, what to do during, how to close, and what to do after. Every part of this is repeated craft — the more you do it, the better you get at the small moves that produce big information.

01
Before
15–30 min prep
01
Re-read the scorecard.Which competencies are you assessing? You should never enter the room without that clarity.
02
Review the CV closely.Mark 3 things you want to probe: a gap, a transition, a result that sounds too good or too vague.
03
Pre-select 4–6 questions.Mix of behavioral and one hypothetical. Match each to a specific competency. Write them down.
04
Confirm your panel handoff.Know which fits and competencies the other interviewers are covering. Don't double-cover.
02
During
45–60 min
01
Open warmly (5 min).Greet, set context, share the agenda, name that you'll take notes, invite them to ask questions at the end.
02
Key background review (5 min).Brief walk through their CV — the recent few roles. Confirms shared understanding and breaks the ice.
03
CBI & competency questions (35–45 min).3–4 questions, deep probing on each. Take notes against the scorecard. Listen for the missing parts of each CAR.
04
Close generously (5–10 min).Their questions. Brief on next steps. Confirm timeline. Thank them. They should leave clearer, not more anxious.
03
After
Within 24 hours
01
Score the scorecard, alone, first.Before reading anyone else's notes. Your independent rating is your contribution to the panel.
02
Document specific evidence.Quote the candidate where possible. "Strong on Ownership" means nothing — quote the moment that showed it.
03
Submit, then debrief.Send your scorecard to HR. Then join the panel debrief and challenge / be challenged on your reading.
04
Re-examine the panel disagreements.Don't average to consensus. Investigate disagreements — they're the most informative part of the process.

Opening matters more than you think

The first 90 seconds of the interview set the candidate's nervous system for the whole conversation. Vulnerable candidates over-perform on small talk and under-perform on hard questions. Confident, settled candidates produce richer answers. Both of these are partly under your control.

A good opening does five things, in order: it sets a friendly tone, lets them know what to expect, tells them what they'll get out of the conversation, names the note-taking explicitly, and keeps the whole thing brief. Don't over-rehearse it — over-rehearsal sounds robotic. Just make sure all five happen.

Underneath the structure, you're meeting two kinds of needs at once.

Personal Needs

What the candidate feels

  • Feel comfortable in the space
  • Be treated with respect
  • Feel welcomed, not interrogated
Practical Needs

What the candidate gets

  • An actual interview, not a chat
  • Acknowledgement of their experience
  • A professional, signal-rich experience

You meet both at once through two simple moves. The first is maintaining or enhancing self-esteem — sincere, specific compliments when warranted, and minimizing negative information you have to share. The second is listening with empathy — reflecting back the feelings and the situation when the candidate shares something charged, positive or negative. Neither requires you to compromise on rigor. Both require you to be a human being first.

The discipline of note-taking

Take notes during, not after. Notes serve four purposes. They keep you focused on gathering complete information instead of being charmed. They keep your in-the-moment impressions from blurring with the candidate's actual answers. They give you specifics for the decision. And they protect the decision from being based on memory and feelings, which always favor the candidate you liked talking to most.

Tell the candidate you'll be taking notes. Most candidates appreciate it — it signals you're listening carefully. Then actually do it. Quote them where you can. Note both what they said and what they conspicuously didn't say.

Closing well

How you close is what they remember. A clean close has three parts: invite their questions and answer them honestly, brief them clearly on next steps and timeline, and thank them sincerely. Don't promise an outcome you can't deliver. Don't give vague timelines you'll miss. Treat the candidate the way you'd want to be treated if your career direction were sitting on the other side of an email you haven't received yet.

The Quiet Test

A great interview leaves the candidate clearer than when they walked in — about the role, about the company, about themselves. Even the candidates you don't hire should leave thinking the process was worth their time.

08 · Decide & Offer

A great hire decision is a calibrated decision, not a confident one.

The hire decision is too important to leave to one person's instinct — including yours.

By this point, the panel has run their interviews. Everyone has a strong opinion. Some are excited. Some are uneasy. Two interviewers might violently disagree. Don't average to consensus. Calibrated decision-making starts from the assumption that each interviewer saw something the others didn't — and the panel's job is to surface those differences before deciding, not to smooth them over.

The calibration matrix

Before debate, each interviewer scores the candidate against the agreed scorecard competencies — alone, before talking to anyone else. Then the matrix gets built. Disagreement becomes the most useful data in the room: where two interviewers split, you investigate, not vote.

Worked Example · Senior Product Manager, Growth

Panel Calibration Matrix

Competency Interviewer A
CBI · Hiring Mgr		 Interviewer B
Technical · Peer		 Interviewer C
Will-do · HR		 Interviewer D
Leadership · CEO		 Consensus
B2C Growth Experience Strong Strong Acceptable Strong Strong
Experimentation Discipline Strong Strong Acceptable Acceptable Strong
Cross-Functional Leadership Acceptable Weak Acceptable Strong Investigate ⚠
Ownership & Accountability Strong Acceptable Strong Strong Strong
Will-Do · Leader Fit Acceptable Strong Strong Acceptable Strong
Recommendation: HIRE  —  Pending a final 30-min leader–candidate conversation on cross-functional collaboration

Notice what the matrix did. The panel disagreed sharply on Cross-Functional Leadership — Interviewer B said Weak, Interviewer D said Strong. Instead of averaging that to "Acceptable" and moving on, the panel surfaced it. The recommendation became "Hire, but verify the disputed corner first." That extra conversation costs 30 minutes. A wrong hire on that vector costs months.

Weighing competencies — and the trainability question

Not every competency carries the same weight. Some are non-negotiable from Day 1. Others are developable with the right leader and time. A candidate who's strong on the must-haves and weak on the developable ones is a different decision than the reverse — even if their overall scorecard looks identical.

High Trainability

Can be built in 3–6 months

  • Tools-specific knowledge (your CRM, your stack)
  • Industry-specific vocabulary
  • Process knowledge (how your company plans, ships, reviews)
  • Internal relationship maps
  • Light technical upskills with a strong coach
Low Trainability

Don't try to develop this in

  • Core attitude — ownership, intellectual honesty
  • Established behavior patterns under pressure
  • Communication maturity for the level
  • Genuine domain experience (years can't be taught)
  • Coaching skill, if hiring a manager

Read the matrix through the trainability lens. A "Weak" on something highly trainable, when the rest of the scorecard is strong, is a small risk. A "Weak" on something untrainable — especially attitude or core behavior — is a deal-breaker regardless of how the rest looks.

From decision to offer — the protocol

Once the panel decides "Hire," the offering process should feel orderly, fast, and respectful. Sloppy offers undo great hiring processes — candidates feel the change in posture and lose trust.

01
Hiring Mgr
Informs HR of the decision to offer, with rationale and pay range from the scorecard.
02
HR / People
Builds the offer against the salary band & benchmarks. Confirms with CEO/COO for approval.
03
HR → Candidate
Formal offer sent. Verbal call first, written follow-up the same day. Clear deadline to respond.
04
CEO/COO + HR
Negotiation, if any, runs between HR and senior leadership. Hiring manager kept informed, not in the negotiation seat.

Salary band logic in 90 seconds

The fairest offer you can defend is one anchored in three things: a documented salary band tied to the role grade, the candidate's specific scorecard fit against that band (where in the band do they land, and why), and an explicit internal-equity check against people at the same grade doing similar work. If you can't articulate all three in a sentence, the offer isn't ready.

The middle anchor — where in the band do they land, and why — is the one most teams get wrong. The tool below makes that part concrete. Drag the slider to set the candidate's % fit against the scorecard. Watch where the offer should land in the band, and read the rationale.

Toolkit · Interactive Salary Sizing

The Fit-to-Offer Compass

Salary band: IDR 45M (Min) → IDR 51.5M (Mid) → IDR 58M (Max) for the worked example role. Adjust the candidate's % fit against the scorecard's must-have competencies. The recommendation updates live.

DON'T OFFER MIN ACCEPTABLE MID · SWEET SPOT ABOVE MID DON'T 45M 48M 52M 55M 58M IDR per month · Salary band for this role's grade ↑ IDR 53.5M
Candidate's % fit against scorecard
100%
Compute % fit as: (must-haves met + 0.5 × nice-to-haves met) ÷ total competencies × 100
Mid Range — Sweet Spot
IDR 53.5M

At 100% fit, the candidate is the right person for the role at full competence. Offer at mid — defensible internally, fair externally. This is the offer you want most of your hires to receive.

Two principles save you from most offer mistakes. First, don't over-pay to close — once you've over-paid an offer, you've also miscalibrated the rest of the team's compensation by setting a new internal benchmark. Second, don't under-pay to test — sending a low offer to "see what they accept" signals what you'll be like as an employer. Make the fair offer first.

The Trap to Avoid

By the time you're at the offer stage, you've spent serious time on this candidate. The instinct is to close the deal at any cost. Resist. The hire that fails at month 5 because you over-paid or over-promised costs you more than the hire you let go.

09 · Onboarding

Onboarding is where the hire begins to embed — or quietly starts to leave.

Most onboarding programs handle paperwork and call it done. Real onboarding makes a new hire feel selected, capable, included, and inspired — in that order.

This section is the section most TA playbooks skip. The req closed, the offer signed — handoff to HR, mission accomplished. But the data is unambiguous: a hire who quietly resigns at month 7 wasn't an "onboarding failure" sitting separately from the hire. It was a hire that failed, full stop. And research consistently shows the difference between hires who embed and hires who churn comes down to what happens in the first 90 days — most of it shaped by the leader, not the program.

Three failure modes — what onboarding is actually protecting against

Early-tenure failures don't all look alike. They cluster into three patterns, and a well-designed onboarding program addresses all three. Treating "onboarding" as a single thing is exactly why so many programs fail.

①
Selection failure

Required competence absent

The wrong person was hired. They don't have — and can't quickly acquire — the core competence the role needs. The interview missed it, the references missed it, the first weeks confirm it.

Counter at hire — not in onboarding Strong scorecard. Rigorous CBI. The 4 fits. Calibrated panel decision. Once a Selection failure is in the door, onboarding cannot rescue it.
②
Role failure

Self-efficacy & role clarity

The candidate is capable but disoriented. They don't know what's expected. They don't feel equipped — no tools, no access, no shadowing, no coaching. They start strong, then quietly stall by week 4.

Counter in onboarding 1-1 role & expectation conversation. Development roadmap with 30/60/90 milestones. Technical onboarding. Knowledge management. Leader CFR habit.

Read across the three. Selection failure is upstream of onboarding — handled in Sections 04 through 08. Role failure and Engagement failure are onboarding's job. A program that handles only one (most handle Role, some handle Engagement, almost none handle both well) will see early-tenure attrition no matter how much budget gets thrown at it.

The five layered C's — the building blocks of real onboarding

Onboarding works in layers. Compliance is the base — necessary, mandatory, but emotionally barely a foundation. Each layer above it does deeper work, builds a different engagement state, and requires a different program. Most companies build the base and call it done. The ones with strong year-one retention build all five.

The 5 C's of Great Onboarding

A maturity pyramid — from paperwork to belonging

Each level builds on the one beneath it. The base is mandatory and necessary; the apex is what makes someone stay. Most companies build the base and stop — and wonder why their year-one retention sags.

C COMPLIANCE C CLARIFICATION C CONFIDENCE C Culture ENGAGED TO COMPANY Believes, defends, refers Connection ENGAGED TO TEAM Belongs, accepted, valued Confidence ENGAGED TO JOB Equipped, capable, autonomous Clarification NOT DISENGAGED Knows what's expected Compliance DISENGAGED Paperwork done, soul absent FOUNDATION ▲ HIGHEST EVOLUTION
C1
Compliance

Mandatory: paperwork, badges, equipment, system access, policy reading. Most companies stop here and call it onboarding.

C2
Clarification

Role clarity. 30/60/90-day expectations. How the organization actually functions. The highest-leverage onboarding investment.

C3
Confidence

Technical onboarding, shadowing, mentor system, ongoing CFR from the leader, accessible knowledge management. Self-efficacy built here.

C4
Connection

Buddy program, team welcoming, stakeholder get-to-knows, HR check-backs, real leader relationship. Strongest single retention lever in year one.

C5
Culture

Values lived, not laminated. Stories of role-modeling. Demonstrated leadership behavior. Embeddedness becomes loyalty here.

Read the engagement state column carefully — that's where the model earns its keep. A new hire stuck at Compliance is, at best, "not disengaged." A new hire who reaches Culture is the kind of person who refers their best friends to apply, defends the company in private conversations, and gives an extra month's notice when they eventually leave. The 5 C's aren't a checklist — they're a maturity ladder where each rung corresponds to a different emotional outcome.

Orientation ≠ onboarding — the split that matters

One of the most common mistakes companies make is collapsing orientation and onboarding into a single overloaded day. The new hire arrives Day 1, gets eight hours of company history, benefits, IT setup, building tour, code of conduct, lunch, culture talk, expectations — and leaves the day genuinely unable to remember most of it.

The right split: Orientation covers the basics — company profile, logistics, rules, welcoming activities, what's coming next. It happens on Day 1. Onboarding covers everything needed for the new hire to be integrated to the company, the team, and the job — and to be able to fulfill the responsibilities of their position. It unfolds across weeks 1–4, not in a single overwhelming session.

The five-phase new hire journey

Every phase has its own purpose, its own owner, and its own success signal. The phase map below is built around the source: what a new hire actually experiences, week by week, and which of the 5 C's gets built at each step.

01
Prior to Day 1 · Preparation
From offer signed to the night before Day 1
PIC · People Ops
Compliance
Contract, NDA, basic role info sent. Clarify any expectations that didn't get pinned down during interviews — title, grade, reporting line, start date logistics.
Clarity
Welcome email with the Day 1 agenda. What to expect, what to prepare (download probation form, explore intranet, connect with team). Removes anxiety; replaces it with anticipation.
Connection
Team & buddy preview — access to a page with PBP and team faces, names, titles, contact info. Optional pre-Day-1 activity: "say hi" link, suggest adding LinkedIn. Small touch, large psychological effect.
Culture
Intranet access with basic company info — products, history, values. Gives the new hire something to read, something to absorb at their own pace before the firehose of Day 1.
02
Day 1 · Orientation
The single most-photographed day of the hire's first year
PIC · People Ops + Leader
Culture
General orientation — Lamudi history & journey, our impact & products, core values. Story-based, not slide-based. Morning session, 9–12 AM. Bite-sized, not overwhelming.
Compliance
Logistics and access set up — laptop, building access, email activation, employee systems (Notion/intranet, Talenta for reimbursement/days off). Probation process explained.
Connection
Welcoming lunch with PBP + buddy introduction. Noon session, 12–1 PM. The lunch is non-negotiable — it's the social anchor for everything that follows.
Connection
Post-lunch team get-to-know-each-other + snack. Casual, low-stakes, lets the new hire put names to faces.
Clarity
1-1 role & grade expectation with leader. The leader walks through what success looks like at this grade, this role, this first 30/60/90 days. Afternoon session, 1–3 PM. The leader must be present — WFH on Day 1 is a Code of Practice violation.
03
Week 1 to Month 1 · Onboarding
Where the bulk of integration actually happens
PIC · Leader + PBP
Culture
Company onboarding — culture activation program, deeper dive on values in action, organization structure and the impact of each team. Delivered by HR, attended by all new hires in the cohort.
Clarity
Leadership onboarding for new leaders — preparing to lead, first-30-days expectations, leadership habit & KBIs, leadership Code of Practice, progressive disciplinary action. Critical: new leaders must receive this before they make their first mistake on team management.
Confidence
Continuous performance management training — C-F-R (Conversation, Feedback, Recognition) habit, how to give and receive feedback, soft-skill development. Coaching skill for those managing people.
Confidence
Functional / technical onboarding — designed by the dept / direct leader. Job-specific training, shadowing, on-the-job coaching, support. Development roadmap with 30/60/90-day milestones documented in the probation form.
Connection
Stakeholder get-to-know meetings — assigned and tracked. ("Meet with Ryan in Finance within your first 30 days.") Each meeting is on the new hire's calendar, not their to-do list.
04
First 90 Days · Probation
Where the embedment is tested under real performance pressure
PIC · Leader
Confidence
Ongoing shadowing, coaching, support. The hire moves from "watching" to "doing" to "owning" — at a pace appropriate to the role's complexity.
Clarity
Continuous CFR habit from the leader. Biweekly 1-1 minimum. Real feedback, not waiting for the formal check-in.
Culture
Culture-fit review — 360 feedback collection from the people the hire is working with. Not for performance — for embedment signal.
Connection
90-day new employee survey — engagement check across all 5 C's. PBP follows up on signals, regardless of whether the hire is on track for probation.
Clarity
Probation evaluation conversation at end of Day 90 — in person, never over Slack. Pass / extend / exit decision communicated with respect and clarity. The full probation rhythm is detailed in the next section (10 · Probation).
05
Month 4 to Month 12 · Post-Probation
Where good hires become embedded ones
PIC · Leader + Talent Mgmt
Confidence
Goal setting for first full performance cycle (6 months). The hire moves from probation milestones to ownership of real outcomes.
Clarity
Personal Development Plan for the first full cycle. Aligns growth ambition to scope and grade.
Culture
Career planning conversation — separate from performance. Where does this person want to go in 12, 24, 36 months? The conversation itself signals "we see you as a long-term hire."
Clarity
Leadership development program — for those in leadership grades, advanced KBIs, Code of Practice review, supporting team member's development.

The leader is the lever — every time

Across every dataset on early-tenure satisfaction, one variable dominates: the direct leader. Engagement scores, probation pass rates, retention through month 12 — all track most closely with the quality of the new hire's leader-relationship. Which means: a great onboarding program with a weak leader still produces weak outcomes. You can't onboard around a bad manager.

This is why what follows is non-negotiable. If your company has hiring managers, your hiring managers need a code of practice — a minimum service standard for what they owe every new hire on their team. Without it, "manager quality" is a wish. With it, it's a measurable bar.

Toolkit · Minimum Service Standard

Leadership Code of Practice

The minimum behaviors every leader owes their team during onboarding, probation, and beyond. Falling below this isn't a style preference — it's a violation. Applies to all leaders grade 4C and above (manager and above).

Onboarding the New Hire
Be at the office (or visibly available) on the new hire's first day — never WFH-ing on Day 1.
Complete the 1-1 role & expectation conversation on the new hire's first day.
Confirm seating, equipment, and access are ready before they arrive — not "we'll figure it out."
Managing the Probationary Period
Hold a 1-1 check-in at least once every two weeks throughout probation.
Submit and update the probation form at Day 30, Day 60, and Day 75.
Provide functional or technical induction — training, coaching, tools, or other concrete resources.
Hold the final probation conversation in person, not over Slack, regardless of outcome.
Engaging All Employees
Never reported as being disrespectful or conducting any harassing behaviour.
In case of exiting employees (resignation), follow all available policy — notice periods, knowledge transfer, dignified offboarding.
Keeping the Team Accountable
Every team member is clear on their role and what's expected of them.
Quarterly goals exist and are understood by every team member.
Biweekly team meeting and weekly progress meeting both run consistently.
Performance ratings come with explicit, specific evidence — never "it's just my read."
Developing the Team
Every team member has a development plan reviewed at least quarterly.
Career conversations happen at least once a year, separately from performance reviews.
Progressive Discipline When Violated

Each leader gets one feedback round and three strikes per 3-month window. First violation: verbal feedback from the People Business Partner. Second: Strike 1 + written warning. Third & Fourth: Strike 2 & 3 + escalating written warnings, each active for 3 months from issuance. The PBP holds a live document tracking the status; the CEO has access and signs warning letters based on the documented violations. The standard is real — or it isn't a standard.

The Closing Truth

TA owns the hire. Onboarding owns the embedment. The direct leader owns the relationship. If any one of the three drops the ball, the hire fails — and the others can't catch it for them.

10 · Probation

Probation isn't a test for the candidate — it's a check on the system that hired them.

If onboarding builds the foundation, probation is where you find out whether the foundation holds.

By the time a hire reaches Day 90, four things should be true: they should be performing at the expected level for their grade, they should feel clear on what's expected, they should feel connected to their team, and they should feel proud to be there. If any one of those is missing, probation is the moment to surface it — not month 6, when the cost of the mistake has compounded.

Probation done well isn't an evaluation event at Day 90. It's a rhythm of small, frequent calibrations across the full 90 days, with structured checkpoints that force the leader, the PBP, and the hire to look at the same data at the same moments. The decision on Day 90 should never be a surprise to either party.

Why people leave — three doors, mapped to the levers you have

Probation only works if you know what it's protecting against. Research on early-tenure turnover keeps surfacing three pathways out — three doors people walk through when they leave. Each door responds to a different intervention, and probation can address two of the three head-on.

01

Life-Shocks & Scripts

Events outside work that re-shuffle priorities — marriage, pregnancy, a partner's relocation, a sick parent, a dream company calling. Also includes planned career trajectories ("I always wanted to try X by age 30"). You can't prevent these. You can sometimes negotiate around them if you've built trust.

Levers: trust with the leader, flexibility policy, genuine empathy when life happens. Probation surfaces these via the leader knowing the human, not just the worker.
02

Work-Related Drivers

Things your company is doing or not doing. Inducement vs contribution imbalance, weak leadership, broken relationships, dysfunctional work environment, bad fit between the person and the job's actual content. The job they expected isn't the job they got.

Levers: leader quality (Code of Practice), compensation fairness, role clarity, team dynamic, the 4 fits caught at hire. Probation surfaces these via the satisfaction survey + the leader's 1-1 cadence.
03

Low Embeddedness

The slow, quiet exit. Weak links to teammates, low fit with the work, nothing meaningful to sacrifice if they leave. People who score low here are open to other opportunities long before they apply. They're not unhappy — they're just not attached.

Levers: buddy program, mentor system, role progression, scope growth, recognition, time-locked benefits. Probation surfaces these via embedment-focused 360 feedback collection.

Doors 2 and 3 are where probation has the most leverage. The 4 fits, caught at hire, prevent most of Door 2. The 5 C's, executed during onboarding and watched during probation, prevent most of Door 3. Together they don't eliminate turnover — they shift it from preventable churn to acceptable life-event turnover.

Why people stay — embeddedness, the opposite of turnover

The opposite of turnover isn't "staying." It's embeddedness — the sense of being in a tribe, of having psychological contracts that matter. The research breaks it down into three components, and a great probation period is one where the leader is actively building all three.

Component 01
Links

The connections an employee would have to sever or rearrange to leave. The more connections, the more reasons to stay. The strongest links are usually the human ones — leader, mentor, best friend at work.

What to build in probation Buddy formally introduced and active. Leader 1-1 cadence consistent. Stakeholder get-to-knows complete. Optional: a mentor outside the direct reporting line.
Component 02
Fit

The extent to which employees see themselves as compatible with — or proud being part of — their job, their organization, and the community around them. Pride in the brand. Pride in the team. Pride in the work itself.

What to build in probation Culture activation stories, awards, public recognition, surfacing real impact ("this is what your work contributed to"). The hire should be able to finish "I'm proud to work here because…"
Component 03
Sacrifice

The forms of value a person would have to give up if they left. Promotion candidacy, succession track, ESOP, role uniqueness, flexibility that would be hard to replicate. The bigger the sacrifice, the higher the embedment.

What to build in probation Visible progression path. Career conversation by Day 90. Clear role of "what comes next" if they perform. Compensation transparency for the next grade.

Where the soft signals show up — pre-probation satisfaction data

Before designing what probation should do, look at where new-tenure dissatisfaction is loudest. The signal table below comes directly from real employee survey data — 74 respondents at 0–3 months tenure, 465 respondents at 4–12 months. Read it as a heat map. Where it's red, your probation rhythm needs the most repair.

Diagnostic · Real Survey Data

Where new-hire satisfaction breaks down

0–3 months tenure (n = 74) vs. 4–12 months tenure (n = 465). The areas to watch are the ones that get worse over time — because they signal something the program isn't catching.

Area 0–3 months 4–12 months What it tells you
Expectation meets reality Acceptable Dissatisfied ↓ Job preview at hire didn't match Day 90+. Tighten Job Fit probes in interviews (Section 06).
The job is challenging and motivating Not satisfied Acceptable ↑ Early onboarding has too much shadowing, not enough ownership. Get them on real work faster.
The KPI was well-explained Satisfied Not satisfied ↓ Day 1 expectation conversation set clear targets — but the leader didn't sustain the conversation. Code of Practice violation.
The goal was well-discussed Dissatisfied Not satisfied Worst score, and it doesn't recover. The biggest single onboarding investment failure.
Satisfying level of recognition Dissatisfied Not satisfied Recognition is treated as a "manager's personality trait" instead of a habit. Build it into the CFR cadence.
Review system is useful / valuable Not satisfied Acceptable ↑ Improves as the hire experiences a full cycle. But the first 90 days feel arbitrary — fix the probation rhythm.
Evaluation was conducted well Not satisfied Acceptable ↑ Probation evaluation lands worse than it should. The conversation itself needs more skill.
Satisfied / Happy (80+) Acceptable (75–80) Not satisfied (70–75) Dissatisfied (≤70)

The red zone — Goal discussion, KPI explanation, and Recognition — is where the leader's habits live or die. None of these can be fixed with a program, a template, or a survey. They're fixed by the leader showing up to 1-1s, asking better questions, and noticing what's worth noticing. Probation done well forces leaders to do these things on a schedule, instead of when they remember.

The probation rhythm — Day 0 to Day 90

The rhythm below isn't aspirational. It's the minimum cadence for probation to do its job. Each checkpoint has an owner, a deliverable, and a conversation that has to actually happen — not just get logged.

Probation Cadence

Day 0 → Day 90 — the seven checkpoints

Owners shift across the 90 days. Day 1 is anchored by the leader. Mid-probation is shared between leader and PBP. Day 90 is the leader's decision, supported by HR. The hire shouldn't be surprised at any checkpoint.

D1 START Expectation set 14 D14 First 1-1 check-in 30 D30 Probation form milestone 1 60 D60 Probation form milestone 2 + 360 75 D75 Probation form milestone 3 85 D85 Survey + decision draft D90 DECIDE Pass / Extend / Exit
Day 1
Expectation Set
Owner · Leader
1-1 role & expectation conversation on Day 1. Leader walks through the probation form together with the hire — what's expected by D30, D60, D90. Both sign. The hire leaves Day 1 with the document open in their drive.
Day 14
First Real Check-In
Owner · Leader
First scheduled 1-1 after Day 1. Less about performance, more about orientation. "How is it going?" "Are you blocked on anything?" "Anything unclear from the expectations we set?" Sets the biweekly rhythm for the rest of probation.
Day 30
Milestone 1 — Probation Form
Owner · Leader + PBP
First formal milestone in the probation form. Three things tracked: (1) competence ramp — are they where they should be at D30, (2) cultural integration — buddy active, stakeholder meetings booked, (3) any early concerns from the leader. Form submitted to PBP. PBP follows up on any signals.
Day 60
Milestone 2 + Mid-Probation 360
Owner · Leader + PBP
Second milestone. 360 feedback collected — short, structured, from 3–5 people the hire is working with. Not a performance review — a culture-fit and embedment signal. If anything red shows up, this is the time to act. Day 90 is too late.
Day 75
Milestone 3 — Decision Direction Forms
Owner · Leader
Final milestone before the decision. By now the leader should already know what the Day 90 call will be — and if extending, the case is being prepared. If exiting, the conversation is being rehearsed. The 1-1 at this stage is also where the leader signals their direction, gently, so the hire isn't blindsided.
Day 85
90-Day Survey + Decision Draft
Owner · PBP + Leader
90-day new employee experience survey sent. Results read alongside the probation form. PBP and leader align on the recommendation: pass, extend, or exit. The recommendation is documented before the Day 90 conversation — not improvised in the room.
Day 90
Probation Evaluation Conversation
Owner · Leader
In person, never over Slack. Decision communicated with clarity and respect, regardless of which decision it is. If passing, talk about what comes next — goal-setting for the first full cycle. If extending, name what specifically needs to change and on what timeline. If exiting, communicate with dignity — the hire spent 90 days here, they deserve a real conversation.

The three possible outcomes — and when each is right

Probation has three honest outcomes. The hardest one isn't exit — it's the borderline case where extending is the right call but the manager wants to either pass or exit because the in-between is uncomfortable. Naming the three outcomes clearly, with criteria for each, removes the temptation to default.

Day 90 Decision Logic

Pass, Extend, or Exit — the criteria for each

Outcome 01

Pass

All three milestones met. Embedment signals strong. 360 feedback is positive or neutral with developable gaps. Leader confident the hire will be a contributing team member at month 6.

What to do

Communicate the pass clearly. Move immediately into goal-setting for the first full performance cycle. Set up the career conversation for month 4–6. Don't celebrate-then-disappear — passing probation is a starting line, not a finish line.

Outcome 02

Extend

Most milestones met but one specific gap is still uncertain — usually around competence ramp or a single 360 signal. The hire is on a trajectory that could be passing in another 30–60 days. Not exiting — but not yet confident enough to commit.

What to do

Name the specific gap. Agree on what "closed" looks like and the timeline. Document the extension. Increase the 1-1 cadence. This is the bravest call — don't pretend to pass to avoid the conversation, and don't exit because the in-between is uncomfortable.

Outcome 03

Exit

Multiple milestones missed. Embedment signals weak. 360 feedback indicates the hire is struggling in a way that more time won't fix. Or — a fundamental fit mismatch surfaced that the interview didn't catch.

What to do

Communicate the exit in person, with dignity. Don't blame the hire for what was a hiring decision. Honor the notice period and any contractual obligations cleanly. Conduct a candid exit conversation — what would help the next hire? Document for the post-mortem.

The Hardest Decision

Extending is the call most managers avoid. It feels like indecision — but it's actually the most honest answer. "I'm not sure yet, and here's specifically what I need to see in the next 30 days" is a more mature decision than a forced pass or a premature exit. Make extension a normal outcome, not a reluctant one.

How to know your probation process actually works — the 4-step audit

Even a well-designed probation rhythm degrades over time. Leaders skip milestones. PBPs stop following up. Surveys become tick-box exercises. Once a year, audit the system itself — not just the hires moving through it.

01
Process Audit & Scoping

Gap analysis of current practice vs. the 5 C's. Direct data audit, interviews with leaders, experience surveys with recent new hires. Identify which building block is weakest right now.

02
Improvement Design

Targeted redesign of the weakest block. Involve SMT and PBPs. Prepare materials, automate communications, set effective date. Don't try to fix everything — fix one thing well.

03
First Implementation

Roll out the new process for 4 months. PBP tracks consistency. Measure new hire feelings & experience throughout probation. Adjust minor issues live; flag major ones for re-design.

04
Readjust & Formalize

Post-implementation review. Develop refined recommendations with project committee, PBPs, SMTs. Execute the updated process. Formalize as the new SOP for the year ahead.

One last check — the system is working when…

You'll know your probation system is working when three things are true. First, the Day 90 conversation surprises no one — the hire knows it's coming, the leader has had the data for weeks, and the PBP has been in the loop throughout. Second, extension is a real outcome, not a euphemism for "we couldn't decide." Third, your 6-month retention starts climbing — because the 90-day decision is being made on real signal, not on hope.

"Probation is a check on the system, not a check on the candidate. If we're surprised on Day 90, the failure is ours, not theirs."
— The Probation Premise
11 · Measuring Success

TA metrics aren't HR metrics. They're business metrics in disguise.

If you can't measure it, you can't tune it. And if you can't tune it, you're hiring by hope.

Most TA dashboards measure activity — time-to-fill, applicants-per-req, offer-acceptance-rate. These are necessary but insufficient. They tell you how the funnel is running. They don't tell you whether the hires you're making are the ones the business needs.

A great TA scorecard measures three things together: velocity (how fast is the funnel?), quality (are the hires actually working out?), and experience (do candidates and hiring managers come away well?). A weak signal on any one of the three is a problem. A weak signal on all three is an emergency.

Sample TA Health Dashboard

Trailing 12 months
Probation Pass Rate
94%

Target: ≥90%. Healthy. Hires are reaching month 3.

90-Day Retention
96%

Target: ≥95%. Strong. Onboarding is doing its job.

12-Month Retention
79%

Target: ≥85%. Below target. Probation succeeded; embedment may not have.

Quality of Hire (NHM rating, mo 6)
4.2/5

Target: ≥4.0. Hiring managers rating their hires as strong contributors at 6 months.

New Hire Satisfaction (90-day survey)
4.4/5

Target: ≥4.2. Strong. New hires feel set up to succeed.

Voluntary Attrition <1yr Tenure
22%

Target: <15% (non-sales). Above target. Investigate Door 2 & 3 from Section 09.

Time to Fill (median)
38d

Target: ≤45d. Fast enough; not so fast that rigor is compromised.

Offer Acceptance Rate
88%

Target: ≥85%. Healthy. Offers are well-calibrated to candidate expectations.

Candidate NPS (post-process)
+38

Target: ≥+50. Decent but improvable. Audit the rejection experience.

The dashboard above tells a real story. Probation pass rates and 90-day retention are strong — the front end is working. But 12-month retention has slipped, and <1-year voluntary attrition is above target. That's the classic pattern of good hiring, weak embedment. The fix lives in Section 09 — the 5 C's beyond Confidence, and Leader Fit in particular.

Leading vs. lagging — what to act on

Half of these metrics are lagging — they tell you what already happened. Half are leading — they tell you what's about to happen. You manage the lagging. You act on the leading. Confusing the two is how TA dashboards become wallpaper.

Leading Indicators

Act on these — they predict

Measured during or immediately after the hiring process. Predict the lagging metrics 3–9 months out.

  • Job scorecard completeness (every req has one before opening)
  • Panel calibration disagreement rates (high = strong process)
  • New hire 30-day check-in score
  • Onboarding C-completion against the 5 C's
  • Direct-leader 1-1 cadence (% on schedule)
  • Probation form submission compliance (D30, D60, D75)
Lagging Indicators

Watch these — they confirm

Measured 3–12 months after hire. Confirm whether the upstream investment worked.

  • Probation pass rate
  • 90-day & 12-month retention
  • Quality-of-hire score at month 6
  • <1-year voluntary attrition
  • Time-to-productivity (vs. role benchmark)
  • Candidate NPS & hiring-manager satisfaction

One number for the boardroom — the question to ask

If you have to pick one number to summarize the health of your TA function for a board or leadership review, it isn't time-to-fill. It's this: what percentage of last year's hires are still here, performing, at month 12? That number captures hiring rigor, onboarding quality, leader effectiveness, and cultural fit — all four — in a single integer. It can't be gamed. It tells the truth.

Track it. Trend it. Defend it. Then trace its components back through this playbook, section by section, and tune the upstream work to move the downstream number.

"TA's real KPI isn't how many people we hired. It's how many of them are still here, doing the work, twelve months later — and proud they joined."
— The North Star Metric

A closing note from Oaks Co.

This is the end of the playbook, but it's the beginning of the work. The frameworks, models, and toolkits across these ten sections aren't ends in themselves. They're scaffolds for the harder discipline underneath — hiring with care, treating candidates as humans, holding leaders accountable for what they owe their people, and refusing to let the hire decision sit on instinct.

Talent acquisition done well is one of the highest-leverage things a company does. It compounds. The hires you make this year shape the team you'll have for years to come — and the team you have shapes everything else. There are no shortcuts. There is, however, a craft. We hope this playbook helps you practice it well.

One Last Thing

If only one idea from this playbook stays with you, let it be this: a hire doesn't end at the offer. It ends at month 12, with someone performing, embedded, and glad they came. Everything else is in service of that.

Complete · 01–11