From Decision to Delivery

B&P Perspective
A decision becomes useful when those involved can explain the specific outcome it is supposed to achieve. A phrase like "improving the customer experience" gives the team a general direction, but leaves important choices unresolved. It can be narrowed down to "enabling the customer to complete a specific request without repeatedly navigating between departments." At that point, the relevant process, the required information, and the authority the team needs to act become clear.
Imagine a hypothetical company that wants to reduce delays in processing customer requests. It purchases a new system and tracks the weekly installation progress. The system might be fully installed while the old approval steps remain the same. The team now has evidence of the system's delivery, but still lacks evidence of improvement in the service itself. This difference affects the question that should be asked in the next meeting.
Start by mapping the current path: where does the request begin, where does it wait, who reviews it, and what constitutes its valid completion? Choose a limited change, name a single owner, and agree on the evidence that justifies continuing. The evidence could be processing time, data completeness, or the number of requests returned for correction. The choice is determined by the actual problem, logging the starting point before the experiment so the comparison makes sense.
Make the boundaries of authority visible. There is someone who approves the decision and its scope, someone who coordinates execution, and someone who verifies the outcome. A small team might combine some of these roles, but the distinction between the required decisions must remain clear. If the proposed change exceeds an agreed-upon limit, the execution owner needs a known escalation path, rather than stalling everyone while waiting for undefined approval.
In the next review, start with what has changed and what proves it, then discuss what is blocking the next step. If the expected improvement does not appear, examine the hypothesis, the measurement method, and the intervention itself before increasing commitment. Completing the task is useful information, but it alone does not prove the goal has been met. The examination might reveal that modifying a step in the process or clarifying a responsibility is required before adding another system.
Try this in your next meeting: take a decision from the previous meeting's agenda, and complete the six fields of the tool provided in this issue. If a field remains unclear, making a definitive choice about it should be your next required action step. A shared log helps the team make better decisions and can be updated when the evidence changes, documenting the reason for altering the course.
Process Tool: The Decision Card
Use a six-field card for an existing decision.
- Required Outcome: Describe the change the beneficiary needs.
- Owner: Name the person responsible for coordinating the execution.
- Evidence: Identify a testable metric or deliverable and its source.
- Next Step: Choose an action that tests the most critical assumption.
- Review Date: Set a date to evaluate the evidence.
- Stopping Point: State when the experiment should be suspended or returned to the authority owner.
Place the card in a shared space already used by the team. Start with a limited, authorized experiment, maintaining the necessary controls. In every review, update the evidence and explain the reason for any change in direction.
An Inspiring Snapshot
A useful review closes a clear cycle: we define the outcome, execute the next step, examine the evidence, and then decide again. Place these four stages next to your meeting agenda. When discussion circles without progress, identify the missing stage and assign someone a single step to reconnect it to the rest of the cycle, with a clear date to review what has changed.
Outcome → Next Step → Evidence → Review
More on Topic
Field reading on strategy, governance and delivery, on capital, ventures and technology.


