Solve-Select
"...decision making is a two-step process: first learning and then deciding." — Ray Dalio
Solve-Select is two teams working in cooperation. The select team, usually leadership, selects the problem, defines it carefully, and makes the final choice. The solve team, usually technical staff and subject-matter experts, builds out the options. The method comes from chapter 18 of Improve (Ellis, 2019) and extends the Problem Solve Canvas for problems too complex to hand to a single team, where the business question and the technical question have to be worked out together.
When a single solve team fails
The standard canvas workflow has one handoff: leadership defines the problem, a solve team takes it away and returns with a solution. For well-bounded problems this works, because the parameters can be fully stated up front. But consider a common case: a competitor has just released a new product and the organization must respond. So little is known at the start that leadership cannot write a clear goal. Should the response be a modification of an existing product, a wholly new one, or, if the threat turns out to be small, nothing at all? Nobody can say until domain experts have bounded the options, and the experts cannot finish bounding them until leadership clarifies what the business will accept. A single handoff silos the two groups exactly when they most need each other.
Dalio's line is the design principle. The organization must first learn together, through alternatives built out by the domain experts best positioned to understand the constraints. Then it can decide together, led by the people responsible for the organization. Solve-Select turns the single handoff into a working partnership: the solve team (domain experts) and the select team (leadership) meet at several points along the way, restating the problem as each round of options sheds light on it.
The solution menu
The central artifact is the solution menu: a small set of genuinely different options, each developed just far enough for a real decision. Not one recommendation with two strawmen beside it, and not a single option presented as inevitable. The menu is what lets the select team learn before it decides. A Solve-Select canvas, a variant of the standard one-page canvas, carries the menu along with the evolving problem statement and the evidence behind each option.
What the waste looks like without it
Organizations without a Solve-Select process pay for it in recognizable ways. Management feels the technical team is hiding the ball, while the technical team feels managers delay decisions or make poor ones, and the resentment compounds. Leadership needs several options developed in parallel but receives information on only one. Lacking a path that drives to a conclusion, the organization debates the same options in meeting after meeting without deciding anything. Each of these maps to one of the eight wastes of knowledge work described in Improve; the chapter 18 discussion walks through the full set.