4.4 Problem Framing and Root Cause

Requests Arrive as Solutions

Most HR requests show up already shaped as solutions: a leader asks for training, a manager asks for discipline, an employee asks for a transfer, a team asks for more staff. Problem framing is the discipline — sitting inside Consultation and Analytical Aptitude — of defining the issue that must be solved before choosing the intervention. Without it, HR spends effort on a visible symptom while the underlying cause continues.

Root-cause thinking need not be complex. HR asks what changed, who is affected, when it began, what evidence exists, and what has already been tried. These questions separate a people issue from a process issue, a skill gap from a motivation gap, and a policy problem from a communication problem.

Framing also changes the tone of the conversation. Rather than telling a manager their proposed fix is wrong, HR says the organization should confirm the cause so the recommendation solves the issue. This preserves the relationship — a respected-business-partner behavior — while improving the decision quality.

Root-Cause Tools and a Framing Template

Three structured tools appear in HR root-cause work:

• 5 Whys — ask "why" iteratively (typically five times) to move from symptom to root cause. "Deadlines missed → why? Rework → why? Specs unclear → why? Requirements not signed off → why? No intake step → root cause: missing process gate."
• Fishbone (Ishikawa / cause-and-effect) diagram — groups possible causes into categories (people, process, tools/technology, environment, management, materials) to avoid fixating on one.
• Pareto analysis (80/20) — focuses on the vital few causes that drive most of the effect.

Frame every issue with this template:

The level of analysis should be proportionate: a routine issue needs a short conversation and a document review; a recurring or cross-functional issue may warrant data analysis, stakeholder interviews, process mapping, or a pilot.

Reframing Common Requests

The most common SHRM-CP trap is the answer that solves the wrong problem quickly. Rolling out training for everyone wastes resources if managers simply aren't reinforcing the process. Disciplining an employee is premature if expectations were never communicated. Adding headcount won't fix a workflow clogged by rework.

When vague labels appear — "bad attitude," "not a team player" — HR reframes them into observable behavior, communicated expectations, prior feedback, and work impact before any corrective path. This protects fairness and supports defensible documentation if discipline becomes appropriate.

On close answer choices, prefer the option that names the problem before prescribing the fix. The Business-cluster lens values practical diagnosis, not analysis for its own sake — the goal is a better, more defensible action that the evidence can later confirm worked.

Skill, Will, and Systemic Causes

A practical diagnostic lens for people problems is the skill-versus-will distinction. If an employee cannot perform (a skill gap), the fix is training, tools, or job redesign. If an employee can but does not perform (a will gap), the fix is feedback, expectations, motivation, or accountability — and training would waste effort. Misreading a will problem as a skill problem (or vice versa) is one of the most common HR errors, and SHRM-CP scenarios reward HR that tests which one is actually present before acting.

Root-cause work also asks whether a problem is individual or systemic. When one person misses targets, coaching may suffice; when an entire team misses them, the cause is more likely a system issue — unrealistic goals, broken processes, inadequate staffing, or poor management. W. Edwards Deming's insight that most performance problems are caused by the system, not the worker is directly relevant: disciplining individuals for a systemic failure neither fixes the issue nor is fair.

Symptom vs. root cause — worked example

• Symptom: new hires quit within 90 days.
• Surface fix (wrong): recruit harder to replace them.
• 5 Whys: they quit → role differs from the posting → managers oversell the job → no realistic job preview → onboarding sets no clear expectations.
• Root cause: a missing realistic-job-preview and structured onboarding step.
• Right fix: add a realistic job preview and a 90-day onboarding plan with check-ins.

This shows why framing precedes solution: replacing recruiters would never have stopped the quitting, while a small process change addresses the actual driver. Proportionate diagnosis — quick for routine issues, deeper for recurring or cross-functional ones — keeps HR efficient while still solving the right problem.