A clinic-registration team on the public-health immunization-registry ART keeps hitting an enterprise identity-provider blocker no team can fix alone. What should the Team Coach do?
Select an answer to reveal the explanation.
Short Explanation
Some clinic blockers the team can move; an enterprise identity wall it cannot. The Team Coach clears the local stuff and escalates the systemic one. That is not a promotion to RTE, and rewriting stories around the wall just hides it.
Full Explanation
When a clinic-registration team on a public-health immunization-registry ART hits an enterprise identity-provider blocker no single team can fix, the Team Coach should clear local impediments the team can influence and escalate the identity constraint as a systemic issue—without taking over train ownership. That dual move keeps registration work moving where possible while making the enterprise wall visible to people who can actually change it.
Personally redesigning the enterprise identity platform so the RTE is no longer needed fails because the coach has left the SM/TC lane and attempted to absorb architecture and train-level ownership. Rewriting clinic-registration stories to pretend the identity constraint does not exist fails because hiding a systemic blocker destroys transparency and leaves residents blocked at registration. Assigning a developer from every ART team into an unofficial identity war room the coach directs fails because it recreates shadow program management and bypasses proper escalation paths.
Exam caveat: escalation is not abdication; the coach still removes what the team can influence while escalating what it cannot. Operational check: inventory local registration impediments and clear them, document the identity-provider dependency for RTE and system stakeholders, stop unofficial war-room staffing by the coach, and verify that clinic registration progress is no longer gated solely on silent workarounds.