Cross-team unblocking protocol

The outcome

The outcome of the cross-team unblocking protocol is a repeatable path through this question: How should teams resolve a dependency or disagreement locally before escalating? The working view makes issue, shared facts, and bilateral discussion visible so discussion can move from general opinion to a specific action or decision.

When to run it

Run the cross-team unblocking protocol when work in team development repeatedly crosses the same stages or handoffs and variation is causing delay, rework, or unclear ownership. Focus the first version on issue, shared facts, and bilateral discussion rather than documenting every possible exception.

How the process works

The cross-team unblocking protocol is a controlled sequence with explicit entry conditions, stages, handoffs, outputs, and exit criteria. Its core working elements are issue, shared facts, bilateral discussion, and options. Those elements belong together because each changes how the others should be interpreted or acted on.

Process stages

1. Issue

Capture issue only at the level needed to answer: How should teams resolve a dependency or disagreement locally before escalating? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the cross-team unblocking protocol, connect this entry to shared facts so the relationship can be reviewed rather than inferred.

2. Shared facts

Capture shared facts only at the level needed to answer: How should teams resolve a dependency or disagreement locally before escalating? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the cross-team unblocking protocol, connect this entry to bilateral discussion so the relationship can be reviewed rather than inferred.

3. Bilateral discussion

Capture bilateral discussion only at the level needed to answer: How should teams resolve a dependency or disagreement locally before escalating? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the cross-team unblocking protocol, connect this entry to options so the relationship can be reviewed rather than inferred.

4. Options

Describe credible alternatives on the same basis so that benefits, costs, risks, dependencies, and reversibility can be compared fairly. Within the cross-team unblocking protocol, connect this entry to explicit request so the relationship can be reviewed rather than inferred.

5. Explicit request

Capture explicit request only at the level needed to answer: How should teams resolve a dependency or disagreement locally before escalating? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the cross-team unblocking protocol, connect this entry to escalation so the relationship can be reviewed rather than inferred.

6. Escalation

Capture escalation only at the level needed to answer: How should teams resolve a dependency or disagreement locally before escalating? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the cross-team unblocking protocol, connect this entry to decision so the relationship can be reviewed rather than inferred.

7. Decision

Name the decision, the person or body with final authority, the date, and the rationale that should remain visible later. Within the cross-team unblocking protocol, connect this entry to follow-up so the relationship can be reviewed rather than inferred.

8. Follow-up

Write a concrete next action with one owner, a due date or trigger, and a visible completion condition. Within the cross-team unblocking protocol, connect this entry to decision so the relationship can be reviewed rather than inferred.