Stress-test an intake form rewrite by proving that each required field and routing rule can place work inside the planned lane, survive override pressure, and avoid trapping operators inside a green form slide that hides long-lived exceptions.
Intake rewrites often list a field count while leaving routing behavior, override authority, and abort ownership implicit. Those edges decide whether a late sales ask stops inside the queue or leaves a promise live under customer load. The exercise should follow actual forms, ticket tools, and on-call paths rather than a clean UX deck.
Inventory the intake path
List every form or intake type with its required fields, routing rule, override behavior, owners, and notification channels. Mark paths that cannot reverse without a manual ticket edit. Attach the last three intake incidents with raw timelines and any waivers. Include the source of truth for open ticket counts during the observation window.
Define the phases for schedule, cutover, observe, abort, and communicate. Each phase needs an owner and an exit condition. Write the point after which a stuck intake would require a different procedure, then review whether that action is still permitted. Capture maximum acceptable requester friction in measurable units, including which cohorts are excluded from the new form and why.
Include the calendar of known events for the next two quarters: sales kickoffs, partner cutovers, and support peaks that shrink the usable change window. An intake budget that ignores those dates will look calm until the week they land.
Failure drills
- A minority high-revenue ask keeps a side-channel while the aggregate form dashboard stays green.
- A rewrite has already left a partner request without a lane.
- The primary ticket dashboard lags beyond the planned observation window.
- An operator skips required fields because a renewal is close.
- Bug and feature forms collide under the new routing rule.
- Abort authority is unclear at quarter end and the page lands on the wrong rotation.
For each drill, identify detection time, customer impact, containment, and the authority to force a form rollback. Require commands and dashboard links in the runbook. A statement that monitoring will catch it does not establish which alert fires or who receives it.
Prove intake changes are timed and owned
Run the package in Pingpong with product ops, sales, support, and engineering seats. Ask sales which customer decision becomes unsafe first if intake still drops requests after the claimed window. Ask engineering whether capacity can absorb a forced override. Ask product ops to show the exact form version or routing export used as the exit condition.
Related reviews include the product ops lead seat, a backlog grooming cadence review, and a priority score model review. Browse the war-game decisions hub for adjacent controls.
Authorize the published form only after a timed drill restores usable intake hygiene inside the documented budget without an undocumented manual step.