Do we combine East and West support into one organization?
Combine into one support organization across both sites while keeping both locations open through the transition, and gate the cutover on a tested failover.
| Finance | For | Cash case holds if the lease exit lands in year one. |
| Operations | Against | One queue fails as one queue, and there's no tested failover yet. |
| West lead | For | Wait times are the problem we can't staff our way out of. |
| East lead | Conditional | East absorbs West peaks only after cross-training. |
| Legal | No block | Two notice obligations, and neither stops the call. |
| HR | Against as sequenced | Fourteen roles change, so they hear it before the announcement, not after. |
We're signing a single point of failure for a customer who already waits too long. Show us failover working before the cutover date, not after.Operations seat · kept on the page per R4
- Operations: failover test, as the cutover gate
- HR: role conversations with all fourteen, first
- Finance: lease exit plan
- East lead: cross-training schedule
- The failover test fails
- West wait times rise during cutover
- The lease exit slips past year one
"Customers won't notice the change." was removed under R3, because no seat's file had a source for it.
COO · owns the outcome · if "send back," cite the page