EN.662.692 Chap.2 Framing Ambiguous Problems
Framing Ambiguous Problems
Hold the solution outside the frame
Ambiguous client requests often contain a proposed technology or causal story. This chapter slows the move to solutions by separating observations, interpretations and assumptions. A defensible frame identifies the affected stakeholder, current condition, desired difference and decision boundary.
Its success condition describes an outcome rather than a chosen product.
Make scope provisional
Scope keeps inquiry manageable, but new evidence may reveal that the wrong process stage, stakeholder or outcome was selected. The chapter gives every boundary a revision trigger and uses fictional service cases to practise neutral wording.
Strong frames guide evidence gathering, preserve rival explanations and identify the decision that will follow.
Build a frame that can survive contact with evidence
Start by copying the client's request and marking every word that names a cause, solution or value judgment. Rewrite those marked phrases as claims to investigate.
If a request says that customers need an app because communication is poor, the observable starting point might instead be that customers contact staff repeatedly before completing a process. The causal explanation and app proposal remain hypotheses.
This separation is valuable because interviews may reveal that unclear eligibility, inconsistent timing or missing authority drives the repeated contact.
A useful boundary names what the team will initially examine and why that slice is decision-relevant. It may specify a stakeholder group, process stage, location, time horizon and decision owner. Every exclusion should have a reopening condition.
If evidence shows that delays originate in an upstream approval, for instance, a downstream-only scope no longer protects focus; it hides the mechanism. Record the trigger and the person authorised to revise the boundary so that scope changes are reasoned rather than opportunistic.
Finally, test the frame against the work it must organize.
Ask whether it supports multiple explanations, produces researchable questions and leads to a real client decision. Define success in observable stakeholder or system terms, while avoiding a metric selected only because it is readily available. Pair the success condition with safeguards for displaced cost, access or workload.
A strong frame remains concise, but its evidence ledger preserves the distinctions behind it: what was observed, who interpreted it, which assumptions remain open and what new finding would require a rewrite.
What this chapter covers
- 01
Observation
- 02
Interpretation
- 03
Assumption
- 04
Success condition
- 05
Decision boundary
- 06
Solution bias
Worked example · free
Remove the solution from a service request
- 2Separate the observed communication gap from the chatbot proposal.
- 2State the stakeholder and desired difference.
- 2Add a boundary and evidence trigger.
Key terms
- Problem Frame
- A Problem Frame defines the observed condition, stakeholders, boundary and desired difference for a decision.
- Success Condition
- A Success Condition describes how improvement would be recognised without prescribing one intervention.
- Revision Trigger
- A Revision Trigger is evidence that would widen, narrow or redirect the current frame.
Framing Ambiguous Problems FAQ
Why should a problem statement avoid solutions?
Putting a preferred product into the frame narrows the evidence search and makes alternative explanations harder to see. A neutral statement defines the current condition and desired difference first, allowing technology, process, staffing and communication options to compete after the causal account is tested.
How are observations separated from assumptions?
An observation records what was seen, measured or reported. An interpretation explains possible meaning, while an assumption fills a gap the team is currently relying on. Keeping them in separate columns exposes where further evidence is needed and prevents one stakeholder statement from becoming a universal fact.
When should scope change?
Change scope when credible evidence shows that the selected stakeholder, process stage, outcome or causal boundary cannot support the decision. Record the trigger in advance where possible, then explain what remains supported and what new evidence must be gathered after the revision.
Assessment move
Collect five broad requests from everyday services and rewrite each without causal or product language. Label every clause as observation, interpretation, assumption, boundary or success condition. Introduce one contradictory stakeholder perspective and revise only the parts it affects. Finish by naming the decision the frame is meant to support and the evidence that would move the boundary.
Compare your neutral rewrite with the original request and list what became a research question rather than disappearing. Test whether two genuinely different solutions remain possible under the frame. Then exchange frames with a peer and ask them to identify the stakeholder, present condition, desired difference, exclusions and reopening trigger without additional explanation.
Working through Framing Ambiguous Problems in EN.662.692? Sia is AskSia’s AI Management tutor — ask any EN.662.692 Framing Ambiguous Problems question and get a clear, step-by-step explanation grounded in how EN.662.692 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.