Operating model stages

Handoff

Package a validated bet, transfer it to an owning team, and support the first 30/60/90 without becoming the owner.

Published

Owner · Director, InnovationUpdated · 2026-07-19

Purpose

Handoff exists so the Accelerator doesn't become the owner. A validated bet without a receiving team is just an interesting demo. This stage transfers the work cleanly — artifact, context, and a bounded support commitment.

Entry: Cleared readiness and owner signed on.
Artifact: Handoff package + 30/60/90 support plan.
Gate: Owned by the receiving team.

The handoff package

Standard shape, every time:

Opportunity brief (the problem, the sponsor, the metric)
Prototype links (live URL, Lovable project, markup.io comment thread)
Prompt library — the prompts that built and iterated the prototype
Validation summary — evidence pack with the decision it supports
Enterprise Readiness review output
Product requirements distilled from the prototype
Delivery recommendations — known risks, integration points, watch items

The 30/60/90 support plan

Onboarding

Day 30

Walk the receiving team through the prototype, prompts, and evidence. Answer questions. Do not take back work.

First iteration

Day 60

Available for one working session on their first meaningful change. Coaching, not implementation.

Retrospective

Day 90

Joint retro. What survived, what didn't, what the next Accelerator should do differently.

Common failure mode

Becoming the shadow owner

The most expensive failure of a handoff is the Accelerator continuing to do the work from the sidelines. If the receiving team can't run without you at day 30, escalate to the sponsor rather than absorb the ownership. Ownership drift kills capacity for the next bet.

Supporting tools

Enterprise Readiness Review output attached to the package.
Project Compass card moved to Handoff, then closed at day 90.