Skip to content
GitHub

Roll out across an enterprise

Widen adoption one stage at a time, with a named owner deciding at each step.

Start with one pilot, then widen to team waves and the whole organization, with a named owner deciding at each stage.

Ask your agent to check the pilot with you before you begin:

Help me prepare a pilot for a task the participant already knows and can verify in minutes. Ask me to confirm the rollout track, reads and writes, human controls, artifact recipient, measures, rollback, and stop condition before we begin. Do not widen the rollout until the named owners accept the stage evidence.

The agent asks for each item until the pilot is fully described. Choose the track from who takes part: technical for engineers and technical product managers, enterprise for clients working with a forward-deployed engineer, and non-technical for knowledge workers and designers.

Four roles hand work forward in order: the champion, the CTO or executive sponsor, the platform team, and the people who use the workflow. Each accepts the handoff by name, and none accepts another role’s decision. Each stage ends with a decision record, and you review it with them:

Review this stage decision with the sponsor, platform owner, and participants. Challenge missing evidence, then return exactly one verdict without widening the recorded scope.

The verdict is stop, revise, hold, or advance, and advance covers only the scope written in the record. The enterprise rollout playbook has the checklist, the fields for each stage, and the record templates.

Next, import and curate skills.