---
title: Collaboration and Interfaces
description: Define clear interfaces between partner factory, customer teams, platform operations, and governance bodies for stable wave operations.
sidebar:
  label: Collaboration and interfaces
  order: 2
source_url: "https://framework.stackit.cloud/migration/design-and-mobilize/migration-factory-setup/collaboration-and-interfaces/"
source_file: "docs/migration/design-and-mobilize/migration-factory-setup/collaboration-and-interfaces.mdx"
---

## Objective

Migration waves fail less often when handovers and decision rights are explicit. This page structures
cross-team collaboration so planning, run operations, validation, and cutover remain synchronized.

## Core Interface Layers

<CardGrid>
  <Card title="Customer delivery interface">
    Coordinates business windows, release approvals, outage communication, and acceptance
    checkpoints.
  </Card>
  <Card title="Partner factory interface">
    Handles wave run operations, runbook operations, issue triage, and reporting rhythm.
  </Card>
  <Card title="Platform operations interface">
    Aligns landing zone constraints, IAM controls, networking requirements, and platform readiness.
  </Card>
  <Card title="Governance interface">
    Connects architecture, security, compliance, and release decision forums.
  </Card>
</CardGrid>

## Interface Design Principles

- **Single owner per decision gate**: Avoid shared accountability at go/no-go points.
- **Time-bounded escalations**: Each severity level has a clear owner and response timeline.
- **Evidence-first handovers**: Handover requires documented checks, not verbal status only.
- **Two-speed communication**: Tactical daily flow for squads and strategic weekly flow for leadership.

## Recommended RACI Scope

Use a RACI matrix at minimum for these topics:

- Wave scope approval and change requests.
- Runbook sign-off and exception approval.
- Cutover authorization and rollback trigger authority.
- Incident communication to business stakeholders.
- Post-wave quality review and corrective action ownership.

## Interface Setup Steps

<Steps>

1. Identify all delivery actors and assign a primary owner for each lifecycle stage.
2. Define decision forums (daily operations, wave board, architecture/security board, executive steering).
3. Establish escalation paths with severity definitions, handoff rules, and notification channels.
4. Define communication artifacts (daily wave report, risk digest, cutover brief, postmortem template).
5. Validate the interface model in a rehearsal wave and remove bottlenecks before scale.

</Steps>

## Typical Failure Signals

- Repeated delays at release decisions due to unclear ownership.
- Parallel escalations to multiple channels with conflicting status.
- Runbook checkpoints passed without verifiable evidence.
- Business communication lagging behind technical incident progression.