Priority labels cost nothing, and anything that costs nothing gets spent recklessly. At first you mark three things P1. Within three weeks, every request that matters to somebody turns up already stamped urgent, and you’re left with the list you always had plus an extra column. The scale didn’t break because people abused it. It broke because nothing in it was scarce.
A priority only means something if it displaces something: a slot, a day, another task’s place in the queue. That’s why the number of levels makes no difference, whether you have three, four or five. Two other things matter far more, and hardly anyone applies them to their own list. The first is an entry test, written down in advance, that someone else can check: a fact a colleague could confirm (“someone outside my team is blocked right now”), not “this is really important”. The second is a cap: one P1, three open P2s. When something new comes into a level that’s already full, something else has to go, and you say so out loud.
That’s the trick. The scale stops being a ranking and becomes a trade-off everyone can see. When someone hands you an “urgent” request, you no longer argue about the label. You ask one question: what moves? And if a P2 hasn’t moved in two weeks, it was never a P2. It either gets a real date or it goes, because it’s almost always avoidance dressed up as a deadline.