# The problem definition process
Executive summary
The problem definition process is the disciplined construction and testing of a provisional account of an undesirable situation: what is happening, compared with what standard, where and when it occurs, who experiences consequences, which boundaries matter, and what decision the organization must make. It deliberately excludes unverified causes and preferred solutions from the initial statement. Problem definition is a negotiated modeling process, not a neutral preface: managers create a decision-worthy frame by separating observations from explanations, testing boundaries and stakeholders, comparing rival formulations, and defining evidence that could justify reframing. The managerial task is to turn the concept into an evidence system: clarify the decision, expose assumptions, observe outcomes, compare alternatives, and revise action when results disagree. This chapter treats the method as a disciplined operating capability rather than a workshop artifact. It integrates theory, implementation, measurement, failure analysis, ethics, and a field exercise so a reader can use the model while respecting its limits.[s1][s2][s3][s4][s5][s6]
Learning objectives
By the end of this lesson, you will be able to:
- Diagnose when problem definition process can materially improve a business decision.
- Design a defensible evidence and implementation process rather than a presentation-only exercise.
- Select leading, lagging, economic, and quality measures that reveal whether the intervention works.
- Identify analytical, organizational, and ethical failure modes before they cause stakeholder harm.
- Translate an insight into a time-bounded test with ownership, thresholds, and a learning loop.
Foundations: what the concept means
The problem definition process is the disciplined construction and testing of a provisional account of an undesirable situation: what is happening, compared with what standard, where and when it occurs, who experiences consequences, which boundaries matter, and what decision the organization must make. It deliberately excludes unverified causes and preferred solutions from the initial statement.
Foundation 1
A situation does not announce one objectively complete problem. People select features, categories, time horizons, comparisons, and causal boundaries. This framing creates a “problem space” in which some evidence and responses become salient while others disappear. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
Foundation 2
Symptoms, causes, constraints, and solutions must be kept distinct. “Low conversion because sales needs training” blends an outcome, a causal claim, and an intervention. A stronger opening statement locates the observed gap and consequence, leaving explanations available for testing. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
Foundation 3
Stakeholders hold different legitimate problem definitions because they experience different consequences and control different resources. Inclusion is epistemic as well as ethical: frontline workarounds, customer barriers, supplier dependencies, and community effects may reveal system conditions invisible to formal process owners. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
Foundation 4
Boundaries determine accountability and tractability. A frame can be too narrow to include the mechanism or too broad to support action. Productive framing preserves the wider system while defining a decision-sized unit, then states assumptions about what remains outside scope. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
The literature provides complementary rather than interchangeable lenses.[s1][s2][s3][s4][s5][s6] A rigorous practitioner uses those lenses to sharpen observation and decision quality, not to borrow academic authority for a conclusion already chosen. Definitions, samples, methods, and boundary conditions should travel with every important claim.
A decision-ready operating framework
A useful framework must specify inputs, transformation, outputs, ownership, and feedback. The following five-stage system creates that chain while leaving room for the method to be adapted to category, organization, and evidence quality.
1. Describe observations and consequences
Record events, patterns, variation, baseline, desired state, and affected outcomes without causal adjectives. Cite the source and reliability of each observation. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Map stakeholders and perspectives
Identify who experiences, contributes to, controls, knows about, or may be harmed by the situation. Elicit their definitions independently before forcing agreement. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Set and challenge boundaries
Vary unit, geography, customer segment, process stage, time horizon, and system level. Ask what each boundary includes, excludes, enables, and makes someone else responsible for. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Write rival problem frames
Create at least three formulations: operational gap, customer or stakeholder outcome, and system interaction. For each, list predicted evidence and solutions it might privilege. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Select a decision-worthy brief
Choose the frame that is material, evidence-linked, ethically defensible, tractable enough to act on, broad enough to contain the mechanism, and paired with explicit reframing triggers. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
This animated problem-definition funnel shows five stages move from observations and stakeholder perspectives through boundary testing and rival frames to a decision-worthy brief with explicit reframing triggers. The sequence remains fully understandable when motion is disabled.
The stages are iterative. New evidence may change the original question, expose a missing stakeholder, or show that an apparently attractive option is infeasible. Governance should allow the team to return to an earlier stage without describing learning as failure.
Worked example: JeevanSetu, a composite regional diagnostic network
Situation
Missed follow-up appointments rose after the network introduced digital scheduling. The initial brief said “patients resist technology,” leading management toward more reminder messages and mandatory app use. The case is hypothetical and composite; it illustrates a reasoning process rather than reporting facts about any real organization. Management agreed to separate observations, interpretations, choices, and measured outcomes so hindsight could not erase uncertainty.
Case movement 1
Analysts removed the causal label and stated the observation: 28 percent of referred patients in three districts lacked a completed follow-up within fourteen days, compared with 16 percent before scheduling changed. Completion differed by clinic, referral type, language, and booking channel. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 2
Interviews included patients, caregivers, reception staff, clinicians, call-centre workers, and transport partners. Their frames ranged from digital literacy and uncertain costs to unavailable slots, referral-data loss, caregiving constraints, and the absence of a human recovery route. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 3
A boundary exercise moved the unit from “patient app use” to “referral-to-care continuity.” That wider frame included the clinic handoff and slot inventory but remained decision-sized. It also revealed that reminder volume could not create capacity or repair incomplete referrals. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 4
Three rival statements predicted different evidence. The selected brief focused on continuity failures where referral information, accessible booking, confirmed price, and suitable slots did not converge. The team retained language access and patient autonomy as non-negotiable constraints. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 5
A test combined a referral completeness check, reserved follow-up slots, multilingual assisted booking, and an opt-in reminder. Completion improved while unwanted messages fell. A new exception among high-risk referrals triggered reframing rather than being averaged into apparent success. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Interpretation
The case matters because action followed the diagnosed mechanism, not the fashionable label. It also preserved a comparison and a boundary statement. A result in one setting changed the next decision; it did not become a universal law.
90-Day Action Plan
Implementation needs an executive sponsor, a working owner, protected access to evidence, and explicit decision dates. The plan below can be compressed for a small reversible choice or expanded for a regulated, capital-intensive, or high-harm decision.
1. Days 1–15: establish the decision charter
Name the decision, sponsor, working owner, affected stakeholders, current state, desired outcome, constraints, evidence sources, and the date on which action is required. Record what is assumed rather than observed. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Days 16–30: build the evidence baseline
Triangulate process data, direct observation, documents, and stakeholder accounts. Define units and denominators, examine variation and exceptions, and document missing or unreliable evidence before proposing causes. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Days 31–50: create and challenge explanations
Develop multiple causal or systemic accounts, identify the prediction each makes, search for disconfirming cases, and involve people close to the work. Select tests by information value as well as cost and speed. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Days 51–70: run a bounded intervention
Choose a reversible option, specify owner, resources, safeguards, comparison, leading indicators, counter-metrics, stop rules, and escalation thresholds. Preserve the old process where rollback may be necessary. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Days 71–90: decide and institutionalize learning
Compare results with the baseline and rival explanation, review stakeholder effects, decide whether to scale, adapt, stop, or reframe, and archive a decision record that distinguishes evidence from interpretation. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
The plan should connect with Organizing information and ideas into common themes, What is problem solving, Improving solutions by arguing for and against your options, Soft system methodology, Root Cause Analysis and the Strategy learning hub. These links are complementary tools, not substitutes for the evidence required by this decision. At day ninety, write a one-page decision record covering the original premise, evidence obtained, decision taken, result, unresolved risk, and next review.
Measurement and review
Measurement should serve learning and accountability. Establish a baseline, define the unit and denominator, segment outcomes where averages can conceal harm, and choose a review interval that matches how quickly the underlying mechanism can change.
1. Problem-definition stability
Track how often the stated problem changes after evidence review and whether revisions clarify mechanism, boundary, stakeholder, and desired outcome rather than merely changing language. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Evidence quality
Rate coverage, provenance, recency, reliability, missingness, triangulation, and the number of serious rival explanations that have been tested rather than dismissed. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Decision-cycle performance
Measure elapsed time from signal to framed decision, time spent waiting for information or authority, experiment cost, rework, and the proportion of decisions revisited on schedule. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Outcome and mechanism
Measure the operational result and the nearer mechanism expected to produce it. Report baseline, denominator, variation, comparison, confidence, and whether the effect persisted beyond the test. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Stakeholder and resilience counter-metrics
Monitor safety, workload, fairness, privacy, accessibility, customer harm, supplier burden, reversibility, unintended consequences, and recurrence after apparent resolution. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
The boundary audit distinguishes symptom, comparison standard, affected stakeholder, chosen scope, and evidence that would require the team to redefine the problem.
Avoid a dashboard in which every number rises when activity rises. Include outcome, quality, economic, and counter-metrics. Predefine a threshold that triggers investigation or stopping, and retain qualitative evidence that explains why the number moved.
Failure modes and corrective action
The most dangerous errors are often organizational rather than technical: incentives reward certainty, a senior sponsor prefers one explanation, or presentation deadlines arrive before evidence. Treat the following patterns as control failures with observable warning signs.
1. Solving the presented symptom
Urgency makes the first description feel authoritative. The warning sign is a solution embedded in the problem statement; correct it by separating observation, consequence, suspected mechanism, and proposed response. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Single-story certainty
A coherent explanation crowds out alternatives. Watch for evidence collected only to confirm one cause; require rival hypotheses, disconfirming evidence, and an explicit confidence level. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Workshop without decision rights
Teams generate maps and ideas but no authorized owner can alter the system. Define authority, resources, decision dates, escalation routes, and the artifact that commits action before convening. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Activity mistaken for outcome
Meetings, ideas, tickets, and training completions rise while the underlying failure persists. Pair activity indicators with mechanism, outcome, recurrence, and harm measures. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Premature standardization
A promising local result is converted into a universal procedure. Test transfer conditions, preserve local feedback, stage the rollout, and specify circumstances that require adaptation or rollback. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
Run a pre-mortem before launch and an after-action review after the first decision cycle. Record near misses, not only visible failures. A healthy team can say that an attractive hypothesis was not supported and redirect resources without reputational punishment.
Ethics, limits, and responsible use
Business usefulness does not excuse deception, avoidable harm, or unsupported inference. The method should be proportionate to the decision and reviewed more carefully when it affects employment, credit, health, safety, privacy, or access to essential services.
Responsibility 1
A problem-solving process must not turn uncertainty into a pretext for surveillance, retaliation, or blame. Protect confidential reporting, separate learning from discipline, and give people affected by a decision a safe route to challenge the evidence and proposed remedy. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Responsibility 2
Analytical elegance does not justify shifting costs onto workers, customers, suppliers, or communities with less power. Map who receives the benefit, who bears risk, whose knowledge is excluded, and what accessible remedy exists when the intervention causes harm. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Responsibility 3
Collect only data proportionate to the decision, document purpose and retention, restrict access, and test whether proxies reproduce structural disadvantage. When employment, health, safety, credit, or legal rights are involved, obtain qualified review and preserve due process. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Responsibility 4
Models simplify reality and therefore create blind spots. State assumptions, uncertainty, scope, and reversibility; distinguish a test from a settled conclusion; and stop when evidence of harm, invalid measurement, or an unrepresented stakeholder makes the original design unsafe. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Limits should be written into the decision record: population, context, time, method, uncertainty, and the conditions under which the conclusion should be revisited. Do not imply individualized legal, medical, financial, or employment advice.
Practice Checklist and Laboratory
Implementation Checklist
- [ ] The audience, decision, accountable owner, and intended value are explicit.
- [ ] Material claims have traceable evidence, sources, limits, and correction ownership.
- [ ] The plan includes a baseline, comparison, primary outcome, cost, and stakeholder counter-metric.
- [ ] Consent, privacy, accessibility, safety, legal, and platform obligations have been reviewed.
- [ ] Stop, escalation, remedy, and after-action review rules are documented before launch.
Complete the exercises with a live but reversible decision. Preserve artifacts so another reviewer can inspect how you moved from evidence to recommendation.
Exercise 1
Take one current operational complaint and write four separate statements: observed condition, consequence, plausible mechanism, and proposed solution. Ask a colleague to mark every word that assumes a cause not yet demonstrated. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Exercise 2
Construct an evidence ledger for the decision with columns for claim, source, method, date, scope, reliability, disconfirming observation, and responsible reviewer. Remove any claim that cannot support the decision being asked of it. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Exercise 3
Design the smallest safe test that distinguishes the two most credible explanations. Specify comparison, duration, sample or cases, expected signal, counter-metric, stop rule, owner, and what each possible result would mean. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Exercise 4
Facilitate a thirty-minute red-team review with someone affected by the proposed change. Record the strongest objection, hidden cost, missing stakeholder, and condition under which the intervention should not proceed. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Finish with a decision memo: “We believed… We observed… We now infer… We will test… We will stop or revise if…” This format makes uncertainty actionable and creates an organizational memory stronger than a polished retrospective.
Key takeaways
- Problem definitions are models that select boundaries, comparisons, stakeholders, and evidence. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Begin with observed gaps and consequences; keep causes and proposed solutions explicitly provisional. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Rival frames reveal hidden assumptions and the interventions each wording privileges. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Stakeholder inclusion improves knowledge and fairness because consequences and mechanisms are distributed. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- A useful boundary contains the mechanism while remaining connected to an authorized decision. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Every problem brief needs a reframing trigger when new evidence contradicts its assumptions. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
Mastery means choosing the method for the decision it can improve, using evidence at the level it supports, and changing course when the world contradicts the model.
References and further reading
The sources below establish the conceptual and methodological foundation. Publication details and locators have been retained so editors can verify every material attribution before publication.
[s1] Donald A. Schön. “The Reflective Practitioner: How Professionals Think in Action.” 1983. https://www.basicbooks.com/titles/donald-a-schon/the-reflective-practitioner/9780465068784/
[s2] Horst W. J. Rittel and Melvin M. Webber. “Dilemmas in a General Theory of Planning.” 1973. https://doi.org/10.1007/BF01405730
[s3] Kees Dorst. “Frame Innovation: Create New Thinking by Design.” 2015. https://mitpress.mit.edu/9780262328845/frame-innovation/
[s4] Jacob W. Getzels. “Problem Finding and the Identification and Development of Talent.” 1982. https://eric.ed.gov/?id=ED210907
[s5] Jonathan Rosenhead. “Problem Structuring Methods in Action.” 1996. https://doi.org/10.1057/jors.1996.95
[s6] Richard O. Mason and Ian I. Mitroff. “Strategic Assumption Surfacing and Testing: A Participative Method for Organizational Planning.” 1981. https://doi.org/10.1002/smj.4250030208
