Part 2: Urgency Is Not Importance, How the Loudest Voice Hijacks Your Roadmap

This is the second in a 6-part series on the behaviours that make prioritisation actually work. If you missed Part 1 on building the "No, Not Yet" muscle, start here.

The Issue: "Urgent" has become the magic word that bypasses every process you've built.

There's a pattern I see in almost every scaling business. A senior stakeholder flags something as urgent. The energy shifts. The team scrambles. Existing priorities get quietly pushed aside. And by the time the dust settles, nobody stops to ask the question that should have been asked at the start: "Was this actually urgent, or did it just feel that way?"

Urgency is one of the most powerful forces in business. It overrides logic. It bypasses governance. It compresses timelines without compressing scope. And when left unchecked, it becomes the single biggest hijacker of an otherwise solid roadmap.

Last week, I talked about the "No, Not Yet" muscle, the behavioural foundation of good prioritisation. This week is about the compass that tells you when to use it. Because distinguishing urgency from importance requires questioning. And saying "No, not yet" requires confidence in those questions. The two behaviours are inseparable.

What I see everyday: Panic masquerading as priority.

A real example, anonymised.

A stakeholder requested a new SaaS tool ahead of a product launch. The ask was framed as critical. The timeline was tight. The pressure was real. But when I dug deeper, the product was launching in a completely new category, meaning there was zero data to show the demand for the capability the tool would provide. We didn't know if customers would need it. We didn't know the volume. We were about to commit budget, integration effort, and team capacity to solve a problem that might not exist at scale.

Instead of rushing the implementation, we brought in temporary staff to handle the process manually. This gave the business time to measure actual demand and make a data-informed decision about whether the SaaS investment was justified. The "urgent" request turned into a deliberate, sequenced decision, and the team didn't burn a single sprint on something that hadn't earned its place on the roadmap yet.

This pattern plays out constantly. A stakeholder has conviction. They have seniority. They have a deadline in their head. But when you ask "What evidence do we have?" the room goes quiet. And that quiet is where the most expensive priority shifts happen, not because the work is wrong, but because nobody questioned whether now was the right time.

In that sense, the damage isn't just the time spent on the task. It's the behavioural precedent it sets. When urgency is determined by volume rather than evidence, your team learns to react to emotion instead of strategy. And that erodes trust in the prioritisation process faster than any framework can rebuild it.

What needs to happen: Ask better questions before anything enters the pipeline as "urgent."

The single most effective behaviour I introduce is brutally simple: before any request is treated as urgent, it must survive three questions.

• "What is the measurable business impact if we don't do this today?" Not this week. Not this quarter. Today. If the answer is "Nothing changes immediately" then it's important, but it isn't urgent. It can be prioritised through the normal process. This question alone eliminates the majority of false urgency I see.

• "What is the specific deadline and why does that date matter?" If someone says "We need this by Friday" but can't explain what happens on Saturday if it isn't done, the deadline is artificial. Real urgency comes with a real consequence attached to a real date, a regulatory deadline, a contractual obligation, a system outage impacting revenue. Everything else is preference disguised as pressure.

• "What evidence do we have that justifies the priority shift?" This is where the SaaS example lives. The stakeholder had conviction but no data. A new product category with no demand data doesn't justify an urgent technology investment, it justifies a measured experiment. Evidence turns an emotional escalation into a rational conversation.

These three questions aren't designed to block work. They're designed to protect the work that's already been agreed as the priority. When a genuinely urgent request survives all three, it absolutely should jump the queue, and the team will respect that because they trust the filter.

A note on the leader's role.

This is especially important for founders and senior leaders. The energy you bring to a request sets the tone for the entire organisation. If you escalate with panic, the team absorbs that panic, even when the situation doesn't warrant it. Over time, your team stops distinguishing between "Leadership thinks this is urgent" and "This is actually urgent." Everything becomes a fire drill. And when everything is urgent, nothing is prioritised.

Lesson learned: the behaviour you model at the top cascades. If you want your team to prioritise calmly and strategically, you need to demonstrate that same discipline, especially when an external voice or a board question triggers the instinct to react immediately.

Tip of the week: Audit your last three "urgent" requests.

Look back at the last three times something was escalated as urgent in your business. For each one, ask:

1. "What was the measurable business impact of not doing it that day?"

2. "Was there a real deadline with a real consequence or was the pressure emotional?"

3. "Did we have evidence to justify the priority shift or did we react to the loudest voice?"

If two out of three don't survive the test, your urgency filter has a leak. And that leak is costing you more than time, it's costing you your team's trust in the process.

Next week in Part 3: The Art of the Challenge, reminding folks what was already agreed and holding the line when priorities start to drift.

• Curious about how we could work together? Book a 20-mintue intro call - no pitch, just pattern matching.

helen.beckford@felicetteconsultancy.com 
www.felicetteconsultancy.com | www.linkedin.com/in/hebeckford