Managing Human Resources

1. 1Define QWL as a measurable construct before improving it: treat it as employees' collective perceptions of physical and mental well-being at work, spanning work-life fit, participation in decision-making, and the social-psychological environment. Name the dimensions you will track so later interventions map to specific perceptions.
2. 2Adopt the book's tri-part evaluation frame: assess every HR intervention against Productivity, Quality of Work Life, AND the Bottom Line simultaneously — because each chapter (pay, benefits, staffing, D&I, technology, safety) carries an explicit 'Impact on QWL' section. Do not optimize productivity or profit while treating QWL as residual.
3. 3Use people analytics to connect QWL perceptions to outcomes rather than asserting them. Apply the LAMP model — Logic (the story linking investment to outcome), Analytics (drawing correct conclusions), Measures (getting numbers right), Process (creating actionable insights) — to demonstrate that employee attitudes move customer behavior and profits.
4. 4Build the measurement engine around employee attitude data collected through surveys, then run the survey-to-financial-outcome linkage as the Sysco example does: employee attitudes → customer behavior → profits. Treat survey feedback as necessary, not merely 'nice,' per the Chapter 3 ethical dilemma.
5. 5Improve work-life fit dimensions through concrete levers the book names: flexibility and nonstandard/gig arrangements (Chapter 1), family-friendly policies (IBM), cafeteria/flexible benefits matched to diverse preferences (Chapter 12), and safety/health plus employee assistance programs (Chapter 15).
6. 6Strengthen the participation and decision-making dimension through structural mechanisms: union-management collaboration and restructuring (Chapter 13), gain-sharing and employee stock-ownership plans (Chapter 11), and procedural justice in employee relations (Chapter 14) so employees perceive fair voice.
7. 7Close the loop: re-survey after each intervention, re-run the LAMP logic to confirm attitude shifts translated to productivity and profit, and feed transparent results back to employees — treating survey feedback as an obligation to act on, not just collect.

Sysco Corporation is the book's grounding case for the QWL-to-profit linkage. Start with Logic: the story that favorable employee attitudes at each operating unit will produce better customer service behavior, which retains customers and lifts profit. Apply Analytics to draw the connection between attitudes, customer behavior, and financial outcomes rather than assuming it. Get Measures right by using consistent employee-attitude survey instruments across units so the numbers are comparable. Then use Process to convert findings into action — targeting units with weak attitude scores. The result demonstrated financial effects of employee attitudes, validating that investing in QWL (the well-being perceptions employees hold) is not soft spending but a driver of customer behavior and profits.

• If you cannot state the Logic connecting a QWL investment to a productivity or profit outcome, then do not fund it yet — build the LAMP story first.
• If workforce diversity in preferences is high, then use cafeteria/flexible benefits rather than a one-size package, because diversity in the workforce means diversity in benefits preferences.
• If employees lack perceived voice in decisions, then prioritize participation mechanisms (gain-sharing, ESOPs, union-management collaboration, procedural justice) over pay-only fixes.
• If a survey reveals negative findings, then treat feedback as necessary and act on it — withholding results damages the psychological environment you are trying to improve.
• If an HR intervention improves the bottom line but degrades QWL perceptions, then it fails the book's tri-part test and should be redesigned.

• Treating QWL as employee happiness rather than a measurable set of perceptions — tell: no defined dimensions and no attitude survey instrument in place.
• Measuring productivity and profit but leaving QWL unexamined — tell: reports omit the 'Impact on Quality of Work Life' dimension that the book pairs with every intervention.
• Asserting the attitude-to-profit link without analytics — tell: claims of 'engagement drives results' with no Logic, Measures, or Process behind them (LAMP skipped).
• Collecting survey data then not feeding it back — tell: employees stop responding and the 'Survey Feedback: Nice or Necessary?' dilemma resolves toward silence.
• Applying uniform benefits/flexibility to a diverse workforce — tell: low uptake and complaints that offerings do not fit individual work-life needs.

• ▸QWL dimension targeted: name it (work-life fit / participation / social-psychological environment).
• ▸Employee perception baseline: current attitude-survey score or measure.
• ▸Logic statement: one sentence connecting this investment to an outcome.
• ▸Analytics plan: how you will draw a valid conclusion from the data.
• ▸Measures: exact metric and instrument used, and its comparability.
• ▸Productivity impact: expected/observed effect.
• ▸Bottom-line impact: expected/observed financial effect.
• ▸Feedback action: what you will report back to employees and by when.
• ▸Re-measure date: when you re-survey to confirm perception shift.

1. 1Build the logic chain first: write the causal story linking a specific HR investment to profitability before touching data. Use the value-profit-chain form — management practices drive employee satisfaction/engagement, which drives innovation and execution, which drives customer satisfaction and purchasing behavior, which drives long-term profitability and growth.
2. 2Integrate data across silos: pull records from financial, operational, sales, and HR information systems. Talent analytics almost always fails at this step, so confirm you can join these sources before promising executives a profitability number.
3. 3Convert employee behaviors into dollars using cost-accounting procedures. Define the unit precisely (per marketing associate, per driver) and attach a replacement/training cost to each so improvements in retention translate to costs not incurred.
4. 4Test the link statistically before claiming causation. Compute the correlation between the employee-related indices (engagement/climate, productivity, retention) and later pretax earnings; report the R² and the time lag (e.g., 6 months later) rather than asserting cause–effect.
5. 5Scale the per-unit savings to the enterprise: multiply per-business-unit dollar effects by number of units and employees, and adjust to current-year dollars so the profitability figure is comparable and defensible.
6. 6Institutionalize the review: have top executives review the human-capital metrics on a fixed cadence (quarterly at Sysco) so the indices function as leading indicators of financial results in their own operating companies.
7. 7State the causal caveat explicitly. Even with a strong correlation, note that exact cause–effect has not been established, and present the profitability link as a modeled assumption, not a proven fact.

Sysco linked employee attitudes to profitability by tracking retention. In 2000, retention was 75 percent for marketing associates and 65 percent for drivers; by 2005 these rose to 88 percent and 87 percent. Replacement and training costs were estimated at $50,000 per marketing associate and $35,000 per driver. Assuming 100 employees per business unit, each unit saved $650,000 among associates and $770,000 among drivers — $1.42 million total ($1.92 million in 2020 dollars). Company-wide, over 10,000 employees, retention savings from 2000 to 2005 totaled $156.5 million ($212 million in 2020 dollars), contributing to long-term profitability and growth. HR researchers then found a multiple correlation of R² = 0.46 among engagement scores, productivity, retention, and pretax earnings six months later — meaning 46 percent of the variation in pretax earnings tracked with those three workforce variables, which is why executives began reviewing the human-capital indices quarterly.

• If you cannot integrate financial, operational, sales, and HR data, then stop and fix the data pipeline before quoting any profitability effect — the number will not hold.
• If a workforce index correlates with later pretax earnings (e.g., R² = 0.46 at a 6-month lag), then treat it as a leading indicator worth executive review, but label the causal link as assumed.
• If a program improves retention, then value it as costs not incurred using per-employee replacement/training cost times the retention gain times headcount.
• If you are comparing savings across years, then restate figures in current-year dollars before summing or presenting to decision makers.
• If technology or process is easy for competitors to copy, then locate the durable profitability advantage in the engaged, hard-to-imitate workforce, not the tool.

• Skipping the logic diagram and jumping to numbers — the tell is executives asking 'so what?' because investments and outcomes were never sewn together.
• Claiming causation from correlation — the tell is presenting R² = 0.46 as proof that engagement 'causes' earnings rather than as an association at a stated lag.
• Leaving data in silos — the tell is analysts calling the required integration 'too difficult and time consuming' and abandoning the profitability case.
• Ignoring inflation when aggregating multi-year savings — the tell is a $156.5 million figure presented without the 2020-dollar equivalent, making magnitude misleading.
• Overemphasizing large-organization examples with no per-unit costing — the tell is a headline savings number with no defined employee unit or per-employee cost behind it.

• ▸Investment/program: name the HR investment being evaluated
• ▸Logic chain: one line from practice through engagement to profitability
• ▸Data sources joined: list financial, operational, sales, HR systems used
• ▸Baseline vs. current metric: e.g., retention rate then and now
• ▸Per-employee cost: replacement/training cost per role
• ▸Affected headcount: employees per unit and total units
• ▸Dollar effect: costs not incurred = cost × retention gain × headcount
• ▸Statistical link: correlation/R² and time lag to pretax earnings
• ▸Inflation-adjusted total: restate savings in current-year dollars

1. 1Start from business strategy, not HR practices. The text places business strategy as the "foundation for all organizational decisions" (Ch. 6). Write down the competitive strategy first, then derive what the workforce must do to deliver it before touching any HR policy.
2. 2Ensure coherence in strategic direction, then map HR strategy to business strategy. Build an explicit link showing how each HR function (staffing, retention, development, adjustment, change) supports a specific strategic goal — a supply-chain view of talent, as the Recruiting chapter treats staffing.
3. 3Translate strategy into workforce requirements through job analysis and competency models. Identify the work to be done and the personal characteristics needed to do it (Ch. 6), then build competency models that define required behaviors per role.
4. 4Run strategic workforce planning: build a talent inventory, forecast internal and external supply, forecast demand, integrate the two, and decide make-or-buy (develop internally vs. recruit externally).
5. 5Align the reward system with the business plan. The Pay chapter names "Strategic Integration of Compensation Plans and Business Plans" — set pay structure and incentives (merit, gain-sharing, profit-sharing, ESOP) to reward the behaviors the strategy needs.
6. 6Integrate performance management as the connective tissue: define performance, facilitate it, encourage it (Ch. 10), and use the strategic dimension of ratings to reinforce the same behaviors pay rewards.
7. 7Build the adjustment and change functions in — procedural justice in employee relations (Ch. 14), discipline, and legal compliance (Ch. 4) — so the system holds up under scrutiny and litigation.
8. 8Control and evaluate the system. The SWP chapter includes "Control and Evaluation of SWP Systems"; measure financial impact via people analytics (LAMP model: Logic, Analytics, Measures, Process) and adjust.

Sysco Corporation (Ch. 3) shows the system working as an integrated whole rather than isolated practices. The logic starts by linking management practices to financial outcomes — connecting employee attitudes to customer behavior and profits. Analytics connect the model to specific management behaviors, and measures get the numbers right on attitudes and outcomes. Sysco then built a web portal (analytics combined with process) so managers could see and act on the value-profit chain. The result was monetary payoffs the firm could integrate into organizational systems. The lesson: each HR practice — from how supervisors manage attitudes to how the data is delivered — is chained to a financial result, which is exactly what "aligned with business strategy" means operationally.

• If HR strategy cannot be traced back to a specific business strategy goal, then stop and re-anchor — the passages make business strategy the foundation for all organizational decisions.
• If forecasted internal supply meets demand for a role, then develop/promote (job posting, internal recruitment); if it does not, then buy externally (university relations, executive search) — the explicit make-or-buy decision.
• If the strategy depends on teamwork, then use team incentives and evaluate the performance of teams, not just individuals — avoid the "me versus we" dilemma the Ch. 10 case names.
• If pay incentives reward behaviors that contradict the performance-management ratings, then realign one to the other — both must reinforce the same strategic behaviors.
• If a policy change (staffing, discipline, benefits) cannot survive legal and procedural-justice review (Ch. 4, Ch. 14), then redesign before deploying.

• Treating HR functions as disconnected silos rather than an integrated system. Tell: recruiting, pay, and performance chapters get run by separate owners with no shared strategic goal.
• Making the "business and ethical case" for an initiative (e.g., D&I) and assuming it drives change. The Ch. 5 feature explicitly warns these cases "Are Not Enough to Bring About Real Change." Tell: strong rationale documents but no structural or accountability change.
• Forecasting demand without integrating supply, or skipping the make-or-buy decision. Tell: recruiting scrambles reactively because no talent inventory or supply forecast exists.
• Compensation set without strategic integration — paying market rate or what the company can afford with no link to rewarded behaviors. Tell: incentives exist but reward the wrong outcomes; "the trust gap."
• Deploying the system without control and evaluation. Tell: no LAMP-style logic connecting HR investments to outcomes, so no one can show financial impact and the system drifts.

• ▸Business strategy goal: state the specific competitive objective this workforce must deliver.
• ▸Required workforce behaviors/competencies: list what people must do (from job analysis + competency model).
• ▸Staffing plan: internal vs. external source and the make-or-buy decision for each key role.
• ▸Supply/demand forecast: current talent inventory vs. forecasted demand, with the gap.
• ▸Retention & reward alignment: which incentive (merit, team, gain-share, profit-share, ESOP) reinforces each behavior.
• ▸Performance-management link: how ratings define, facilitate, and encourage the required behaviors.
• ▸Adjustment & compliance check: discipline, procedural-justice, and legal risks addressed (Ch. 4/14).
• ▸Change management: what shifts in structure/practice are needed and who owns them.
• ▸Evaluation metric: the LAMP logic/measure connecting this HR investment to a financial or strategic outcome.

1. 1Treat human capital as a stock you build through five manager activities named in the text: staffing, retention, development, adjustment, and managing change. Map each to who owns it and how you measure it.
2. 2Tie every human capital decision to the book's three outcome variables — productivity (output relative to labor, capital, equipment inputs), quality of work life (employees' perceptions of physical and mental well-being at work), and profit (revenue minus total costs). If a development spend can't be argued to move one of these, defer it.
3. 3Assign accountability to line managers, not just HR. The text's core assumption is that all managers add value by managing their people effectively; make competency-building part of each manager's job, not a specialist function.
4. 4Use staffing (Ch. 8) and training/on-boarding (Ch. 9) as your two levers for enhancing the stock: staffing selects the existing competencies you bring in; training and on-boarding raise the competencies of people already present.
5. 5Diagnose the skills gap in your workforce against demand. The passages flag that highly skilled workers gain rising opportunities while low-skill workers face joblessness and slow adjustment to shocks — so identify where your workforce sits and where automation or trade pressure erodes value.
6. 6Make the business case before investing (Ch. 2/3 logic): specify what you want the outcome to do, quantify it via people analytics — the financial impact of HRM activities — and don't overlook finance or IT sign-off.
7. 7Build for the small-business reality too: where capital is limited and one manager wears many hats, prioritize the development practices with the clearest line to productivity and retention rather than large-firm programs.
8. 8Re-evaluate continuously in the concept-to-evidence-to-practice loop: measure whether the competencies you added actually raised output or QWL, then adjust the staffing and development mix.

Consider the 'trade shock' case in the passages: economists Autor, Dorn, and Hanson found that after the rise of China as a manufacturer, U.S. workers' adjustment was 'stunningly slow,' with local unemployment elevated for a full decade after onset. About 6 million U.S. manufacturing jobs disappeared in a single decade. The human-capital lesson for a manager is that competencies are not automatically redeployable — the conventional assumption that displaced workers move into more enriching roles did not hold. A firm relocating capital and labor to 'the most economically advantageous places' captures profit gains, but the human capital of low-skill workers depreciates because their skills don't transfer. If you manage such a workforce, you treat development (retraining toward higher-skill work) as the mechanism that keeps their stock of value from collapsing. Doing nothing means watching that human capital become stranded, exactly as the trade-shock communities did.

• If a proposed development or staffing spend can't be linked to productivity, quality of work life, or profit, then defer it until you can articulate the connection.
• If a role's competencies are being automated or exposed to a trade shock, then invest in retraining toward higher-skill work rather than assuming workers will self-adjust — adjustment is slow and costly.
• If you are a line manager, then treat staffing, retention, development, adjustment, and change management as part of your own accountability, not something to hand off entirely to HR.
• If capital resources are limited (small business), then concentrate human-capital investment on the few practices with the clearest tie to productivity and retention.
• If you cannot make a defensible business case with people-analytics numbers, then do not present the initiative to finance or IT.

• Overemphasizing large-organization practices and copying programs a small business can't afford — the tell: your plan assumes staff and budget the 'many-hats' manager doesn't have.
• Assuming displaced or low-skill workers will naturally move into better roles — the tell: no retraining plan, and you're surprised when unemployment or disengagement lingers.
• Treating human capital as HR's problem alone — the tell: line managers disclaim responsibility for staffing, retention, and development of their own people.
• Investing in development without measuring impact on productivity, QWL, or profit — the tell: you can describe activity (courses run, hires made) but not outcomes.
• Confusing profit gains from relocating capital with genuine human-capital growth — the tell: margins rise while the workforce's actual competencies and well-being erode.

• ▸Competency targeted: name the specific knowledge/skill/ability you want to add or raise
• ▸Current source: staffing (bring in) or development/on-boarding (raise existing) — pick one
• ▸Owning manager: the line manager accountable for this competency, not HR generically
• ▸Productivity link: how this changes output relative to labor/capital/equipment input
• ▸Quality-of-work-life link: how this affects employees' perceived physical/mental well-being
• ▸Profit link: the cost-vs-revenue effect expected
• ▸Business case number: the people-analytics estimate justifying spend
• ▸Finance/IT check: sign-off status from those functions
• ▸Re-evaluation date: when you will measure actual impact and adjust the mix

1. 1Establish the logic first: write the explicit story that connects an employee-attitude investment to a financial outcome, using the LAMP model (Logic, Analytics, Measures, Process). Do not measure engagement until you can state how vigor, dedication, and commitment are supposed to move customer behavior and profit.
2. 2Choose measures that isolate the three attitude dimensions — engagement (vigor, dedication, absorption), job satisfaction, and organizational commitment — using established scales rather than a single ad hoc survey item. Add complementary measures like organizational citizenship behavior and perceived organizational support if you are testing motivation pathways.
3. 3Link attitudes to behavioral outcomes downstream: voluntary turnover, absenteeism, customer satisfaction. Cost these outcomes in money (cost of turnover components, cost of absenteeism) so the attitude data attach to dollars a line manager recognizes.
4. 4Run the analytics to connect management practices to the attitude scores, then to operational outcomes, then to financial outcomes — respecting that motivation- and opportunity-enhancing HR practices drive attitudes more than skill-enhancing ones.
5. 5Deliver the insight through Process: build a portal or dashboard that gives line managers their own unit's attitude, customer, and profit numbers so they can act, because talent management accountability now sits with the line, not HR alone.
6. 6Assign ownership to line leaders as 'Chief Talent Officers' and give HR the role of technical expertise — scale design, analytics, interpretation — rather than sole responsibility for the outcome.
7. 7Re-measure on a cycle, feed results back into the value-profit chain, and check whether engagement gains actually reduced turnover and absenteeism and raised customer satisfaction, not just survey scores.

Sysco Corporation used the LAMP model to connect employee attitudes to money. The logic: better management practices raise employee attitudes, which improve customer behavior (satisfaction and loyalty), which raises profits — the value-profit chain. Analytics connected the model to specific management behaviors, and measures captured employee attitudes at the operating-unit level. Sysco then delivered these numbers to managers through a web portal (the Process step), so each unit could see its own attitude, retention, and customer data and act on them. The monetary payoffs were tracked and the value-profit chain was integrated into organizational systems rather than left as a one-off study. The point: engagement mattered because it was tied through an explicit chain to customer behavior and profit, and put in managers' hands.

• If you cannot state the logic connecting an attitude score to a financial outcome, then do not launch the survey — you will produce numbers no one can act on.
• If your goal is stronger attitudes (satisfaction, commitment, engagement), then invest in motivation- and opportunity-enhancing practices (rewards, involvement, flexible job design, information sharing), because skill-enhancing practices move human capital instead.
• If turnover appears in your data, then cost its components before judging it, because some turnover is good or bad for the organization depending on who leaves.
• If line managers own the results, then give them unit-level data through a portal or dashboard; if only HR sees the data, then no behavior changes.
• If you measure engagement, then measure its sub-dimensions (vigor, dedication, absorption) plus satisfaction and commitment separately, since they are distinct and operate through different pathways.

• Treating engagement as a single number rather than a multidimensional attitude — the tell is a survey with one 'are you engaged?' item and no separate satisfaction or commitment scales.
• Assuming all HR practices lift attitudes equally — the tell is a training-heavy program (skill-enhancing) expected to raise motivation, when motivation is driven by rewards, involvement, and job design.
• Collecting attitude data with no logic linking it to customer behavior or profit — the tell is a dashboard full of scores no manager uses.
• Leaving accountability with HR — the tell is that senior leaders treat talent as 'an HR thing' rather than owning their role as Chief Talent Officers.
• Reading a raw turnover or absenteeism spike as automatically bad — the tell is action taken without costing the components or asking whether the departures were functional.

• ▸Logic statement: one sentence linking an attitude investment to a customer/financial outcome
• ▸Attitude measures: named scales for engagement (vigor/dedication/absorption), satisfaction, commitment
• ▸Driving practices: which motivation/opportunity-enhancing HR practices you will change
• ▸Behavioral outcomes: turnover, absenteeism, OCB, customer satisfaction to be tracked
• ▸Cost translation: dollar method for turnover components and absenteeism
• ▸Analytics link: how you'll connect practices → attitudes → operational → financial outcomes
• ▸Process delivery: the portal/dashboard giving line managers their unit-level data
• ▸Owner: named line leader accountable as Chief Talent Officer
• ▸Re-measure date: next measurement cycle and the outcome you expect to have moved

1. 1Separate the two components of stability before you measure anything: unscheduled absenteeism and voluntary turnover cost differently and demand different interventions. Use the LAMP model to structure each — Logic (the story connecting the investment to retention), Analytics (the method), Measures (the numbers), Process (how insight becomes action).
2. 2Cost absenteeism first because it recurs daily. Capture total employee-hours lost to unscheduled absence, load each hour with the employee's compensation plus benefits plus the supervisory and lost-productivity time absorbed managing the gap, then divide by total employee-hours to get a cost-per-employee-day figure managers can act on.
3. 3Cost turnover using its three components: separation costs (exit interviews, administrative processing), replacement costs (recruiting, selection, hiring), and training costs (orientation, ramp-up to full productivity). Sum these into a total cost of turnover per departure so the dollar magnitude is visible.
4. 4Split turnover into voluntary versus involuntary and functional versus dysfunctional — ask explicitly whether the departure is good or bad for the organization, because retaining low performers is not stability worth paying for.
5. 5Use selection at the source: screen for person-organization fit on values and personality (conscientiousness and emotional stability predict lower turnover), because employees whose values match the firm's stay materially longer.
6. 6Build the value-profit chain link: connect management practices to employee attitudes to customer behavior to profit, as Sysco did, so stability is defended as a financial outcome, not an HR nicety.
7. 7Put the numbers where managers see them — a web portal or dashboard — so absenteeism and turnover costs become actionable, not archived. Analytics only matters combined with Process.
8. 8Warn on faking when using personality screens in hiring: tell applicants distortion is detectable and carries consequences, which measurably reduces intentional distortion and protects the fit signal you're relying on to reduce turnover.

A public accounting study followed 904 college graduates hired by six firms over seven years. Graduates hired by firms emphasizing interpersonal-relationship values (team orientation, respect for people) stayed an average of 45 months. Those hired by firms emphasizing work-task values (detail, stability, innovation) stayed only 31 months. That 14-month gap in survival is a direct workforce-stability signal traceable to selection on values. Costed out, the shorter tenure translated to an opportunity loss of at least $12.5 million (in 2019 dollars) per firm emphasizing work-task values. The lesson is operational: how you select on cultural fit moves retention by more than a year per hire, and that year has a dollar value you can put in front of leadership.

• If turnover is voluntary AND the departing employee is a high performer, then treat it as dysfunctional and intervene on retention drivers; if the departure is a low performer, then it may be functional and not a stability loss worth spending on.
• If you are hiring for fit to reduce turnover, then select explicitly on conscientiousness and emotional stability using job-analysis-driven measures, because those validities are highest when theory and job analysis guide the choice.
• If you use personality or integrity tests in selection, then warn applicants that distortion is detectable and carries consequences, because warnings reliably reduce faking across studies.
• If absenteeism costs recur and are visible daily while turnover costs are episodic, then dashboard both continuously so the smaller daily leak isn't ignored beside the larger one-time loss.
• If analytics produce a sound conclusion but no manager can act on it, then the Process element has failed — route the number to a portal or dashboard tied to specific management behaviors.

• Treating all turnover as bad. Tell: reports show a single turnover rate with no functional/dysfunctional or voluntary/involuntary split, so retaining poor performers gets counted as a win.
• Costing only the obvious. Tell: turnover cost equals recruiting fees only, omitting separation processing and the training/ramp-up cost until the replacement reaches full productivity.
• Selecting on job-task credentials while ignoring values fit. Tell: hires are technically qualified but tenure stays short — the 45-vs-31-month pattern reappears because value congruence was never screened.
• Trusting personality scores without controlling faking. Tell: no warning is given about distortion, coaching inflates scores, and the fit signal you relied on to lower turnover is corrupted even though validity looks unchanged.
• Building analytics with no Process. Tell: elegant absenteeism and turnover models exist in a deck but never reach the managers whose behaviors drive the numbers, so stability never moves.

• ▸Absenteeism hours lost (period): total unscheduled employee-hours absent
• ▸Loaded hourly cost: comp + benefits + supervisory/lost-productivity time per hour
• ▸Cost per employee-day of absence: absenteeism cost divided by total employee-days
• ▸Separation cost per departure: exit interview + administrative processing
• ▸Replacement cost per departure: recruiting + selection + hiring
• ▸Training/ramp cost per departure: orientation + time to full productivity
• ▸Turnover type flag: voluntary/involuntary and functional/dysfunctional
• ▸Fit-selection criterion: named values + Big Five traits screened at hire
• ▸Action owner + dashboard location: who acts and where the number lives

1. 1Define the numerator and denominator before you measure: output is goods and services produced; input is labor, capital, and equipment. Do not conflate revenue with output—hold input constant to isolate real efficiency gains.
2. 2Compute unit cost as total input cost divided by units of output. Track it over time; the passage's operating principle is that the more productive an industry, the lower its unit costs and the stronger its competitive position.
3. 3Attribute productivity change to a specific HRM practice using the LAMP model: Logic (the story linking the investment to the outcome), Analytics, Measures, and Process. State the causal story explicitly before you crunch numbers.
4. 4Cost the human inputs that erode productivity—absenteeism and turnover—using the analytics in Chapter 3. Break turnover into its cost components (separation, replacement, training) to see the total cost, then decide whether the turnover is good or bad for the organization.
5. 5Link employee attitudes and behaviors to financial output the way Sysco did: connect management practices to customer behavior to profits, then feed measures back through a portal so managers can act.
6. 6Convert findings into monetary payoffs so productivity gains show up against the third theme—profit (income remaining after total costs are deducted from total revenue). A gain that does not move unit cost or profit is not yet demonstrated.
7. 7Feed conclusions back to line managers as actionable insight (Process), not as a report—productivity is optimized by every manager who allocates material, capital, and human resources, not by HR alone.

Sysco Corporation treated productivity as an output-to-input chain and made the causal story explicit before measuring. The Logic linked management practices to employee attitudes, employee attitudes to customer behavior, and customer behavior to profits—a value-profit chain. Analytics connected the model to specific management behaviors, and Measures pinned down the numbers so the relationships were quantifiable, not asserted. The Process step delivered these results back through the Sysco web portal, giving managers actionable insight they could act on directly. Because each link was measured, Sysco could estimate monetary payoffs and integrate the value-profit chain into ongoing organizational systems. The result: an HRM investment defended by output and dollars, not by anecdote—showing that better people practices lower the input needed per unit of value generated.

• If two units generate equal output but one uses less labor, capital, or equipment, then that unit is more productive and carries the lower unit cost—benchmark the rest against it.
• If you cannot state the Logic (the story connecting the investment to the outcome) before pulling data, then you are not ready to claim a productivity effect—build the LAMP story first.
• If a proposed HRM program does not reduce unit cost or increase profit (revenue minus total costs), then treat its business case as unproven regardless of how positive the attitude survey looks.
• If turnover or absenteeism costs are rising, then cost them by components first; only after seeing the total cost decide whether the turnover is good or bad for the organization.
• If an insight never reaches the line manager who allocates resources, then it will not move productivity—route every finding through a Process step like Sysco's portal.

• Measuring output as revenue instead of goods and services relative to input; the tell is a 'productivity' number that jumps whenever prices rise even though nothing operational changed.
• Skipping the Logic step and data-mining for correlations; the tell is a finding you cannot explain as a causal story linking investment to outcome.
• Ignoring hidden input costs like absenteeism and turnover; the tell is a productivity story that never quantifies the cost of people leaving or not showing up.
• Stopping at a positive attitude survey without connecting it to customer behavior and profit; the tell is enthusiasm with no monetary payoff and no change in unit cost.
• Treating productivity as HR's job alone; the tell is line managers who never receive actionable insight and keep allocating material, capital, and human resources unchanged.

• ▸Output measured: name the goods/services counted and the unit
• ▸Inputs counted: list the labor, capital, and equipment consumed
• ▸Unit cost: total input cost ÷ units of output (record baseline and current)
• ▸Logic: one-sentence story linking the HRM investment to the productivity outcome
• ▸Analytics: the method connecting the model to specific management behaviors
• ▸Measures: the exact numbers you will collect and their source
• ▸Process: how and to which line manager the insight is delivered for action
• ▸Monetary payoff: projected change in unit cost and in profit (revenue − total costs)