Reconciling Conflicting Needs and Acceptance Boundaries
6 min read
Lesson objectives
- Reconcile conflicting needs into separate registration and dispatch acceptance boundaries.
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.
Listing stakeholders does not resolve conflict between their needs. In the pump-maintenance service, a resident wants to lodge a report quickly, a field crew wants a reliable location before travel, and the service manager wants the centre to avoid a backlog of incomplete reports. These needs can be met at different points in one case journey: accept a report, triage it, and release a work order after the safety information is complete. The central distinction is between permission to enter a process and permission to advance to a consequential step. If both decisions share one accept button, the service either loses a potentially important report or sends a crew with inadequate information. NASA's decision-analysis guidance supports comparing alternatives against explicit criteria; the weights and thresholds in this teaching case are local assumptions, not rules prescribed by NASA.
Start a needs register that names the stakeholder, harm if the need is ignored, available evidence, and any condition that cannot be traded away. Rank neither a request nor its owner automatically. Ask the person for a situation in which the service fails, then separate the need from a proposed means. Send every report straight to the crew is a proposed means; avoid losing an urgent report is a need. Reject every report without a location is another means; avoid sending a crew without a usable location is the underlying need. The design can retain an incomplete report for human triage without issuing a field order. This separation lets us specify an acceptance condition for each transition and trace it to the need, requirement and test taught in earlier lessons.
Define the denominator and observation period before comparing numbers. Suppose a fictional training week produces 50 reports, 15 without a reliable location. Alternative A rejects those 15. Alternative B keeps each with a pending-location state and contacts the reporter, sending a crew only when details are complete. If 12 locations are completed, B retains a follow-up route for all 15 and may release 12 after triage; the other three do not become work orders automatically. Completion among initially incomplete reports is 12÷15=80%, while the share of all reports needing completion is 15÷50=30%. Those denominators answer different questions. One invented week cannot establish the same result in another city or during a network outage. Collect operational evidence and review delay and privacy risks before setting a product threshold.
Turn the chosen policy into three separate acceptance boundaries. The service accepts an initial report when it stores a unique case number and a follow-up route or agreed alternative channel, even if its location remains unverified. Once the location meets the triage procedure, it issues a work order and records it as issued, awaiting acknowledgement; issue does not mean the crew received it. Mark the order received and permit travel only after crew acceptance matching the order identifier and version. If acknowledgement is missing, keep a named owner and escalation time for the pending state; do not automatically issue another order. Test report retention, the block on issuing without a location, and the travel block before acknowledgement separately. Training figures must not silently become formal product limits; the service owner must agree privacy, safety and operational constraints before final requirements are approved.
Lesson summary
Balance retaining a report with protecting the field crew; define follow-up, dispatch and conflict-resolution authority.