G Generate.
Generate is the third SAGE phase (formerly Execution). With the FD approved at Gate B, Generate turns the plan into built software. Unlike Situation and Assess, Generate doesn't use BEARINGS worksheets — it uses blueprints, sprints, and cutover artifacts.
The four stages of Generate
1. Blueprint
The blueprint is the detailed technical design handed from Assess to the delivery team. It's signed off before Sprint 0 so the build starts from a shared picture.
2. Sprint 0
Sprint 0 is setup: environment provisioning, UAT script creation, wire-frames for any undecided UI, and the release/rollout plan draft. No production build yet — just the scaffolding the team will work inside.
3. Delivery sprints
Design → Build → Test → Review, repeated across however many sprints the scope requires. Work moves through Epics, Features, User Stories, and Story Actions. Problems and alignments surface through the TAP Log; decisions land in the decision log; weekly touchpoints keep the program honest.
4. Cutover readiness
The final stage before go-live. UAT is finalized, training materials are built, the rollout plan is locked, and rollback/monitoring plans are written down before anyone needs them.
Artifacts
- Blueprint package (technical design at the right depth)
- UAT scripts and wire-frames (Sprint 0)
- Working increments per sprint + demo evidence + release notes
- Training materials and rollout plan
- Rollback / monitoring plan
- Execution Exit Gate approval record (Gate C)
Exit criteria: Gate C
Generate ends at Gate C — the Execution Gate, which approves go-live. Nothing ships to production without Gate C. The next phase is E Embed, which verifies the benefits the program claimed it would deliver.
Duration
Typical duration: 4–16 weeks, depending on scope. Small enhancements may ship in a single delivery sprint; large rollouts can run many sprints across quarters.