Can eight teams launch on the same green status?
Align a shared interface, its consumers and the decision owner.
“identifying dependencies and technical risks that affect their teams.” (opens the source)
The question
Northstar is replacing a shared identity interface used by eight product teams. An AI-generated status digest marks all eight teams green because their local feature tests pass. The programme release gate covers consumer compatibility, not only local completion.
| Local tests pass | Shared contract tests pass | |
|---|---|---|
| Teams A–F | 6 | 6 |
| Teams G–H | 2 | 0 |
The rows count teams. Six plus two is the full set of eight.
Every consumer must pass the shared contract suite against the same proposed interface version. The identity lead owns interface compatibility; each consumer lead owns its test evidence.
“State what is ready, who must act and what evidence permits the shared release.”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Read the shared gate
What would you do here? Open the move you’d make.
Hold the shared launch pending both consumer results.
The strong move. Local completion and cross-team compatibility answer different questions.
Treat eight green team updates as full compatibility.
Tempting, but it misses something. Local tests do not prove that all eight consumers accept the shared interface.
See how a strong candidate says it
“All eight teams pass local tests, but only six of eight pass the shared contract suite: 75% consumer coverage. The programme has not met its release gate.”
Why it works: Local completion and cross-team compatibility answer different questions.
Step 2: Name the handoff
What would you do here? Open the move you’d make.
Set one interface version and named test owners.
The strong move. A dependency needs a supplier, a consumer and evidence of acceptance.
Ask the AI digest to use a more cautious colour.
Tempting, but it misses something. A different status colour does not provide the versioned contract or consumer test results.
See how a strong candidate says it
“The identity lead must publish the versioned interface and test contract. G and H must run it and return results. I would record each owner, result and next check in the programme plan.”
Why it works: A dependency needs a supplier, a consumer and evidence of acceptance.
Step 3: Reopen the decision
G passes the shared suite. H fails because it still sends the retired field. No tested way to isolate H from the shared release is available.
What would you do here? Open the move you’d make.
Hold the shared launch until H passes or tested isolation is approved
The strong move. Progress does not waive a gate, and isolation is not yet established.
Launch all eight because the average has improved.
Tempting, but it misses something. H still fails the shared contract, and no tested isolation plan permits a partial launch.
See how a strong candidate says it
“Seven of eight consumers now pass, or 87.5%. H still fails. I would defer the shared launch or seek an explicit, tested isolation plan approved by the release owner.”
Why it works: Progress does not waive a gate, and isolation is not yet established.
Step 4: Give a useful escalation
What would you do here? Open the move you’d make.
Escalate the specific dependency and required decision.
The strong move. Escalation should secure a decision or a missing commitment.
Replace the blocked date with an unconfirmed estimate.
Tempting, but it misses something. An unconfirmed date does not resolve H’s failed test or secure its owner’s commitment.
See how a strong candidate says it
“I would tell the sponsor which customer commitment is at risk, who owns H’s fix and when the next test result is due. I would not give a new date until H’s owner confirms the fix and test plan.”
Why it works: Escalation should secure a decision or a missing commitment.
The answer, in short
- Decision
- Keep the shared launch gated.
- Because
- One consumer remains incompatible with the proposed interface.
- What would change it
- A passing H result, or an approved and tested isolation design, would permit a new release decision.
Common traps
- Averaging team colours.
- Treating a dashboard as an accepted handoff.
Check your answer
- I separated local and shared tests.
- I counted all eight consumers.
- I named supplier and consumer owners.
- I revised the decision after new evidence.
Last reviewed Nov 10, 2026