Case: Disaster-Response Logistics
Define clear authority, accountability, and operational boundaries when coordinating urgent disaster-response supplies. Identify who can authorize and promise resources, how commitments are verified, and who is responsible for tracking fulfillment. Establish a shared ledger to record requests, available supplies, confirmed commitments, deliveries, and outstanding needs. Assign explicit responsibilities to participating organizations and distinguish requests, offers, reservations, confirmations, and completed deliveries. Maintain separate, traceable records for each information type to prevent confusion and duplication. Prioritize concrete operational reasoning over vague assumptions, and ensure every proposed action respects established permissions and constraints. Prevent duplicate commitments, conflicting allocations, and miscommunication through clear ownership, verification procedures, and transparent status tracking. Align every decision with reliable, accountable, and timely relief delivery.
You now have the whole framework: frame the decision, ask the questions that change the design, split the outcome into branches, model the records, trace the pipeline and workflow, and plan validation.
This chapter runs it end to end on full cases, and the first case stresses the hardest part of a workflow: deciding who is allowed to promise something. The prompt is “Help a regional team coordinate urgent disaster-relief supplies.” A useful answer establishes who can promise supplies, what confirms that promise, and how the coordinator knows the request was fulfilled.
The organizations and rules here are a practice case for interview reasoning, not guidance for running real relief operations.
What should you ask before seeing the case facts?
Preparation guidance recommends this order: clarify the end user and the available data, state assumptions, agree on scope, and then develop a high-level design through dialogue. Begin with the prompt alone. Reserve 10–12 minutes of independent practice, split between this opening attempt and the changed-condition attempt at the end.
Try it as a short mock interview: the interviewer asks for your ranked questions first, then gives you the answers and asks where you would start.
A short mock interview on a disaster-relief prompt. Answer each question as you would out loud; the interviewer gives feedback at the end.
Here's the prompt: "Help a regional team coordinate urgent disaster-relief supplies."
That's all you get for now.
Before you design anything, what three questions would you ask, in order of importance, and what would each answer change in your design?
A published decomposition preparation guide includes disaster-response coordination as a practice category. Its drill covers users, incoming data, workflows, permissions, and a first version.
Here are the consequential questions and the design choices their answers change:
Decision and objective: “Which decision should improve, and who makes it?” The interviewer answers: “One regional coordinator needs to avoid duplicate commitments to approved urgent requests and track accountable fulfillment.” This selects a commitment workflow over a general situation map.
Authority: “Who may commit supplies and confirm receipt?” The interviewer answers: “Supplying partners confirm their own commitments; designated receiving organizations confirm accepted quantities.” A proposed assignment therefore needs separate confirmation evidence.
Approved evidence and connectivity: “Which partner updates may be shared, how current are they, and can the coordinator reach the shared system?” The interviewer answers: “Approved structured exports and authorized manual updates are available. Partner connectivity is intermittent; the central coordination desk is connected.” This supports a shared ledger with visible ...