People Analytics For Dummies - Book PDF

1. 1Define commitment as an attitude to be measured separately from attrition. Commitment is the bond and the desire to stay and contribute. Attrition is the behavior that may follow. Track both and keep them in separate columns so you can test whether one predicts the other.
2. 2Measure commitment with survey items, not inference from exits. Include commitment to the company alongside related attitudes such as overall satisfaction and motivation, the same set a multi-company employee survey measures. Ask the identical items each cycle so results can be compared over time and against outside benchmarks.
3. 3Measure the behavior side with exit counts and retention rate. Build exit rate by segment, as in the 2017 Exit Rate % by segment view. Retention rate and exit rate come from the same headcount base, so use one consistent definition of headcount.
4. 4Segment before you interpret. Slice commitment scores and exit rates by basic facts such as department and tenure group. Build calculated segments, for example a 1/0 flag for tenure under 1 year computed from Hire Date. Cross-tab two variables at a time. A company-wide average hides the pockets where commitment is thin.
5. 5Read the whole survey, not only the commitment line. High commitment can coexist with a weak category, such as a lower Speaking Up score. Compare each category against your benchmark group and write down every category where you trail, even when the overall picture is strong.
6. 6Find what drives commitment with key driver analysis. Correlate the other survey items with the commitment score and rank them. Use the ranking to decide where to spend time, rather than acting on all 100 items.
7. 7Test whether commitment predicts leaving. Run a binary logistic regression with 'left / stayed' as the outcome and commitment score plus segment variables as predictors. This tells you whether the attitude is a usable retention signal in your company.
8. 8Check the common assumptions about why people stay or leave against your own data. Treat exit surveys cautiously because they carry known problems. Prefer patterns from who actually stays and who goes, then evaluate whether any management action changed the result.

A well-run pharmaceutical company joined a confidential multi-company employee survey. It covered roughly 50 aspects of the employee experience through roughly 100 items and compared the company with high-performing companies across industries. Categories included leadership, managers, pay, benefits, learning and development, plus satisfaction, motivation, and commitment to the company. The company scored above peers in nearly all categories, and its employees were on average more committed, more motivated, and happier, which was statistically validated. It scored slightly below peers on Speaking Up, meaning whether employees felt safe voicing concerns or disagreements to superiors. This was odd because the company prided itself on consensus decision-making. Because everything else looked strong, no substantive new action was decided, although the head of human resources expressed concern. The lesson for commitment work is that a strong commitment score does not clear the other categories. Take the weak category, segment it by group and tenure, and test whether it relates to exits before dismissing it as an anomaly.

• If commitment is high overall but one category trails peers, then segment that category and test its link to exits before deciding to ignore it.
• If exit rate is high in one segment but commitment scores there look normal, then question the survey (who answered, what was asked) before concluding the attitude is fine.
• If you have limited time, then run key driver analysis on commitment and work only the top-ranked drivers rather than the full item list.
• If a proposed retention practice is justified by what other companies do, then require evidence from your own past data or a prediction you can later check; there is no universal set of best HR practices.
• If your only evidence on why people leave is exit surveys, then treat it as provisional and corroborate it with who-stays-and-who-goes patterns.

• Reporting a single company-wide commitment average. The tell: no segment cuts by tenure group or department, and surprises appear later in exit-rate-by-segment charts.
• Letting a strong overall result excuse an odd weak category. The tell: a below-peer item is described as 'strange' and no action or follow-up analysis is recorded.
• Confusing commitment with retention. The tell: one number labeled 'commitment' is computed from exits, with no attitude survey behind it.
• Copying best practices from successful companies. The tell: a retention program justified by a peer's success, with no check against your own data and no later evaluation of whether it worked.
• Relying on exit surveys alone for causes. The tell: the leading explanation for departures comes only from leavers' self-reports and is never tested against patterns in the data.

• ▸Survey source and date: name the survey, the comparison group, and the cycle.
• ▸Commitment items used: list the exact items and any satisfaction and motivation items alongside.
• ▸Overall commitment score vs. benchmark: record your score and the comparison score.
• ▸Categories below benchmark: list every category where you trail, however small the gap.
• ▸Segments analyzed: note department, tenure group (e.g., under 1 year flag), and any calculated segments.
• ▸Exit rate and retention rate by segment: enter both for the same period and headcount base.
• ▸Top key drivers of commitment: list the highest-ranked items from the key driver analysis.
• ▸Does commitment predict leaving?: state the result of the logistic regression or your plan to run it.
• ▸Action and check: record the one action chosen, the prediction it makes, and the date you will test it.

1. 1Define performance as the value side of Employee Lifetime Value (ELV). Write one sentence for the role you are studying: what output does this person contribute, and to which business result (sales, customer loyalty, team effectiveness)? The source frames people as the face, heart, and hands of the company, so tie the output to a customer or business number rather than to activity.
2. 2Break performance into the ABC chain: Antecedents (what sets the behavior up), Behaviors (what the person does), Consequences (what follows). List the behaviors you believe drive the result, and list the antecedents and consequences around each. This turns 'performance' into things you can observe and change.
3. 3Pick the measures for each behavior. Pull outcome data from the systems the source lists: performance management systems, HRIS, payroll, and employee surveys. For behaviors that have no system record, such as a skill like Listening, use a Behaviorally Anchored Rating Scale (BARS) and the Critical Incident Technique to define observable anchors.
4. 4Segment before you average. Cut performance by basic employee facts (the book's tenure-group example is one) and by calculated segments. Compare metrics across segments to see where performance differs, then cross-tab two variables to find where the difference concentrates.
5. 5Add the 'activation' view. The source separates lifetime value from activation and combines them as Net Activated Value (NAV). Measure activation with a survey built on the CAMS elements. Use it to separate capable but not-yet-productive people from people who are simply low performers.
6. 6Find what moves performance. Run Key Driver Analysis on survey items against a performance or effectiveness outcome (the source uses items correlated with Team Effectiveness). Then test the top candidates with multiple regression so several drivers are weighed together.
7. 7Test interventions on a small group, as the pet retailer did. Apply the change to a few units, keep comparison units without it, and compare using the metrics you already track. Expand only if the difference holds.
8. 8Convert the result to ELV. Compare the value an employee or segment contributes with its cost across the employment lifetime, and rank the actions by their ELV effect. The source's example is the average software engineer, shown as cost, value, lifetime value, and ELV.

The pet retailer wanted to know whether adding services such as grooming would pay off. The services needed more skilled, better-paid employees, and rolling them out everywhere without observation 'could bankrupt the company.' So it introduced the services in a small set of stores and kept another set without them as a comparison. Using the same metrics it already tracked (store visits, sales, loyalty), it compared the two groups with 'relatively simple math.' Stores with services showed higher visits, spending, and loyalty. A less obvious finding was that groomed pets' owners spent more on the pet over its whole lifetime. The higher-paying service roles also created a ladder of jobs, which made the company a long-term career option for the people it wanted to attract. For employee performance, the lesson is the structure of the test. You attribute the value of a new role or behavior by comparing groups on existing outcome metrics before scaling, then follow the effect over a lifetime rather than one transaction. The passages do not give the figures, so you supply your own.

• If you cannot name the business outcome a role's behaviors feed, then stop and define it before measuring anything; otherwise you get activity without a clear result.
• If an intervention is costly or risky to scale, then pilot it in a few units with comparison units and use your existing metrics, as the pet retailer did.
• If average performance looks flat, then segment (tenure, calculated segments, cross-tabs) before concluding nothing differs.
• If performance is low in a segment, then check activation (the CAMS survey) and the antecedents and consequences before judging the individuals.
• If you have many survey items and one performance outcome, then use Key Driver Analysis to rank candidates and regression to test them together, rather than reacting to every item.

• Measuring output with no link to a business result. The tell: a dashboard of activity metrics that nobody can connect to customer or financial outcomes.
• Skipping the experiment and rolling out to everyone. The tell: results improve or worsen and you have no comparison group to say why.
• Treating performance as only individual effort and ignoring antecedents and consequences. The tell: coaching conversations that blame people for outcomes driven by setup or incentives.
• Reading company-wide averages. The tell: a stable overall number hiding strong and weak segments.
• Reading correlation as cause from survey drivers. The tell: you act on the top correlated item without testing whether it moves the outcome.

• ▸Role / segment: name the role and the segment (for example tenure group) you are analyzing.
• ▸Business outcome: the customer or financial result this role's output feeds.
• ▸Key behaviors: the 3-5 observable behaviors you believe drive the outcome.
• ▸Antecedents and consequences: for each behavior, what triggers it and what follows it.
• ▸Measures and sources: the metric or rating scale (such as BARS) and the system it comes from.
• ▸Activation check: CAMS survey result or planned survey, and what it shows or would show.
• ▸Top drivers: survey items or variables from Key Driver Analysis or regression, ranked.
• ▸Pilot design: test units, comparison units, metrics compared, and the decision date.
• ▸ELV effect: expected change in value and cost across the employment lifetime, and the recommended action.

1. 1Pull one record per employee with a hire date and, for leavers, a termination date. Tenure is only as good as those two fields, so check them before you calculate anything.
2. 2Pick a report date for active employees and use it consistently. Your source's headcount reports are run as of a fixed date (for example 9/30/2017). Tenure for an active employee runs from hire date to that date; for a leaver it runs from hire date to termination date.
3. 3Calculate tenure in days first (end date minus hire date, as in the Excel walk-through), then convert days to years in a separate column. Keep both columns so you can switch between months and years later.
4. 4Create tenure groups and categorize every employee into one, then chart headcount by group. This shows the shape of your workforce: how many people are new and how many are long-serving.
5. 5Add an if-then flag column: 1 if tenure is under 1 year, 0 for everyone else. The flag makes early-tenure analysis a simple filter or sum.
6. 6Use tenure as a segment on your existing metrics. Voluntary attrition rate by tenure sits beside division, job function, performance rating, and region as a standard cut. Compare each tenure segment's exit rate with the company average and express the gap as a multiple.
7. 7When one tenure segment stands out, break it down by job. Then use applicant and employee history data to find the characteristics that predict who stays longer.
8. 8Treat tenure as the time dimension of Employee Lifetime Value. When you model ELV, record how a change in retention would extend tenure for the segment.

A children's hospital knew its first-year nurse attrition rate was 25 percent, meaning 1 in 4 new nurses left within a year. Average employee attrition was 10 percent, or 1 in 10 people in a given year. Comparing the early-tenure segment with the company average gives 25 ÷ 10 = 2.5 times worse. The problem reinforced itself: each exit needed a replacement who was identified, hired, onboarded, and trained, and the replacement might leave just as quickly. New nurses were also more likely to make mistakes in complex situations. Analysis of applicant and employee history data showed that hiring more experienced nurses, rather than nurses straight out of nursing school, produced people more likely to succeed and more likely to stay beyond their first year. Experienced hires cost more in pay. The hospital still chose to hire for the characteristics that predicted longevity, with the aim of lowering first-year attrition.

• If you report attrition, then always split it by tenure as well as by division, job function, performance rating, and region. An average hides the early-tenure spike.
• If a tenure segment's exit rate is a large multiple of the company average (like 25% vs 10%), then treat it as a priority problem. Replacement hiring and training costs and error risk compound it.
• If early-tenure exits are high, then check applicant and employee history data for hire characteristics that predict staying before you spend on retention programs.
• If a hire characteristic extends tenure but costs more (experienced nurses paid more), then weigh the higher pay against replacement cost and success rates, not against pay alone.
• If you need tenure cuts across many metrics and segments every month, then automate the calculation in a dashboard rather than hiring more people to rebuild it by hand.

• Reporting only one company-wide attrition number. The tell: nobody can say whether the problem sits in the first year or among long-serving staff.
• Mixing end dates, for example measuring leavers to termination date and actives to an unspecified date. The tell: tenure figures change depending on who ran the report or when.
• Leaving tenure in raw days or ad hoc groups. The tell: charts are unreadable, or groups differ between reports so segments cannot be compared.
• Fixing early exits by only refilling the seat. The tell: replacements leave just as quickly, and the cycle of hiring, onboarding, and training repeats.
• Judging a hiring change on its salary cost alone. The tell: the case against hiring experienced people ignores their higher success rate and likelihood of staying past year one.

• ▸Report date: the fixed as-of date used to calculate tenure for active employees.
• ▸Hire date and termination date source: the systems and fields these come from, and who verified them.
• ▸Tenure in days: end date minus hire date for each employee.
• ▸Tenure in years: the converted figure, kept in a separate column.
• ▸Tenure groups: the bands you assign every employee to, with headcount per band.
• ▸Under-1-year flag: 1 if tenure is less than one year, 0 otherwise.
• ▸Segment exit rate vs company average: exit rate for each tenure group, company average, and the multiple (e.g. 25% ÷ 10% = 2.5x).
• ▸Cross-cut: the job, division, or region where the highest-risk tenure segment is concentrated.
• ▸Predictor hypothesis and action: the hire characteristic that appears to predict staying, and the decision it supports.

1. 1Pick one segment before you calculate anything. The source shows ELV varying by segment (Figure 6-4), so an all-company average hides the differences you need. Start with a single role, such as the average software engineer used in Figure 6-1.
2. 2Build the tenure side from your own records. Calculate each employee's tenure from Hire Date in Excel, convert days to years, and group by tenure band, as in Chapter 4. For leavers, use the segment's exit rate to judge how long a typical hire stays.
3. 3Estimate the value created per period for that role, which is the performance half of the definition. Tie it to your business value creation model (Figure 2-1) so the number reflects business outcomes rather than activity.
4. 4List the cost of the employee over the same period, then lay out the four items in the order Figure 6-1 does: cost, value, lifetime value, ELV. Value accumulated over expected tenure is lifetime value. Net of cost, it is ELV.
5. 5Write the formula in one line: ELV = (value created per period × expected tenure) − cost. This is constructed from the definition (performance × tenure, net). The passages do not supply the arithmetic, so state your assumptions beside every input.
6. 6Scale it. Multiply the per-person ELV by the number of hires to see the aggregate effect, as Figure 6-2 does for 50 hires. This turns a per-head estimate into a resource decision.
7. 7Test each lever separately (Figure 6-3: there is more than one way to increase ELV). Map them to the triple-A framework. Attraction affects cost, activation affects value created, and attrition affects tenure. Change one input at a time and see which moves ELV most.
8. 8Compare ELV across segments and spend time and resources where a change in value or tenure produces the largest gain. Feed the result back into your employee journey map (Chapter 8) so you act on the stages that move ELV.

The source's pet retailer shows the logic without printing an ELV figure. The retailer added grooming and other pet services in a set of stores and compared them with stores that had none. Those stores saw more visits, spending and loyalty. Store-level employee data then showed that satisfaction and retention of the new service employees affected customer loyalty and sales more than that of cashiers or stockers. Across all jobs, the more pet-specific knowledge a job required, the more its attrition hurt the company. In ELV terms, tenure is the lever with the most leverage for those roles: each lost service employee cuts the years over which their value accrues and forces a new hire's cost. To put numbers on it, compute for each job ELV = (value per year × expected years) − cost, using real tenure from hire dates and real exit rates by job. Then rank the jobs. The prediction from the source is that jobs needing distinct pet knowledge will gain the most from longer tenure, so retention spending belongs there first.

• If ELV differs sharply between segments, then allocate hiring and retention effort to the high-ELV segments first, and do not use a company-wide average.
• If a role's value per period is high but expected tenure is short, then work on attrition (reasons for leaving, commitment) before attraction volume.
• If tenure is healthy but value created is low, then work on activation (the ABCs of a productive worker) before spending on retention.
• If cost per hire is the dominant term, then look at talent acquisition efficiency (time-to-fill, funnel conversion) before changing the other two levers.
• If two levers could raise ELV by similar amounts, then pick the one you can change and measure with the data you already have.

• Using one company-wide average ELV. The tell: every role shows nearly the same number and no resourcing decision changes.
• Counting value without cost. The tell: ELV is positive for every segment, including ones you suspect lose money, because only the lifetime value step was done.
• Using guessed tenure instead of tenure from hire dates and exit rates. The tell: the tenure input cannot be traced to an employee list or an attrition report.
• Treating ELV as a precise figure. The tell: no stated assumptions, and a single number is presented to executives with no range or sensitivity test.
• Changing several levers at once. The tell: ELV rises but you cannot say whether attraction, activation or attrition caused it.

• ▸Segment/role: name the single role or segment you are valuing (e.g., software engineer).
• ▸Expected tenure (years): from hire-date tenure and the segment's exit rate; note the source.
• ▸Value created per year: your estimate of performance in business terms, with the assumption behind it.
• ▸Cost per employee: total cost for the same period and basis as the value figure.
• ▸Lifetime value: value per year × expected tenure.
• ▸ELV: lifetime value − cost.
• ▸Headcount scenario: number of hires (e.g., 50) × ELV to show aggregate effect.
• ▸Lever to test: attraction (cost), activation (value) or attrition (tenure); change one only.
• ▸Revised ELV and decision: ELV after the lever change, and where you will direct time and resources.

1. 1Name the business outcome you are trying to move before you pick any people metric. The passages frame it as profitability, productivity, and the avoidance of costly failures such as a recall that cost billions. Write the outcome and the people decision you think affects it in one sentence.
2. 2Measure broadly before you know what matters. The pharmaceutical company's survey covered roughly 50 aspects of the employee experience using roughly 100 items, and the category that later mattered (Speaking Up) was one nobody had flagged. Keep survey breadth, because you don't know what you don't know.
3. 3Benchmark against a stated comparison group. That company compared itself with other high-performing companies across all industries. For each category, record whether you are above or below the group, and treat any category where you trail as a candidate finding, even when the overall picture is strong.
4. 4Investigate every below-benchmark result against a specific business risk. Ask what decision or behavior would go wrong if this result were true. Do not dismiss it because every other score is good. Assign an owner and a follow-up inquiry before closing it.
5. 5Quantify known problems as a ratio to the company baseline. The children's hospital compared 25 percent first-year nurse attrition with 10 percent overall attrition, which made early-tenure attrition 2.5 times worse than average. State the cost in operational terms: identify, hire, onboard, and train a replacement, plus a higher mistake rate among new nurses.
6. 6Use applicant and employee history data to find the characteristics that predict the outcome you want. The hospital found that experienced nurses were more likely to be successful and to stay beyond year one, even though they cost more to pay. Test the alternative before committing to it.
7. 7Change the decision and then evaluate it. Shift hiring toward the characteristics that predicted longevity, then track the same attrition metric afterward to see whether the fix worked and what to improve next.
8. 8Close the loop to the business outcome. Translate each people-metric change into its effect on productivity, cost, or risk so the result is read as business success rather than HR activity.

A large pharmaceutical company, successful for over a hundred years, took part in a confidential cross-company employee survey of roughly 100 items across roughly 50 aspects of the employee experience. It beat other high-performing companies in nearly all categories, including commitment, motivation, and satisfaction. It scored slightly below them on Speaking Up, which measured whether employees felt safe voicing concerns or disagreements to superiors. Leadership read this as an echo of its debate over breaking the consensus culture, and with every other score strong, took no substantive action. A research director then overrode scientists' concerns about a possible drug safety issue. The drug was later recalled, which risked lives, cost billions, and nearly took down the company. The lesson in the source: had the Speaking Up gap been taken seriously, a channel for the scientists could have checked the director. The rule is to chase the one below-benchmark category, however good the overall average looks.

• If a metric trails a high-performing benchmark while most others lead, then investigate it before you celebrate the overall result.
• If a leadership narrative explains away an unexpected score, then require data from a second source before accepting the explanation.
• If a problem rate is known, then express it as a multiple of the company average (25% vs. 10% = 2.5 times) to size its urgency.
• If a candidate fix costs more per unit, as experienced nurses do in pay, then test whether the outcome gain (success and retention) outweighs the cost before rejecting it.
• If a solution is implemented, then re-measure the same metric afterward so you can evaluate it and improve going forward.

• Averaging away the warning: a strong overall survey score hides a weak category. The tell is that no action items exist for any below-benchmark item.
• Letting results excuse behavior: a high performer with a big ego wins arguments because he delivers. The tell is that concerns raised by others are squelched in favor of progress.
• Explaining anomalies with a convenient story: the Speaking Up result was attributed to culture-change efforts without testing. The tell is an explanation nobody can verify.
• Treating the obvious fix as obvious without data: assuming experienced hires help without quantifying the effect. The tell is that you cannot state how much difference it makes operationally.
• Fixing the symptom with replacement hiring: backfilling early exits with the same profile. The tell is that the first-year attrition rate stays at 25 percent, because replacements leave as quickly.

• ▸Business outcome at stake: state the profitability, productivity, or risk outcome in one sentence.
• ▸Metric or survey category: name the people measure under review.
• ▸Your score vs. benchmark: record your result and the comparison group's result.
• ▸Direction of gap: mark above or below, and note any category where you trail despite a strong overall score.
• ▸Baseline ratio: divide the problem rate by the company average (e.g., 25% / 10% = 2.5x).
• ▸Operational cost of the problem: list the replacement, training, and error costs.
• ▸Candidate decision change: describe the hiring or management change the data suggests.
• ▸Owner and follow-up date: name who investigates and when.
• ▸Re-measure result: record the same metric after the change and what you will adjust.

1. 1Anchor attraction in the triple-A framework. Attraction is one of three people problems (attract, activate, control attrition), so write down what the business needs from hiring before you measure anything: which roles, how many, and how fast the company is growing.
2. 2Map the front end of the employee journey. The journey starts when a person becomes aware of the job opportunity. List each stage a candidate passes through, then add the company touchpoints at each stage (sourcing channel, screen, interview, offer). Decide how you will measure each touchpoint, using system data or a survey.
3. 3Define the process metrics in writing before you count. The source names hire rate, growth rate, time-to-fill, time-to-start, and talent acquisition efficiency. Use one standard definition per metric, in the style of the HR Metric Definitions Guide, with explicit start and stop events, so every recruiter and report counts the same thing.
4. 4Build the funnel for each sourcing channel and compare funnels side by side (the 'tale of two funnels'). Count candidates at every stage and look for the stage where one channel or team loses people the other keeps. That stage is where you intervene.
5. 5Segment before you conclude. Cut every metric by job family, location, business unit, and any other basic employee fact. An average hides the team that needs to 'step up its game'.
6. 6Define the job and its competencies before you change interviewing (Appendices C and D, job analysis and competency analysis). Then build structured interview scoring with a Behaviorally Anchored Rating Scale, such as the Listening skill example, and use the Critical Incident Technique to collect real examples of effective and ineffective behavior as scale anchors.
7. 7Value the hire, not just the speed. Use Employee Lifetime Value (ELV) to judge whether more time or money in sourcing and selection is worth it, and compare ELV across segments. Check whether the lever is more hires, better hires, or longer-staying hires (there is more than one way to raise ELV).
8. 8Run the loop. Change one attraction practice, ideally as an experiment with a comparison group (Chapter 16), and re-measure the same funnel and efficiency metrics. Track whether those hires later activate and stay, so attraction is judged by what happens downstream.

The source contains no numeric attraction case, so this walk-through uses placeholder numbers (hypothetical, not from the book). You run talent acquisition for engineering and compare two funnels, referral and job board. Per 100 applicants, say 20 referrals reach interview versus 8 job-board applicants, but both channels convert interviewees to hires at the same rate. The problem is therefore upstream screening for the job board, not interviewing. You also compute time-to-fill and time-to-start by segment, using one written definition for each, and find that one location is slow while the others are fine. Next you look at ELV for the software engineer role (the book's Figure 6-1 case), where cost, value, and lifetime value are laid out, and judge whether a longer search for a better-fit hire pays back. You then change the screen for the weak channel and re-measure the same funnel next quarter. After the change, you check whether those hires show up later in activation and attrition data.

• If hire volume is short, then look at the funnel stage-by-stage by channel before spending more on sourcing; the leak is usually at one stage.
• If a metric differs across teams or locations, then check that the definitions match before acting on the gap.
• If you are tempted to cut time-to-fill, then check ELV first; speed that lowers quality or retention can cost more than the delay.
• If interviewers disagree or rate on gut feel, then do job analysis and competency analysis and install behaviorally anchored rating scales before changing sourcing.
• If you want to claim a practice change worked, then compare against a control group or a prior baseline measured with the same definitions, not an anecdote.

• Counting without agreed definitions: two recruiters report different time-to-fill for the same req. The tell is that dashboards never reconcile with each other.
• Reporting only company-wide averages: one healthy number masks one failing team. The tell is that leaders say 'hiring is fine' while a specific manager keeps open reqs.
• Optimizing speed and cost while ignoring value: time-to-fill improves but new hires underperform or leave early. The tell is falling ELV and weak activation from recent cohorts.
• Unstructured interviews with no anchored criteria: ratings drift by interviewer. The tell is that interview scores don't relate to later performance and nobody can cite specific behaviors behind a rating.
• Treating attraction as isolated from the journey and the other A's: recruiting is measured on its own, so problems in activation or attrition are blamed on 'bad hires'. The tell is attraction metrics being reviewed separately from onboarding and exit data.

• ▸Role / segment: Name the job family, location, and business unit being analyzed.
• ▸Business need: State the hiring volume and timing the business requires.
• ▸Sourcing channel: List each channel (e.g., referral, job board) as a separate funnel.
• ▸Stage counts: Record candidates at each stage from application to start, per channel.
• ▸Metric definitions: Write the start and stop events for hire rate, time-to-fill, and time-to-start.
• ▸Metric values by segment: Enter each metric for each segment so gaps are visible.
• ▸Selection method: Note the interview format and whether a behaviorally anchored scale is in use.
• ▸ELV note: Record the role's ELV (cost, value, lifetime value) and which lever you are trying to move.
• ▸Change and re-measure date: Describe the one practice you are changing and the date you will re-pull the same metrics.

1. 1Place activation inside the triple-A frame (attraction, activation, attrition). Activation is the stage where a hired person becomes productive. Write down which population you are examining (one function, one location, or one tenure band) so the levers are measured against one group.
2. 2Write a working definition of each CAMS lever in one sentence. Capability: can people do the work. Alignment: do they know what the business needs from them. Motivation: does the environment give them reason to put in effort. Support: does the workplace give them what they need to perform. Keep the wording identical across every later step.
3. 3Build a CAMS survey with a block of items for each of the four factors, all on the same response scale. Draft the items before you open the survey tool. Each item should belong to exactly one factor so the factor scores stay separable.
4. 4Score each factor as a subindex, then combine the four into one activation score. Report the four subindex scores next to the total, because the total hides which lever is weak.
5. 5Segment the results with the Chapter 4 methods: basic employee facts, then calculated segments. Example: a tenure-under-1-year flag built from hire date with an if-then formula. Compare factor scores by segment to see where one lever is low for one group.
6. 6Run a key driver analysis, or a multiple regression if you have an outcome measure, to see which CAMS factor moves the outcome you care about. Fix the lever that is both low and strongly linked to the outcome, not simply the lowest score.
7. 7Translate the chosen lever into management actions using the ABC logic (antecedents, behaviors, consequences). Name the condition you will change, the behavior you expect to shift, and the consequence that will reinforce it.
8. 8Re-survey the same population on the same items after the action. Compare the subindex that was targeted against the others. Connect the activation change to employee lifetime value through Net Activated Value to size the business impact.

This is an illustration, not a case from the source. A company wants to know why a customer-support team is less productive than its peers. You define activation for that team alone and field a CAMS survey with identical items per factor. Subindex scores come back with Capability, Alignment, and Motivation similar to the company average and Support clearly lower. You build a tenure-under-1-year flag from hire date and cross-tab: the Support gap is concentrated among the newest employees. A key driver analysis against a productivity measure shows Support carries the strongest relationship, so it is both low and influential. You treat Support as the antecedent to change, choose one specific workplace condition to fix for new hires, and state the behavior you expect to improve. After the change you repeat the same survey. If Support rises and the other three stay flat, you have evidence the action worked. If all four move, you cannot attribute the gain to the lever you changed.

• If one subindex is clearly lower than the others, then target that lever first; if all four are low, then check survey design and segment definitions before acting.
• If a lever scores low but shows a weak link to the productivity outcome in key driver analysis, then rank it below a moderately low lever with a strong link.
• If the overall score looks acceptable, then still read the four subindexes and the segment cuts, because averages hide a weak lever concentrated in one group.
• If you cannot name the behavior a lever is supposed to change, then do not fund the action; define the antecedent-behavior-consequence chain first.
• If the follow-up survey uses different items or a different population than the baseline, then treat the comparison as invalid and do not claim the intervention worked.

• Treating CAMS as a single engagement score. The tell: the report shows one number and no subindexes, so nobody can say which lever to pull.
• Survey items that blur factors, such as one question about both training and goals. The tell: factor scores move together and cannot be separated.
• Acting on the lowest score without testing whether it relates to performance. The tell: effort goes into a lever and the productivity outcome does not move.
• Running the analysis company-wide with no segmentation. The tell: the average looks fine while one tenure or location group is struggling.
• Starting with tools, surveys, and data cleanup before defining the problem focus. The tell: lots of activity and no clear decision the data was meant to inform.

• ▸Population and segment: name the group being assessed (function, location, tenure band) and the calculated segment rule, if any.
• ▸Outcome measure: state the productivity or performance measure the levers are expected to influence.
• ▸Capability subindex score: enter the score from the survey items assigned to Capability.
• ▸Alignment subindex score: enter the score from the survey items assigned to Alignment.
• ▸Motivation subindex score: enter the score from the survey items assigned to Motivation.
• ▸Support subindex score: enter the score from the survey items assigned to Support.
• ▸Strength of link to outcome (per lever): record the key driver or regression result for each factor.
• ▸Priority lever and ABC chain: name the lever chosen, the condition to change (antecedent), the expected behavior, and the consequence that will reinforce it.
• ▸Re-survey date and success test: set the follow-up date, confirm identical items and population, and state what change in the targeted subindex counts as success.

1. 1Anchor the case in a value model. Draw the business value creation chain from people inputs (acquisition, experience, engagement, retention) to financial outputs, so executives see where retention spend connects to results. Retention is a long-term driver, and quarterly-earnings thinking will otherwise push it aside.
2. 2Define the key talent segments before you measure anything. Pick key jobs (those requiring distinct, hard-to-replace knowledge) and key performance levels (highest performers). Overall averages hide the differences that matter.
3. 3Compute exit rate for the company overall, then cut it by key job and by performance level. Compare each segment to the company average. A flat or rising company average means nothing until you see whether key talent leaves faster or slower than everyone else.
4. 4Test whether the money is working. State the purpose of each retention program (for example, a performance-based pay differential meant to make top performers hard to poach). Then check whether the highest performers' attrition rate is lower than that of average and lowest performers. If it isn't, the spend is not doing its job.
5. 5Rank jobs by how much attrition in them hurts outcomes. Link store- or unit-level attrition and satisfaction by job to customer loyalty and sales, as the pet retailer did. The more distinct the job knowledge, the more attrition costs. Allocate the people budget to those jobs rather than spreading it thinly.
6. 6Check the perception chain for pay-based retention. Ask whether pay differences are large enough to matter, whether top performers notice them, whether they see pay as fair, and whether they are happier and more committed than average. Use a survey cut by key segments.
7. 7Build the supporting structure: a ladder of jobs of increasing skill, open to lower-level employees who want to move up (the pet retailer let entry-level store workers apply for the more lucrative service jobs).
8. 8Test before scaling. Run retention strategies as experiments, collect feedback continuously, and expand only what shows an effect on the target segment's exit rate.

A pet retailer thin on margin added in-store pet services. Analysis showed stores with services produced more of the desired business outcomes than stores without, so the company decided to expand the program. Store-level employee data over time then showed that the satisfaction and retention of the new service employees affected customer loyalty and sales more than that of cashiers or stockers. Across all jobs, the more distinct pet-related knowledge a job required, the more its attrition hurt the company. The company concentrated its people budget on reducing attrition in those key jobs instead of spreading resources thinly across every job, which could have produced weak or no results for the same cost. It also kept a ladder of jobs open, so any entry-level worker could apply for the more lucrative service roles, and many did. The initiative was targeted by job, backed by data, and paid for within a limited budget.

• If the company exit rate is rising or falling, then do not call it good or bad until you segment by key job and performance level.
• If key talent exits faster than the company average, then treat it as a problem even when the overall rate looks fine.
• If high performers leave at a lower rate than average and low performers at a higher rate, then the retention strategy is working. Keep the pay differential.
• If attrition in a job measurably moves customer or financial outcomes more than in other jobs, then concentrate retention resources there rather than spreading them evenly.
• If top performers do not notice, or do not see as fair, the pay differences you built, then the program is wasted money. Fix communication and fairness before adding spend.

• Reading the aggregate exit rate alone. The tell: the debate is about whether the number is 'good' with no segment comparison.
• Spreading retention budget evenly across all jobs. The tell: the same perk for cashiers and specialist roles, with no link to outcome impact.
• Pay-for-performance with negligible differences. The tell: heavy performance-management effort, but top and bottom performers' pay and attrition look about the same.
• Spending to make people happier without checking outcomes. The tell: engagement scores rise but key-talent exit rates don't move.
• Copying other companies or relying on anecdotes. The tell: programs justified by 'what competitors do' rather than your own segmented data.

• ▸Key jobs and why: list the jobs where attrition hurts outcomes most (e.g., distinct knowledge required) and the evidence.
• ▸Key performance segment: define who counts as highest performers.
• ▸Company exit rate (period): overall baseline to compare against.
• ▸Key job exit rate vs. average: record each key job's exit rate and whether it is above or below the company rate.
• ▸Exit rate by performance level: record highest, average, and lowest performer rates.
• ▸Program and stated purpose: name each retention program and the outcome it is meant to produce.
• ▸Perception check: do top performers notice, perceive as fair, and feel more committed because of the program? (survey, cut by segment)
• ▸Decision: expand, adjust, or stop, with the segment-level evidence behind it.
• ▸Test and review date: the experiment or follow-up measurement that will confirm the effect.

1. 1Define hiring quality in your own terms before you measure it. The passages offer no universal formula, so pick outcomes tied to your goals, such as first-year retention, success in the role, and contribution. Write each down as a number you can pull from your systems.
2. 2Choose a project where hiring quality is the problem. Use the passages' selection test: which of recruiter output, hiring time, hiring cost, or hiring quality offers the best return? Start with early-tenure attrition if it runs well above your company average, as the hospital's did (25 percent against 10 percent).
3. 3Establish the baseline by segment. Compute first-year attrition for the target job and compare it to the overall rate. Express the gap as a ratio (25% / 10% = 2.5 times worse). Segment by job function, tenure, and region, since the passages say segment cuts usually surface what executives care about.
4. 4Assemble candidate and employee history in one dataset. Pull candidate facts from your systems: source/channel, most recent employer, most recent university, education level, test score, and requisition ID. Join them to outcomes (stayed past year one, performance, success in the role).
5. 5Test which prehire characteristics predict the outcome. Start with scatterplots and correlations in Excel, then move to regression (binary logistic regression for stay/leave). The passages' own chapter titles include 'First-year exit and prehire characteristics' and binary logistic regression in SPSS.
6. 6Turn the strongest predictor into a hiring criterion, then price it. Calculate what the higher-quality hire costs (the hospital paid experienced nurses more) against what you save in recruiting, onboarding, and training from fewer replacements. Proceed only if the savings offset the premium.
7. 7Pilot on a small scale before full rollout. The passages recommend evaluating solutions at small scale to confirm they work. Apply the new criterion in one unit or requisition group and compare its attrition to the baseline.
8. 8Track the lagging indicators and report them. Re-measure first-year attrition and the operating results that matter. The hospital's showed attrition falling, costs falling, and patient safety measures rising. Make the measurement the accountability loop.

A children's hospital found that first-year nurse attrition was 25 percent, meaning 1 in 4 new nurses left within a year, against a 10 percent attrition rate overall. That made early-tenure nurse attrition 2.5 times worse than average. It was also self-reinforcing, because each replacement could leave just as quickly. Every exit meant identifying, hiring, onboarding, and training another nurse. Newer nurses were also more error-prone in complex situations. Analysis of applicant and employee history data showed that hiring experienced nurses, rather than nurses straight out of nursing school, produced hires who were more successful and more likely to stay beyond year one. Experienced nurses cost more to pay. Even so, targeting the characteristics that predicted longevity was projected to cut first-year attrition from 25 percent to 15 percent, and the savings in recruiting and training more than offset the pay premium. Over time, attrition fell, costs fell, and patient safety measures rose. The point is that the hospital knew the direction was 'obvious' but did not know the operational size of the effect until it looked at the data.

• If first-year attrition for a role is well above your company average, treat it as a hiring-quality problem and look first at prehire characteristics such as experience, source, and test score.
• If a data-backed hiring criterion raises compensation cost, then compare the premium to the saved recruiting, onboarding, and training cost before adopting it. Adopt it only if the savings more than offset the premium.
• If a finding is plausible but unproven in your setting, then pilot it at small scale before rolling it out.
• If another company's hiring practice worked for them, don't copy it as a 'best practice'. Test whether it predicts outcomes with your own data, goals, and culture.
• If attrition matters more in jobs requiring distinct, hard-to-replace knowledge (as in the pet retailer), then concentrate hiring-quality effort on those key jobs rather than spreading budget thinly across all jobs.

• Treating hiring quality as an assumption rather than a measured outcome. The tell: you cannot state the first-year attrition rate for a role or compare it to the company average.
• Acting on the 'obvious' answer without sizing it. The tell: you hire for experience, or any other trait, with no estimate of the attrition reduction or net cost.
• Counting only the hiring premium and ignoring replacement cost. The tell: the business case compares higher salaries to nothing, so the experienced hire looks like pure added expense.
• Copying best practices from other companies. The tell: your criteria come from what 'Acme Company' did, not from your own applicant and employee history.
• Spreading effort evenly across all jobs. The tell: the same hiring-quality investment goes to cashier-type roles and to specialized, high-impact roles alike, and no result shows up in the key ones.

• ▸Target role: name the job or job family where early attrition or poor performance is concentrated.
• ▸Baseline first-year attrition (%): share of hires in this role who leave within 12 months.
• ▸Company average attrition (%): overall annual rate for comparison.
• ▸Gap ratio: baseline divided by company average (the hospital's was 25/10 = 2.5).
• ▸Prehire characteristics tested: list the candidate facts analyzed (source, prior employer, university, education level, test score, experience).
• ▸Strongest predictor of staying/success: the characteristic with the clearest relationship to the outcome, and the method used (correlation, regression).
• ▸Projected attrition after change (%): the expected rate if you hire on that predictor (the hospital's projection was 15%).
• ▸Cost comparison: extra pay or sourcing cost per hire versus saved recruiting, onboarding, and training cost per avoided exit.
• ▸Pilot scope and result: where you tested the criterion at small scale, and the attrition and operating-metric changes observed.

1. 1Split the state into its four components exactly as defined: Capable (can I do the job), Aligned (do I see how my work serves organizational goals), Motivated (will I exert effort), Supported (do I have the tools and resources). Treat each as its own subindex. One blended 'engagement' number hides which component is failing. The source's Chapter 10 'activation subindex scoring' and its CAMS survey tables point to this subindex structure.
2. 2Write survey items per component, with several statements for each. Use the same agree/disagree format throughout so subindexes are comparable. Keep a one-row-per-item sheet showing which component each item feeds. The book's 'Setting up a CAMS survey' and 'Elements of a CAMS survey' tables are the layout to follow.
3. 3Field the survey as a measurement of a psychological state, not a satisfaction poll. Ask about the job, goals, effort, and resources. Do not ask about perks or general happiness. The source's example survey measured commitment, motivation, and happiness well and still missed a gap elsewhere, so breadth on general attitudes does not substitute for the four components.
4. 4Score each subindex separately, then compare against other high-performing companies or internal benchmarks. Read the results by component first and the overall score last. Anything below benchmark gets flagged, even slightly, even when the overall result looks excellent.
5. 5Segment the subindex scores using the Chapter 4 facts you already hold: department, tenure group, location, manager. A state that looks healthy company-wide is often low in one segment, and segments are where action becomes possible.
6. 6For each weak subindex, work backward with the ABC model (Antecedents, Behaviors, Consequences). Ask what antecedents (tools, direction, expectations, safety to speak) or consequences are shaping the behavior. Name one lever per weak component. Activation levers are the cause and the state is the outcome, so you change levers and re-measure the state.
7. 7Connect the state to value. Pair each segment's activation score with its Employee Lifetime Value to get Net Activated Value (the Chapter 7 combination). Prioritize the segments where high lifetime value meets low activation.
8. 8Re-run the same items on a fixed cadence and compare like with like. Judge a lever by whether the targeted subindex moved, not by whether the overall score moved.

The source describes a well-run company whose survey covered opinions on future prospects, leadership, managers, pay, benefits, and development, plus attitudes such as satisfaction, motivation, and commitment. It beat other high-performing companies in nearly all categories, and employees were more committed, more motivated, and happier, validated statistically. One category, Speaking Up (a safe environment to express concerns or disagreements with superiors), came in slightly below other high-performing companies. That was odd, because the company prided itself on decision-making by consensus. Because everything else was strong, no substantive new action was decided, though the head of human resources expressed concern (the passage cuts off here, so no outcome is given). Read through the four components, the lesson is that an overall result can sit above benchmark while one condition for activation, here feeling safe and supported enough to voice concerns, lags. A subindex review would flag Speaking Up as the item to trace through antecedents and consequences, rather than letting the strong overall score close the question.

• If the overall activation score is above benchmark but one component subindex is below it, investigate that component anyway. A strong average is not evidence the weak part is harmless.
• If a segment's subindex is low and that segment has high Employee Lifetime Value, prioritize it over a larger segment with low value (Net Activated Value logic).
• If the weakest component is Supported, check tools and resources before touching motivation programs. Motivation efforts cannot fix a missing resource.
• If a finding contradicts the company's self-image (such as consensus culture alongside low Speaking Up), treat the contradiction as the signal and trace the antecedents. Do not explain it away.
• If a re-measure shows no movement in the targeted subindex, change the lever. Do not wait for the overall score to move.

• Collapsing the four components into one engagement score. The tell: leaders say 'we scored high' but cannot name which of capable, aligned, motivated, or supported is weakest.
• Measuring attitudes instead of the state. The tell: the survey is mostly satisfaction, pay, and benefits items, with few about skills, goal clarity, effort, or resources.
• Dismissing a small gap because everything else is strong. The tell: the minutes record 'no substantive new actions' after a below-benchmark category, as in the Speaking Up case.
• Reading only company-wide numbers. The tell: no segment cut exists, so action plans are generic.
• Treating the state as the lever. The tell: the plan says 'raise motivation' with no named antecedent or consequence to change.

• ▸Segment: name the group scored (department, tenure band, location, or manager).
• ▸Capable score and benchmark: record the subindex result and the comparison figure.
• ▸Aligned score and benchmark: record the subindex result and the comparison figure.
• ▸Motivated score and benchmark: record the subindex result and the comparison figure.
• ▸Supported score and benchmark: record the subindex result and the comparison figure.
• ▸Weakest component and gap: name the component furthest below benchmark, even if the overall score is fine.
• ▸Antecedents and consequences (ABC trace): list what precedes and follows the target behavior that could explain the gap.
• ▸Lever chosen and owner: one change, one accountable person.
• ▸Employee Lifetime Value of segment and NAV priority: note the value and rank this segment against others.
• ▸Re-measure date and result: record when the same items re-run and whether the targeted subindex moved.