An urgency scale is an agreed and explicit definition of levels of urgency and priority for requests between units, for example normal, urgent and very urgent, with clear response times for each level. Omri Gefen presents it as a simple solution to one of the most painful issues in interfaces: the clash between my tasks and the requests of those who need me. The definition creates a clear procedure and a shared language instead of constant struggle.
This article is based on the book "The Power of Collaboration: From Ego-System to Eco-System" by Omri Gefen, in which he opens the discussion with a sentence every manager knows: "The issue of priorities is a painful one, raising tension in many interfaces."
Why is an urgency scale needed?
A role holder in one unit wants to help another unit, but the request does not always fit the tasks and priorities set by their own managers, especially in a world of many tasks and limited resources. Omri Gefen notes that "The dilemma between our tasks and the tasks of others who rely on us occurs on a daily basis and is often unresolved." In this built-in conflict, the question is how the partners conduct themselves: in constant war, or in constant and reciprocal communication, with interim solutions and compromises.
When there is no shared definition, each side defines "urgent" according to its own feeling. What is very urgent to one is routine to the other. And this gap turns into disappointment, escalation and suspicion.
How do you build an urgency scale?
The most common definition is simple: three levels, normal, urgent and very urgent. The terms and time ranges vary from organization to organization according to its tasks. In hospitals, in interfaces between departments, the definitions will be in minutes. Some organizations define the levels in colors: red, yellow and green.
Omri Gefen gives an example from a bank, where many difficulties and crises arose in the interface between business client managers and the legal department, because of gaps in understanding levels of urgency. Working together, they defined that the most urgent level requires a response within 24 hours at most, the second level within three working days, and the third within eight working days. According to Omri Gefen, "This clarity helped to significantly improve internal collaboration and provide better solutions for customers."
Why is it important to build the scale together?
Because a scale dictated by one side will be perceived as that side's tool. The power of an urgency scale comes from both sides defining it together, understanding each other's constraints and committing to the same language. In his work with senior management teams and in complex processes within and between organizations, Omri Gefen sees that simple definitions like these, which look technical, remove much of the tension that builds up in interfaces. They do not resolve every dispute, but they take the unnecessary disputes off the table. We expanded on how to manage the disputes that remain in the article on conflict management in organizations.
How to start in practice
It is worth choosing one interface and asking.
When the other side writes "urgent" to me, what do they actually mean? And do I know?
How many of my requests to others are marked urgent, and how many of them really are?
Have we ever sat together to define what counts as normal, urgent and very urgent, and how quickly we respond?
And what happens when I have no solution to the dilemma: do I go to war, or to a conversation?
Frequently Asked Questions
What is an urgency scale?
An agreed definition of levels of urgency for requests between units, usually three levels, with a clear response time for each.
How are the response times defined?
Together with the other side and according to the nature of the tasks. In the bank Omri Gefen describes, 24 hours, three working days and eight working days were set. In hospitals the definitions are in minutes.
Does an urgency scale resolve all the tension in an interface?
No. It removes misunderstandings about urgency, and leaves room for conversation about the real dilemmas.
About the Author
Omri Gefen is a leading organizational consultant to CEOs and senior management teams. He founded Gevim Group and served as its CEO for more than two decades. He specializes in complex processes within and between organizations, including interfaces between the business, public, security and social sectors. His areas of expertise are collaboration, trust, negotiation, mediation and consensus building. He heads negotiation training in the Lahav Executive Program at Tel Aviv University, previously taught at Reichman University and Ben-Gurion University, and developed the Effective Collaboration Architecture (ECA) model. Omri Gefen is the author of "The Power of Collaboration: From Ego-System to Eco-System" (Routledge).
Organizations that want to reduce tension in interfaces and build a shared language for priorities are welcome to learn about Omri Gefen's way of working on the consulting page of the website.