Find the Decision Behind the Prompt
Identify the decision-maker and the actions they are authorized to take before designing a solution. Clarify the roles of the dispatcher, sponsor, and affected individuals, then define a focused mission that connects desired outcomes to authorized actions. Choose relevant, actionable success measures to evaluate improvements in emergency response times. Distinguish operational measures from broader objectives, avoid unsupported commitments, and make accountability for decisions explicit.
You can now tell a strong answer from a weak one, and the clearest signal was clarifying before designing. The framework starts there. “Help our city improve emergency response” names an outcome, but not the decision that should change or who is allowed to make it. A decision-centred frame connects the mission to an authorized person’s action and to a way of judging whether that action improves. In an interview opening, your goal is a frame that makes those links visible while keeping the unanswered questions in plain sight.
Which decision sits behind “improve emergency response”?
Take the emergency-dispatch brief:
Help our city improve emergency response.
A dispatcher assigning a unit, a planner choosing deployment locations, and a driver choosing a route need different information. Preparation guidance uses this distinction to explain why identifying the decision and its user should precede architecture.
The request alone does not choose among those decisions. Start by resolving that:
Candidate: Which decision should improve, and who makes it?
Interviewer: Focus on the dispatcher assigning an available response unit to an incoming incident under existing dispatch rules.
Candidate: Then the immediate mission is to support that assignment decision, rather than build a general city analytics platform.
The broad outcome is still timely emergency response. The operational endpoint is now specific: an incoming incident receives an assignment from an authorized dispatcher.
That answer changes the frame:
Before clarification: Improve emergency response; decision and actor unknown.
After clarification: Support the dispatcher’s assignment of an available unit to an incoming incident under current rules.
Why isn’t a dashboard the mission?
A requested dashboard, model, or database is an artifact: something the work produces. Its value depends on what someone can do with it in a workflow; requests for apparently similar tools can conceal very different permissions and consequential actions.
A dashboard might eventually help the dispatcher inspect information before assigning a unit. It becomes a defensible proposal only once you explain that contribution. Simply displaying response times does not provide that explanation.
Who requests the work, who acts, and who bears the consequences?
A mission is only half a frame until you know who sits around the decision. The interviewer supplies the rest of the roles: ...