Problem Solve Canvas
"The first step toward solving a problem is to clarify what is not understood, i.e., to make clear distinction between what we know and understand and what we do not." — Shigeo Shingo
The Problem Solve Canvas is a single page, organized into about six sections, that tells the whole story of a problem: why it matters, what is actually happening, what the root cause is, and what the team will do about it. It comes from chapter 12 of Improve (Ellis, 2019), where weak problem solving is treated as one of the eight wastes of knowledge work, the waste of Inferior Problem Solving.
This waste deserves its own name because it cuts at the core of what knowledge staff do. Other wastes slow experts down; this one undermines the contribution itself. It appears when smart, hard-working, well-meaning people solve the wrong problem, treat symptoms instead of root causes, or install countermeasures that quietly fail because nobody tracked the results. It is partly human nature, since we see patterns that are not there, and partly a lack of diligence, since moving on to solving feels better than sitting with the evidence. Unlike most wastes, it is also hard to hide: the customer who complained at the start keeps complaining until the problem is actually gone.
The canvas
The canvas borrows heavily from the Toyota A3 method described by John Shook in Managing to Learn. Shook's own book includes five A3 variants; there is nothing magic in any particular set of steps. The discipline is in telling the whole story on one page, adapting the sections to the problem at hand, and refusing to skip the left side to get to the right side faster. If the Toyota A3 page is the method's lineage, this page is its working format.
See it broken, watch it work
Lean practice calls visiting the real work "going to Gemba." The canvas splits that idea into two sharper instructions, because teams reliably do the first and skip the second.
See it broken: every person on the solve team must observe the effects of the problem with their own eyes before proposing causes. Secondhand problem descriptions are where wrong problems come from.
Watch it work: after the countermeasure is in place, return and observe it actually working. This is the half that gets ignored. We install a fix, become subconsciously convinced it will hold, and never go back. The mistake is not believing our solutions are guaranteed; nobody believes that when asked. The mistake is failing to consciously decide that there are too many unknowns to trust a solution unobserved.
Why a formal process frees creativity rather than stealing it
A common first reaction to formal problem solving is that it sounds like a stodgy process that will smother creative work. The experience is the opposite. The canvas removes the needless creativity spent on the tedious parts, deciding what to write down and how to present it, so that expertise and creativity concentrate on the part that deserves them: understanding and solving the right problem. The method begins from respect for the experts. Its starting assumption is a compliment: this team will solve the problem well once its attention is aimed at the right one.
For problems too large or too ambiguous for a single solve team, the canvas extends into the Solve-Select workflow, which keeps leadership and domain experts working the problem together.