A problem statement is more than a description. It is a choice about what to notice, what to ignore, whose actions matter, and what would count as progress. “The elevator is too slow” invites mechanical changes; “the wait feels unpleasant” invites a different set of questions. Neither wording is automatically better. The point is that a frame shapes the solution space before anyone begins solving.
Patternverse’s Reframing collection offers small thinking moves for examining that choice. It is inspired by Thomas Wedell-Wedellsborg’s work on problem reframing, but these are original Patternverse adaptations, not official implementations or reproduced book text. The patterns are tools for inquiry, not engines for discovering one hidden “real problem.” A situation can contain several causes, several values, and several useful ways to describe it. Different frames may help at different stages.
Solving, analyzing, and reframing
Solving asks what to do given a problem: “How can we answer more support tickets each day?” Analyzing looks more closely inside that account: “Which ticket categories take longest, and where do they wait?” Reframing asks whether the account itself is the right starting point: “Why are so many tickets being created, and what outcome are customers seeking when they contact us?” All three activities matter. Reframing is not a more sophisticated replacement for evidence or execution. It is valuable when a useful solution might lie outside the current question.
Suppose a team says, “We cannot keep up with incoming support tickets.” A capacity frame suggests staffing, schedules, or tooling. A demand frame asks which product defects or unclear instructions generate repeat contacts. A routing frame asks whether requests reach the right person. A priority frame asks whether every ticket needs the same service level. A self-service frame asks whether people could resolve some needs without waiting. A goal frame asks whether “close more tickets” is the right measure, or whether customers chiefly need reliable resolution. These frames imply different evidence and different possible actions. Hiring more agents might help one version while leaving the others almost untouched.
The team need not choose a winner by argument alone. It could examine a week of tickets by cause and resolution path, interview a few customers about what they tried before contacting support, and measure where work waits. Perhaps both a capacity problem and a product-quality problem exist. A good frame can be useful without being exclusive.
Explore the current frame—or break it
Some reframing moves explore the existing frame. If the support queue is genuinely the issue, finding that one category takes most of the time sharpens the investigation. Verify the Statement checks whether a claim is supported; Map Stakeholders identifies who is inside the story; Expand the Time Window looks at events before and after the visible episode. These moves can make an existing question more accurate.
Other moves break a premise. Detect a Baked-In Solution notices when “we need a chatbot” has replaced the underlying service need. Remove Constraints asks whether only this team, budget, or channel can act. Rethink the Goal questions whether ticket closure is the outcome customers actually value. Breaking a frame does not mean rejecting every original observation. It means allowing a different question to compete.
Review the Frame is a quick scan for which move might matter now. Look Outside the Frame searches context that the present wording excludes: a favored professional tool, the broader timeline, hidden systemic conditions, or properties of resources already available. Each specialist pattern is small enough to use on its own in a conversation, decision, project, or everyday dilemma.
Frame → Reframe → Move Forward
The collection’s central rhythm is short and repeatable:
- Frame. Put the concern into a provisional sentence, leaving uncertainty visible.
- Reframe. Use one or two relevant lenses to find genuinely different interpretations.
- Move forward. Select a promising frame and ask what observation or limited experiment could support or weaken it.
- Learn and frame again. Let the result change the question if needed.
Rapid Reframe offers this route when someone is stuck and does not know which lens to pick. Generate Real Options guards against a long list of choices that all share the same assumption. Validate the Frame turns an appealing interpretation into a test that could change your mind.
Short bursts matter. Reframing can become an analysis trap if each alternative spawns five more and no one returns to the world. After a few meaningful candidates, ask which one is worth testing now. Not every issue needs reframing: a narrowly defined, well-evidenced problem may be ready for action. And when safety, urgency, or another person’s immediate needs dominate, speculative reframing should not delay a necessary response.
These patterns preserve the user’s agency. They should offer “another way to see this might be…” rather than announce a secret cause or motive. Emotional experience can be valid while its explanation remains uncertain. A stated goal can be legitimate while its route is questioned. Reframing helps people see options; observation, consent, practical constraints, and judgment determine what to do with them.
Begin with Frame the Problem if the concern is still diffuse, or choose a specialist from the groups below. The articles teach each move with examples and limitations, so they can be read without running anything.