Frame a problem as a testable gap between a current and desired state.
Define an initial scope, constraints, affected stakeholders and triggers for scope expansion.
Separate the problem definition from an assumed solution or unverified cause.
Define the gap before becoming attached to a solution
A statement such as “we need a new system” sounds practical, but it describes a solution rather than a problem. A stronger problem definition shows the current state, the desired state, the gap between them, the scope, important constraints, and who is affected by the decision. A new system may later become an alternative, but it should not own the question before the desired change is understood.
Six elements of a workable frame
Ask in sequence: What is happening now? What do we want instead? Where and when does it occur? What is the consequence of the gap? Which constraints cannot be ignored? Who is affected or holds part of the decision authority? The answers do not require false precision. If some boundaries are unknown, record them as open questions rather than inventing numbers. The team should know what is inside the initial inquiry, what is outside it, and what would count as improvement.
The desired state is not the name of an intervention
“Deploy AI,” “change supplier,” or “hire more people” are not desired states by themselves; they are possible interventions. A desired state describes the improvement to be observed, such as reducing rework to 10% or less or reducing late delivery within a stated service level. Separating the outcome from the intervention keeps multiple routes to improvement open.
Lesson summary
Good framing describes the gap, scope, desired state and constraints while keeping solutions and possible causes open until evidence is sufficient.