Fundamentals Hrm Bauer

1. 1Start with job analysis to map the KSAOs each role requires, then audit whether the workplace supplies the conditions (tools, information, authority) needed to apply those KSAOs — opportunity fails when ability and motivation exist but the 'chance to do' is missing.
2. 2Use workflow analysis to trace how work moves through the unit; identify handoff points, approval bottlenecks, and missing inputs that block an employee from executing what they were hired to do.
3. 3Redesign jobs deliberately using job design considerations to raise autonomy — expand decision authority, add flexible work arrangements where the task allows, and remove unnecessary sign-offs.
4. 4Verify that the information systems function is putting the right information in front of the right people; a global or local HRIS supports scheduling and training so employees and managers both have what they need to perform.
5. 5Confirm resource support from adjacent functions: accounting/finance for compensation and human-capital budgets, marketing for applicant awareness, IT for data access — opportunity is cross-functional, not owned solely by HR.
6. 6Set the tone from the top: the CEO and top management team signal how much human capital is valued, which determines whether managers actually grant the autonomy and resources on paper.
7. 7Measure the gap with benchmarking — compare your unit's practices against a peer organization to expose where your conditions lag and where performance is being suppressed by opportunity, not talent.
8. 8Close the loop through performance management: when appraisals show underperformance, separate ability/motivation deficits from opportunity deficits before assigning cause.

A global IT service provider studied across Argentina, Brazil, China, India, Latvia, and Slovakia illustrates opportunity as a workplace condition rather than an individual trait. Employees assigned to other countries had the ability and motivation to perform, but performance and retention depended on whether the environment supported them. The presence of a global HRIS gave new employees and their managers the resources — scheduling and training support — needed to actually do the job in an unfamiliar setting. Where that condition was present, staff retention rose and turnover fell, especially for cross-border assignees. The 'chance to do' here was a system that delivered timely, accurate information to the people who needed it. Absent that HRIS, the same capable employees would have faced conditions that blocked effective performance.

• If an employee has the KSAOs and is motivated but still underperforms, then investigate opportunity (resources, information, authority) before questioning ability.
• If approval or handoff steps in the workflow add no value, then remove them to widen autonomy — the chance to act is being constrained.
• If the top management team does not visibly value human capital, then documented autonomy will not translate into real decision authority; address tone at the top first.
• If turnover concentrates among employees in demanding or remote assignments, then check whether supporting systems (HRIS, scheduling, training) are supplying the conditions to perform.
• If your unit's practices trail a benchmarked peer, then treat the difference as an opportunity deficit to be engineered, not a talent shortfall.

• Attributing every performance gap to ability or effort. Tell: coaching and incentives are applied repeatedly with no improvement because the real block is missing tools or authority.
• Granting autonomy on paper while retaining approval gates. Tell: employees say they're 'empowered' but every decision still routes upward.
• Treating opportunity as HR-only. Tell: IT can't deliver needed data, finance won't fund the resource, yet HR is blamed for low performance.
• Deploying systems without the environment to use them. Tell: an HRIS or new tool exists but managers and new employees still lack scheduling and training support, so performance and retention don't move.
• Copying headquarters 'best practices' into other locations without adapting conditions. Tell: transported practices ignore local laws and norms and are 'doomed to fail' despite capable staff.

• ▸Role & required KSAOs: list from job analysis what the person must be able to do.
• ▸Autonomy level: note current decision authority vs. approval gates that constrain it.
• ▸Resource inventory: tools, budget, and support this role needs to perform (one line).
• ▸Information access: does the HRIS/IT function put the right data in front of this person? Y/N + gap.
• ▸Cross-function support: which of finance, IT, marketing must supply an input, and is it flowing?
• ▸Workflow bottleneck: name the handoff or sign-off that currently blocks execution.
• ▸Top-management signal: does leadership visibly back the autonomy/resources on paper? Y/N.
• ▸Benchmark gap: how does this condition compare to a named peer organization?
• ▸Opportunity vs. ability verdict: state whether the performance block is 'chance to do' or capability.

1. 1Deploy engagement and attitude surveys on a recurring cadence to measure vigor, dedication, and absorption before turnover shows up in exit data — treat the survey as your leading indicator, not a satisfaction poll.
2. 2Apply sentiment analysis to open-text responses, internal communications, and survey comments to assess engagement at scale rather than relying only on Likert scores.
3. 3Segment engagement results by team, tenure, and role so you can locate where disengagement concentrates instead of averaging it away across the organization.
4. 4Cross-reference low-engagement segments against your turnover predictors — the passages tie retention management to both engagement surveys and focused analysis of turnover predictors.
5. 5Gain upper-management support before acting; the source lists this as the first retention lever, because engagement interventions without executive backing stall.
6. 6Feed engagement findings into high-commitment HR practices — structured onboarding, career development, coaching, and a feedback culture — rather than treating engagement as a standalone program.
7. 7Run exit interviews on leavers and compare their stated reasons to prior survey signals to validate whether your engagement measures actually predicted departures.
8. 8Re-measure after each intervention and track whether vigor/dedication/absorption scores and turnover move together, closing the loop as a descriptive-then-predictive analytics cycle.

Mars, Inc. is the retention case featured in Chapter 10, where engagement is positioned as a retention driver. Following the source's sequence, you would first secure upper-management support for a retention initiative, then field an engagement and attitude survey across teams. Sentiment analysis on the comments (the book's named technique for assessing engagement) flags a manufacturing unit whose absorption and dedication scores lag and whose free-text mentions signal disengagement. You cross that segment against turnover predictors and confirm elevated flight risk, then investigate with exit interviews from recent leavers in that unit. The data points to weak onboarding and thin career development, so you invest in high-commitment HR practices — structured onboarding experiences and a feedback culture with manager coaching. On the next survey cycle you re-measure engagement and monitor whether turnover in that unit declines, verifying the intervention worked.

• If engagement scores drop in a segment but turnover hasn't yet risen, then treat it as an early warning and intervene before separations begin — engagement is the leading indicator.
• If you lack upper-management support, then delay the intervention and secure it first, since the source lists it as the prerequisite retention lever.
• If survey scores look flat but sentiment analysis of comments is negative, then trust the text signal and probe further rather than declaring engagement healthy.
• If a low-engagement segment also scores high on turnover predictors, then prioritize it for high-commitment HR practices over segments with only one warning sign.
• If exit interviews contradict what your engagement survey predicted, then revisit your survey items and measurement approach, not just the intervention.

• Measuring satisfaction instead of engagement — the tell is a survey that asks only 'are you happy?' and never touches vigor, dedication, or absorption.
• Reporting a single company-wide engagement average — the tell is that no team-level or tenure-level segmentation exists, so hotspots stay hidden.
• Surveying without acting — the tell is repeated survey cycles with no linked onboarding, career, coaching, or feedback-culture changes; engagement scores stagnate and cynicism rises.
• Ignoring open-text comments — the tell is dashboards full of Likert averages and zero sentiment analysis, missing qualitative signals of disengagement.
• Launching engagement work without executive backing — the tell is stalled follow-through and interventions that die between survey cycles.

• ▸Segment (team/role/tenure): name the population you are measuring
• ▸Vigor / Dedication / Absorption scores: record each dimension separately, not one blended number
• ▸Sentiment analysis result: summarize the tone of open-text and comment data
• ▸Turnover predictors present: list which risk factors this segment triggers
• ▸Leading-indicator flag: mark whether engagement dropped before turnover rose
• ▸Upper-management sponsor: name the executive backing the intervention
• ▸High-commitment HR action: specify onboarding/career/coaching/feedback change to apply
• ▸Re-measurement date: set when you will resurvey to close the loop
• ▸Exit-interview cross-check: note whether leaver reasons matched survey signals

1. 1Gain upper-management support first: retention initiatives require budget for surveys, onboarding redesign, and high-commitment practices, so secure the executive sponsorship before building programs.
2. 2Deploy engagement and attitude surveys on a recurring cycle to capture how the organization is meeting employee stakeholder needs (e.g., learning and development), then treat low-scoring units as retention risk zones.
3. 3Run structured exit interviews with departing employees to identify the causes of voluntary turnover, and code responses so patterns (manager, pay, opportunity) become visible across cohorts.
4. 4Hire for fit at the front end so newcomers match the role and culture, reducing the early separations that drive the bulk of avoidable turnover.
5. 5Structure onboarding experiences deliberately rather than leaving them to chance, since newcomer onboarding shapes whether employees stay past the vulnerable early period.
6. 6Invest in high-commitment (high-performance) HR practices—enhance perceptions of job security, promote from within, tie financial incentives to performance, offer training, and provide flexible work arrangements.
7. 7Focus on turnover predictors using HR analytics: collect people-related data, build a model that flags who is likely to leave, and target retention resources at high-potential employees before they exit.
8. 8Apply the ability-motivation-opportunity lens to diagnose why people leave—confirm employees have the ability, the motivation, and the opportunity to perform, since a gap in any one erodes retention.

Mars, Inc. anchors this chapter's opening case on employee retention. Treat the process as it is laid out: management commits to retention as a strategic outcome, then engagement surveys reveal which teams score low on being met as employee stakeholders. Exit interviews with leavers are coded and show, for instance, that early departures cluster among newcomers who never received structured onboarding. HR responds by hiring for fit and rebuilding the onboarding experience, then layering in high-commitment practices—internal promotion and training—so employees see a path to stay. A predictive model built from people-related data flags at-risk high performers, and managers intervene before those employees exit. The result is voluntary turnover falling, which the balanced scorecard reads as a healthier organization meeting its employee stakeholders' needs.

• If exit interviews repeatedly name the same manager or unit, then treat it as a localized retention problem and intervene there rather than launching a company-wide fix.
• If an employee is a high performer flagged by turnover predictors, then prioritize retention resources on them, because higher performers also refer higher-potential candidates.
• If engagement survey scores drop in learning-and-development items, then invest in training and internal promotion, since those are evidence-based best practices that lift retention.
• If early-tenure separations dominate the data, then fix hiring-for-fit and onboarding structure before spending on later-stage perks.
• If you lack budget or executive backing, then secure upper-management support first, because retention programs fail without it.

• Relying on gut instinct instead of data-driven decisions—the tell is retention 'solutions' that no survey or exit-interview evidence supports.
• Skipping exit interviews or not coding them, so causes of voluntary turnover stay invisible and the same losses repeat.
• Leaving onboarding unstructured and assuming culture 'takes care of itself'—the tell is a spike in first-year departures.
• Treating all leavers as equal and spreading retention effort thin, instead of focusing on high-performer and high-potential predictors.
• Adopting isolated perks rather than a coherent system of high-commitment practices—ability, motivation, and opportunity must all be addressed, so fixing one while ignoring the others leaves the gap open.

• ▸Unit/team: name the group and its current voluntary turnover rate
• ▸Executive sponsor: who owns and funds the retention effort
• ▸Engagement survey signal: lowest-scoring stakeholder-need item this cycle
• ▸Exit-interview themes: top coded causes of departures
• ▸Fit gap: where new hires mismatch role or culture
• ▸Onboarding status: structured / ad hoc / none
• ▸High-commitment practices in place: job security, internal promotion, incentives, training, flexible work (check present)
• ▸Turnover predictors flagged: at-risk high performers to target
• ▸Action + owner + date: intervention, responsible manager, deadline

1. 1Anchor the balanced scorecard to strategy first: state the organization's strategic objectives (short- and long-term), then derive which financial, operational, customer, and employee measures actually signal progress toward those objectives — not generic metrics.
2. 2Populate all four scorecard dimensions with specific measures: financial results (e.g., profitability), operational efficiency (e.g., productivity), customer satisfaction, and employee outcomes. Do not let any dimension go unmeasured.
3. 3Trace the causal chain from HR practices to outcomes: specify how a system of HR practices (selection, training, performance management, rewards) is expected to influence the employee-outcome measures that in turn move operational and financial results.
4. 4Set targets and baselines for each measure using existing data from your HRIS so metrics are trackable over time rather than one-off snapshots.
5. 5Apply the HR analytics scientific process to any performance question: identify the problem, do background research, form a hypothesis, test it via experimentation, analyze the data, and communicate the results.
6. 6Review the scorecard on a fixed cadence, checking whether gains in one dimension (e.g., productivity) are being purchased at the cost of another (e.g., employee well-being or turnover), and rebalance HR practices accordingly.
7. 7Communicate findings back to management in meaningful terms so HR functions as a business partner informing strategy, not just a reporting function.

Costco's approach illustrates a balanced-scorecard logic in practice: it invests in employee outcomes — higher wages and better treatment than many competitors — as a deliberate HR strategy. The hypothesis is that stronger employee outcomes reduce turnover and raise productivity (operational efficiency), which supports customer satisfaction and ultimately profitability (financial results). To evaluate this, you would measure each dimension: pay-driven retention and engagement (employee), sales-per-employee and shrink (operational), customer loyalty (customer), and margins (financial). If the employee investment coincides with lower turnover costs and stable margins, the scorecard confirms the HR practices are moving organizational performance across dimensions rather than trading one off for another. This mirrors the book's argument that organizations managing people, data, and analytics effectively can use HRM to inform and support strategy.

• If a proposed metric does not map to a stated strategic objective, then drop it — measurement without strategic linkage adds noise.
• If any one of the four scorecard dimensions is empty, then the scorecard is not balanced; fill it before reporting performance.
• If financial or operational gains appear alongside worsening employee outcomes (rising turnover, falling satisfaction), then flag an unsustainable trade-off and revisit the HR practice driving it.
• If you cannot articulate a hypothesis for how an HR practice influences an outcome, then treat the effect as unproven and test it via the scientific process before scaling.
• If data for a measure is not captured in the HRIS, then instrument it first — you cannot manage performance you cannot track.

• Measuring only financial results and calling it performance — the tell is a dashboard with profitability but no customer or employee measures.
• Copying generic 'best practice' metrics without linking them to your own strategy — the tell is metrics that no one can connect to a strategic objective.
• Optimizing one dimension in isolation (e.g., cutting cost to boost short-term productivity) while employee and customer measures quietly erode — the tell is improving numbers in one box and rising turnover or complaints elsewhere.
• Reporting correlations as proof without hypothesis or testing — the tell is claims that an HR practice 'caused' results with no experiment or background research behind them.
• Building the scorecard once and never rebalancing — the tell is static targets that no longer reflect current strategy or labor conditions.

• ▸Strategic objective: state the specific short- or long-term goal this scorecard serves
• ▸Financial measure + target: e.g., profitability metric with baseline and goal
• ▸Operational measure + target: e.g., productivity metric with baseline and goal
• ▸Customer measure + target: e.g., satisfaction/loyalty metric with baseline
• ▸Employee outcome measure + target: e.g., turnover, engagement with baseline
• ▸Linking HR practice: which selection/training/reward/PM practice is expected to move the employee measure
• ▸Hypothesis: one sentence on how the HR practice influences the outcome chain
• ▸Data source: where in the HRIS this measure is captured and how often
• ▸Trade-off check: which other dimension could be harmed and how you will monitor it

1. 1Diagnose the current culture before launching any HR initiative: determine whether decisions are made on gut/intuition or on data, because a culture that does not value data will resist an HR analytics function regardless of the tool's quality.
2. 2Secure manager and upper-management support first — enlist leaders to publicly value evidence-based practices, since manager support is the prerequisite that gives the initiative a chance to implement changes.
3. 3Pair every initiative with structured change management: apply the 'systematic process of applying knowledge, tools, and resources to transform organization from one state of affairs to another,' anticipating that people naturally resist change.
4. 4Cultivate two cultures in parallel — one supportive of data-driven decision making and one of continuous change — so employees expect and accept ongoing adjustment rather than treating each initiative as a one-off disruption.
5. 5Build the training/work environment to match reality so support translates into behavior: when you train employees on a new software system, use the same equipment they will use on the job, and teach the underlying principles (e.g., balancing fairness and customer satisfaction) rather than rote scripts.
6. 6Verify supervisor support at the point of transfer: after training, confirm managers reinforce (not dismiss) the new skills, because an unsupportive climate blocks transfer even when the training itself is strong.
7. 7Embed ethics into the culture as an explicit norm: before collecting sensitive people data (e.g., scraping social media, wearable-tracker data), require the team to ask 'Just because we can, should we?' and apply scientific rigor to that decision.
8. 8Measure whether the culture is receiving the initiative: track alignment signals like the training function's net promoter scores within the organization (as Xerox does) to see how the initiative is actually perceived.

A bank implements a training program to improve employees' interactions with customers, and trainees show strong improvement in interpersonal skills inside the training environment. But when they return to work, bank managers tell them the training is nonsense and there is no time to interact with customers that way. Despite the strength of the training, the knowledge and skills fail to transfer because of the unsupportive climate. Contrast this with Company A, which trains customer-service workers on the principles behind handling complaints — balancing fairness and customer satisfaction — while Company B only tells trainees to apologize; Company A's employees handle a wider range of complaints and produce better customer satisfaction. The lesson: culture and supervisor support, not just program quality, determine whether an HR initiative changes on-the-job behavior. Support has to exist in the environment employees return to, or the investment produces knowledge that never becomes performance.

• If executives make major decisions on gut instinct and the culture does not value data, then build manager support and an evidence-based culture before standing up an analytics function.
• If you are rolling out change, then pair it with formal change management and expect resistance — assume people will naturally resist unless a culture of continuous change is already cultivated.
• If supervisors are not supportive of a trained behavior, then predict non-transfer and fix the climate (get manager buy-in) rather than blaming the training design.
• If the training environment does not resemble the work environment, then redesign it to match (same systems, real principles) before expecting results.
• If a data practice is technically possible but ethically questionable, then stop and ask 'should we?' — apply the same rigor as the scientific process to what data to use and whether to run the analysis.

• Treating a strong program as sufficient on its own — tell: trainees improve in the classroom but performance on the job never changes because managers dismiss it.
• Launching analytics into a gut-driven culture without manager support — tell: recommendations get ignored and decisions still default to intuition.
• Skipping change management — tell: the initiative stalls amid visible resistance and people revert to old behaviors.
• Training on scripts instead of principles or in an artificial setting — tell: employees handle only the exact scenario drilled and fail on any variation (Company B's 'just apologize' approach).
• Collecting sensitive data because it is possible and predictive without asking whether it should be used — tell: privacy backlash and ethical exposure from practices like scraping social media or misusing wearable data.

• ▸Initiative name: what HR practice or analytics function you are introducing.
• ▸Current decision norm: is this area run on gut/intuition or on data today?
• ▸Manager support secured: which leaders publicly back evidence-based practice, and what will they say/do?
• ▸Change-management plan: the specific knowledge, tools, and resources moving the org from current to target state.
• ▸Resistance points: where do you expect people to resist, and how does a continuous-change culture address it?
• ▸Environment match: does the training/rollout setting mirror the real work environment and teach underlying principles?
• ▸Supervisor reinforcement: how will managers reinforce the new behavior after rollout so it transfers?
• ▸Ethics screen: for any sensitive data used, the answer to 'Just because we can, should we?'
• ▸Perception metric: the alignment/reception measure you will track (e.g., net promoter score of the function).

1. 1State the business strategy in operational terms first: is it cost leadership or differentiation, and what employee behaviors does it require? You cannot align HR to a strategy you have not made explicit.
2. 2Audit each HR practice — recruitment, selection, training, performance appraisal, rewards — and ask whether it signals and rewards the behaviors the strategy needs. Treat the practices as a system, not isolated tools, because systems thinking means the practices must reinforce each other and the context.
3. 3Translate strategy into performance appraisal criteria that motivate strategy-consistent behaviors. If the strategy is differentiation through service, the appraisal must measure service behaviors, not just punctuality.
4. 4Cascade the top management team's valuation of human capital downward: get the CEO/CHRO to set the tone that HRM is a strategic function, then have HR managers partner with line managers so the practices are applied consistently.
5. 5Instrument the alignment with HR analytics — link HR systems, policies, and practices to employee, operational, stakeholder, and financial outcomes so you can show whether the practices actually move the strategic needle.
6. 6Align your analytics strategy with organizational strategy too; build a clear plan for integrating analytics into decision making rather than reporting descriptive metrics that answer no strategic question.
7. 7Re-audit on a cycle: when the strategy shifts, revisit each practice and retire the misaligned metrics deliberately, as the appraisal system must keep tracking what the strategy currently requires.

Zappos ran a performance appraisal system built around metrics like meeting deadlines and being punctual. On review, they found the system lacked strategic alignment — it measured administrative compliance, not the differentiated customer experience their strategy depended on. They replaced it with a system that measures how well employees demonstrate Zappos's 10 core values, such as showing humility and delivering 'wow' levels of customer service. This is HR-strategy alignment in one practice: the appraisal now motivates behaviors consistent with the company's strategic direction. Contrast Costco, referenced as an opening case, where valuing human capital is set from the top — the top management team sets the tone for how much HRM is valued as a strategic function. The lesson: alignment is not achieved once; Zappos only got there by auditing an existing system and rebuilding it around strategic behaviors.

• If the strategy is differentiation, then design appraisal and reward practices around the distinctive behaviors (service, values, quality); if it is cost leadership, then align practices around efficiency and consistency.
• If an HR practice rewards behavior the strategy does not need, then it is misaligned — retire or redesign it, as Zappos did with punctuality metrics.
• If HR analytics cannot link a practice to an employee, operational, stakeholder, or financial outcome, then you cannot prove alignment — build that measurement before defending the practice.
• If the top management team does not value HRM as a strategic function, then alignment stalls regardless of HR design — secure CEO/CHRO tone-setting first.
• If analytics strategy is not aligned with organizational strategy, then treat the gap as a risk — a lack of alignment between HR analytics and strategy can have damaging effects on the organization and its employees.

• Measuring what is easy instead of what is strategic. Tell: the appraisal tracks punctuality and deadlines while the strategy is about differentiated service — Zappos's original system.
• Treating HR practices as isolated tools rather than a reinforcing system. Tell: recruitment selects for one profile while rewards incentivize the opposite behavior.
• Stopping at descriptive analytics. Tell: HR can report what happened last quarter but cannot connect any practice to a strategic outcome or predict future impact.
• Leaving alignment to HR alone. Tell: line managers apply practices inconsistently because the top management team never signaled that HRM is a strategic function.
• Never re-auditing after strategy shifts. Tell: the appraisal still rewards behaviors the previous strategy needed, and no one has retired the stale metrics.

• ▸Business strategy (state as cost leadership or differentiation): one line naming the strategy.
• ▸Required behaviors: list the specific employee behaviors this strategy needs.
• ▸HR practice under review: name one practice (recruitment, selection, training, appraisal, rewards).
• ▸What this practice currently signals/rewards: describe the behavior it actually incentivizes.
• ▸Alignment verdict: aligned / partially / misaligned — one word plus reason.
• ▸Outcome link (analytics): the employee, operational, stakeholder, or financial outcome this practice should move.
• ▸Redesign action: the specific change needed to align it (e.g., swap punctuality metric for core-values metric).
• ▸Owner and tone-setter: which HR manager owns it and which top-management sponsor backs it.
• ▸Re-audit trigger: the strategy-change event that forces a re-review.

1. 1Frame the decision as a question before touching data. Follow the six-step scientific process the text lays out: (1) identify the problem, (2) do background research, (3) form a hypothesis, (4) test it via experimentation, (5) analyze the data, (6) communicate the results. Do not skip to analysis before the problem is stated in decision terms.
2. 2Set the analytics level you actually need. Descriptive analytics answers 'what happened' (e.g., percentage of the sample with a college vs. high school education). Predictive answers 'what is likely to happen given what is known' (e.g., how college vs. high school relates to job performance by probability). Prescriptive answers 'what should be done.' Pick the lowest level that resolves the decision.
3. 3Gather the right data through your HRIS. Use the system's ability to track the employee life cycle and produce metrics so your inputs are current and consistent rather than assembled ad hoc.
4. 4Choose an analysis that matches the question type, then test the hypothesis (ideally experimentally where the passages point to controlled testing) before drawing conclusions.
5. 5Interpret findings against the strategic objective and check them against legal/ethical constraints (privacy, security, EEO compliance) at Step 4 and Step 5, not after publication.
6. 6Communicate results to senior executives in a convincing, decision-ready form — the SHRM Foundation report names presentation-to-executives as a top missing skill, so treat the report-out as a deliverable equal to the analysis itself.
7. 7Tie the metric back to organizational performance. Use the balanced scorecard framing so people data connects to business outcomes rather than sitting as an isolated HR statistic.

Take the Deloitte finding cited in the text: 75% of surveyed companies believe HR analytics is important, but only 8% believe their own organization is strong at it. A data-driven HR leader treats that gap as Step 1, the problem: perceived importance far exceeds internal capability. Background research (Step 2) surfaces the SHRM Foundation report identifying two missing skills — analytics ability and the ability to present findings convincingly to senior executives. The hypothesis (Step 3): building both skills, not just tooling, closes the readiness gap. Rather than buying an analytics platform first, the leader tests targeted skill-building and measures whether HR recommendations start reaching executive decisions. Step 5 analyzes whether the two named skills move; Step 6 reports it to leadership in the same convincing format the gap called for. This mirrors how firms like Pfizer, AOL, and Facebook moved analytics from aspiration to practice.

• If the question is 'what happened,' use descriptive analytics; do not spend on predictive/prescriptive modeling the decision does not require.
• If the decision needs 'what is likely given what we know,' move to predictive; if it needs 'what should we do,' go prescriptive — and only then.
• If you cannot state the problem as a decision in one sentence (Step 1), stop — you are not ready to collect or analyze data.
• If a finding touches applicant/employee data, run it through privacy, security, and EEO compliance checks before it informs any policy.
• If the analysis is sound but cannot be presented convincingly to senior executives, treat it as unfinished — the SHRM report flags this as the skill that determines whether analytics gets used.

• Buying an HRIS or analytics tool before defining the problem — the tell is a platform in place but no stated decision it answers; the 8% strength figure is what this produces.
• Reaching for predictive or prescriptive models when a descriptive count would answer the question — the tell is elaborate modeling on a 'what happened' question.
• Skipping hypothesis and testing, going straight from data to conclusion — the tell is claims with no experiment or comparison behind them.
• Producing correct analysis nobody acts on because it is not communicated for executives — the tell is analytics reports that never reach a strategic decision.
• Ignoring privacy, security, and EEO checks until after publication — the tell is a finding retracted or challenged on legal/ethical grounds after it has already shaped a policy.

• ▸Problem statement — the decision, written as one question (Step 1)
• ▸Analytics level needed — descriptive, predictive, or prescriptive, with why
• ▸Background research — prior findings/benchmarks that inform the question (Step 2)
• ▸Hypothesis — what you expect and how you'll know if you're wrong (Step 3)
• ▸Data source & metric — which HRIS/life-cycle data and the specific metric
• ▸Test/analysis method — how the hypothesis is tested and analyzed (Steps 4–5)
• ▸Legal/ethical check — privacy, security, EEO issues cleared (yes/no + note)
• ▸Strategic link — which organizational objective / scorecard measure this serves
• ▸Executive communication plan — format and message for senior leaders (Step 6)

1. 1Start from strategy, not from HR practices. Formulate the organizational strategy first (strategy formulation), then map which employee behaviors that strategy requires, and design HR practices backward from those behaviors so the system supports strategy implementation.
2. 2Target the AMO levers explicitly. For each role, list the practices that build ability (selective hiring, extensive training), motivation (performance-based rewards, pay-for-performance), and opportunity (job design that grants autonomy, participation, information sharing), so no lever is left unaddressed.
3. 3Check internal alignment across practices. Verify that selection, training, performance management, and rewards send the same signal — e.g., if you hire selectively for collaboration, your reward system should not pay purely on individual output.
4. 4Check external alignment with the strategy and context. Apply systems thinking: confirm the practice set fits the labor market, legal environment, and organizational culture rather than importing 'best practices' wholesale.
5. 5Instrument the system for data-driven decisions. Attach measures to each practice and connect them to organizational outcomes using the balanced scorecard, so you can test whether the system moves the outcomes it was designed to move.
6. 6Test with the scientific process. Identify the problem, do background research, form a hypothesis about which practice drives which outcome, test via experimentation, analyze the data, and communicate results before scaling.
7. 7Feed retention and separation data back in. Use engagement surveys, exit interviews, and turnover predictors to detect where the system is failing to sustain ability, motivation, or opportunity, and revise the corresponding practice.

Costco, used as the opening HR-in-Action case, illustrates an aligned system rather than isolated tactics. Its strategy competes on efficient, high-volume retail delivered by a stable, capable workforce, so its HR practices are built to reduce turnover and raise employee capability together. Selective hiring and above-market, performance-linked pay raise motivation; investment in training raises ability; and the culture and job structure give employees opportunity to contribute. Because each practice reinforces the others, the system as a whole lowers turnover costs and supports the strategy — no single practice explains the result. A firm that copied only Costco's high pay while keeping thin training and rigid jobs would break the alignment and not reproduce the outcome. That is the point of systems thinking: the practices influence organizational outcomes collectively, through their fit with each other and with strategy.

• If a proposed HR practice does not trace back to a behavior the strategy requires, then do not adopt it — it adds cost without alignment.
• If two practices send conflicting signals (e.g., individual bonuses plus team-based work), then redesign one until they reinforce the same behavior.
• If you cannot state a measurable outcome and a hypothesis for a practice, then treat it as unvalidated and pilot it before rolling it out.
• If turnover, engagement, or exit-interview data show erosion, then diagnose which AMO lever (ability, motivation, or opportunity) is failing before changing the whole system.
• If a 'best practice' worked elsewhere but conflicts with your legal, cultural, or labor-market context, then adapt or reject it rather than transplanting it.

• Adopting high-performance practices as a checklist of isolated fads. The tell: each practice is owned by a different HR silo and none references the business strategy.
• Reward-motivation mismatch — paying for one behavior while asking for another. The tell: unintended behavioral consequences like the goal-setting incentives that drove the Wells Fargo scandal.
• Overweighting motivation and ignoring opportunity. The tell: employees are well-paid and well-trained but job design blocks autonomy and participation, so performance stalls.
• Copying benchmarks without context. The tell: 'we do it because Company X does' with no data linking the practice to your outcomes.
• Skipping measurement, so you cannot tell if the system works. The tell: no balanced-scorecard metrics or hypothesis test tied to the practices, only anecdote.

• ▸Strategic priority: state the business strategy this system must support.
• ▸Required employee behaviors: list the behaviors that priority demands.
• ▸Ability practices: name selection/training practices building capability for those behaviors.
• ▸Motivation practices: name rewards/pay-for-performance signals reinforcing those behaviors.
• ▸Opportunity practices: name job-design/participation/information practices enabling those behaviors.
• ▸Internal alignment check: note any conflicting signals across the practices above.
• ▸Context fit check: note legal, cultural, and labor-market constraints on each practice.
• ▸Outcome metric + hypothesis: state the scorecard measure and the expected practice-to-outcome link.
• ▸Feedback source: name the survey/exit/turnover data used to revise the system.

1. 1Start by analyzing how the job is currently experienced from the employee's perspective — is it stressful, boring, or meaningful? Job design is defined as identifying how a job's characteristics are experienced to enhance well-being and performance, so gather that experiential data before redesigning anything.
2. 2Diagnose which lever the job lacks. If the job is monotonous, target enlargement (more responsibilities) or rotation (moving across jobs). If workers lack control, target enrichment (greater decision-making power).
3. 3Apply job enlargement by adding responsibilities that make the work less boring and more motivating — for example, assigning a worker a new project different from those she has handled before, adding challenge and building new skills.
4. 4Apply job enrichment by pushing decision-making power downward — for example, let a team of workers in a high-tech manufacturing firm manage themselves rather than being directed solely by a supervisor or team leader.
5. 5Apply job rotation by moving employees from one job to another, which reduces boredom and lets them learn new skills across positions.
6. 6Screen for individual fit before rolling out enriched or enlarged jobs: some employees prefer not to take on additional responsibilities, and others may not perform well with them. Design in an opt-in or match employees to the level of responsibility they can handle.
7. 7Later, address the physical/ergonomic dimension of the job separately to improve worker safety and health — treat that as a distinct redesign track from the motivational one.

Take a worker on a repetitive high-tech manufacturing line who reports the job as boring. First you confirm the experience: the work is monotonous and offers little control. You apply enlargement by assigning her a new project unlike prior ones, adding challenge and letting her build skills. You then apply enrichment by moving her onto a self-managing team that runs its own decisions rather than waiting on the team leader. To keep the work fresh and broaden skills further, you rotate her periodically across adjacent jobs. Before committing, you check fit — she is willing to take on the added responsibility, so the redesign proceeds; a coworker who prefers a narrower role is kept in place. The result targets improved motivation, better attitudes, well-being, and performance.

• If the complaint is boredom, then use job enlargement or job rotation to add variety and skill-building rather than more autonomy.
• If workers feel controlled or micromanaged, then use job enrichment to grant greater decision-making power.
• If an employee prefers not to take on more responsibility or performs poorly with it, then do not enrich or enlarge that person's job — match the design to the individual.
• If the problem is physical strain or safety, then treat it as an ergonomic redesign, separate from motivational job design.
• If you cannot describe how the job is currently experienced by the worker, then do not redesign yet — collect that perspective first.

• Assuming every employee wants more responsibility — the tell is falling performance or resistance after an 'improvement,' because not all employees do well with enriched or enlarged jobs.
• Redesigning from the manager's view of the job rather than how workers actually experience it (stressful, boring, meaningful) — the tell is that stated pain points never change.
• Confusing enlargement (more responsibilities) with enrichment (more decision-making power) and applying the wrong one — the tell is added tasks that increase load without addressing a control problem.
• Adding volume of tasks without added challenge or skill-building, so enlargement just means more of the same boring work — the tell is no change in engagement.
• Ignoring the physical/ergonomic dimension while chasing motivation — the tell is safety and health problems persisting despite a 'motivating' redesign.

• ▸Job title: the role being (re)designed
• ▸Current experience: how the worker describes it (stressful/boring/meaningful) and evidence
• ▸Primary problem: boredom vs. lack of control vs. physical strain
• ▸Enlargement action: specific new responsibility or challenging project to add
• ▸Enrichment action: specific decision-making power to hand to the worker/team
• ▸Rotation plan: which adjacent jobs the worker will move through and how often
• ▸Fit check: does this employee want and perform well with added responsibility? (yes/no)
• ▸Ergonomic/safety note: physical redesign needed, handled separately
• ▸Target outcomes: motivation, attitudes, well-being, performance measures to watch

1. 1Run a job analysis first to define the KSAOs the role actually demands — use Task–KSAO Analysis to link each task to the knowledge, skills, abilities, and other characteristics required to perform it.
2. 2Choose the analysis method that fits your need: Critical Incidents Technique to surface behaviors distinguishing high from low performers, the Position Analysis Questionnaire for standardized structured data, or O*NET to import validated occupational KSAO profiles.
3. 3Translate the required KSAOs into selection procedures with proven reliability and validity — cognitive ability tests, work samples, SJTs, structured interviews, integrity or personality tests — and estimate utility before adopting.
4. 4Assess the current workforce against required KSAOs through a training needs assessment that runs organizational analysis, job analysis, and person analysis to locate the specific gaps.
5. 5Close ability gaps with fit-for-purpose training methods: on-the-job training, simulators, behavioral modeling, eLearning, or programmed instruction, chosen against the KSAO type being built.
6. 6Design conditions that enhance learning and transfer — account for trainee characteristics and shape the organizational context so learned skills carry back to the job.
7. 7Measure whether ability actually improved using defined measures of training effectiveness, and tie training data back to performance outcomes.
8. 8Reassess periodically as work changes, re-running job analysis when tasks shift so the KSAO baseline stays current.

In the Chapter 8 case 'Tying Training Data to Performance,' the sequence starts with a training needs assessment: organizational analysis confirms strategic support, job analysis identifies the tasks and required KSAOs, and person analysis pinpoints which employees lack them. Suppose the person analysis reveals a group cannot perform a technical task the job analysis flagged as essential. You develop specific training goals for that gap, then select a method matched to the skill — a simulator or behavioral modeling training rather than a lecture, since the deficit is a hands-on skill. You attend to trainee characteristics and build the organizational context so the skill transfers back to the job. Finally, you apply measures of training effectiveness and connect that training data to performance, demonstrating whether the 'can do' component actually rose.

• If tasks or the nature of work have changed, then re-run job analysis before assessing ability — an outdated KSAO baseline measures the wrong thing.
• If a performance problem is a 'can do' (ability) gap rather than a 'will do' (motivation) gap, then route it to selection or training; if person analysis shows the skill is absent, train, not incentivize.
• If you need to measure ability at hiring, then pick procedures with established reliability and validity and positive utility — cognitive ability tests and work samples over unstructured judgment.
• If the KSAO is a concrete, observable skill, then use on-the-job training, simulators, or behavioral modeling; if it is procedural knowledge, programmed instruction or eLearning suffices.
• If you cannot connect training data back to a performance measure, then treat the effectiveness claim as unproven and audit the evaluation design.

• Skipping job analysis and defining KSAOs from intuition — the tell is selection criteria and training content that no one can trace to an actual task.
• Confusing a motivation problem with an ability problem, so you train employees who already 'can do' the work — the tell is training that produces no performance change.
• Choosing a training method by convenience (a lecture) rather than by KSAO type — the tell is high satisfaction scores but no on-the-job skill transfer.
• Ignoring transfer conditions and trainee characteristics — the tell is skill demonstrated in training but absent back on the job.
• Never measuring effectiveness or linking it to performance — the tell is repeated training spend with no evidence ability improved.

• ▸Role / task analyzed: name the position and the specific task from job analysis
• ▸Required KSAOs: list knowledge, skills, abilities, other characteristics tied to the task
• ▸Analysis method used: Task–KSAO, Critical Incidents, PAQ, or O*NET
• ▸Current workforce level: result of person analysis for this KSAO
• ▸Gap identified: the specific difference between required and current
• ▸Intervention type: select (hire/test) or train — and why
• ▸Method/procedure chosen: the specific selection tool or training method matched to the KSAO
• ▸Transfer conditions: trainee and organizational context factors to address
• ▸Effectiveness measure: how you will measure ability change and link it to performance

1. 1Locate motivation in the performance equation before acting: Performance = Ability × Motivation × Opportunity. Confirm the gap is the 'will do' component, not the 'can do' (ability) or 'chance to do' (opportunity) component, because a fix aimed at the wrong element returns nothing.
2. 2Diagnose whether motivation is near zero. The model is multiplicative, so if motivation falls to zero, performance is zero regardless of high ability or opportunity. Rank motivation against ability and opportunity to find the binding constraint before spending on any intervention.
3. 3Apply expectancy theory to the effort question. Break motivation into whether the employee believes effort leads to performance, performance leads to a reward, and the reward is valued. Test each link separately so you fix the broken one rather than the whole chain.
4. 4Design the job to raise motivation using the Job Characteristics Model. Increase skill variety, task identity, and task significance to build experienced meaningfulness; increase autonomy to build experienced responsibility; increase feedback to build knowledge of results. These three psychological states drive motivation and performance.
5. 5Deploy pay-for-performance deliberately as a motivator: connect valued rewards to measured performance through individual or group programs so the effort-performance-reward links stay intact.
6. 6Segment for who values enriched work. Not every employee responds equally to enrichment; some value enriched jobs more than others, and age may determine which characteristics matter, so match the design to the person.
7. 7Measure motivation-driven outcomes after the change, not just satisfaction. Track job performance, burnout, and intention to quit, since the meta-analytic evidence links autonomy, task variety, and task significance to these specifically.
8. 8Watch for unintended behavioral consequences of reward systems. Verify the incentive actually raised effort toward the intended goal rather than gaming, pay compression pressure, or side effects.

Tesla's HR analysts mined data from the company's employee referral program and found a motivation-relevant pattern in effort directed at referrals: higher-performing employees referred higher-potential candidates, midrange employees referred lower-performing candidates, and lower-performing employees referred candidates at all levels. Rather than assuming everyone was equally motivated to refer well, the team read the differing referral quality as differing effort and judgment channeled toward a company goal. They then devised ways to improve recruitment and selection practices to attract and attain high-potential people—redirecting the referral behavior toward the strategic objective of acquiring talented people. This shows the 'will do' component in action: employees had the opportunity to refer, but the effort and quality they exerted varied, and HR data made that variation visible. The fix targeted the process so that motivated referral behavior produced the outcomes the company wanted. The lesson is that motivation is observable through the effort patterns in behavioral data, not just self-report.

• If ability and opportunity are already high but performance is low, then treat the deficit as motivation and address the 'will do' component directly.
• If the employee doubts that more effort will actually produce higher performance, then fix the effort-performance link (clarity, tools, feedback) before touching rewards.
• If the employee performs but the reward is not valued or not clearly tied to performance, then redesign the reward, not the job.
• If the job scores low on autonomy, task significance, or feedback, then enrich those characteristics to raise experienced meaningfulness, responsibility, and knowledge of results.
• If two employees respond differently to the same enrichment, then segment by individual differences (including age) and match design to the person rather than standardizing.

• Treating a motivation problem as a training problem. Tell: you keep adding skills the person already has and performance stays flat because the constraint was 'will do,' not 'can do.'
• Assuming high ability guarantees effort. Tell: talented hires underperform, and the model reminds you that ability and motivation do not imply one another.
• Adding rewards without checking they are valued or believed. Tell: incentive spend rises but effort does not, because a broken expectancy link (effort→performance or reward→value) was never diagnosed.
• Enriching every job the same way. Tell: some employees engage and others disengage, because you ignored that some value enriched jobs more than others.
• Measuring only satisfaction after a job redesign. Tell: you declare success on satisfaction while burnout and intention-to-quit—the outcomes tied to autonomy and task significance—go untracked and quietly worsen.

• ▸Performance gap: describe the specific goal or output falling short (one line)
• ▸Constraint check: rate Ability / Motivation / Opportunity high-med-low; circle the binding one
• ▸Expectancy link 1: does the employee believe effort leads to performance? (yes/no + why)
• ▸Expectancy link 2: does performance lead to a reward, and is it valued? (yes/no + why)
• ▸JCM scan: rate skill variety, task identity, task significance, autonomy, feedback (low/high each)
• ▸Target state: which psychological state to raise—meaningfulness, responsibility, or knowledge of results
• ▸Individual fit: does this employee value enriched work? note age/preference factors
• ▸Intervention: the single change to make and the effort behavior it should increase
• ▸Outcome metric + review date: performance, burnout, or intention-to-quit measure to track