Problem Framing and Issue Architecture
10 min read
Lesson objectives
- Analyze a professional situation by separating visible symptoms from the strategic issue and building a testable issue tree without assuming the answer and justify a reviewable decision.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
Your client says: we must cut price to recover subscribers. That request bundles the problem with an assumed solution. Reframe it around the outcome: why do subscribers leave, and which intervention would improve renewal? This separates the price explanation from the user-experience explanation. Evidence can now distinguish solutions instead of merely justifying a discount selected in advance.
An issue tree breaks a large question into smaller questions that evidence can answer. Start with renewal, then examine value relevance, usability, and price burden. Define each branch's boundary. A malfunctioning feature belongs under user experience; having no need for the feature belongs under value. These distinctions let you combine branch findings without counting the same complaint twice.
Prioritize branches by their ability to change action. A survey of all customers may take a month, while weekly usage records reveal the timing of a decline within an hour. Start with that record if it distinguishes two explanations, then choose interviews that explain the observed behavior. Keep the question open to a third mechanism if the pattern fits neither pricing nor usability.
Create a four-column table: branch question, predicted signal, available records, and the action affected by the answer. The price branch might predict cancellation just after billing; the experience branch might predict failed task completion before cancellation. The final column explains why the question deserves time: billing evidence suggests changing payment terms, while task failure suggests repairing the journey. Drop a question that cannot alter a choice even when it is interesting. Then test coverage against a sample of cancellations. Select cases with different tenure, prices, and usage intensity and try to explain each through the branches. If a group fits nowhere, add a branch or revise a definition. This tests coverage rather than requiring a fixed branch count. Retain the reason for revision so a colleague understands why the analysis changed. Revisit priorities after the first evidence arrives. A previously small branch may become decisive when it changes intervention cost or speed. A useful tree evolves with knowledge while remaining understandable to the client.
Before closing scope, run a harm test: who is affected if diagnosis is wrong, which decision is hard to reverse, and which information needs protection? Raise the evidence threshold where consequences are high. This also identifies when legal, financial, or technical expertise is needed instead of expanding the consultant’s claim. Apply it here to examine contrary evidence.
The module workshop produces a four-page engagement file. Page one records the decision question, owner, deadline, and constraints. Page two contains an issue architecture with a test for each branch. Page three holds an evidence register with source, period, definition, quality, and opposing evidence. Page four lists hypotheses, confidence, and the next discriminating step. Review the file through an advocate for the strongest rival explanation and state what would make it correct. Then test usability: can the sponsor take a defined action, and do they know what the analysis does not establish? If not, narrow the question or repair traceability. Add an interview protocol covering purpose, confidentiality, use, and escalation when information falls outside scope or reveals a conflict. The success criterion is that a new reader can reconstruct the diagnosis without attending meetings and can distinguish verified fact from reviewable professional judgment. Use it here to compare two rival explanations.
Close the module with a brief engagement review led by someone who did not frame the hypotheses. That person identifies the decision, rival evidence, confidence boundary, and next discriminating step, then compares the result with the team’s intent. Any difference reveals ambiguity that must be repaired in the record rather than explained orally after delivery. Test it here before favoring a recommendation.
For Problem Framing and Issue Architecture, separate four layers: direct observation, interpretation, assumption, and judgment. An observation is inspectable, such as a changed rate or documented behavior. An interpretation connects observations and may have rivals. An assumption is a condition not yet resolved. Judgment is a professional choice under uncertainty. This separation stops the first executive narrative from becoming fact and turns disagreement into an investigable question rather than a contest of opinions. Apply it here to examine contrary evidence.
At the education platform, compare renewal among users of the core feature with renewal among nonusers. A decline in both groups supports a price explanation, while concentration after a malfunction supports experience. Also ask about competing alternatives: a satisfied user may leave because another service better fits a changed need. Each branch predicts a different signal, making its test useful even when the client rejects your first interpretation.
A discount may quickly increase renewal while reducing contribution. Compare retention with subscriber value, then contrast discounting with repairing the feature. If usage recovers but renewal does not, investigate perceived value or payment timing. If renewal improves without actual use, the discount may only postpone cancellation for one cycle. That distinction changes follow-up because renewal alone does not establish a healthy customer relationship.
Renewal at an education platform fell from 72% to 61% after a 6% price rise and a 24% drop in use of the core feature. Build an issue tree around value, user experience, and ability to pay. Use declined six weeks before cancellation, so test a repaired core journey against a control group instead of discounting everyone. Success is recovering half the lost use and gaining five renewal points. Price effects remain unresolved and require a later limited offer that does not mix the causes. To verify the reasoning, the learner explains which case evidence changed the recommendation in Problem Framing and Issue Architecture and what evidence could reverse it.
Use questions rather than solutions as branch labels. 'How do we expand advertising?' chooses a means before demand is understood. 'Which segments need the service and can be reached economically?' leaves advertising, partnerships, and referrals available. Define reach operationally: awareness, starting a subscription, or using it after payment? Each definition requires different evidence. Confusing the purchase journey with the usage journey can direct money into advertising when account activation is the real problem.
Lesson summary
Problem Framing and Issue Architecture separates evidence from assumptions, compares genuine alternatives, and links the recommendation to conditions and review indicators.