Resource
Department Builder Workflow Scorecard
People Opsintermediate20 minclaudecodex
Workflow shortlist
| Workflow | Department | Frequency | Leverage | Repeatability | Risk | Data access | Adoption pull | Total | | --- | --- | ---: | ---: | ---: | ---: | ---: | ---: | ---: | | | | | | | | | | |
Score each category 1-5.
Scoring guide
Frequency
How often does this workflow happen?
- 1: rare
- 3: weekly
- 5: daily or always-on
Leverage
How many people benefit if this works?
- 1: only the Builder
- 3: a pod or team
- 5: a full department or customer-facing motion
Repeatability
How standard is the workflow shape?
- 1: every case is different
- 3: repeatable with judgment
- 5: highly structured
Risk
Can the workflow be governed?
- 1: high-risk with unclear review
- 3: manageable with review gates
- 5: low-risk or easy to supervise
Data access
Can the Builder access the source material needed?
- 1: blocked
- 3: partial access
- 5: readily available
Adoption pull
Will the department use it?
- 1: no clear demand
- 3: some pain
- 5: obvious pain and manager support
Recommendation
- 24-30: build now.
- 18-23: pilot if risk is controlled.
- Below 18: defer or redesign the workflow.