| name | cross-functional-alignment |
| description | Align multiple functions around a shared outcome by making decision rights, dependencies, commitments, conflicts, evidence, and handoffs explicit without making every team interchangeable. |
Cross-Functional Alignment
Use when product, engineering, design, go-to-market, operations, support, finance, legal, or other functions must coordinate around one outcome.
Procedure
- Define the shared outcome and the evidence that will show it has been achieved.
- Identify the required functions and the smallest capable set of owners; avoid inviting roles that add no decision or deliverable.
- Make decision rights explicit: who owns product behavior, architecture, implementation, quality, launch, commercial, legal, and operational decisions implicated by the work.
- Map dependencies and handoffs, including what each owner needs before starting and what evidence they must return.
- Surface conflicting incentives, timelines, assumptions, or definitions early and route each conflict to the proper decision owner.
- Establish a durable coordination surface for commitments, blockers, artifacts, and decisions rather than relying on memory or chat scrollback.
- Confirm changes to scope or dates with all owners materially affected by them.
- Close the loop by checking that the assembled cross-functional outcome, not just each individual deliverable, satisfies the original goal.
Decision rules
- Alignment does not mean consensus on every detail.
- Respect specialist authority while keeping shared dependencies visible.
- More participants can increase coordination cost without increasing quality.
- Escalate unresolved ownership conflicts rather than letting two roles silently make incompatible decisions.
Quality gate
Alignment is real when the shared outcome, decision rights, owners, dependencies, conflicts, and handoffs are explicit; affected teams are working from the same current commitments; and no critical integration decision exists only in one person's context.
