4.6 Project Support and Implementation Controls

HR's Project Role

Project management is an explicit sub-skill of the Consultation competency, so the Business cluster expects HR to think beyond the idea and help manage execution. HR frequently supports projects that affect people even when HR does not own them outright: new systems, schedule changes, onboarding redesigns, policy updates, manager training, workforce planning, and process improvements.

Every project moves through a lifecycle — initiating, planning, executing, monitoring and controlling, and closing. HR's contribution is strongest in planning (defining people impact) and monitoring (watching adoption and risk). The work starts with scope: what is changing, who is affected, what is out of scope, and what has already been decided. Without a defined scope, projects expand (scope creep), confuse stakeholders, and miss the people impact that ultimately determines adoption.

The triple constraint — scope, time, and cost (with quality at the center) — frames the tradeoffs: compressing the timeline or cutting budget usually forces a change in scope or quality, and HR should make that tradeoff visible when preparation steps are being skipped.

Implementation Controls

HR applies a set of controls to keep a people-affecting project on track:

• Scope — define the work, boundaries, and intended outcome.
• Roles — clarify sponsor, project owner, HR role, manager role, and approvers, often with a RACI matrix (Responsible, Accountable, Consulted, Informed).
• Milestones — mark decisions, communications, training, launch, and review points.
• Risks — assess policy, employee-relations, communication, workload, and adoption risks.
• Change support — prepare managers and employees for new expectations.
• Measures — decide how the team will know the project is working.

A stakeholder analysis — mapping who is affected, their influence, and their concerns — helps HR target communication and manage resistance before it surfaces.

Change Management and Common Traps

Projects that change how people work require change management, and the BASK expects familiarity with the main models:

• Lewin — unfreeze, change, refreeze.
• Kotter's 8 steps — create urgency, build a coalition, form a vision, communicate it, empower action, generate short-term wins, consolidate gains, anchor the change.
• ADKAR — Awareness, Desire, Knowledge, Ability, Reinforcement, focusing on the individual transition.

Two exam traps recur. First, late HR involvement — waiting until after launch, then reacting to resistance and confusion. If a project changes employee work, schedules, responsibilities, data, or policies, HR should engage early enough to identify people risks. Second, overbuilding — applying a heavy formal plan to a small change. Control should be proportionate: a small team process change needs a brief checklist and a manager note; a cross-functional change affecting many employees needs a formal timeline, sponsor alignment, training, and post-launch review.

Communication is a major control: the team should know who communicates what, to whom, and when. Employees need to know what is changing, why, when, what they must do, and where to ask questions — and managers must be prepared before employees look to them for answers. On SHRM-CP scenarios, choose the answer that makes execution visible — defining roles, anticipating risks, supporting adoption, and including a way to learn after launch — rather than one that waits until employees report confusion.

Managing Resistance and Measuring Adoption

Resistance is normal, not insubordination, and HR's job is to anticipate and address it rather than override it. People resist change for predictable reasons: fear of the unknown, loss of competence or status, distrust of leadership, change fatigue, or simply not understanding the rationale. The remedies map to the cause — information for misunderstanding, involvement for low ownership, support and training for competence fears, and visible leadership commitment for distrust. Identifying why a group resists lets HR choose the right response instead of a generic communication blast.

Adoption must be measured, not assumed. A project is not successful at go-live; it succeeds when people actually use the new system or follow the new process. Useful adoption signals include:

• Usage rates — what share of employees use the new tool or process as intended.
• Error or rework rates — falling errors suggest the change is working.
• Help-desk and question volume — a spike points to gaps in training or communication.
• Manager and employee feedback — pulse checks after launch surface friction early.

Proportionate control by project size

A post-implementation review (sometimes called a lessons-learned or retrospective) closes the project loop: what worked, what did not, and what to carry into the next initiative. This connects project support back to Analytical Aptitude and Evidence-Based Recommendations — the same discipline of defining success, measuring it, and adjusting. The recurring exam signal is the same throughout the Business cluster: HR adds value by making people impact and execution visible and managed, scaled sensibly to the size of the change.