Explaining Problems & Proposing Solutions — I can explain a problem, describe what happened, and propose a next step in common situations (work, services). - Adult Literacy Intermediate

SECTION 1

Why This Skill Matters

Almost everyone needs to explain a problem out loud at some point — telling a boss about a mistake, calling a company about a broken item, or asking a landlord to fix something. These conversations can feel stressful, especially if you are frustrated. But there is a simple pattern that makes these talks easier for both you and the other person: say what is wrong, explain what happened, and suggest what to do next.

This pattern works the same way whether you are speaking in person, on the phone, or in a short message. Once you know the pattern, you can use it in many different situations. Here are some common moments where this skill comes in handy.

At Work • Telling Your Boss About a Problem

You notice something has gone wrong — a mistake, a delay, a scheduling conflict — and you need to explain it clearly and suggest a fix.

On the Phone • Calling Customer Service

You call a company because something you ordered or paid for did not go as expected, and you want a specific solution, like a refund or a replacement.

With a Landlord • Reporting a Repair Issue

Something in your home is broken, and you need to describe the problem clearly so the landlord or repair person understands what to fix.

By Email or Text • Writing a Short Message

Sometimes you explain a problem in writing instead of speaking. The same three-step pattern works just as well in a short message.

Every Day • Building Confidence

The more you practice this pattern, the easier it becomes to speak up calmly and clearly, even when a situation feels frustrating.

This lesson answers one simple question: How do you explain what went wrong, describe what happened, and suggest a next step — while staying calm and clear? Whether you are talking to a supervisor, a customer service worker, or a coworker, the answer is a simple three-step pattern that we will practice in this lesson.

SECTION 2

Core Steps for Explaining a Problem

No matter the situation — a late delivery, a broken appliance, or a mistake at work — the same three steps help you explain a problem clearly. Learning these steps well means you can handle almost any problem-reporting conversation with more confidence, and the other person is more likely to want to help you.

State the Problem First

Start with one or two short sentences that say what is wrong. Do not start with a long story. The listener needs to know what the problem is before they can understand why or how it happened.

Describe What Happened

After you state the problem, explain what happened in order, step by step. Stick to the facts you saw or know — do not guess who is to blame. This helps the listener trust you and keeps the talk focused on solving the problem.

Suggest a Next Step

End with one clear, doable suggestion instead of leaving the listener to guess what you want. Asking instead of demanding — 'Could we…?' or 'Would it be possible to…?' — invites them to work with you. A quick follow-up question, like 'What do you think?', shows you want their input too and turns your suggestion into a conversation.

💡

One Tone, Three Steps

Staying calm and professional is not a fourth step — it is the tone you keep going through all three steps above. Asking what the other person thinks is not a separate step either; it is simply part of how you offer your suggestion in Step 3. These two habits support the three-step plan; they do not add extra steps to it.

✦

KEY TAKEAWAY

Think of these three steps like a short recipe: first say what is wrong (the problem), then explain the steps that led to it (what happened), and finish with what you want to happen next (your suggestion). Just like skipping a step in a recipe can ruin the dish, skipping a step in this pattern can confuse the listener and make the conversation harder than it needs to be.

SECTION 3

The Three-Step Plan

The diagram below shows the three steps of a clear problem-solving conversation. Each step builds on the one before it: the Problem Statement tells the listener what is wrong, the What Happened part gives the facts, and the Proposed Solution moves the conversation toward a fix. The arrows show how each step leads naturally to the next.

The three-step plan shows how to move from stating the problem (Step 1) through explaining what happened (Step 2) to suggesting a next step (Step 3). The panels below show the tone and key phrases to use the whole time.

The arrows in the diagram make an important point: each step naturally leads to the next one. If you jump straight to Step 3 and suggest a solution before explaining the problem, the listener often does not have enough information to say yes. On the other hand, if you spend too long on Step 2 and never get to Step 3, you may sound like you are only complaining. A clear conversation moves through all three steps, giving roughly equal attention to each one.

SECTION 4

Useful Phrases for Each Step

Certain simple phrases help the listener know which step of the conversation you are in. Just like a sign on a door tells you what room you are entering, these phrases tell the listener whether you are stating the problem, explaining what happened, or suggesting a next step. Learning a few of these phrases makes the three-step plan much easier to use in real conversations.

Step 1: Starting the Conversation

Start with a short phrase that tells the listener a problem exists. At work, you might say, "I wanted to talk to you about an issue with…" or "I need to flag a concern regarding…" With a service company, you might say, "I'm calling because there's a problem with…" or "I'd like to report an issue with…" These openings do two things: they let the listener know something is wrong, and they help the listener get ready to listen for the details. Be as specific as you can — name the exact item, order, or service that has the problem.

Step 2: Telling What Happened

When you explain what happened, use simple order words like "first," "then," "after that," and "at that point." These words help the listener follow the events in the right order. It also helps to use phrases like "I noticed," "it looked like," or "as far as I could tell" instead of blaming someone directly. This keeps your account fair and calm, which matters a lot in workplace situations where jumping straight to blame can make things worse. Include useful details such as dates, times, amounts, and order or account numbers — these give the listener what they need to look into the problem.

Step 3: Suggesting a Next Step

When you suggest a solution, polite words like "could," "would," and "might" soften your request and invite the listener to be part of the decision. Phrases like "If we could reschedule, that would fix the problem" or "Would it be possible to issue a credit?" show that you are looking for a solution together, not making a demand. It also helps to give a short reason why your suggestion would fix the problem — this shows you have thought it through instead of just reacting.

This chart lists helpful phrases, features, and examples for each of the three steps. Notice how the example sentences get more specific from left to right, ending with a suggestion that gives the listener two choices.

SECTION 5

Using This at Work vs. With Services

The three-step plan works everywhere, but the details change a little depending on whether you are talking to a coworker or boss or a service worker. At work, you usually already know the person and share some history and goals. With a service company — a utility, a repair company, a billing office — the person you speak to often does not know you yet and may be helping many other customers too. These differences change how much detail you give, and what kind of solution you can ask for.

Dimension	Workplace Context	Service Context
Relationship	Ongoing; you share some history and goals with the listener	Usually one-time; the listener may not know you at all
Background Info Needed	Less — coworkers often already know the background; you can just name the project	More — give account numbers, order numbers, and dates, since the listener doesn't know your situation yet
Tone	Friendly and focused on solving the problem; using 'we' works well	Polite and patient; remember the person you're talking to didn't cause the problem personally
Typical Solutions Proposed	Changing a process, reassigning a task, adjusting a schedule, or getting more help	A refund, a replacement, a credit, talking to a manager, or changing the service agreement
Example Opening	"Hey Maria, I wanted to discuss the deadline for the Henderson report—there's a complication."	"Hi, I'm calling about my account, number 893-4102. I received my latest bill and there's an incorrect charge."

Key differences between workplace and service contexts for problem-solution conversations.

One important idea is what to do if the first conversation doesn't fix the problem. At work, this often means talking to a shared supervisor or bringing it up at a team meeting. With a service company, it usually means asking for a manager or filing a complaint. In both cases, treat this as another step in solving the problem, not as a fight. Saying something like "I appreciate your help so far — could I also speak with someone who might be able to help further?" keeps things calm while still moving your request forward.

💡

Cultural Sensitivity Note

Different workplaces and cultures have different habits about how directly people speak. In some places, saying a problem in plain, direct words is completely normal. In others, a softer approach ('I was wondering if we might look at…') is more common. If you're not sure which style fits, start polite and adjust based on how the other person responds.

SECTION 6

Worked Example: Reporting a Scheduling Error at Work

Let's walk through a full example of the three-step plan in a common workplace situation. Imagine you are a project coordinator who discovers that two team members have been scheduled for the same time slot for two different tasks. This will delay the project if it isn't fixed. You need to explain this to your manager, Daniela, during a short check-in.

Scenario: Double-Booked Team Members

1
Step 1 — State the Problem

Begin with a short, specific statement: "Daniela, I need to flag a scheduling conflict. Alex and Jordan are both booked for Thursday afternoon, but they've been assigned to two different tasks that each need their full attention." This opening does three things: it names the type of problem (a scheduling conflict), names the people involved (Alex and Jordan), and gives the time frame (Thursday afternoon).

The listener knows right away that the problem is a scheduling conflict involving two team members on Thursday.
2
Step 2 — Tell What Happened

Give the events in order: "Here's what happened: on Monday, I assigned Alex and Jordan to the data migration task for Thursday afternoon based on the original plan. Then, yesterday, the client requested an emergency quality review, and I saw that the QA lead put Alex and Jordan on that review for the same time slot. I noticed the overlap this morning while updating the shared calendar." Notice the words that show order ("on Monday," "then, yesterday," "this morning") and words that stick to what was seen ("I noticed," "I saw that") instead of blaming. This way of explaining what happened does not say "the QA lead messed up" — it just gives the facts, like the task names and when the problem was found.

The listener understands the sequence of events and sees how the conflict happened without anyone being blamed.
3
Step 3 — Suggest a Next Step

"I have a couple of ideas for how we could handle this. One option would be to move the data migration to Friday morning and keep the QA review on Thursday, since the client deadline for the review is sooner. Or, we could split the team — Alex on QA and Jordan on migration — though that would slow both tasks down a little. What do you think would work best?" This suggestion is specific (it gives two clear options), explains why one might be better (the client deadline), and asks the manager what they think — all part of proposing the next step.

The listener can now choose between concrete options instead of having to come up with a solution from scratch, and feels included in the decision.
4
After Step 3 — Confirm and Follow Up

The conversation doesn't end with your suggestion. Daniela might suggest a third option, ask a question, or pick one of your ideas. Either way, confirm what was decided: "Great, so we'll go with moving the migration to Friday. I'll update the calendar and let Alex and Jordan know. Should I also loop in the QA lead so they're aware of the change?" This last part confirms what was decided, takes on the follow-up task, and checks if there's anything else to do.

A clear decision is reached, next steps are assigned, and both people leave the conversation on the same page.

✦

WHAT MADE THIS EFFECTIVE

This whole conversation probably took less than two minutes, but it moved smoothly from the problem to a plan. The speaker did the hard thinking before the conversation — figuring out the conflict, gathering the facts, and coming up with options — so Daniela could focus on making a quick decision instead of asking a lot of follow-up questions. Preparing ahead of time is what makes a short conversation feel clear and organized.

SECTION 7

Common Mistakes and How to Fix Them

Even when you know the three-step plan, it's easy to fall into habits that make a conversation harder instead of easier. The table below shows common mistakes next to better ways of speaking — the difference between a conversation that solves a problem and one that just lets off frustration.

Pitfall	Why It Fails	Effective Strategy
Starting with a long story — talking for a while before saying what the problem is	The listener has to hold onto details without knowing what matters, which leads to confusion and impatience	Say the core problem in the first sentence or two, then give the details
Assigning blame — using accusing words ('You guys messed up my order')	This makes the listener defend themselves instead of helping you	Use words based on what you saw: 'I noticed the order contained…' or 'It looks like there was a mix-up with…'
Venting without proposing — sharing frustration but offering no solution	This leaves the whole job of fixing things to the listener, and you can come across as only complaining	Always bring at least one suggestion, even a small one: 'One option might be…'
Being vague — leaving out details like dates, reference numbers, or amounts	The listener can't check or act on the problem without the right details	Have the details ready before you call or speak: account numbers, dates, amounts, names
Ultimatums — making rigid demands ('Either fix this now or I'm leaving')	This leaves no room to work together, and can push the listener into an argument	Offer more than one acceptable option and ask what works: 'Would option A or B work better on your end?'

Five common pitfalls in problem-solution conversations and their effective counterparts.

✦

KEY TAKEAWAY

The difference between complaining and having a helpful conversation is not about your feelings — it's about how you organize your words. You are allowed to feel frustrated. What matters is whether you turn that frustration into a clear problem statement, a fair account of what happened, and a useful suggestion. It's like the difference between a messy pile of notes and a short, clear list: both have the same information, but only one is easy for someone else to use.

SECTION 8

Tips for Trickier Situations

The three-step plan works well in most situations, but some conversations are harder than others — maybe the other person is busy, upset, or disagrees with your idea. The table below gives simple tips for handling these tougher moments while still using the same three steps you've already practiced.

Skill You Practiced	A Harder Version of This Situation	What You Can Do
Stating the problem clearly	The other person seems too busy or distracted to listen	Ask for a good time to talk, or lead with the most important word, like 'urgent' or 'safety issue'
Telling what happened in order	You feel upset or nervous while talking	Take a breath, speak slowly, and stick to just the facts you remember clearly
Suggesting a next step	The person turns down your first idea	Have a backup idea ready, and ask what would work better for them
Staying calm and polite throughout	The other person raises their voice or argues	Keep your voice steady, calmly repeat your main point, and ask to speak with someone else if needed
Asking for their input during Step 3	You need to talk to a group instead of just one person	Let each person share their view before you suggest a next step

Simple ways to handle tougher versions of common problem-solving conversations.

These tougher situations do not need a whole new set of skills. They just need you to stay patient and keep using the same three steps: say the problem, explain what happened, and suggest a next step — one small piece at a time.

SECTION 9

Practice Problems

The following five problems ask you to use the three-step plan in situations that get a little harder each time. For each one, put together a spoken response with a problem statement, what happened, and a suggested next step. Then compare your answer to the model response provided.

Question 1: CONCEPTUAL

In your own words, explain why stating the problem before telling the backstory works better than the other way around. How does this order help the listener?

Show answer

Starting with the problem lets the listener know right away what you need help with. This helps them pay attention to the right details as you explain what happened next. If you tell the whole story first, the listener may get confused or interrupt to ask, 'What's the actual problem?' Starting with the problem keeps the conversation clear and moving forward.

Question 2: BASIC APPLICATION

You ordered a laptop online, and it arrived with a cracked screen. Write a three-step script for calling the retailer's customer service line. Include a problem statement, a short account of what happened, and a suggested solution.

Show answer

Step 1 (Problem Statement): "Hi, I'm calling about order number 77210. The laptop I received has a cracked screen." Step 2 (What Happened): "I placed the order last Tuesday, and it was delivered yesterday. When I opened the box, I noticed the screen had a large crack across the bottom. The outside packaging looked fine, so the damage may have happened during shipping." Step 3 (Suggested Solution): "Could you send a replacement as soon as possible? I need the laptop for a class project next week. If a fast shipping option is available, that would help a lot. If not, I'd also be okay with a refund so I can buy one locally." This response works well because it gives the order number for easy lookup, describes the damage clearly, avoids blaming anyone, and offers two acceptable options while explaining why it's urgent.

Question 3: INTERMEDIATE

You are an intern at a marketing firm, and you discovered that a social media post scheduled for tomorrow contains an error — the client's product name is misspelled. Your supervisor, Kenji, is in a meeting for the next two hours. Write what you would say to Kenji when his meeting ends, keeping in mind your role as an intern and the time-sensitive nature of the issue.

Show answer

Step 1: "Kenji, sorry to catch you right after your meeting, but there's a time-sensitive issue with the Greenfield Organics post scheduled for tomorrow morning. The client's product name is misspelled in the graphic." Step 2: "About an hour ago, I was doing a final check of tomorrow's post and noticed that 'Greenfield' is spelled 'Greefield' in the main image. I checked the client's brand guide to be sure, and it is an error. I didn't want to change anything without your okay since it's client-facing." Step 3: "Would it be alright if I send the correction to the design team now so they can fix it before the end of the day? That way we'd still be ready for tomorrow's post. I can also send a quick note to the account manager to keep them updated — would that be helpful?" This response shows respect for the supervisor's role ("I didn't want to change anything without your okay") while still showing initiative, since the intern has already checked the error and has a plan ready. It also respects Kenji's time by staying short while still covering all three steps.

Question 4: APPLIED

Your apartment building's management company charged you a $150 'late fee' on your rent, even though you have a bank statement showing the payment was made two days before the due date. You call the management office. Write your three-step script, and explain how you would respond if the representative says, 'Our system shows the payment was late.'

Show answer

Step 1: "Hello, I'm a tenant in unit 4B at Riverside Apartments. I'm calling because my latest statement has a $150 late fee, but I believe my payment was on time." Step 2: "I paid my rent through the online portal on March 1st, two days before the March 3rd deadline. I have a bank statement showing the payment went through that same day, March 1st. But the statement I got on March 10th still shows the late fee." Step 3: "Could you check your payment records? I'm happy to email or bring in a copy of my bank statement as proof. If the records show the payment was on time, could you remove the fee from my account?" Handling pushback: If the representative says the system shows a late payment, stay calm and say something like: "I understand that's what your system shows, and I appreciate you checking. Is it possible there was a delay on the portal's end? I have proof from my bank that the money left my account on March 1st. Would it help if I sent that to you, or to a supervisor who could look into it?" This response respects what the representative said without giving up your point, offers a possible reason for the mix-up, provides proof, and politely opens the door to asking for more help.

Question 5: CRITICAL THINKING

Two coworkers disagree about the cause of a project delay. One believes it was due to unclear instructions from the client; the other believes it was due to poor task tracking. As the team lead, how would you use the three-step plan to talk about this at a team meeting in a way that respects both people, names the real problem, and moves toward a fix?

Show answer

This situation needs care because two coworkers disagree about what caused the delay. Step 1: Start with a problem statement that does not blame either person: "We're here because the Henderson project was submitted four days late, and I want us to figure out how to avoid this next time." Step 2: Talk about what happened using both people's information as facts, not as an argument: "It looks like two things happened. First, the client's original instructions were less clear than usual, which led to some guessing about what was needed. Second, our task list wasn't updated every week, so a few steps were missed until the last minute. Neither of these is about one person doing something wrong — they're both things we can fix." Step 3: Suggest next steps that fix both problems: "I'd like to try two changes: meeting with the client within two days of getting new instructions to clarify anything unclear, and updating our task list every Friday. What do you both think — would this help?" This approach treats the delay as a shared problem to solve together, not a contest about who is right. It lets both coworkers feel heard while moving the team toward a clear plan.

SUMMARY

Lesson Summary

Summary

This lesson introduced a simple three-step plan for explaining problems and suggesting solutions, both at work and with services. The three steps are: a short problem statement that tells the listener what's wrong, a clear, fact-based account of what happened, and a next step you suggest in a polite, open way. Staying calm and using simple, clear phrases throughout helps the listener follow along and want to help.

Key habits to remember: lead with the problem instead of burying it in a long story, describe what happened without blaming anyone, offer a specific and doable next step, and ask what the other person thinks. Common mistakes — being vague, blaming, complaining without suggesting anything, or making ultimatums — can all be avoided by planning your three steps before you start talking. With practice, this simple plan will help you handle even harder conversations with more confidence.