Collaborative problem solving is about combining knowledge from multiple people to reach better solutions faster than any individual could alone. It depends on psychological safety, meaning people must feel safe enough to speak up and share what they have witnessed. Diversity in the team matters too: different views create a richer picture of the problem, and a clear shared understanding of the problem makes finding a solution straightforward.
Key Takeaways
- Psychological safety is destroyed faster than it is built: a single blame remark can undo weeks of trust, so facilitators must interrupt blaming the moment it appears.
- If a team cannot generate at least three distinct solutions to a problem, the problem is not yet understood well enough, and exploration must continue.
- Diversity in a team is a prerequisite for collaborative problem solving, because each person holds only part of the picture, and different views produce a richer, more accurate shared understanding.
- Making retrospective actions visible on the daily task board, assigned to a person and framed as a testable experiment, is what separates actions that get done from sticky notes that stay untouched.
Collaborative problem solving starts with how a team works together
The way a team solves problems depends on how its members work together day to day. Ben Linders describes culture as “how we do things around here,” and that simple definition matters more than any toolset. Collaborative problem solving is not about individual strength or individual knowledge. It is about combining what people know to reach a better solution, and often a faster one.
The point of collaboration is the result. A solution found together is more likely to solve the problem effectively, because no single person holds the whole picture. Everyone who has witnessed part of the problem carries a piece of the puzzle. The work is bringing those pieces together.
Why understanding the problem matters more than finding a solution
Solving a problem is easy once you understand it. The hard part is the understanding. Most teams skip ahead to solutions before they have a shared picture of what actually happened, and they end up acting on the wrong aspect of the problem.
A shared understanding only forms when people contribute what they have seen. That means speaking up, sharing what happened, offering ideas, and putting the parts of the puzzle on the table. Without that, the picture stays incomplete and the solution misses the root cause.
Ben recommends staying in the problem space far longer than feels comfortable. Not complaining about the problem, but building a deeper understanding of it. The reward for that patience is that the solution often becomes obvious once the picture is clear.
Psychological safety is the foundation, not a side effect
People only contribute their part of the puzzle when they feel safe enough to speak. If that safety is missing, people stay silent, the full picture never emerges, and the team works with gaps it does not even know about.
Building psychological safety has a chicken-and-egg quality. You need some safety to work on safety. Ben calls this bootstrapping: start by creating a small pocket of safety that gives you something to build on, rather than expecting a few exercises to make everyone comfortable at once.
A retrospective is a practical place to start. Certain techniques help people feel at home and willing to share at least some of what they know. Once that begins, it becomes a foundation you can grow. Safety is nurtured over time, not switched on.
The flip side is fragile. What takes weeks to build can be destroyed by one or two remarks. Anyone working on team culture has to watch for behavior that tears it down, because destruction moves much faster than construction.
What behaviors destroy safety, and how to counter them
Blaming and finger-pointing are the typical killers. The moment someone is told they did something wrong, the willingness to share starts to drain away.
One countermeasure is the prime directive: assume that everyone did the best they could given the situation, their knowledge, and what happened along the way. You still have a problem, so the question becomes what the team can learn and do differently next time. The assumption removes the threat without removing the inquiry.
For facilitators, the rule is direct. If you see blaming starting, step in and steer the conversation back to something productive. A useful technique is rephrasing: instead of telling someone they did something wrong, describe what happened. Name the situation, not the person.
Diversity makes the picture richer and powers change
Different views are an asset when you are trying to understand a problem. A team where everyone shares the same background and works together every day may never surface the real image. Conflicting perspectives produce a richer, deeper view of what happened.
Diversity also drives change. A team with no diversity tends to be stable and stuck, because nobody initiates anything. Too much diversity tips into chaos. For most teams the real risk runs the other way: too little diversity, not too much.
Psychological safety is not about avoiding conflict. It is about handling conflict in a mature way. Problem solving usually surfaces conflicting issues, and the productive move is to approach them positively, to understand them rather than dodge them. Avoiding conflict does not solve the problem.
How to give quiet people room to contribute
Strong communicators and provocative voices can dominate a room, while more introverted people hold back. Often the quieter people have a clearer view of what actually happened than the extroverts. Their ideas and questions are exactly what you need.
The way to draw them out is simple. Invite them to speak, and ask everyone else to listen for a moment. Creating that space lets another view enter and completes the picture.
Visualize the problem instead of only talking about it
Talking alone does not stick. Writing things down and making the problem visible helps people comprehend it and shows where information is solid and where it is missing.
Several techniques fit different problems:
- Causal analysis diagrams trace a problem from surface causes down to root causes.
- Sticky notes collect and organize information in a way you can move around and rearrange.
- Drawing and images capture aspects that words alone leave fuzzy.
The reason to keep it movable is that the early phase should stay fluid. You diverge first, opening up and gathering all the available information. Then you converge, narrowing toward a solution once the picture is good enough. Visual artifacts make both phases easier to manage.
Demand at least three solutions before you decide
If you have only one solution, you do not yet understand the problem well enough. Ben points to Jerry Weinberg’s idea here: come up with at least three different solutions before deciding.
If you cannot generate three options, go back to exploring the situation, because the understanding is still too thin. Once you have several, you can choose, and the answer may turn out to be a combination of two or three of them. The goal is real choice, not a single guess.
Why retrospective actions die on the board, and how to keep them alive
Actions stall when they are vague. To survive contact with daily work, an action has to be genuinely actionable: clear on what will be done, who will do it, and how. Add the expectation too, so the team knows what problem the action should solve and what they expect to witness as a result. Treating it as an experiment with a predicted outcome gives it shape.
Fewer actions work better than many. Aim for one, two, or at most three coming out of a retrospective. The fewer you commit to, the higher the chance they actually happen.
Visibility is the other half. Put the actions where people see them every day, on the task board, whether physical or online. Reserve a space for them, or turn them into tasks that someone can pick up and move across the board. Then follow up in the standup to check whether the work is really happening. What is visual gets done.
How gamification lowers the barrier to speaking up
Gamification means borrowing principles from games and applying them outside a game. Used in problem solving, it creates an environment where speaking up feels easier. It is another bootstrapping route into psychological safety.
Games also normalize trying things out. In a game you experiment, and if it fails you lose a life and try again next week. The same mindset helps when changing something in a team or organization: it might work, it might not, so feel safe enough to try and safe enough to fail.
Ben runs a game around impediments in his workshops. Players pick up signals, work out what the impediment really is, and decide whether to take an action or run an experiment. They gain points, things happen along the way, they can win or lose management support, and they can even end up in jail. The fun is the point. A lighter, more neutral setting makes it easier for people to talk about things that actually made them uncomfortable, and to focus on what they can try rather than what they cannot do.
First steps for running a collaborative problem-solving session
Start with a problem that genuinely matters. Ask what is keeping the team awake, the thing that would make a real difference if it were cleared out of the way. Do not run a game just for fun; anchor it in a situation the team cares about.
Bring in a neutral facilitator. Someone running this kind of session needs to stand outside the problem, possibly without even knowing the details, so they can help the team explore it and reach solutions. Their job is to guide the steps of the process and draw out the best information, not to push their own answer.
Check the environment before you begin. Look for hurdles that need clearing first: someone who says they do not want to talk about this, who feels uncomfortable, or who sees no solution at all. Get the main obstacles out of the way before the session, so the team can actually work on the problem once it starts.
