<aside> 📈 Expand takes what worked in the pilot and scales it carefully. New contexts introduce new variables.
</aside>
Objective: Determine whether your solution transfers to a new context, and what adaptations are needed if it does not. Expanding is not copying.
When to use: Before every expansion deployment. Start with the Quick Pass; go deeper only if "Different" ratings appear.
Inputs: Pilot documentation (what worked, what assumptions it relied on), new context profile (users, workflow, volume, integrations, constraints), access to someone who knows the new context.
Position: Architect owns assessment. Domain experts provide context knowledge.
How to fill out: One row per candidate context. Rate each of the 5 dimensions (Users, Workflow, Volume, Integrations, Constraints) as Same, Similar, or Different against your pilot. Document gaps and make a Go/No-Go/Go-with-changes decision.
<aside> ⚠️ All Same or Similar? Replicate unchanged. Any Different? Investigate before deploying. Wingman's Phoenix failure happened because they treated a "Different" workflow as "Similar."
</aside>