Trigger
What exact event starts the work?
A practical prioritization worksheet
When everything feels connected to the owner, do not start with the fanciest automation or the easiest process to draw.
Start with recurring work where frequency, consequence, and owner dependency overlap. The score is a place to investigate—not an automated diagnosis.
Campaign source reviewed
Compare up to five workflows
Nothing entered here is submitted or saved. Frequency: 1 is rare and 5 is daily or nearly daily. Consequence: 1 is a minor inconvenience and 5 is meaningful operating impact. Owner dependency: 1 means the team can carry it and 5 means it slows, stops, or becomes guesswork without the owner.
| Workflow | Frequency 1–5 | Consequence 1–5 | Owner dependency 1–5 | Priority score | Recent evidence |
|---|---|---|---|---|---|
| Frequency × consequence × owner dependency | |||||
| Frequency × consequence × owner dependency | |||||
| Frequency × consequence × owner dependency | |||||
| Frequency × consequence × owner dependency | |||||
| Frequency × consequence × owner dependency |
After the comparison
What exact event starts the work?
Which role owns the next move?
What must that person know, and where is the current answer visible?
What breaks the normal flow, who can decide, and when must the owner be involved?
What visible condition proves the work is complete and the next promise is owned?
Use evidence
Verify the scores with a recent real example and with the people who do the work. The first improvement might be clearer responsibility, one visible handoff, a trusted information source, a decision boundary, or a small automation.
Review the same operating condition after the test: did owner touches, waiting time, rework, missed handoffs, or customer delay decrease?
A practical next step
Bring the completed map—not an assumed solution—to a focused conversation with Seth Woodall.