---
title: "Problem Solving Examples in Real Life: 12 Worked Examples"
description: "12 problem solving examples from real life for students, solved step by step (define, break down, try, check, improve), with 3 Python models and output."
slug: problem-solving-examples-in-real-life
canonical: https://learn.modernagecoders.com/blog/problem-solving-examples-in-real-life/
date: 2026-11-15
dateModified: 2026-11-15
category: "Problem Solving"
tags: ["Problem Solving", "Thinking Skills", "Students", "Python", "Real Life"]
keywords: ["problem solving examples in real life", "problem solving examples for students", "real life problem solving examples", "examples of problem solving skills", "problem solving steps with examples", "everyday problem solving"]
readTime: "17 min read"
author: "Modern Age Coders Team"
---
# Problem Solving Examples in Real Life: 12 Problems, Solved Step by Step

> Everyday problems students actually meet, each solved with the same five steps and tied to the thinking skill it trains. Three come with a Python model you can run.

![Problem solving examples in real life: a bus stop, a phone, a timetable and a plant, each with a short label for the step that solved it](/images/blog/problem-solving-examples-in-real-life/00-hero.png)

*By Modern Age Coders Team · 2026-11-15 · 17 min read*

**Quick answer:** Real-life problem solving means solving everyday problems on purpose: define the problem and what a fix looks like, break it down, try something small, check whether it worked, and improve. This post works through 12 examples students meet, from missing the school bus and a full phone to exam planning and sharing chores, each linked to a thinking skill such as decomposition, testing one change at a time or prioritising by need. Three include a short Python model with real output.

Problem solving in real life means taking an everyday problem, such as always missing the bus, a phone that is full or too many exams at once, and solving it on purpose instead of hoping. Every example below follows the same five steps: **define** the problem and what a fix looks like, **break it down**, **try** something small, **check** whether it worked, and **improve**. Each one also names the thinking skill it practises, and three of them come with a short Python model and its real output.

These twelve problems are the kind students meet at home, at school and online. Read them as worked examples: cover the steps, try the problem yourself, then compare. If you want the method itself explained in depth, with a coding and a maths problem, start with [how to improve problem solving skills](/blog/how-to-improve-problem-solving-skills).

## The 12 examples at a glance

| # | Real-life problem | Thinking skill |
| --- | --- | --- |
| 1 | Late for the school bus every morning (with Python model) | Decomposition: measure each part |
| 2 | The Wi-Fi keeps dropping | Change one thing at a time |
| 3 | Lost keys | Search in order of likelihood |
| 4 | Sharing chores fairly | Turning a word into a rule |
| 5 | Five exams, two weeks (with Python model) | Prioritising by need |
| 6 | A silent group-project teammate | Facts versus assumptions |
| 7 | Finishing a long book before term | Rates and working backwards |
| 8 | Phone storage is full (with Python model) | Biggest cause first |
| 9 | Choosing the fastest route to school | Measuring instead of guessing |
| 10 | A plant that keeps dying | Experiments and evidence |
| 11 | Scaling a recipe from 4 to 10 people | Proportional reasoning |
| 12 | Packing a bag under a weight limit | Trade-offs under a constraint |

![Twelve everyday problems arranged around the five steps of problem solving, each labelled with the thinking skill it practises, such as decomposition, testing one change at a time and prioritising by need](/images/blog/problem-solving-examples-in-real-life/01-twelve-problems.png)

*Twelve ordinary problems, one method, a different thinking skill in each.*

## Problems at home

### 1. Late for the school bus every morning

Aarav wakes at 6:30, the bus leaves at 7:25, and he misses it about twice a week. His parents say "just hurry up", which is not a plan.

- **Define:** arrive at the stop before 7:25 with a few minutes to spare, every day.
- **Break down:** the morning is six separate steps: snooze, bathroom, dressing, breakfast, finding things, walking. Time each one for a week.
- **Try:** add up the averages. The model below shows he reaches the stop at 7:34: nine minutes late on an average day.
- **Check:** the biggest single surprise is 11 minutes spent finding shoes, bag and ID card. Packing the night before gets him there at exactly 7:25, which is still too tight: zero spare minutes means any slow day is a late day.
- **Improve:** drop the snooze as well. Now he arrives at 7:16 with nine minutes to spare. The note to keep: a plan with no margin is not finished.

**Thinking skill: decomposition.** "The morning is too slow" cannot be fixed. "Finding things takes 11 minutes" can.

**school_bus.py**

```python
# Late for the school bus: model the morning, find where the time goes.
wake_up = 6 * 60 + 30          # 6:30 in minutes after midnight
bus_leaves = 7 * 60 + 25       # 7:25

steps = [                      # measured for one week, average minutes
    ("snooze", 9),
    ("bathroom", 15),
    ("get dressed", 8),
    ("breakfast", 14),
    ("find shoes, bag, ID card", 11),
    ("walk to the stop", 7),
]

def clock(minutes):
    return f"{minutes // 60}:{minutes % 60:02d}"

t = wake_up
for name, mins in steps:
    t += mins
    print(f"{name:<26} {mins:>3} min   done at {clock(t)}")
print("Arrive at stop:", clock(t), "| bus leaves:", clock(bus_leaves),
      "| spare minutes:", bus_leaves - t)

# Improve: pack the bag the night before, cut the search step to 2 minutes
steps[4] = ("find shoes, bag, ID card", 2)
arrive = wake_up + sum(m for _, m in steps)
print("After packing the night before, arrive at", clock(arrive),
      "| spare minutes:", bus_leaves - arrive)

# Check again: zero spare minutes means one slow day makes you late. Improve once more.
steps[0] = ("snooze", 0)
arrive = wake_up + sum(m for _, m in steps)
print("And with no snooze, arrive at", clock(arrive),
      "| spare minutes:", bus_leaves - arrive)
```

**Output**

```plaintext
snooze                       9 min   done at 6:39
bathroom                    15 min   done at 6:54
get dressed                  8 min   done at 7:02
breakfast                   14 min   done at 7:16
find shoes, bag, ID card    11 min   done at 7:27
walk to the stop             7 min   done at 7:34
Arrive at stop: 7:34 | bus leaves: 7:25 | spare minutes: -9
After packing the night before, arrive at 7:25 | spare minutes: 0
And with no snooze, arrive at 7:16 | spare minutes: 9
```

![Two timelines of a school morning: the first ends at 7:34, nine minutes after the 7:25 bus, with 11 minutes spent finding things; the second, with the bag packed the night before and no snooze, reaches the stop at 7:16](/images/blog/problem-solving-examples-in-real-life/02-morning-timeline.png)

*Same morning, two small changes, nine minutes to spare.*

### 2. The Wi-Fi keeps dropping

The internet cuts out during online classes. The family has restarted the router several times and moved it twice, all on the same evening, so nobody knows what helped.

- **Define:** the connection stays up for a whole evening on the device that matters.
- **Break down:** is it one device or all of them? One room or every room? One time of day or always?
- **Try:** test one question at a time. The phone in the same room stays connected, so the router is not dead. The laptop drops even next to the router.
- **Check:** the problem follows the laptop, not the room. Updating the laptop's network driver and forgetting and re-joining the network fixes it for three evenings in a row.
- **Improve:** next time, change one thing, then wait and see. Changing three things at once tells you nothing about which one worked.

**Thinking skill: change one thing at a time.** This is the same habit programmers use to find a bug, and scientists use to run a fair test.

### 3. Lost keys

Keys are missing ten minutes before leaving. The usual approach is to look everywhere at once, quickly, which means looking nowhere properly.

- **Define:** find the keys, and stop it happening again.
- **Break down:** where were they last definitely seen? Where have you been since? Which places are most likely?
- **Try:** retrace the route in order: front door, coat pocket, school bag, kitchen counter. Search each place properly once, then cross it off.
- **Check:** found in the coat worn yesterday. Checked in order, it took four minutes.
- **Improve:** a hook by the door. Most repeated problems are better solved by changing the system than by searching faster.

**Thinking skill: searching in order of likelihood.** A methodical search that checks each place once beats a frantic one that checks some places five times and others never.

### 4. Sharing chores fairly

Three siblings argue every weekend about chores. Each one is sure they do the most.

- **Define:** fair means each person does about the same amount of effort each week, not the same number of jobs.
- **Break down:** list every chore and give it points for effort: dishes 3, bins 1, vacuuming 4, laundry 3, watering plants 1.
- **Try:** share them so each sibling gets 4 points, and swap jobs each week so nobody is stuck with the worst one.
- **Check:** after two weeks, ask everyone: does it feel fair? The points can be adjusted, but the argument is now about numbers, not feelings.
- **Improve:** if one chore keeps causing trouble, give it more points instead of reopening the whole system.

**Thinking skill: turning a word into a rule.** "Fair" means different things to different people until someone defines it. Once it is a rule, it can be checked.

## Problems at school

### 5. Five exams, two weeks

Meera has five exams and about 30 hours of study time. She keeps revising the subjects she enjoys, because they feel productive.

- **Define:** share the 30 hours according to need, not enjoyment.
- **Break down:** for each subject, do one past paper and rate confidence out of 10. Need is 10 minus confidence.
- **Try:** share the hours in proportion to need. The model below does the arithmetic.
- **Check:** maths, her weakest subject, gets 10 hours and computer, her strongest, gets 2. The plan adds up to exactly 30, which is the first thing to check about any plan built from rounded numbers.
- **Improve:** after a week, do another past paper and re-rate. The plan should change as confidence changes.

**Thinking skill: prioritising by need.** Effort feels good when it goes to things you already know. It works when it goes to things you do not.

**study_plan.py**

```python
# Five exams, 30 study hours: share the hours by need, not by mood.
hours_available = 30
subjects = {          # confidence out of 10 (self-rated after a past paper)
    "Maths": 4,
    "Science": 6,
    "English": 8,
    "History": 5,
    "Computer": 9,
}
need = {s: 10 - c for s, c in subjects.items()}     # lower confidence, more need
total_need = sum(need.values())

plan = {s: round(hours_available * n / total_need) for s, n in need.items()}
for s in sorted(plan, key=plan.get, reverse=True):
    print(f"{s:<9} confidence {subjects[s]}/10  ->  {plan[s]} hours")
print("Total planned:", sum(plan.values()), "of", hours_available)
```

**Output**

```plaintext
Maths     confidence 4/10  ->  10 hours
History   confidence 5/10  ->  8 hours
Science   confidence 6/10  ->  7 hours
English   confidence 8/10  ->  3 hours
Computer  confidence 9/10  ->  2 hours
Total planned: 30 of 30
```

### 6. A silent teammate on a group project

Four students share a science project. One has not replied for five days, and the group chat is starting to turn unkind.

- **Define:** the project is finished on time, and everyone knows what they are responsible for.
- **Break down:** separate the facts (no reply for five days, their section is not started) from the guesses (they do not care, they are lazy).
- **Try:** one private message that asks a question instead of blaming: is everything all right, and can you still do the results section by Thursday?
- **Check:** they reply that they have been ill. The section is split so someone else does the graphs.
- **Improve:** next time, agree who does what and by when at the very first meeting, written down.

**Thinking skill: separating facts from assumptions.** Many people problems get worse because the guess is treated as a fact.

### 7. Finishing a long book before term starts

A 420-page set novel must be read before school starts in 21 days, and a family holiday takes up 5 of them.

- **Define:** the book is finished by day 21, with notes on each chapter.
- **Break down:** pages, days actually available, a daily target.
- **Try:** 21 days minus 5 is 16 reading days. 420 divided by 16 is 26.25, so 27 pages a day.
- **Check:** 27 pages a day for 16 days is 432, which covers 420. Each evening, check whether you are ahead or behind.
- **Improve:** if you fall behind, recalculate from today. A fixed plan that is already broken is less useful than a new honest one.

**Thinking skill: rates and working backwards.** The total is scary; the daily number is not.

## Problems with technology

### 8. Phone storage is full

The phone says storage is full and will not update. The first idea is to delete a few apps one by one, which takes ages and frees almost nothing.

- **Define:** free enough space for the update, without losing anything that matters.
- **Break down:** read the phone's storage screen and list each category with its size.
- **Try:** sort the list from biggest to smallest and add a running total. The model below does this.
- **Check:** videos alone are over 41% of the used space, and the top two categories are 60%. Deleting small apps was never going to work.
- **Improve:** move old videos to a computer or cloud storage the family already uses, and set the chat app to stop saving every video automatically.

**Thinking skill: biggest cause first.** When a few causes make most of the problem, sorting by size tells you where to start.

**phone_storage.py**

```python
# Phone storage full: find the few things taking most of the space.
items = {             # sizes in GB, read from the phone's storage screen
    "Videos": 21.4,
    "WhatsApp media": 9.8,
    "Photos": 7.5,
    "Games": 6.2,
    "Music downloads": 3.1,
    "Other apps": 2.6,
    "Documents": 0.9,
    "Notes": 0.2,
}
total = sum(items.values())
running = 0
for name, gb in sorted(items.items(), key=lambda kv: kv[1], reverse=True):
    running += gb
    print(f"{name:<16} {gb:>5.1f} GB   running total {running / total:6.1%}")
print(f"Total: {total:.1f} GB")
```

**Output**

```plaintext
Videos            21.4 GB   running total  41.4%
WhatsApp media     9.8 GB   running total  60.3%
Photos             7.5 GB   running total  74.9%
Games              6.2 GB   running total  86.8%
Music downloads    3.1 GB   running total  92.8%
Other apps         2.6 GB   running total  97.9%
Documents          0.9 GB   running total  99.6%
Notes              0.2 GB   running total 100.0%
Total: 51.7 GB
```

![Bar chart of phone storage from the Python model: videos 21.4 GB, WhatsApp media 9.8 GB, photos 7.5 GB, games 6.2 GB, and four small categories; the top two make up 60 percent of the space used](/images/blog/problem-solving-examples-in-real-life/03-storage-bars.png)

*Sorted from biggest to smallest, the answer is obvious. Unsorted, it hid.*

### 9. Choosing the fastest route to school

Two routes to school. Everyone in the family has a favourite and an opinion.

- **Define:** find the route that gets there fastest on a normal school morning, on average.
- **Break down:** the two routes, the time of day, and the number of trips needed to be fair.
- **Try:** time both routes on five mornings each, at the real leaving time.
- **Check:** compare the averages and also the worst day. A route that is a minute faster on average but sometimes 15 minutes slower may not be the better choice.
- **Improve:** repeat the test when something changes, such as roadworks or a new bus timetable.

**Thinking skill: measuring instead of guessing.** Opinions about routes are memories of unusual days. Measurements are about normal ones. Maps apps do something similar at huge scale; our post on [how maps find the fastest route](/blog/dijkstras-algorithm-fastest-route) shows the algorithm.

## Problems with planning and measuring

### 10. A plant that keeps dying

A basil plant on the windowsill has died twice. Was it too much water, too little light, or the pot?

- **Define:** keep one plant healthy for six weeks, and know why it is healthy.
- **Break down:** possible causes: water, light, the pot's drainage, temperature.
- **Try:** check the cheapest thing first: the pot has no drainage hole, so the roots sit in water.
- **Check:** re-pot into a pot with a hole, change nothing else, and note the leaves each week.
- **Improve:** if it still struggles, change the next single thing, such as moving it to a brighter window.

**Thinking skill: experiments and evidence.** Changing one factor at a time is how you learn which one mattered.

### 11. Scaling a recipe from 4 to 10 people

A recipe serves 4 and needs 300 g of flour, 2 eggs and 1 teaspoon of baking powder. Ten people are coming.

- **Define:** the same recipe, scaled to 10 servings.
- **Break down:** find the scale factor, multiply each ingredient, and then deal with anything that cannot be split.
- **Try:** 10 divided by 4 is 2.5. Flour 300 &times; 2.5 = 750 g; eggs 2 &times; 2.5 = 5; baking powder 2.5 teaspoons.
- **Check:** estimate: about two and a half times the original amount of everything, and 750 g is about two and a half times 300 g. Does the bigger amount still fit in one tin? Will it bake in the same time?
- **Improve:** use two tins of the original size instead of one giant one, so the baking time stays the same.

**Thinking skill: proportional reasoning.** Multiplying is the easy part; noticing what does not scale, like baking time, is the real problem solving.

### 12. Packing a bag under a weight limit

A school trip allows one bag of up to 10 kg, and the first attempt weighs 13 kg.

- **Define:** everything essential is packed, and the bag is under 10 kg.
- **Break down:** sort items into must-have, nice-to-have, and can-borrow-there.
- **Try:** weigh the bag after taking out the nice-to-haves first.
- **Check:** 11.2 kg is still over, so look at the heaviest items, not the most numerous ones. Two thick jumpers and a hardback book account for most of the excess.
- **Improve:** swap one jumper for a light fleece and the book for a paperback. 9.6 kg. Keep the list for the next trip.

**Thinking skill: trade-offs under a constraint.** When you cannot have everything, decide what matters most, then check against the limit, not against a feeling.

## How to practise with these examples

1. Pick one example and read only the first paragraph.
2. Write your own define, break down, try, check and improve before reading ours.
3. Compare. Where did you differ, and which version would work better?
4. Find a problem from your own week that uses the same thinking skill, and solve it the same way.
5. For the three Python models, change the numbers to your own and run them. Then add one improvement of your own.

These work well for students from about 10 upwards. Younger children can do the same steps out loud with a parent, using problems like tidying a room or sharing a snack fairly. Many of the same skills appear in our [computational thinking examples](/blog/computational-thinking-examples), which name them the way schools and computer science courses do.

## Why these skills matter more when AI can write code

Look back at the twelve examples. In almost every one, the hard part was not the calculation. It was defining the problem (what does fair mean?), choosing what to measure (time each step of the morning), or checking an answer that looked fine (zero spare minutes is not a fix). Those are the parts an AI assistant cannot do for you, because they depend on your situation and your judgement.

AI tools can now write models like the three above in seconds, and that is a real help. GitHub's documentation for its Copilot coding assistant is clear about what remains: it says Copilot "may generate code that appears to be valid but may not actually be semantically or syntactically correct", and that "Users are responsible for reviewing and validating suggestions before accepting them" ([GitHub Docs](https://docs.github.com/en/copilot/responsible-use/inline-suggestions)). The study plan model is a good test: a person who knows the hours must add up to 30 will notice if a generated version does not.

> **AI tools and age limits**

> Most AI chat tools require users to be at least 13. ChatGPT's terms ask for a parent's or guardian's permission for under-18s, and Claude is for adults (18 and over) only. Younger students can practise every example on this page without any AI tool at all; the thinking is the part worth practising.

## How we teach it

The principles on our [how we teach](/how-we-teach) page are the five steps in practice: students explain their thinking, we trace code line by line until the student can predict every step, learners derive a rule before they see it written down, we show the same problem three ways, and mistakes are data, not failures. They run through our [problem solving course for kids](/courses/problem-solving-and-computational-thinking-for-kids), the [Python course for teens](/courses/python-complete-masterclass-teens), where real-life models like the three above are a regular exercise, and our page on [how we teach thinking](/we-teach-you-how-to-think). Classes are one to one or in groups of 15 to 20, and the first class is free.

[Book a free class](/book-demo) [Book a priority demo](/book-demo)

## Frequently asked questions

**What are some examples of problem solving in real life?**

Being late for the bus every morning, a Wi-Fi connection that keeps dropping, lost keys, too many exams at once, sharing chores fairly, a full phone, a plant that keeps dying, a silent teammate, scaling a recipe, packing under a weight limit, reading a long book on time and choosing the fastest route. Each is solved step by step in this post.

**What are problem solving examples for students?**

Planning revision for several exams, finishing a set book before term, working with a teammate who has gone quiet, and packing for a school trip are four student examples in this post. Each one uses the same steps: define, break down, try, check, improve.

**What are the 5 steps of problem solving?**

Define the problem and what a fix looks like, break it into parts, try something small, check whether it worked against your definition, and improve. The improve step often leads back to define, so it is a loop rather than a straight line.

**What is a good example of problem solving skills for an interview or essay?**

Choose a real problem you solved, then describe it in the five steps: what the problem was and how you defined success, how you broke it down, what you tried first, how you checked it, and what you changed. The checking and improving steps are what make an example convincing.

**How do you teach problem solving to kids with real-life examples?**

Use problems from their own day, such as tidying a room, sharing a snack or being late for school. Ask them to say what done looks like before they start, try one small thing, and check it. Praise the checking, not just the answer.

**How does coding help with real-life problem solving?**

Coding forces each step to be explicit. A program cannot run on a vague goal, so you must define it; it fails on the cases you forgot, so you learn to check. The three Python models in this post show everyday problems written as code.

**Can AI solve real-life problems for students?**

AI can help with parts, such as doing arithmetic or drafting a plan, but it cannot know your situation, decide what matters to you or check that the result fits your life. Those are the steps students still need to practise, and most AI chat tools have a minimum age of 13 anyway.

---

*Source: https://learn.modernagecoders.com/blog/problem-solving-examples-in-real-life/*
