Useful blocker escalation.
Put impact, attempted actions and the actual decision in one packet.
The everyday problem
An escalation without attempted actions or downstream impact creates another round of questions.
TestingStill blocked
Actions triedEvidence attached
Illustrative workflowHuman decision
The project owner reviews evidence and decisions before changing the agreed plan.
- 01
Input
Testing: Blocked: test account missing; Actions tried: Requests D2 / D3; Rehearsal D5: Who can authorise access?
- 02
Give instruction
Escalate this blocker with the right context.
- 03
Agent works
T-409 / Test-account blocker
- 04
Human decision
The project owner reviews evidence and decisions before changing the agreed plan.
Expected impact
Put impact, attempted actions and the actual decision in one packet.
What to measure
Escalation clarification rounds; time to an accountable decision.
SME
The project owner reviews evidence and decisions before changing the agreed plan.
Enterprise
Confirm the relevant teams, source permissions, licensed modules and review owners during scoping.
ProjectOSIllustrative workflows. Tool availability, access and configuration require validation.