Gather the decision trigger, available evidence, and hard constraints; park solution ideas initially.
Problem Framing Workshop
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
Prerequisite
What needs to be finished first
Research and operations evidence, stakeholder and context map, assumption log, problem frame, and How Might We question
Preparation
What needs to be ready before start
Research and operations evidence, stakeholder and context map, assumption log, problem frame, and How Might We question
Facilitator · problem owner · affected/customer perspective · domain and delivery perspectives · decision owner
Gather the decision trigger, available evidence, and hard constraints; park solution ideas initially.
90–150 minutes with evidence collected beforehand.
Prepare a workspace with Evidence · Actors · Impact · Boundary · Question; separate example from live data.
Core question
The one question this method answers
Which concrete problem for which people in which context is evidenced, meaningfully bounded, and open to several solutions?
Flow
Phases with goal, actions, output and pitfall
Die Gruppe prüft, welche Beschreibung des Problems belastbar ist, welche Annahmen darin stecken und welche Sichtweise das Feld unnötig verengt. Daraus entsteht ein präziserer Rahmen, der spätere Ideen und Entscheidungen deutlich besser trägt.
Problem Framing Workshop · working structure
Fictional example
Fictional values show the actual method fields.
Evidence view
Gather observations, data, and quotes; separate facts, interpretations, and solutions.
19 of 32 part searches start in chat; 11 end with a warehouse call; quote: “Inventory is from yesterday.”
Actor context
Describe affected people, context, desired progress, and current obstacles concretely.
Mobile technicians during a customer job must find a compatible part before the service window ends.
Problem core
State undesired outcome, significance, and observable impact without presuming cause or solution.
Stale inventory information extends search and customer waiting; cause remains a hypothesis.
Scope
Negotiate in-scope, out-of-scope, constraints, assumptions, and knowledge gaps.
In: part search during job; out: procurement; constraint: weak network; open: frequency of compatible alternatives.
Working question
Translate the frame into an open How Might We question and test evidence, solution openness, and agency.
How might mobile technicians find reliable compatible parts during a job, even with weak connectivity?
All values are fictional.
- 1
Evidence
Evidence view

Goal
Evidence view: Gather observations, data, and quotes; separate facts, interpretations, and solutions.
Inputs for this step
- Gather the decision trigger, available evidence, and hard constraints; park solution ideas initially.
- Research and operations evidence, stakeholder and context map, assumption log, problem frame, and How Might We question
Actions
- Gather observations, data, and quotes; separate facts, interpretations, and solutions.
Output
Evidence view
Gather observations, data, and quotes; separate facts, interpretations, and solutions.
Quality check
Can every finding be traced to a source or case?
Pitfall
Workshop opinions replace user and operational evidence. Mark every statement as observation, interpretation, or hypothesis.
Timing: 20–30 minutes
- 2
Actors
Actor context

Goal
Actor context: Describe affected people, context, desired progress, and current obstacles concretely.
Inputs for this step
- Evidence view
Actions
- Describe affected people, context, desired progress, and current obstacles concretely.
Output
Actor context
Describe affected people, context, desired progress, and current obstacles concretely.
Quality check
Is a concrete group in a situation named rather than a market segment?
Pitfall
All users are treated as one audience. Bound context and variation; create separate frames for different situations.
Timing: 15–25 minutes
- 3
Impact
Problem core

Goal
Problem core: State undesired outcome, significance, and observable impact without presuming cause or solution.
Inputs for this step
- Actor context
Actions
- State undesired outcome, significance, and observable impact without presuming cause or solution.
Output
Problem core
State undesired outcome, significance, and observable impact without presuming cause or solution.
Quality check
Does it describe outcome and impact rather than a symptom label or solution wish?
Pitfall
We need a new search becomes the problem. Remove the solution and state observed obstacle plus consequence.
Timing: 15–25 minutes
- 4
Boundary
Scope

Goal
Scope: Negotiate in-scope, out-of-scope, constraints, assumptions, and knowledge gaps.
Inputs for this step
- Problem core
Actions
- Negotiate in-scope, out-of-scope, constraints, assumptions, and knowledge gaps.
Output
Scope
Negotiate in-scope, out-of-scope, constraints, assumptions, and knowledge gaps.
Quality check
Are boundary and exclusions relevant and traceable?
Pitfall
Scope expands to the whole service process. Bound the smallest meaningful decision space and track dependencies separately.
Timing: 15–25 minutes
- 5
Question
Working question

Goal
Working question: Translate the frame into an open How Might We question and test evidence, solution openness, and agency.
Inputs for this step
- Scope
Actions
- Translate the frame into an open How Might We question and test evidence, solution openness, and agency.
Output
Working question
Translate the frame into an open How Might We question and test evidence, solution openness, and agency.
Quality check
Does it permit several paths while staying with the evidenced need?
Pitfall
The question already says through AI search. Remove mechanism and return to actor, progress, and context.
Timing: 15–25 minutes
Artifact
What comes out at the end
Sketch: what the artifact looks like
Problem frame with actor, context, need, evidence, impact, scope, assumptions, and open design question.
Record date, owner, source state, and review date; preserve prior versions.
- Evidence wall
- Problem frame canvas
- Assumption and scope log
problem-frame-markdown.md
Set subject, evidence, roles, flow, and review.
Problem Framing Workshop: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Complete run Time: 90–150 minutes with evidence collected beforehand.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Research and operations evidence, stakeholder and context map, assumption log, problem frame, and How Might We question
- Roles: Facilitator · problem owner · affected/customer perspective · domain and delivery perspectives · decision owner
- Advance information: Gather the decision trigger, available evidence, and hard constraints; park solution ideas initially.
- Overall time needed: 90–150 minutes with evidence collected beforehand.
- Setup: Prepare a workspace with Evidence · Actors · Impact · Boundary · Question; separate example from live data.
Prepare for the work steps
Evidence: Evidence view
- Gather the decision trigger, available evidence, and hard constraints; park solution ideas initially.
- Research and operations evidence, stakeholder and context map, assumption log, problem frame, and How Might We question
Actors: Actor context
- Evidence view
Impact: Problem core
- Actor context
Boundary: Scope
- Problem core
Question: Working question
- Scope
Problem Framing Workshop · working structure
Evidence view
Gather observations, data, and quotes; separate facts, interpretations, and solutions.
...
Actor context
Describe affected people, context, desired progress, and current obstacles concretely.
...
Problem core
State undesired outcome, significance, and observable impact without presuming cause or solution.
...
Scope
Negotiate in-scope, out-of-scope, constraints, assumptions, and knowledge gaps.
...
Working question
Translate the frame into an open How Might We question and test evidence, solution openness, and agency.
...
The blank worksheet contains prompts only.
Reference · original teaching example
Evidence: Evidence view
Expected artifact: Evidence view
Gather observations, data, and quotes; separate facts, interpretations, and solutions.
Entry:
...
- Can every finding be traced to a source or case?
Actors: Actor context
Expected artifact: Actor context
Describe affected people, context, desired progress, and current obstacles concretely.
Entry:
...
- Is a concrete group in a situation named rather than a market segment?
Impact: Problem core
Expected artifact: Problem core
State undesired outcome, significance, and observable impact without presuming cause or solution.
Entry:
...
- Does it describe outcome and impact rather than a symptom label or solution wish?
Boundary: Scope
Expected artifact: Scope
Negotiate in-scope, out-of-scope, constraints, assumptions, and knowledge gaps.
Entry:
...
- Are boundary and exclusions relevant and traceable?
Question: Working question
Expected artifact: Working question
Translate the frame into an open How Might We question and test evidence, solution openness, and agency.
Entry:
...
- Does it permit several paths while staying with the evidenced need?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/problem-framing-workshop/run-sheet
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
problem-framing-workshop-beispiel.md
Concrete filled scenario, fictional example
Fictional teaching example: Problem Framing Workshop · working structure
Evidence view
19 of 32 part searches start in chat; 11 end with a warehouse call; quote: “Inventory is from yesterday.”
Actor context
Mobile technicians during a customer job must find a compatible part before the service window ends.
Problem core
Stale inventory information extends search and customer waiting; cause remains a hypothesis.
Scope
In: part search during job; out: procurement; constraint: weak network; open: frequency of compatible alternatives.
Working question
How might mobile technicians find reliable compatible parts during a job, even with weak connectivity?
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Evidence viewWorkshop opinions replace user and operational evidence.View in phase
- Actor contextAll users are treated as one audience.View in phase
- Problem coreWe need a new search becomes the problem.View in phase
- ScopeScope expands to the whole service process.View in phase
- Working questionThe question already says through AI search.View in phase
Evidence view
Workshop opinions replace user and operational evidence.
Mark every statement as observation, interpretation, or hypothesis.
Actor context
All users are treated as one audience.
Bound context and variation; create separate frames for different situations.
Problem core
We need a new search becomes the problem.
Remove the solution and state observed obstacle plus consequence.
Scope
Scope expands to the whole service process.
Bound the smallest meaningful decision space and track dependencies separately.
Working question
The question already says through AI search.
Remove mechanism and return to actor, progress, and context.
Stop criteria
When to pause, resolve prerequisites, or choose another approach
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

