Builder Cohort Canvas

Cohort intent

The Builder cohort is not a generic advanced training track. It is a small investment in people who can package reusable capability for a department.

Cohort setup

| Field | Answer | | --- | --- | | Cohort dates | | | Departments in scope | | | Number of Builders | | | Executive sponsor | | | Manager sponsors | | | Tooling available | | | Data and compliance constraints | | | Required shipped artifact | |

Builder selection

| Candidate | Department | Domain leverage | Judgment | Manager support | Technical comfort | Workflow idea | Decision | | --- | --- | ---: | ---: | ---: | ---: | --- | --- | | | | | | | | | |

Score each candidate 1-5. A strong Builder does not need to be the most technical person. They need domain leverage, good judgment, and a workflow other people will actually use.

Cohort rhythm

| Week | Focus | Builder output | | --- | --- | --- | | 1 | Workflow selection | One-page workflow spec | | 2 | Prototype | Prompt, command, skill, script, SOP, or tool draft | | 3 | Pilot | Tested with 3-5 real users | | 4 | Package | Reusable asset, usage notes, review rules, owner |

Graduation standard

A Builder graduates when they ship a reusable workflow that:

• Solves a real department problem.
• Has clear inputs and outputs.
• Has review gates and forbidden actions.
• Is used by people other than the Builder.
• Has a named owner for maintenance.
• Has at least one adoption metric.