Human Resource Champions

1. 1Define your key HR activities as processes and prioritize them; break each into manageable chunks and document its variations, involving subject matter experts (Step 1 of the reengineering road map).
2. 2Build 'As Is' models: conduct workflow analysis (who does what, when, where, how), identify hand-offs, and audit constraints in existing systems for data compatibility, integrity, and consistency.
3. 3Determine current-process problems from the customer's point of view — measure baseline cost, cycle time, and error rate so improvement is quantifiable (e.g., a six-month staffing cycle).
4. 4Streamline and automate: consolidate duplicated systems into one (the firm with 24 separate training registration systems merged them into a single system), targeting cost savings and reduced cycle time.
5. 5Move to Phase 2 — rethink value creation, not just cut cost: reframe how the work is conceptualized rather than merely simplifying the existing flow.
6. 6Sort work by type: route routine, standardized transactions (benefits changes, payroll, 401(k), tax withholding) to a shared service center, and reserve specialized work for centers of expertise.
7. 7Choose the organizing structure deliberately (service center, center of expertise, broker of services, integrated solutions) based on whether the work is transactional or consultative — don't default to the centralize/decentralize debate.
8. 8Improve overall business efficiency beyond HR by hiring, training, and rewarding managers who raise productivity and reduce waste.

A firm audited its training administration and found twenty-four separate registration systems doing essentially the same job across units. Because the work was routine, standardized, and duplicated, it qualified as transaction-based — the kind best handled through a single standardized process. HR reengineered by streamlining and automating these into one system, which produced measurable cost savings. A second firm applied the same discipline to staffing: it measured the existing cycle at an average of six months to fill key positions, treated that cycle time as the target metric, redesigned the process, and cut the time to one month. In both cases efficiency came from consolidating duplication and re-sequencing workflow rather than from adding headcount, delivering the 'do more with less' outcome while holding service quality.

• If the activity is routine, standardized, and common across business units (benefits changes, payroll, 401(k), tax withholding), then route it to a shared service center for standardized delivery.
• If the work requires technical depth and business-specific judgment, then place it in a center of expertise rather than a transaction center.
• If you're arguing centralize vs. decentralize, then stop — it asks the wrong question; ask instead who uses the service and what they need.
• If a process shows duplication (multiple systems doing one job), then consolidate and automate into a single system before optimizing anything else.
• If you've only cut cost and simplified work, then you're not done — proceed to Phase 2 and rethink how the value is created.

• Stopping at cost-cutting and process simplification and calling it administrative expertise — the tell: no Phase 2 rethinking of value creation, so gains plateau and 'often did not go far enough.'
• Getting trapped in the centralize/decentralize power debate — the tell: conversations focus on who has authority to design systems instead of who uses the services.
• Overdoing everything ('anything worth doing is worth overdoing') — the tell: every decision routed to a high-performing team, every employee pushed through the same training, work piling up like closet clutter.
• Skipping baseline measurement — the tell: you can't state the before number (e.g., six months, twenty-four systems), so improvement can't be proven.
• Treating all work as transactional and shoving it into a service center — the tell: consultative, integrated work gets low quality and isolation because 'not all work is transactional.'

• ▸Target process name: the key HR activity, framed as a process
• ▸Priority rank: where it sits vs. other processes and why
• ▸Process chunks: the manageable sub-steps and documented variations
• ▸As-Is workflow: who does what, when, where, how — plus hand-offs
• ▸System constraints: data compatibility, integrity, consistency issues found
• ▸Baseline metrics: current cost, cycle time, error rate (e.g., 6 months to staff)
• ▸Work type: transactional (→ service center) or expert (→ center of expertise)
• ▸Value-creation rethink: how the work is reframed, not just simplified
• ▸Target metric + owner: the goal number and the champion/steering-committee accountable

1. 1Define the outcome, not the activity: state that the deliverable of the employee-contribution role is increased employee commitment AND competence, and hold your programs accountable to raising both, not to running staffing/training/reward mechanics.
2. 2Adopt the employee-champion role: get HR involved in the day-to-day problems, concerns, and needs of employees, and explicitly link each employee contribution back to the organization's success so the connection is visible to workers and executives.
3. 3Build listening channels that surface employee views. Copy the passage's own examples: run all-employee meetings (Microsoft-style) where views are voiced and heard, and stand up an employee services center reachable by an 800 number (Apple-style) staffed to answer policy and administrative questions.
4. 4Provide resources to employees so competence to do good work is matched by capacity to do it — this is the activity Ulrich pairs with the role in Table 2-1.
5. 5Repair the eroded employer-employee psychological contract: after downsizing, keep paying attention to employee needs rather than reverting to transactional, policy-only HR, because that contract is what commitment rides on.
6. 6Treat intellectual capital as the asset: where it is a critical source of firm value, be active and aggressive in developing that capital rather than passively administering it.
7. 7Measure by client impact, not your intentions. Ask employees whether services met their needs and delivered results — the passages warn that HR judged its services by its own good intentions while clients judged by impact received.
8. 8Aggregate the function, not just individuals: ensure the employee-relations experts who understand and meet employee needs are forging their talent into leveraged, shared competence with the rest of HR.

In the firm Ulrich describes, HR services were 'either misunderstood by employees or failed to meet their needs.' The HR professionals had been judging their services by their own good intentions, while their clients judged them by the impact and results of the services received. Using an HR role-assessment survey as a diagnostic, the firm compared ratings made by HR professionals, line managers, and others, which exposed the gap between intention and perceived value. This surfaced the reality that even where employee-relations experts 'worked effectively to understand and meet employee needs,' the function as a whole was 'woeful' because the individuals did not respect or like one another. Once they shared concerns, discussed differences openly, and focused on common goals, they began to speak with one voice about the purpose and value of HR. The lesson: raising employee contribution requires both meeting employee needs and validating that impact through client data, not self-assessment.

• If intellectual capital is a critical source of the firm's value, then be active and aggressive in developing it rather than merely administering transactions.
• If you can't show how a program raises either employee commitment or competence, then it is not delivering employee contribution — redesign or drop it.
• If employees judge a service by impact while you judge it by intention, then trust the client rating and treat the gap as the work to fix.
• If downsizing has eroded the psychological contract, then keep the employee-champion role active — do not retreat into policy-only, transactional HR.
• If an employee need is surfaced through listening channels, then respond by providing the resource that closes it, and make the link to organizational success explicit.

• Judging HR services by your own good intentions instead of client impact — the tell: HR reports success while employees report the service was misunderstood or missed their needs.
• Organizing around what HR does (staffing, training, rewards) instead of what it delivers — the tell: chapter-heading thinking where activities are counted but commitment and competence are never measured.
• Reverting to administrative, transactional, policy-only work after downsizing — the tell: employees disengage and the psychological contract keeps eroding while HR calls it efficiency.
• Building competent individual employee-relations experts who don't work as a team — the tell: strong one-on-one talent but a 'woeful' function that can't speak with one voice.
• Listening without responding — the tell: all-employee meetings and hotlines exist, but employee views are collected and not acted on, so contribution stays flat.

• ▸Employee need identified: what day-to-day problem, concern, or need surfaced
• ▸Listening channel used: meeting / hotline / survey through which it was heard
• ▸Response / resource provided: what was delivered to meet the need
• ▸Link to organizational success: how this contribution ties to firm goals
• ▸Commitment effect: evidence the response raised diligence/investment
• ▸Competence effect: evidence the response raised skill/capability to do good work
• ▸Client-impact rating: how employees rated the result (not HR's intention)
• ▸Intention-vs-impact gap: difference between HR self-rating and client rating
• ▸Owner and follow-up date: who closes the gap and by when

1. 1Separate the two sub-capabilities before you start: speed of implementing new initiatives (doing initiatives faster) versus fundamental transformation (culture change). They require different diagnostics and pacing, so name which one you are building.
2. 2Run the change through the seven-factor diagnostic from the GE work: leading change, creating a shared need, shaping a vision, mobilizing commitment, changing systems and structures, monitoring progress, and making it last. Score each factor honestly for the initiative at hand.
3. 3For shaping a vision, force behavioral definition: require employees to describe what they will do differently as a result of the change, whether they get excited by the result, and how it benefits customers and stakeholders. If you cannot state the change in behavioral terms, it is not yet a vision.
4. 4For mobilizing commitment, build a coalition and a responsibility matrix — identify who else needs to be committed, enlist key individuals, and assign accountability. Line managers, not HR alone, own this.
5. 5For modifying systems and structures, link the change to every HR system: staffing, training, appraisal, rewards, structure, and communication. Institutionalize it so it survives the sponsor's attention shifting elsewhere.
6. 6For monitoring progress, measure both the results of the change and the process of implementing it; benchmark both. Set a baseline before you begin so you can gauge movement.
7. 7For making it last, write a short- and long-term plan to keep attention focused, define the first concrete steps to get started, and plan to adapt the change over time rather than declaring victory once.

General Electric institutionalized capacity for change by turning benchmarking findings into repeatable process. A senior management team examined management practices at some of the best managed firms in the world to identify key processes for improving productivity, then derived a set of principles that became a course, 'Productivity/Best Practices,' attended by over 1,000 GE managers. In parallel, GE worked with a design team of outsiders (Steve Kerr, Dave Ulrich, Craig Schneier, Jon Biel, Ron Gager, Mary Anne Devanna) and GE employees (Jacquie Vierling, Cathy Friarson, Amy Howard) to develop the seven-factor change model. Note the two moves: they codified best practice into an institutionalized course so speed of adoption scaled beyond a single team, and they built a diagnostic that any sponsor could reuse. That is capacity for change made institutional — not a one-time win but a repeatable capability, addressing the 75 percent failure rate that dooms soft-capability efforts like TQM and reengineering.

• If the initiative is soft capability (TQM, reengineering, culture change), then assume a 75 percent failure baseline and over-invest in 'making it last' and systems modification rather than launch energy.
• If employees cannot state the change in behavioral terms — what they will do differently — then stop; you have a slogan, not a vision.
• If line managers treat the change as an HR program rather than a piece of total business management, then commitment is not yet mobilized and you should rebuild the coalition before proceeding.
• If you can name the best product built today but not who can build it repeatedly across changing markets, then you are optimizing competence, not capacity for change.
• If no baseline and no measure of both result and process exist, then do not launch; you will have no evidence the change took hold.

• Confusing individual competence with organizational capability — training great people while the team system stays fragile. The tell: the initiative collapses when a key sponsor or star leaves, like fearing the 49ers were doomed when Steve Young was injured, when the shared capability actually carried the team.
• Treating change as a launch event, not an institutionalized capability. The tell: high energy at kickoff, no short- and long-term plan to keep attention focused, and quiet abandonment within months.
• Skipping systems and structures — the vision is announced but staffing, appraisal, and rewards still reward the old behavior. The tell: people know the new direction but the incentives contradict it.
• Benchmarking only hard metrics (technology, financial ratios, quality) and copying a specific practice instead of the underlying principles. The tell: the Digital finding is ignored — best practice is a set of general principles and an integrated theme, not a single transplantable practice.
• Leaving change ownership entirely with HR as 'policy police.' The tell: line managers are absent from the responsibility matrix and treat the effort as someone else's initiative.

• ▸Change type: mark 'faster initiative' or 'fundamental transformation / culture change'
• ▸Leading change: who is the sponsor and are they visibly accountable?
• ▸Shared need: why must this happen, stated so people feel the pressure?
• ▸Vision in behavioral terms: what will employees do differently, and how does it benefit customers?
• ▸Mobilizing commitment: coalition members and responsibility matrix (who owns what)
• ▸Systems and structures: which HR systems (staffing, training, appraisal, rewards, structure, communication) will be re-linked to the change
• ▸Monitoring progress: baseline, result measure, and process measure to benchmark
• ▸Making it last: first step to start, short-term plan, long-term plan, and adaptation trigger

1. 1Define competitiveness as value created for three stakeholder groups simultaneously — investors (financial results), customers (satisfaction/loyalty), employees (attraction/retention) — not any one alone. Score each group so you can't claim a win by starving another.
2. 2Ask your executives the diagnostic question Ulrich opens seminars with: 'To be competitive, what are the top five business challenges your executives must pay attention to?' Collect answers across hierarchy levels to surface the shared competitive reality.
3. 3Map the value chain your firm sits inside — suppliers and customers — and redirect practices outward, since responsiveness (innovation, faster decisions, price/value leadership, supplier linkage) is what customers pay for.
4. 4Use the employee-attitude-to-customer-attitude correlation: measure employee attitude as a leading indicator of customer attitude, then act on employee needs to move the customer number.
5. 5Resolve the growth-versus-cost paradox explicitly: build structures that give autonomy for growth AND discipline to control costs, and begin transformation work while still climbing the growth curve rather than after cresting.
6. 6Convert 'doables' into 'deliverables' — for every practice, name the outcome it produces (administrative efficiency, employee commitment and competence, customer responsiveness) and hold it to that standard.
7. 7Kill any practice that fails to add value or impedes performance; keep only what demonstrably creates value or delivers results.

Deborah Engle, VP of HR for 3Com, faced the classic competitiveness paradox: sustaining rapid growth (investor and customer demands) while controlling costs (financial discipline). Most firms wait until they have crested on the growth curve to restructure and cut costs; Engle argued the opposite. She convinced 3Com executives to begin transformation work while the firm was still climbing its growth curve. She did this by examining the firm's culture, how work gets done, its lines of communication, and how employees are hired, trained, motivated, and organized. The result: 3Com managed growth and costs simultaneously for sustained profitability. The move works because it treats competitiveness as a multi-stakeholder balance rather than choosing growth now and paying the cost-control bill later.

• If a practice adds value or delivers results, keep it; if it fails to add value and impedes performance, do away with it.
• If employee attitude scores are falling, then expect customer attitude to follow — treat the employee number as an early warning and intervene before the customer defects.
• If you are choosing between growth and cost control, then design structure to deliver both (autonomy plus discipline) rather than sequencing them.
• If a chapter/initiative heading names an activity, rename it as an outcome — if you can't state what happens because of it, it isn't yet a deliverable.
• If a merger shows strong financial and strategic fit but dismal cultural fit, then treat competitiveness as at risk, because that mismatch is why many mergers fail.

• Optimizing one stakeholder at the expense of others — e.g., pleasing investors by gutting the employee base; the tell is a financial win alongside eroded employee commitment and, downstream, falling customer attitude.
• Measuring doables (activities, headcount, programs run) instead of deliverables (value produced); the tell is HR/functional reports full of what was done and silent on what happened because of it.
• Waiting to restructure until after the growth curve crests; the tell is scrambling to cut costs during a downturn instead of transforming while still climbing.
• Focusing practices inside the firm and ignoring the value chain; the tell is training and compensation that never involve suppliers or customers as evaluators.
• Assessing merger/expansion compatibility on financial and strategic fit only because cultural fit is harder to measure; the tell is 'remarkable financial fit' cited while cultural attributes go unexamined.

• ▸Investor value delivered: name the financial result and its current metric
• ▸Customer value delivered: name satisfaction/loyalty measure and current level
• ▸Employee value delivered: attraction/retention and commitment/competence measures
• ▸Employee-to-customer link: current employee attitude score and the customer number it predicts
• ▸Value-chain reach: which supplier/customer touchpoints this practice includes
• ▸Doable → deliverable: state the activity, then the outcome it produces
• ▸Growth/cost paradox: autonomy mechanism and discipline mechanism in place
• ▸Cultural fit check (for mergers/expansion): attributes assessed beyond financial/strategic
• ▸Keep-or-kill verdict: does it add value or impede performance?

1. 1Start with deliverables, not activities: define the outcome you owe the business (strategy execution) before listing any HR program, so partnering translates into results rather than tasks.
2. 2Join line management in the strategic planning process—sit in the meetings where strategy is set, and talk in terms of how competitive challenges dictate HR activities rather than defending HR programs.
3. 3Run an organizational diagnosis: ask the four capability questions—what capabilities currently exist, what will be required for future success, how do we align them with strategy, and how do we design HR practices to create them.
4. 4Translate the identified capabilities into concrete HR practice changes across staffing, training, appraisal, rewards, communication, and organization design—each redesign must be justified by the capability it builds, not by tradition.
5. 5Refocus HR practices onto the value chain: apply training, compensation, and evaluation to suppliers and customers, not only to people inside the firm, using customer criteria to redefine every activity.
6. 6Measure the accomplishment: translate HR work into financial performance and business results, since the impact of HR practices can and must be measured.
7. 7Force vigorous debate when strategy and organizational reality conflict—be confrontative and challenging on HR issues that block execution rather than staying a ward of management.
8. 8Sequence transformation before the growth curve crests, examining culture, workflow, communication lines, and how people are hired, trained, motivated, and organized while still climbing, so growth and cost control run simultaneously.

Deborah Engle, vice president of human resources for 3Com, pushed the firm to reinvent itself during its most rapid growth ever. She argued that most firms wait until they crest the growth curve before restructuring and cutting costs, then convinced 3Com executives to begin transformation work while still climbing. Her diagnosis examined the firm's culture, how work gets done, its lines of communication, and how employees are hired, trained, motivated, and organized. By treating these organizational dimensions as the levers of strategy rather than as separate HR programs, 3Com managed growth and costs simultaneously for sustained profitability. This is strategic partnering in operation: an HR executive participating in the strategic conversation, diagnosing organizational capability, and translating a business goal—profitable growth—into specific HR priorities.

• If you are about to list an HR activity, then first name the deliverable it produces; if you cannot, drop it—focus on deliverables, not means.
• If you have identified a required future capability but no current HR practice builds it, then redesign a practice (staffing, reward, training) explicitly to create it.
• If an HR practice is aimed only inside the firm, then test whether it should extend to suppliers and customers on the value chain and redefine it against customer criteria.
• If a manager treats HR as soft and unaccountable, then translate the proposed change into measurable business/financial impact before proceeding.
• If the firm is still climbing the growth curve, then begin transformation and cost work now rather than waiting for the crest.

• Organizing work around HR activities (staffing, rewards, comms) instead of deliverables—the tell: chapter-heading thinking where success is measured by programs run, not outcomes delivered.
• Becoming a ward of management: attending endless meetings on topics far removed from real issues—the tell is employees seeing HR as management's agent rather than a partner in execution, and HR unable to name the strategy it serves.
• Hiring, training, and rewarding individuals without tying those actions to organizational capability—the tell: strong individual competence but no repeatable capability to perform over and over (the 49ers stay strong when a star is injured because capability outranks individuals).
• Assessing only financial and strategic fit in mergers while ignoring cultural fit—the tell: remarkable financial fit but dismal cultural compatibility, and integration failing.
• Retreating into comfort work over strategy alignment—the tell: HR seen as therapy or health-and-happiness patrol, making employees comfortable rather than competitive.

• ▸Business strategy/goal: state the specific competitive challenge driving this
• ▸Capabilities that currently exist: what the firm already does better than competitors
• ▸Capabilities required for future success: the gap to close
• ▸Alignment check: how each required capability maps to the strategy above
• ▸HR practice redesign: which practice (staffing/training/reward/org design/comms) will build the capability
• ▸Value-chain extension: how this practice reaches suppliers and customers
• ▸Measure of success: the business/financial metric that proves the deliverable landed
• ▸Line-manager owner: who co-champions this with HR
• ▸Timing: what starts now versus later on the growth curve

1. 1Start with the outcome, not the activity: define administrative efficiency as reduced cost while quality of service is maintained, and make that the standard every process gets judged against.
2. 2Map the flow of each HR process (information, decisions, materials, resources to serve the internal customer) so you can see where value is added and where bureaucratic waste sits.
3. 3Reengineer the HR process itself before you redesign delivery: strip out steps that don't add value for the line manager or employee receiving the service.
4. 4Choose a delivery model for each process from the menu the passages name — shared services, outsourcing, or the learning organization — matching model to process type.
5. 5Route high-volume transactional, administrative, and policy work (staffing, benefits, compensation administration) into shared services or outsourcing so specialists handle repeatable work at scale.
6. 6Retain and elevate expertise-dependent work: develop and manage guidelines/plans/policies, act as an internal consultant in a discipline, and take responsibility for continuous improvement in that field.
7. 7Measure the impact: translate the redesign into financial performance, proving cost reduction against maintained or improved service quality — do not treat HR's contribution as unaccountable soft-side work.
8. 8Keep the recognized-expert standard alive: stay current on issues in each discipline so continuous improvement, not one-time reengineering, becomes the pattern.

General Electric's approach to processes shows how administrative expertise operates on flows rather than functions. GE identified six core processes — Order to Remittance, New Product Introduction, Quick Market Intelligence, Globalization, Supplier Management, and Productivity — each defined as a flow of information, decisions, materials, or resources to serve customers. Supplier Management, for instance, is explicitly the process for managing supplier relationships to reduce costs, and Productivity is the process for increasing efficiency. Applying this logic to HR, you define each HR service as a flow and ask what actually adds value for the internal customer. You then reengineer that flow and pick a delivery model — shared services for repeatable transactions, outsourcing for non-core administration — so cost drops while service quality holds. The Clorox administrative experts model the retained side: they develop and manage HR guidelines and policies, consult within a discipline, and own continuous improvement so the redesign keeps compounding.

• If work is high-volume, transactional, or policy-driven, then move it to shared services or outsourcing rather than staffing it with expensive generalists.
• If a process step adds no value for the line manager or employee receiving the service, then eliminate it before automating or outsourcing it.
• If cost reduction would degrade service quality below the standard, then the redesign fails the administrative-efficiency test — rework it, don't ship it.
• If you cannot translate a proposed change into measurable financial performance, then you haven't yet proven it adds value — treat HR impact as measurable, not soft.
• If work depends on discipline expertise and continuous judgment, then retain it in-house and elevate the owner to internal consultant status.

• Framing administrative expertise as pure cost-cutting — the tell is HR positioned as the function whose job is to control and reduce costs rather than to reduce costs while maintaining quality and adding value.
• Optimizing what HR does instead of what it delivers — the tell is chapter-heading thinking (staffing, benefits, compensation) with no reference to the outcome of administrative efficiency.
• Reengineering delivery models before reengineering the underlying process — the tell is outsourcing or shared services layered on top of workflows still full of no-value steps.
• Reverting to the bureaucratic pattern — the tell is that clients still expect HR only for administrative, transactional, and policy work, because expectations were never reset.
• Skipping measurement — the tell is treating HR as soft-side and unaccountable, so cost and quality gains are asserted but never translated into financial performance.

• ▸Process name: the specific HR service being examined (e.g., benefits administration).
• ▸Flow map: list the information/decision/material/resource steps from request to delivery.
• ▸Value test: for each step, note whether it adds value for the receiving line manager or employee.
• ▸Steps to eliminate: name the no-value steps to strip out before any redesign.
• ▸Delivery model: choose shared services, outsourcing, or in-house learning-organization — with the reason.
• ▸Retained expertise: what discipline knowledge and continuous-improvement ownership stays in-house.
• ▸Quality standard: the service-quality level that must be maintained after redesign.
• ▸Cost baseline vs. target: current cost and the reduced-cost target after reengineering.
• ▸Financial proof: how the change will be translated into measurable financial performance.

1. 1Reframe your target from doables to deliverables: state the employee-championing outcome as employee contribution and commitment, not activity volume. Ask what happens because HR does this work, not how well the work is done.
2. 2Diagnose the demand/resource balance the way a financial auditor examines receivables and payables: systematically inventory the demands placed on employees against the resources (skills, tools, decision authority, support) available to meet them, then name the gaps.
3. 3Build a two-way listening channel so employee concerns surface and get a response — treat this as fair treatment of employees, a past HR issue that stays central to the future.
4. 4Convert listening data into competence-building actions: where a demand exceeds resources, add training, retraining, skills assessment, or authority so employees remain competent under the demand.
5. 5Aim the whole cycle at commitment, not comfort: measure whether employees become more committed and contribute, not whether they are happier. Refuse the health-and-happiness patrol framing.
6. 6Connect employee attitude to business results explicitly, using the research that employee attitude correlates highly with customer attitude, so championing employees reads as competitiveness, not welfare.
7. 7Force the vigorous debate when a demand is unreasonable: be confrontative and challenging with managers to rebalance demands rather than silently absorbing them onto employees.

Frontier faced a changing telecommunications market that required a cultural transformation to survive. Chairman Ronald Bitner stated no vision can be achieved without an able and dedicated employee body, and committed to a fresh, critical assessment of the skills and competencies each employee needs to move forward — bringing expertise in from outside where it was lacking. This is employee championing framed as competence: the organizational demand (become the premier telecommunications company through quality and customer focus) is balanced against a resource audit of employee skills. Bitner hired senior HR executive Janet Sansone to champion the effort, tasking her to keep culture change in the discussion and to build a process that continually realigns the organization with changing business requirements. In local markets that process meant constructing cost-competitive organizations while absorbing acquisition-driven demands. The move keeps employees competent (assess and add skills) and committed (a dedicated employee body serving the vision) instead of merely comfortable.

• If a request will make employees happier but not more committed or competitive, then decline it — HR practices exist to help employees become committed, not comfortable.
• If an organizational demand exceeds available employee resources, then either add resources (training, retraining, authority) or force a debate to lower the demand — do not let the gap fall silently on employees.
• If a manager treats compliance or morale as HR's problem, then reassign ownership: managers own compliance and commitment; HR helps them commit employees and administer policy.
• If you cannot tie an employee initiative to a business result such as customer attitude or competitiveness, then reframe or drop it — impact must be measurable.
• If a concern surfaces repeatedly through your listening channel, then treat it as a fair-treatment issue requiring a response, not an isolated complaint.

• Running HR as a health-and-happiness retreat: the tell is initiatives justified by employee comfort or morale with no line to commitment or business results.
• Professing instead of being professional — writing value statements and preaching rather than acting; the tell is more talk and jargon than measured delivery.
• Owning compliance and morale for managers so they disengage; the tell is managers routing all people problems to HR as 'HR's job.'
• Being the nice people who never confront: the tell is demands stacking on employees because HR avoids the vigorous, challenging debate with managers.
• Loading demands without auditing resources, so employees are asked to move forward without the required skills; the tell is competence gaps discovered only after performance fails.

• ▸Employee concern heard: state the concern surfaced through your listening channel.
• ▸Organizational demand: name the specific demand placed on these employees.
• ▸Required competencies: list the skills/competencies the demand needs.
• ▸Current resources: inventory skills, tools, authority, and support available now.
• ▸Gap: name where demand exceeds resource.
• ▸Balancing action: training, retraining, added authority, or demand renegotiation.
• ▸Commitment measure: how you will verify employees become more committed, not just comfortable.
• ▸Business result link: the competitiveness/customer outcome this supports.
• ▸Owner and response date: who acts and when the employee gets a response.

1. 1Separate the two workstreams you own: incremental change (improving initiative design and reducing cycle time across all activities) and transformation (fundamental cultural change). Name which one the situation demands before choosing tools.
2. 2Diagnose readiness by asking the four capability questions from the passages: What capabilities exist now? What will future success require? How do we align capabilities with strategy? How do we design HR practices to create them? Answer these in writing with line managers.
3. 3Run the change-agent action sequence in order: identify and frame the problem, build relationships of trust, solve the problem, then create and fulfill an action plan. Do not skip trust-building to rush to solutions.
4. 4Ground the change in the past. Convene a deliberate dialogue about values — appreciate and respect the tradition and history of the business — then identify the specific new behaviors that keep the firm competitive going forward.
5. 5When transformation is underway, split your role explicitly: act as cultural guardian (protecting what still serves) and cultural catalyst (forcing the shift). For change proper, act as process-identifier — build commitment to the process and ensure change occurs as intended.
6. 6Help employees let go of the old culture and adapt to the new; treat 'letting go' as its own task, not a byproduct of announcing the new state.
7. 7Measure the deliverable, not the activity. The outcome is capacity for change — flexibility and agility for constant innovation — so track cycle time on initiatives and whether change built on and maintained itself (learning), not how many workshops you ran.

The passages define the change agent's job as producing one deliverable: capacity for change. Take an organization launching a reengineering initiative — an incremental change where the goal is improving implementation and reducing cycle time. As change agent you first frame the problem (post-reengineering trauma and burned-out employees threaten follow-through), then build trust by facilitating a dialogue about values that honors the firm's history before naming new behaviors. You solve by identifying a repeatable process for managing the change and building commitment to it among line managers, who own compliance. You then create and fulfill an action plan and measure success by reduced cycle time and whether the change maintained itself rather than by activity counts. If the initiative were instead a full culture change, you would additionally play cultural guardian and catalyst, helping employees let go of the old culture and adapt to the new.

• If the goal is faster, better initiative implementation and shorter cycle time, then treat it as incremental change and focus on process; if the goal is fundamental cultural change, then treat it as transformation and add cultural guardian/catalyst work.
• If people distrust the effort, then stop and build relationships of trust before attempting to solve the problem — trust precedes solution in the action sequence.
• If employees resist, then check whether you have helped them let go of the old culture; adaptation to the new fails when the old is not released.
• If line managers treat the change as HR's project, then reassign ownership — managers own compliance and the change is as important to them as finance or strategy.
• If you cannot answer the four capability questions, then you are not ready to facilitate the change; diagnose readiness first.

• Chasing activities instead of the deliverable. The tell: you can list workshops delivered but cannot show reduced cycle time or self-sustaining change.
• Skipping trust to jump to solutions. The tell: action plans exist on paper but stall in execution because relationships were never built.
• Erasing the past instead of grounding change in it. The tell: employees feel their history and tradition are dismissed, and resistance hardens around values.
• Announcing the new culture without helping people let go of the old. The tell: new behaviors are stated but old behaviors persist; adaptation never happens.
• Letting HR own the change alone. The tell: line managers stay spectators and compliance erodes because no manager treats the change as their own.

• ▸Change type: mark incremental (cycle-time/design) or transformational (culture).
• ▸Capabilities now: what capabilities currently exist in the firm.
• ▸Capabilities needed: what future success will require.
• ▸Alignment: how these capabilities connect to business strategy.
• ▸Problem frame: the change problem stated in one sentence.
• ▸Trust step: who must trust whom, and how trust will be built.
• ▸Past-to-honor: traditions/values to appreciate before naming new behaviors.
• ▸New behaviors: specific behaviors that keep the firm competitive.
• ▸Deliverable metric: how capacity for change is measured (cycle time; did change sustain itself).

1. 1Start with business strategy, not HR programs: participate in defining the strategy so you know what daily actions it demands, then work backward to the HR practices that produce those actions.
2. 2Run an organizational diagnosis: examine current HR practices (staffing, development, compensation, communication, organization design) against the strategy and ask where they align and where they contradict it.
3. 3Identify the specific capability the strategy requires — the thing the organization must do better than competitors (e.g., seamless global talent movement, high-quality service, low labor cost per store).
4. 4Translate the strategy into HR priorities: for each strategic objective, name the concrete policy or practice change that moves conception to execution faster.
5. 5Redesign the practice to differentiate in the relevant 'market' — sometimes the internal talent pool is the customer, so design the offer around what that customer values.
6. 6Set the metric so the practice ties to a business result (labor cost per store, global revenue, service quality perception, cycle time), not to HR activity.
7. 7Ask the questions that move strategy to action in every planning session — force the debate about whether the organization is actually designed to deliver, rather than assuming intent equals execution.

When Marriott decided to enter the Hong Kong market, executives knew service quality was their primary differentiator and that quality of employees correlated with perceived service. They defined the strategic requirement as attracting and retaining the most qualified employees in the area — treating the talent pool (people then working for competitors) as the customer to be enticed. HR and line executives together examined the company's HR practices to find a way to distinguish Marriott in that labor market. They offered a five-day workweek instead of the six-day week competing hotels required. That single, simple policy became the cornerstone of the service-quality strategy, letting Marriott advertise, solicit, and secure the talent needed. Here HR did not run a generic staffing program — it translated a specific business strategy into a specific practice that produced the required daily behavior.

• If a strategic objective cannot be named as a concrete HR practice change, then execution capability is missing — keep diagnosing until the practice is explicit.
• If the practice measures HR activity rather than a business result (cost, revenue, service, cycle time), then rewrite the metric to a business outcome.
• If the strategy depends on a soft organizational capability (speed, talent mobility), assume high failure risk (surveys show ~75% failure for soft capabilities) and design deliberately rather than declaring it.
• If HR is treated as compliance police or health-and-happiness patrol, then it is not a strategic partner — reposition its work toward committing employees to strategy.
• If the time from conception to execution of a strategy is long, then attack the HR practices that slow translation before adding new strategic ambitions.

• Organizing HR around doables (staffing, training, rewards) instead of deliverables — the tell is that HR reports list activities completed, not business objectives achieved.
• Declaring a capability instead of building it — teams announce 'we are global' or 'we do TQM' with no changed practice; the tell is the ~75% implementation failure and no altered daily behavior.
• Skipping organizational diagnosis and jumping to a best-practice program — the tell is HR practices that are innovative and elegant but disconnected from the current strategy.
• Treating employees as customers to be made happy rather than committed — the tell is satisfaction surveys rising while strategy execution stagnates.
• Waiting until growth crests to align organization to strategy — the tell is restructuring only in decline; contrast 3Com's Deborah Engle, who pushed transformation while still climbing the growth curve.

• ▸Business strategy: state the specific objective in one line (e.g., increase global revenue).
• ▸Required capability: what must this organization do better than competitors to deliver it?
• ▸Customer of this practice: who must behave differently (external customer, talent pool, employees)?
• ▸Current HR practice: what staffing/reward/development/design practice exists today?
• ▸Alignment gap: where does the current practice support or contradict the strategy?
• ▸Redesigned practice: the concrete policy change that produces the required daily action.
• ▸Business metric: the result this practice must move (cost, revenue, service, cycle time).
• ▸Speed check: does this shorten time from conception to execution? Yes/No + why.
• ▸Owner: which line manager and HR partner jointly own delivery?