What You'll Learn
- Why the problem you're first given is rarely the problem you actually need to solve
- How to recognize when you're being handed a symptom rather than a cause
- The discipline of pausing before solving, and what that actually looks like in practice
- Where this lesson's job ends and the rest of this section's job begins
Why This Matters
HR Fundamentals 101 built the instinct to check what's missing before deciding, and to trace a visible problem back toward where it likely started. This course asks you to do that systematically, as a repeatable discipline, not just a helpful habit you apply when you happen to remember to.
A boundary worth stating plainly before we go further: this lesson is about recognizing that a presenting complaint is usually a symptom, and building the discipline to pause before solving it directly. It does not teach you how to trace a symptom back to its root cause, that's Lesson 3. It doesn't teach you how to frame a sharp diagnostic question, that's Lesson 2. This lesson is the mental reset that makes those later skills necessary, and worth doing properly.
The Big Idea
Presenting Problems vs Real Problems
A presenting problem is what you're actually told or asked to fix, "morale is low," "we need a new onboarding program," "this manager needs coaching." At this stage, HR should treat it as a starting point, not assume it represents the underlying problem or cause. This gap exists for an understandable reason: the person raising a concern usually experiences a symptom directly, frustration, low morale, a string of resignations, and proposes the first plausible-sounding fix that comes to mind. That isn't a flaw in the person raising it. It's simply how people describe problems, from what they can see and feel, not from whatever is actually producing it.
Solutions That Arrive Pre-Packaged
A particularly common trap: someone doesn't just name a symptom, they name a symptom and a proposed solution together, "engagement is low, we need more recognition programs." Accepting the solution along with the symptom skips the diagnostic step entirely, it assumes the diagnosis is already correct without ever checking it. Separating the problem as stated from the problem as it actually is, is the core move this course is built around.
The Discipline of Pausing
This isn't about being suspicious of everyone who raises an issue, or slow-walking every request that comes your way. It's a specific habit: before committing to a solution, ask whether this is the actual problem, or simply how the problem is currently being described, and hold that question open rather than answering it immediately with whatever fix was proposed alongside it.
A symptom and a solution arriving together should raise your attention, not lower it.
How It Works
- Notice when a presenting problem arrives bundled with a proposed fix. That bundling is itself a signal worth pausing on, not a reason to move faster.
- Ask what's actually being described. An outcome or symptom, attrition, complaints, disengagement, or an interpretation of what is causing it. At this stage, the important distinction is between what has been observed or reported and what has actually been established.
- Resist proposing or agreeing to a fix at this stage. The job right now is recognizing that more work is needed before a fix, not doing that work yet, that's the rest of this section.
Example
A department head, Sanjay, tells HR: "Our onboarding is clearly broken, we need to redesign it completely. Three new hires on my team have quit in their first two months, and I think it's because the training is too slow-paced and boring." He wants a full onboarding redesign greenlit by next week.
Ananya, in HR, doesn't immediately agree to the redesign, and doesn't dismiss the concern either. She notices that the presenting problem, "onboarding is broken", arrived bundled with both a proposed fix and a stated cause, "too slow-paced and boring", that hasn't actually been checked. It's Sanjay's theory, not a confirmed finding. Rather than committing to a redesign, she tells him she wants to look into what's actually driving the departures before recommending anything specific, exactly the kind of investigation the rest of this section will cover.
Practitioner Lens
The instinct to be helpful and move fast can work against you here. Genuinely helping a frustrated stakeholder sometimes means not agreeing with their diagnosis immediately, even though agreement is the path of least resistance in the moment. A quick agreement that solves the wrong problem costs far more later than a short pause to check first would have.
Common Mistakes
- Accepting a bundled symptom-plus-solution as if the diagnosis were already established. The fact that a fix was proposed doesn't mean the cause behind it was verified.
- Treating a stakeholder's frustration as evidence of what's actually causing the problem. Frustration is real. It isn't the same thing as a confirmed cause.
- Moving straight to solving because pausing feels unhelpful or slow. Urgency is sometimes genuine, but it's worth checking whether it actually is before letting it skip this step.
- Assuming a presenting problem is illegitimate just because it isn't yet the full picture. The concern is real, even when the stated cause turns out to be wrong.
- Confusing "I've spotted a symptom" with "I now know the real problem." Recognizing the gap is the first step in this process, not the diagnosis itself.
Key Takeaways
- A presenting problem, what you're told or asked to fix, is often a symptom, not the actual underlying cause.
- Solutions that arrive bundled with the problem statement should be treated as unverified theories, not confirmed diagnoses.
- The discipline this lesson teaches is pausing before solving, not yet tracing the cause or framing the right question, those come next.
- Recognizing you're looking at a symptom is the first step in this section's process, not the last.