Problem-Solving Examples
Real problem-solving examples worked step by step — at work, in a team and in everyday life — each one showing the five-step process in action and the technique that cracked it. Try the approach before you reveal the solution.
The fastest way to learn problem solving is to watch the process work on a real situation. Below are four worked examples — at work, in a team, in everyday life and in an interview — each showing the five-step process and the technique that cracked it. Try to work out the approach before you reveal the solution.
Sign-ups on a website dropped 30% the week after a redesign. The team is tempted to roll the whole thing back.
Show the worked solution
Define: sign-ups fell 30% after the redesign — is the redesign the cause, or something else that week? Analyse: instead of guessing, they look at the funnel and find users now drop off on the new email-verification step; asking "why?" shows the verification email is landing in spam. Generate & decide: rather than reverting everything, they fix the email sender settings. Review: sign-ups recover to above the old level — so the redesign was fine; one step was broken. Rolling back would have thrown away a good change.
A support team is overwhelmed; tickets keep rising and customers are frustrated.
Show the worked solution
Define: ticket volume up 50% over two months. Analyse: a fishbone diagram maps causes across product, documentation, onboarding and billing; counting tickets (Pareto) shows two issues — a confusing billing screen and a missing help article — cause about 80% of them. Decide & act: they redesign the billing screen and publish the article. Review: ticket volume falls back, and the team tackles the long tail next. The lesson: fix the vital few, not everything at once.
You keep arriving late to work despite leaving "on time".
Show the worked solution
Define: late three mornings out of five. Analyse: tracking the journey shows one unreliable bus connection causes every late arrival — the root cause, not "I'm disorganised". Generate & decide: working backward from "be at my desk by 9", you find an earlier, more reliable route. Review: a week later you're on time every day. Solving the real cause beat simply trying harder.
How would you describe a problem you solved, in an interview?
Show the worked solution
Use the process as your structure: the Situation (a recurring stock-out), the Problem you defined (a forecasting gap for one product line), how you found the Cause (analysis showed promotions weren't fed into the forecast), the Action you took (added promotion data to the model), and the measurable Result (stock-outs down 60%). Clear cause-to-result reasoning is what interviewers are really listening for.
The pattern behind every example
Notice the shape they share: define the problem precisely, find the real cause instead of guessing, act on that cause, and check the result. That discipline — and the reasoning underneath it — is what the critical thinking test measures. For the full toolkit, see problem-solving techniques and the structured 8D method.
Frequently asked questions
What is an example of problem solving at work?
A team's sign-ups drop after a website change. Instead of guessing, they define the problem precisely, analyse the funnel to find where users leave, test a fix on that step, and review the result — the five-step process applied. This page works several such examples in full.
What is an everyday example of problem solving?
Your commute keeps making you late. Rather than just leaving earlier, you find the real cause (one unreliable connection), try an alternative route, and check whether it actually helps. Same process, smaller scale.
How do I describe a problem-solving example in an interview?
Use a clear structure: the situation, the problem you defined, how you found the cause, the action you took, and the measurable result. The worked examples here follow exactly that shape.