Problem Solving Examples from Work, School and Daily Life

A problem solving example is any situation where someone notices a gap between what is happening and what should happen, works out the real cause, picks a fix and checks that it worked. A team that cuts missed deadlines by moving its weekly review from Friday to Monday, or a student who stops failing quizzes by testing themselves instead of rereading, are both problem solving examples.

Below are 14 worked problem solving examples from work, school and everyday life. Each one is broken into the same four moves (define, generate, choose, test) and ends with a note on why it worked. After that you'll find how to turn an example into an interview answer, four practice problems with a time box and model answers, and a short section on how to use all of this.

What Counts as a Problem Solving Example

Not every fix is a good example. The ones worth learning from share four moves:

1. Define. State the problem as a gap you can observe: "Orders ship two days late," not "the warehouse is a mess."
2. Generate. List more than one possible cause and more than one possible fix before committing. One option is a guess, not a choice.
3. Choose. Pick a fix with a reason: cheapest to test, biggest effect, fewest side effects.
4. Test. Try it, watch the result and keep or change course.

When an example skips a step, it usually shows. Skipping "define" means solving the wrong problem. Skipping "generate" means the first idea wins by default. Skipping "test" means you never learn whether the fix did anything. Each example below names all four moves so you can see the pattern, then reuse it.

Problem Solving Examples at Work

1. Late weekly reports. A manager notices the team's weekly status report arrives late most weeks.

• Define: The report is due Friday at 3 p.m. and usually arrives Monday.
• Generate: Too much to compile; the data comes from three people who send it late; Friday afternoon is already crowded; nobody owns the deadline.
• Choose: The manager asks and learns two of the three inputs arrive Friday at noon. The real bottleneck is upstream, so moving the inputs' deadline to Thursday is the cheapest fix to try.
• Test: Inputs move to Thursday for a month. The report lands on time three weeks out of four.
• Why it worked: The manager asked about the cause before fixing the symptom. Pushing the report-writer to "work faster" would have changed nothing.

2. A spike in customer complaints. Support tickets about "can't log in" double in a week.

• Define: Login complaints went from about 20 to about 40 a week, starting on a specific day.
• Generate: A code change that week, a password-reset email landing in spam, one large customer onboarding many new users, a browser update.
• Choose: The team lines up the start date against recent changes and finds that a new password rule went live that morning.
• Test: They add a clear message explaining the rule on the sign-up screen. Complaints fall back to the old level within two weeks.
• Why it worked: Matching the timing of the problem to the timing of each candidate cause eliminated most options in minutes.

3. A meeting that never ends on time. A recurring one-hour meeting runs 20 minutes over every week.

• Define: The overrun comes from the last agenda item, which is always "open discussion."
• Generate: Shorten the agenda, add a timekeeper, move open discussion to a written thread, end the meeting at a hard stop.
• Choose: A written thread costs nothing and keeps the discussion, so the team tries it first.
• Test: After three weeks the meeting ends on time and the thread gets more contributions than the live slot did.
• Why it worked: The fix kept what people valued (the discussion) and removed only what caused the problem (doing it live at the end).

4. Budget cut without a layoff. A small team is told to cut 10% of its spending for the quarter.

• Define: Find a fixed amount of savings without losing people or a key project.
• Generate: List every line item, from software licenses and travel to contractors and conference tickets.
• Choose: Unused software seats and one conference trip cover most of the gap with no effect on output.
• Test: The team reviews spending monthly. The last bit comes from renegotiating one contract.
• Why it worked: Listing every option first, instead of reaching for the biggest line, surfaced cuts that nobody would miss.

5. A new hire who keeps missing the point. A new team member's work is consistently off-target.

• Define: Three assignments came back solving a different problem from the one intended.
• Generate: Unclear briefs, a skills gap, reluctance to ask questions, different assumptions about the audience.
• Choose: Rereading the briefs shows each one described the task but not the goal. That's the cheapest cause to rule out.
• Test: The next briefs start with one line on who the work is for and what "done" looks like. The work lands on target.
• Why it worked: The lead checked their own side of the problem before assuming it was the new hire's.

Problem Solving Examples at School

6. Failing quizzes despite studying. A student studies for hours and still scores poorly.

• Define: Scores are low on questions that ask students to apply an idea, but fine on definitions.
• Generate: Not enough time, the wrong study method, test anxiety, missing a foundational topic.
• Choose: The student realizes their studying is all rereading notes, which practices recognizing an idea, not using it.
• Test: They switch to answering practice questions with the notes closed. Application scores rise on the next two quizzes.
• Why it worked: The student compared which questions they missed with how they were studying, and the mismatch pointed to the cause.

7. A group project with one person doing everything. One member of a four-person group is doing most of the work.

• Define: Tasks are vague ("work on the slides"), so nobody else knows what's theirs.
• Generate: Complain to the teacher, split tasks by section, set internal deadlines, rotate a coordinator.
• Choose: Splitting by section with named owners and dates is fast and fair.
• Test: A shared list goes up the same day. Every section is drafted by the internal deadline.
• Why it worked: The real problem was unclear ownership, not laziness, and the fix addressed exactly that.

8. Running out of time on exams. A student leaves the last questions blank on every timed test.

• Define: They spend too long on hard questions early and never reach easier points at the end.
• Generate: Practice speed, skip and return, budget minutes per question, start from the back.
• Choose: A simple rule: any question taking more than double its share of time gets marked and skipped.
• Test: On the next exam they reach every question and return to two of the skipped ones.
• Why it worked: The rule removed a judgment call made under stress, which is when judgment is worst.

Problem Solving Examples in Real Life

9. The car that won't start. It's a cold morning and the engine cranks but won't catch.

• Define: The engine turns over, so the problem is not a fully dead battery.
• Generate: Fuel, the fuel pump, the spark system, a security-key fault.
• Choose: Start with the cheapest checks. The gauge shows fuel, and the usual fuel pump hum is missing when the key turns.
• Test: The mechanic checks the pump first, and it's the fault.
• Why it worked: Testing in order of cost eliminated causes quickly. The convergent thinking examples post walks through this one step by step.

10. A neighbor dispute over parking. A neighbor keeps parking across your driveway.

• Define: It happens on weekday evenings, when their own spot is taken by visitors to another house.
• Generate: Leave a note, call the city, talk face to face, paint a line, offer a swap.
• Choose: A short friendly conversation is cheap and keeps the relationship.
• Test: The neighbor didn't know the curb was part of your driveway. It stops.
• Why it worked: Defining when it happened suggested a cause that wasn't bad faith, which changed which fix made sense.

11. A monthly budget that never balances. Money runs out a week before payday every month.

• Define: Spending is unclear, so the gap can't be located.
• Generate: Cut eating out, cancel subscriptions, change the pay date, track every purchase for a month.
• Choose: Track first, because every other option is a guess without the data.
• Test: One month of tracking shows small food delivery orders add up to more than any single bill. Capping those closes most of the gap.
• Why it worked: Measuring before cutting pointed straight at the real leak, which wasn't the one anyone expected.

12. A toddler who won't go to bed. Bedtime takes 90 minutes every night.

• Define: The fight starts at the moment screens go off.
• Generate: Earlier bedtime, a reward chart, no screens after dinner, a fixed routine with a visual checklist.
• Choose: Move screens off an hour earlier and replace that slot with a predictable three-step routine.
• Test: After a week, bedtime takes 25 minutes on most nights.
• Why it worked: Pinpointing the trigger (screens going off) made the fix specific instead of a general crackdown.

13. A leaking kitchen sink. A puddle appears under the sink every few days.

• Define: The cabinet floor is wet, but only after the dishwasher runs.
• Generate: A loose drain joint, a cracked pipe, the dishwasher hose, a failing tap seal.
• Choose: The timing points to the dishwasher drain hose, so check that connection first.
• Test: The hose clamp is loose. Tightening it ends the leak.
• Why it worked: Noticing when the leak happened eliminated three of the four candidates before any tools came out.

14. A commute that keeps getting worse. A 30-minute drive now takes 50.

• Define: The delay is concentrated at one junction between 8:10 and 8:30.
• Generate: Leave earlier, take a different route, switch to a train, shift work hours.
• Choose: Leaving 15 minutes earlier costs the least and avoids the worst window.
• Test: The drive drops back to about 32 minutes.
• Why it worked: Locating the delay in time and place turned a vague complaint into a narrow problem with an obvious cheap fix.

Problem Solving Examples for Interviews

Interviewers ask "Tell me about a time you solved a problem" to see the same four moves. The standard structure is STAR: Situation, Task, Action, Result. Here is example 2, the login complaints, rewritten as an answer.

• Situation: "Login complaints doubled in a single week, and our support team was falling behind."
• Task: "I was asked to find out why and stop it before it hurt renewals."
• Action: "I lined up the date the complaints started against everything we had changed that week, which pointed to a new password rule. I proposed a one-line message on the sign-up screen as the quickest fix to test."
• Result: "Complaints returned to normal within two weeks, and we added a checklist so rule changes now ship with user-facing copy."

What makes this strong:

• It names a measurable problem, not a vague one.
• It shows how the cause was found, not just what the fix was.
• The result is specific, and it includes what changed afterward so the problem doesn't come back.

To build your own, pick a real problem from your work or studies, then write one sentence for each STAR line. If you can't fill in the Action line with how you found the cause, choose a different example. That line is the one interviewers are listening for.

Problem Solving Practice Problems

Try each one with a timer. Write down your four moves before reading the model answer. There's no single right answer; the model shows one good path.

Practice 1: The empty gym class (10 minutes). A community center's 7 a.m. fitness class dropped from 15 regulars to 4 over two months. Define the problem, list at least four possible causes, choose what to check first and say how you'd test a fix.

Model answer: Define it as "attendance fell by about two thirds since a specific date." Causes: a new instructor, a schedule change, a price rise, a new competing gym, the season getting darker and colder. Check first: what changed around the start date, by asking three former regulars. If the answer is the new instructor's style, test by running the old format two days a week for a month and counting attendance.

Practice 2: The shared kitchen (5 minutes). In an office kitchen, dirty dishes pile up by Wednesday every week. List five fixes and pick one to test first, with a reason.

Model answer: Fixes: a rotating cleaning rota, fewer mugs, a dishwasher schedule, a sign, assigned mugs. A good first test is removing half the shared mugs. It costs nothing, and if fewer mugs exist, fewer can pile up. Check on Wednesday for two weeks.

Practice 3: The lost customer (10 minutes). A small bakery's biggest wholesale customer, a café, has cut its order in half without explanation. Define the problem as a gap, list three causes and plan one conversation.

Model answer: Define it as "weekly order dropped from 40 to 20 units, starting three weeks ago." Causes: a price issue, a quality issue with one batch, the café's own sales falling. Plan: call the owner and ask what changed on their side, before offering a discount. A discount fixes only one of the three causes.

Practice 4: The double-fed dog (5 minutes). A family keeps forgetting whether the dog got its evening meal, so it sometimes eats twice and sometimes not at all. Design a fix and say how you'd know it worked.

Model answer: The cause is that nobody can see whether the meal happened. Fix: a paper chart on the fridge with a box for each evening, ticked when the bowl is filled. It worked if, after two weeks, every box has exactly one tick.

For a guided version of these steps, the Creative Problem Solving drill walks you through a challenge in stages: clarify it by reframing it three different ways, ideate a list of bold solution starters, then develop your favorites with pros and cons into a plan you can act on. You can run it untimed or set a 2, 5 or 10 minute timer.

How to Use These Problem Solving Examples

• Read one, then do one. Pick an example close to your own life, then apply the same four moves to a real problem you have this week.
• Write the define step as a gap. "X is happening; Y should be happening." If you can't state it that way, you aren't ready to generate fixes.
• Generate before you choose. Force yourself to list at least four causes or fixes, even if the first seems obvious. Timed idea generation in the Divergent Thinking drill builds this habit.
• Test the cheapest option first. Most examples above found the cause with a question or a look, not an expensive change.
• Think one step past the fix. Ask what the solution might cause next. The Second Order Consequences drill trains exactly that.
• Keep a log. A one-line record of each problem, cause and fix becomes your own example bank for interviews.

For the underlying skills and how to improve them, read problem solving skills. For a full method with idea generation built in, see creative problem solving, and for famous breakthroughs that followed the same pattern, see these creative problem solving examples. If your examples keep stalling at the define step, problem reframing covers ways to restate a problem so new fixes appear.

Frequently Asked Questions

What is a good example of problem solving? A manager whose weekly report keeps arriving late asks why, finds that two inputs come in Friday at noon, and moves their deadline to Thursday. It's a good example because the cause was found before a fix was chosen, and the result was checked over a month.

What are some problem solving examples in real life? Finding a sink leak by noticing it only happens after the dishwasher runs, tracking spending for a month to find where the budget leaks, shortening bedtime by changing when screens go off, and beating a bad commute by leaving 15 minutes earlier. Each one locates the cause before choosing a fix.

How do I answer "Give an example of problem solving" in an interview? Use the STAR structure: Situation, Task, Action, Result. Spend most of your answer on the Action, especially how you found the cause, and end with a specific result plus what changed afterward so the problem didn't return.

What are the four steps of problem solving? A common way to break it down is define, generate, choose and test. Define the problem as an observable gap, generate several causes and fixes, choose one with a clear reason and test whether it worked. Many models use different names, but most follow this shape.

How can I practice problem solving? Take one small real problem a week and write down all four steps, with a 5 to 10 minute timer for each practice round. Short drills that train idea generation and thinking through consequences help with the generate and choose steps.

What are problem solving skills examples? Defining a problem precisely, asking questions to find the cause, listing alternatives, weighing trade-offs, testing a fix on a small scale and checking results. The examples on this page show each skill in a concrete situation.

---

Ready to train your creativity? Try science-backed exercises that measure and improve your creative thinking. Start a Free Exercise