The email subject line was URGENT: Immediate Alignment Required. Nobody knew what required alignment, but the word urgent appeared twice in the first sentence, and the calendar invitation began in seven minutes. Mara, who was halfway through an actual urgent task involving a delivery arriving at the wrong entrance, closed the shipping form and joined the call. The meeting organizer, Derek, opened by thanking everyone for prioritizing the issue. He then spent five minutes waiting for a participant who had been marked as optional.
When the call finally began, Derek explained that the organization needed a shared definition of urgency. Recently, messages labeled urgent had been receiving slower responses, possibly because the label was being used too often. “This is a serious issue,” he said. “I would call it urgent.” The group waited for him to recognize the trap. He did not. Instead he displayed a slide showing a red triangle, an orange square, and a yellow circle. These represented Critical, Urgent, and Important. Somebody asked where Normal fit. Derek said Normal was being handled in Phase Two.
Mara asked whether the delivery problem could be handled first, since the truck was still waiting and the driver had just called a third time. Derek appreciated her commitment to operational realities but suggested the meeting should remain focused on terminology. “If we can't distinguish urgent from critical,” he said, “how can we respond appropriately?” Mara said the truck could probably provide an answer, since it was accumulating parking fees in real time. Derek noted her comment under Examples for Future Discussion.
The group spent twenty minutes discussing colors. Finance opposed red because it appeared in too many unfavorable charts. Marketing preferred purple because it was less alarming and had recently tested well in a staff survey. Human Resources asked whether people with different visual abilities would be able to distinguish the categories. This was an excellent question, which temporarily halted the proposal to use color as the primary signal. Derek added icons to the slide and promised to circulate a revised deck. No one had yet defined what should happen when a person received an actual urgent request.
At 10:13 the meeting acquired a second meeting. A participant suggested that team leaders should review the definitions privately before they were announced. Derek agreed and scheduled a 30-minute alignment session for Thursday. Then someone said the current discussion might need a working group to examine edge cases. A working group was created, with six members and a rotating chair. Mara was nominated because she had provided a practical example. She declined, pointing out that the practical example was still parked outside. The group recorded her reluctance as a capacity constraint.
The call ended forty-six minutes after it began, having produced a draft escalation matrix and three follow-up meetings. Mara returned to her phone and discovered that the delivery driver had moved to a different loading area after speaking with a security employee who had simply asked where the boxes needed to go. The boxes were already unloaded. The security employee had not used the word urgent. He had used a radio.
That afternoon Derek sent the draft policy. It defined Critical as requiring action immediately, Urgent as requiring action soon, and Important as requiring thoughtful attention. It did not explain what immediately or soon meant, but the document contained attractive colored bands and was therefore considered a significant improvement. At the bottom was an invitation to provide feedback by Friday. The email was marked URGENT. Mara replied with one question: “If something needs to happen now, may I just call the person who can do it?”
Derek's answer arrived the next morning: “Great point. Let's align on this in a short meeting.” Mara placed the email in a folder called Not Actually Urgent, where it joined seventy-three predecessors. The folder was her most organized work product of the month.

