Part 3: The Art of the Challenge, Reminding Folks What Was Already Agreed

This is the third in a 6-part series on the behaviours that make prioritisation actually work. If you missed the earlier parts: Part 1: The "No, Not Yet" Muscle [Link] | Part 2: Urgency Is Not Importance [Link]

The Issue: Agreeing on priorities is the easy part. Holding the line is where most businesses fail.

Every leadership team I work with can sit in a room and agree on priorities. The strategic outcomes are clear. The roadmap is aligned. The portfolio is visible. Everyone leaves the session feeling focused and confident.

Then Monday happens.

A founder comes back from a conference with a new idea. A board member raises a question that triggers a knee-jerk initiative. A department head quietly starts scoping work that was explicitly parked two weeks ago. And slowly, sometimes suddenly, the roadmap that everyone agreed on starts to drift.

In Part 1, I talked about building the confidence to say "No, not yet." In Part 2, I covered the compass that helps you distinguish urgency from importance. This week is about the hardest behaviour of all: the discipline to hold the line, repeatedly, even when it's uncomfortable.

What I see everyday: Priority drift disguised as "strategic agility."

Priority drift rarely announces itself. It doesn't arrive as a formal change request. It arrives as:

• "I've been thinking, can we just explore this quickly?"

• "The board mentioned something last week, can we get a view on it?"

• "I know we agreed to park this, but circumstances have changed."

Each of these sounds reasonable in isolation. And sometimes they genuinely are. But when you add them up across a month, the cumulative effect is devastating. The roadmap that was agreed four weeks ago now has three additional workstreams. The team is context-switching. Delivery velocity drops. And the original strategic priorities, the ones that were supposed to move the needle, are quietly slipping because bandwidth has been redirected to the latest idea.

In that sense, the problem isn't that new ideas are bad. It's that every new idea carries a cost that nobody is making visible. And without someone in the room willing to challenge, to remind everyone what was already agreed and what the trade-off is, drift becomes the default operating mode.

What needs to happen: Make the agreed priorities impossible to ignore.

Here's one of the simplest habits I've adopted that makes a disproportionate difference: I keep the agreed priorities open on my laptop at all times. Favourited. Ready to share my screen. Ready to pull up the moment a conversation starts drifting.

It sounds almost too simple. But there is something powerful about a visual reminder of what was already committed to. When a stakeholder raises a new ask, I don't start by saying no. I start by showing them what's in flight. Then I ask three questions:

• "Help me understand, why is this coming up now?" This isn't confrontational. It's curious. Sometimes there's a genuine trigger, a market shift, a regulatory change, a customer escalation. Sometimes the answer is "Someone mentioned it in a meeting." The quality of the answer tells you everything about whether this is a real priority shift or drift in disguise.

• "What happens if we don't do this right now?" This question alone stops the majority of new requests in their tracks. Because when the stakeholder is forced to articulate the consequence of waiting, and that consequence is "Nothing changes immediately", the urgency evaporates. The request might still be valid. But it doesn't need to displace what's already agreed.

• "If we proceed, what are we comfortable deprioritising?" This is the trade-off question that makes the cost visible. Context-switching isn't free. Every new initiative that enters the active pipeline displaces capacity from something else. When you frame it as "We can absolutely do this, but here's what slows down or stops", the conversation shifts from abstract enthusiasm to concrete decision-making.

A note on the emotional reality of challenging.

Let me be honest, challenging stakeholders can be uncomfortable. Especially when the person you're pushing back on is the CEO, the founder, or a board member. There will be frustration. There will be moments where the stakeholder doesn't want to hear it. There will be circular conversations where the same request resurfaces in a different meeting with a different framing.

That's normal. And it's exactly why this behaviour is so rare and so valuable.

Most people avoid the discomfort. They nod. They absorb the new ask. They quietly try to fit it into an already overloaded plan. And the team pays the price in context-switching, slower delivery, and eroded trust in the roadmap.

The art of the challenge isn't about winning an argument. It's about creating a consistent, data-backed rhythm where the agreed priorities are protected by default, and any change to them requires a conscious, informed trade-off. Over time, this consistency builds trust. Stakeholders learn that the process isn't there to block them, it's there to protect the strategic outcomes they already signed up to.

The discipline to hold the line, repeatedly.

Holding the line isn't a one-time event. It's a daily practice. The same stakeholder may raise the same request three times in three different forums. Your job isn't to shut it down, it's to bring the conversation back to the same agreed framework every single time.

"Here's what we committed to. Here's what's in flight. Here's what the trade-off looks like. And here's when we'll revisit this."

The first time you say it, there's resistance. The second time, there's familiarity. By the third time, the stakeholder starts self-filtering, because they know the question is coming and they've already run through the logic themselves.

Lesson learned: the businesses that hold their priorities aren't the ones with the best frameworks. They're the ones where someone, whether that's an embedded consultant, a COO, or a Head of IT, has the discipline to keep the agreed plan visible and the courage to challenge every time it starts to drift.

Tip of the week: Make your agreed priorities physically visible in every meeting.

Before your next leadership or steering meeting:

1. Open the agreed priority portfolio on your laptop or print it. Have it ready before the meeting starts.

2. The first time a new ask enters the conversation, share your screen or slide the page across the table. Don't say no, say "Let me show you what's currently committed."

3. Ask: "Why now? What if we wait? And what moves to make room?"

4. Document the outcome, whether the new ask was parked, approved with a trade-off, or rejected, and share it with the group within 24 hours.

If you do this consistently for four weeks, you'll notice a shift. Fewer ad-hoc requests. Faster decisions. And a leadership team that starts protecting the plan instead of constantly adding to it.

Next week in Part 4: The Founder's Blind Spot, when emotional attachment to a pet project overrides strategic logic.

• 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