“Strong problem-solving skills” appears in countless job postings. At work, problems range from small (a report that does not balance) to large (a process that keeps causing customer complaints). Employers value people who can approach problems calmly and systematically instead of guessing or immediately escalating everything.
You do not need a complicated method. A simple, repeatable framework helps you think clearly, explain your reasoning and get better results.
The six-step framework
| Step | Question to ask |
|---|---|
| 1. Define | What exactly is the problem? |
| 2. Understand | What is causing it? |
| 3. Options | What could we do about it? |
| 4. Decide | Which option is best, and why? |
| 5. Act | How will we implement it? |
| 6. Review | Did it work, and what did we learn? |
Step 1: Define the problem precisely
Vague problems lead to vague solutions. Turn “The report is wrong” into a specific statement:
Defining a problem
“The October shipment report shows 412 deliveries, but the carrier’s invoice lists 428. The difference of 16 deliveries affects the invoice approval due Friday.”
Include what is happening, where, since when, how often and why it matters.
Step 2: Understand the cause
Gather facts before jumping to solutions:
- Look at the data or examples.
- Ask people involved what they see.
- Check what changed recently.
- Compare with cases where things worked.
A simple technique is asking “Why?” several times (often called “5 Whys”):
- Why is the total different? Some deliveries are missing from our report.
- Why are they missing? They were entered in a different sheet.
- Why? A new colleague used an old template.
- Why? The old template was still in the shared folder.
- Why? Nobody archived it when the new one was created.
The root cause is the outdated template, not the colleague. Our guide to organizing cloud folders shows how to prevent this kind of problem.
Step 3: Generate options
List several possible actions before choosing:
- Quick fixes (merge the missing entries now).
- Root-cause fixes (archive old templates, add a “current version” note).
- Process improvements (a checklist for new staff).
Involve others when the problem affects them; they often have useful ideas.
Step 4: Decide
Compare options by:
- Impact: how well does it solve the problem?
- Effort and cost.
- Risk: what could go wrong?
- Time: how quickly can it be done?
A simple table helps:
| Option | Impact | Effort | Risk |
|---|---|---|---|
| Merge entries now | Fixes this month | Low | Low |
| Archive old templates | Prevents repeats | Low | Low |
| New-starter checklist | Prevents similar issues | Medium | Low |
Often the best answer combines a quick fix with a root-cause fix.
Step 5: Act
- Agree who does what and by when.
- Communicate the plan to people affected.
- If you need approval, present the problem, cause, options and your recommendation together.
Presenting a solution to your manager
“I found why the October totals didn’t match: 16 deliveries were logged in an old template. I’ve merged them, and the totals now match the invoice. To prevent it, I’d like to move old templates to an archive folder and add a ‘current version’ note. Is that okay?”
This approach shows initiative while respecting decisions that belong to your manager.
Step 6: Review
After implementing, check whether it worked. Did the next report match? Did the issue come back? Note what you learned. Small reviews like this build expertise over time and make great examples for interviews and reviews.
Problem-solving habits that impress managers
- Bring options, not only problems. Even one suggested solution shows initiative.
- Separate facts from assumptions.
- Escalate early when the problem involves money, safety, privacy or customers, or when it is outside your authority.
- Document the solution so others can use it.
- Stay calm. Problems are a normal part of work.
Use this framework in interviews
Many behavioral questions ask about problem-solving. The six steps map neatly onto the STAR method: the situation and task define the problem, your actions cover understanding, options, decision and implementation, and the result covers the review.
Define the next problem in one sentence
Next time something goes wrong at work, write a one-sentence problem definition and ask “why” at least three times before proposing a fix. Then present your finding and recommendation to your manager using the template above. For mistakes you made yourself, see our guide on handling mistakes at work.