7sc~ |
Driving Complex Decisions | Garrett D Bates
https://garrettdbates.com/driving-complex-decisions
Saved on 2025-09-24 [20355 edays] via garrettdbates.com
Modified 2025-09-25 [20356 edays]
work
https://garrettdbates.com/driving-complex-decisions
Saved on 2025-09-24 [20355 edays] via garrettdbates.com
Modified 2025-09-25 [20356 edays]
work
| Step Number | Step Name | Description | Acceptance Criteria | Maximum Timeframe |
|---|---|---|---|---|
| 1 | Provocation Creation | Driver creates an initial proposal to kickstart discussion | At least one viable solution is documented and ready to share. Sequence diagram between relevant systems created. Driver can defend the proposal against basic inquiry. | 1-2 days |
| 2 | Initial Provocation Shareout | Driver presents the initial proposal to stakeholders | All relevant stakeholders have been briefed on the provocation proposal | 1 day |
| 3 | Provocation Understanding | Driver follows up until stakeholders comprehend the initial proposal | Questions about the provocation have been answered; All stakeholders explicitly confirm they understand the baseline option. | 1-2 days |
| 4 | Stakeholder Brainstorms | Driver facilitates sessions to gather alternatives and input | Every stakeholder acknowledges they understand every option and its corresponding pros/cons. The team has no further options or pros/cons to add to the discussion. Salient points have been written down for future reference. | 1-2 days |
| 5 | Stakeholder Brainstorm Follow Ups | Driver gets insights from subject matter experts and completes data investigations | All stakeholders explicitly confirm there are no outstanding follow ups necessary to make the decision | 2-3 days |
| 6 | Stakeholder Brainstorm Distillation | Driver organizes the teams thoughts and ideas | All options and corresponding pros/cons have been written down in a way that is easily consumable at a glance; distillation provided to the approver | 1 day |
| 7 | Approver Declares Intent | Approver provides a preview of the option they plan to choose | Approver informs the team of what decision they plan on making | 1 day |
| 8 | Approval Fillibuster | Approver facilitates getting feedback from team members before finalizing the decision | All team members acknowledge that the approver adequately understands the full implications of their intended decision | 1 day |
| 9 | Decision Made | Approver makes the final call | Stakeholders informed verbally; execution effectively unblocked | 1 day |
| 10 | Cascade Broadly | Driver documents the decision for broad consumption | Decision recorded in conjunction with approver signature; Link to decision shared with front line engineers | 1-2 days |