Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

How do we know which tickets are really urgent?

You take tickets in the order they land. Fair enough. But you've made the queue your judge, and the queue doesn't judge anything. It just lines things up in a row. So you wait. You wait for a voice to get loud, for a manager to ping, for someone to say 'drop everything.' That is not a system. That is letting other people do your thinking for you, one shout at a time. Here is what you can control, together: the line between urgent and not-urgent. No one handed that line to you from on high. You can write it down, agree on it as a team, and stop waiting for the next escalation to tell you what you should have already known.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The team already knows what a ticket is; what's missing is agreed action, so guidance leads over teaching.
How the two dials adapt to you →
What’s really going on

You cannot read urgency off a ticket. It isn't written there. Urgency is a judgment your team must make before the ticket arrives, not after someone shouts. Sit down together now and write what counts as urgent — whose time it costs, what breaks, who it touches. Decide the rule before you need it.

🔒 What you’ll build togetherUnlock by starting
A moveGather your pod this week and list the last ten escalations — find what they actually had in common.
A moveWrite three plain rules for what counts as urgent, before the next ticket arrives.
A movePost the rules where the whole team can see them, and say them out loud when you triage.
A moveWhen a ticket doesn't fit the rules, tell the person who sent it — don't just quietly bump it up.
A moveReview the rules as a group every month and change what isn't working.
PractiseUrgency Line · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team applies the same standard to every ticket instead of guessing.
  • Fewer surprise escalations, because urgency gets defined before the ticket lands.
  • You can explain to anyone why a ticket was or wasn't treated as urgent.
  • The team trusts the queue again, because everyone helped build the rule.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.