Lesson
C1ENProblem-Solving Conversations
Master the language of collaborative problem solving — the conversations that happen when something goes wrong, a decision needs to be made, or a team needs to find a way forward together. From framing problems clearly and exploring options to reaching agreement and following up, this lesson builds the communication skills B2-C1 professionals need to solve problems productively with colleagues, partners, and clients.
How Do You Solve Problems at Work?
Talk Time
- Describe a time when a conversation with a colleague or partner actually solved a problem that had been stuck for weeks. What made it work?
- Do you prefer to think through a problem alone first, or talk it through with someone immediately? Why?
- Have you ever been in a meeting where a problem was discussed for an hour but nothing was actually resolved? What went wrong?
- What's the difference between a productive problem-solving conversation and an unproductive one?
- How do you handle a situation where you and a colleague see the same problem very differently?
- Is it ever useful to bring in someone from outside the team to help solve an internal problem?
Problem-Solving Vocabulary
Speed Match
- Reframe→To describe a problem from a different angle to open up new solutions
- Root cause→The underlying reason a problem occurred, not just its symptoms
- Workaround→A temporary solution that solves the immediate problem without fixing the cause
- Trade-off→A situation where gaining one thing requires giving up something else
- Alignment→When all parties share the same understanding of a problem and agree on the direction
- Constraint→A limitation that restricts the available solutions
- Brainstorm→To generate ideas freely without immediately judging or filtering them
- Escalate→To bring a problem to a higher level of authority when it cannot be resolved at the current level
- Stalemate→A situation where no progress can be made because parties cannot agree
- Pilot→A small-scale test of a solution before full implementation
- Buy-in→The agreement and commitment of key stakeholders to a proposed solution
- Debrief→A structured conversation after an event to identify what went well and what to improve
The Language of Problem-Solving Conversations
Swipe Battle
I think we might be solving the wrong problem — can we take a step back?
This phrase helps refocus the conversation before time is wasted on the wrong issue.
Let me understand the situation from your perspective before we talk about solutions.
Seeking understanding before proposing solutions almost always leads to better outcomes.
We've always done it this way, so that's probably the best approach here too.
Past practice is the most reliable guide to solving new problems.
What would success look like to you at the end of this conversation?
Agreeing on the desired outcome at the start gives the conversation a clear direction.
Let's just pick the first solution that works and move on — we don't have time for analysis.
Speed is more important than quality when solving workplace problems under pressure.
Before we decide, can we identify what's actually causing this — not just the symptom?
Addressing the root cause rather than the symptom produces more durable solutions.
I disagree with your analysis, and here's why I think the real issue is different.
Honest disagreement, expressed professionally, leads to better problem definitions.
Let's avoid talking about the problem and focus only on solutions.
Skipping the problem definition saves time and leads to faster resolution.
What constraints are we working with — what can't we change?
Understanding constraints early prevents the group from proposing solutions that aren't feasible.
If we can't agree, let's escalate immediately and let someone else decide.
Escalating immediately is always the most efficient response to disagreement.
What's the smallest change we could make that would have the biggest impact?
Looking for high-leverage, low-effort solutions is a sound problem-solving strategy.
The problem is clearly X — let's not waste time on anything else.
Closing down alternative interpretations of a problem too early often leads to the wrong solution.
How to Have a Better Problem-Solving Conversation
Jigsaw Reading
Fragment A: Define Before You Solve
The most common reason problem-solving conversations fail is that the participants are solving different problems. One person sees a communication breakdown; another sees a resource issue; a third sees a leadership failure. Before any solution is proposed, the most valuable investment is time spent agreeing on what the problem actually is — in specific, observable terms. "We missed the deadline" is a description. "We missed the deadline because the brief changed three times without a formal process for updating the project scope" is a definition that points toward a real solution.
Fragment B: Separate the Problem from the Person
In tense problem-solving conversations — especially when something has gone wrong — it is easy for the conversation to shift from "what happened and why" to "who is responsible." This shift is almost always counterproductive. It triggers defensiveness, reduces honesty, and narrows the conversation to the past rather than the future. The most effective problem-solving conversations maintain a consistent focus on the situation rather than the behaviour: not "you didn't flag this early enough" but "how do we make sure this kind of issue gets flagged earlier next time?"
Fragment C: Generate Options Before Choosing
One of the most reliable ways to get a better solution is to generate more than one before committing to any of them. When the first plausible solution is proposed in a group, there is a strong pull to accept it — especially under time pressure. Deliberately generating three or four options before evaluating any of them consistently produces better outcomes. It also reduces the risk of groupthink, because different options tend to reflect different assumptions about the problem, which surfaces disagreements that would otherwise remain hidden.
Fragment D: Close With Clarity
Even productive problem-solving conversations can end weakly — with a vague sense of agreement that evaporates by the following morning. A strong close names specifically what was decided, who is responsible for each action, and when the next check-in will happen. It also explicitly addresses any unresolved issues rather than leaving them hanging: "We haven't agreed on the budget question — let's flag that as a separate conversation for Thursday." Clarity at the end of a problem-solving conversation is what turns a good discussion into actual progress.
Comprehension questions
- The first fragment says participants often solve different problems. Think of a recent work conversation where this happened. How did you eventually get aligned?
- The second fragment says effective conversations focus on the situation, not the person. How easy is it to maintain this distinction when emotions are running high?
- The fourth fragment says conversations often end with a vague sense of agreement. What does a strong close to a problem-solving conversation look like in practice for you?
Problem-Solving Phrases in Context
Word Choice
- Before we look at solutions, can we make sure we're all clearfocusedalignedagreed on what the actual problem is?
- I think we might be addressing the effectissueproblemsymptom rather than the root cause — can we dig a little deeper?
- Let's considerexploregeneratediscuss a few options before we commit to anything — what else could we try?
- Given the constraintsfactorsissueschallenges we're working with — time, budget, and team capacity — which of these options is actually feasible?
- I'd like to reviewdiscussescalateaddress this — if we can't resolve it at our level by end of week, we need to involve the director.
- Can we agree on a reviewpilottrialdraft — a smaller test of this solution before we roll it out to the whole team?
- Before we close, let's make sure we're clear on the next stepsdecisionsplanoutcomes — who does what, and by when.
Reframe the Problem
Elevator Pitch
Useful phrases
- The real question here is...
- What we actually need is...
- If we look at it differently...
- The underlying issue is...
- What would need to be true for...
Our team keeps missing deadlines
Reframe this problem in a way that points toward a solution. Don't describe what's wrong — describe what needs to be true.
The client is unhappy with our service
Reframe: what is the client actually trying to achieve that isn't happening? Start with their goal, not your failure.
We can't agree on the right approach
Reframe: what would we need to understand or agree on first before the right approach becomes obvious?
The Problem-Solving Conversation
Roleplay Quest
Scenario
A joint project between two teams is behind schedule and a client deadline is approaching. Each side believes the other is responsible for the delay. A senior stakeholder has called an urgent meeting to resolve the situation and agree on a clear path forward before the client is informed.
Project Manager
You believe the delay was caused by the other team consistently missing their deliverables without flagging the issue early enough. You've had to manage client expectations alone for three weeks.
Secret goal: Focus on the future, not the past. You want a clear process for flagging delays early and a realistic revised timeline. Do not get drawn into blame — but don't accept sole responsibility either.
Technical Lead
You believe the scope of work changed twice without formal sign-off, which made it impossible to deliver on the original timeline. You flagged concerns informally but they weren't acted on.
Secret goal: Be specific about what changed and when. Propose a change request process for the future. Do not be defensive — acknowledge where communication could have been better on your side too.
Senior Stakeholder
You've been asked to facilitate this conversation, not to take sides. Your goal is to get both parties to a specific, agreed plan before the meeting ends.
Secret goal: Ask questions rather than giving answers. Keep the conversation focused on what needs to happen next, not what went wrong. Push for specific commitments — names, dates, actions.
Client Liaison
You've been managing the client relationship and you need something concrete to tell them by end of day. You don't care whose fault it is — you need a revised timeline and a clear message for the client.
Secret goal: Keep bringing the conversation back to the client impact. Push for a realistic revised commitment. Do not let the meeting end without a specific answer you can share externally.
Problem-Solving Conversation Dilemmas
Speed Debate
Useful phrases
- In a collaborative context...
- The risk with escalating too early is...
- From a team dynamics perspective...
- The most effective problem solvers I've seen...
- That depends on the urgency and the...
- You could argue the opposite — that...
- In practice, the conversations that work best...
- In a problem-solving conversation, you should always agree on the problem definition before proposing any solutions.
- It's better to escalate a problem quickly than to spend too long trying to solve it at the wrong level.
- The person who identifies a problem should always be responsible for solving it.
- In a collaborative problem-solving conversation, the most senior person in the room should speak last.
- A good workaround is always better than waiting for the perfect solution.
- It's more important to reach a decision in a problem-solving meeting than to reach the right decision.