Agency operations workshop / 5 MIN READ
Escalate the decision, with enough context to make it
Give the responsible leader a clear choice, consequence and decision deadline.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A useful escalation explains why the current team cannot resolve an issue and what authority is needed next. It preserves the work already done so the next person can decide without reconstructing a long dispute.
What you will leave with: A concise escalation brief with facts, options, consequences and a requested decision.
Use this when
- Two teams remain blocked after a reasonable attempt to resolve an issue.
- A deadline depends on authority the project team does not hold.
This is not a route for bypassing mandatory reviewers, making accusations or shifting routine responsibility upward.
Identify the decision that exceeds your authority
Atlassian’s clean-escalation guidance supports clarifying options and trade-offs at the appropriate decision level. State the specific choice that remains blocked.
Explain why the current owners cannot settle it: conflicting commitments, missing authority or a trade-off affecting another team. Distinguish a decision problem from a question that simply needs factual investigation. If you have not yet asked the responsible counterpart for clarification, do so unless the issue’s urgency or sensitivity requires an immediate specialist route.
Summarize the facts and prior attempts
Provide the current agreed plan, the material change or conflict and the steps already taken. Include source links or records the recipient can access, but avoid forwarding a sprawling thread with no synthesis. Separate verified facts from assumptions and disputed interpretations.
Use neutral language about people and teams. “The venue confirmation remains unresolved” helps the decision; “the partner never cooperates” adds an allegation without clarifying the choice. Share sensitive details only with the appropriate recipients. An escalation should make the issue understandable without unnecessarily widening access to private information.
Present workable options and consequences
Describe a small set of realistic choices and what each would change. Include the effect on customer promises, timing, scope and any necessary approvals. State which option you recommend and why, while leaving the decision-maker able to choose differently.
Give a real decision deadline tied to consequences. If the date passes, explain what becomes impossible or which default action is already authorized. Do not create artificial urgency to force agreement. Where no safe default exists, say so. A decision-maker needs to know both the cost of acting and the consequence of waiting.
Close the loop after the decision
Confirm the chosen option, conditions and responsible owner. Tell the affected teams what changes in their work through the agreed route. Keep formal approval separate where the escalation decision does not itself authorize spending, contract changes or publication.
Update the working plan and close the escalation only when the decision is operationally clear. If new facts invalidate the choice, return with the changed evidence rather than repeating the original argument. Review recurring escalation patterns later to find missing authority or unclear agreements, without turning every issue into a leadership meeting.
Make the reasoning concrete.
A fictional campaign team cannot secure an approved venue by the last practical booking date. One team wants to delay; another wants to switch to a smaller online session.
Forward the argument
Opening: Send leaders the full email thread and ask them to resolve it urgently.
Hypothesis: All prior discussion is technically available.
Risk: The decision and practical consequences remain buried.
Prepare a decision brief
Opening: Summarize the venue gap, viable alternatives, implications and final decision point.
Hypothesis: The authorized leader can choose with relevant context.
Risk: Additional approvals may still be needed to execute the chosen option.
The leader selects the online format subject to the required supplier changes. The project owner updates the plan and sends the specific implications to the affected teams.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Choice
What decision cannot be made at the current level?
Facts
What is verified, assumed or disputed?
Attempts
What has already been tried to resolve it?
Options
What changes under each realistic choice?
Deadline
What consequence makes a decision necessary by this point?
Watch for the wrong conclusion.
- Escalating a thread without identifying the decision.
- Using blame to make an issue seem more urgent.
- Treating a leadership preference as every required execution approval.
Your next action
Rewrite one blocked issue as a choice between realistic options and state the exact authority needed to resolve it.
Sources & scope
The workflow, worksheets and hypothetical examples are original editorial analysis. Sources support only the identified principles. No measured business results or named human reviewer are claimed.
- Atlassian Team Playbook: Clean Escalations →Primary framework-publisher guidance · Supports: Escalation can clarify options and trade-offs for the appropriate decision level; the campaign brief is original analysis.