Frameworks Don't Prioritise. Behaviours Do. (4/6)

This is the fourth in a 6-part series on the behaviours that make prioritisation actually work. Catch up on earlier parts: Part 1, The "No, Not Yet" Muscle | Part 2, Urgency Is Not Importance | Part 3, The Art of the Challenge.

The Issue: The initiative you're most passionate about might be the one your business can least afford right now.

Over the last three weeks, I've covered the confidence to say "not yet," the compass to filter urgency from importance, and the discipline to hold the line when priorities drift. Each of those behaviours is hard. But they all share one thing in common, they assume the person in the room can look at the data objectively.

This week is about what happens when they can't.

Every leader, founder, CEO, COO, department head, has an initiative they're emotionally invested in. Maybe they conceived the idea. Maybe they championed it to the board. Maybe the team has already invested significant time and budget. Whatever the source, the attachment is real. And when the data suggests that initiative should be parked, the emotional response often overrides the strategic logic.

This isn't a founder-only problem. I've seen it at every level of leadership. And it's one of the most difficult prioritisation behaviours to navigate, because you're not just challenging a business case. You're challenging someone's identity.

What I see everyday: Data that gets ignored because the emotional investment is too deep.

The pattern is predictable. A senior leader champions a new capability. They've invested time building the case. They've socialised it internally. They've mentally committed to delivering it. And then the prioritisation process surfaces an uncomfortable truth, other initiatives have a stronger ROI, a clearer strategic link, or a more pressing deadline.

Instead of accepting the data, the leader pushes back. They reframe the initiative. They challenge the methodology. They escalate. Not because the data is wrong but because letting go feels like admitting the idea wasn't good enough. Or worse, that the time and budget already invested was wasted.

In that sense, the sunk cost amplifies the emotional attachment. The more that's been invested, the harder it becomes to park, even when parking is clearly the right strategic call.

A real example, anonymised. I worked with a C-suite member who was championing a new SaaS capability. They had conviction. They had energy. They had support from parts of the business. But when we pressure-tested it against the portfolio, two things became clear.

First, there were higher priority initiatives directly tied to a major product launch in a new category. These touched customer experience, pricing, and legal compliance. The data on ROI was unambiguous. These had to come first.

Second, and this was the harder conversation, the new capability was designed to support a process that didn't exist yet. We had no data on volume. We had no data on what the process actually needed to look like. We were being asked to invest in a technology solution for a problem we hadn't yet measured.

That conversation didn't happen once. It happened multiple times. The C-suite member kept revisiting it, not because they were being difficult, but because they genuinely believed in the initiative. Each time, I brought the discussion back to the agreed priorities, the data, and the trade-offs. Each time, with empathy but consistency.

What finally shifted the conversation wasn't saying "no." It was building a bridge.

The turning point came when we stopped talking about why not now and started talking about what instead, and what needs to happen to revisit this. Together, we brainstormed how to bridge the gap at product launch without the SaaS tool. We brought in temporary staff to manage the process manually. This gave the business real operational data, actual volumes, actual process steps, actual pain points, that would inform whether the SaaS investment was justified after launch.

Critically, we also agreed on the specific conditions for revisiting the initiative. Not "we'll look at it later." A clear trigger: "After the product launch, once we have X weeks of operational data, we review."

That combination, an interim solution plus a clear re-entry point, gave the leader confidence that their initiative wasn't being killed. It was being parked with intention. And that distinction made all the difference.

What needs to happen: Apply the same discipline, with greater empathy, and revisit until it lands.

Navigating emotional attachment requires the same tools as Parts 1-3, data, trade-off visibility, and the confidence to challenge. But it demands something extra: empathy and patience.

Here's how I approach it:

1. Acknowledge the investment. Before challenging, validate the work that's gone into the initiative. "I can see the thinking behind this. The business case has merit." This isn't flattery, it's respect. A leader who feels heard is far more likely to accept a "not yet" than one who feels dismissed.

2. Separate the idea from the timing. The initiative might be genuinely valuable, just not right now. Frame the conversation around sequencing, not rejection. "This could absolutely be the right move, once we have the data to confirm the approach. Right now, the portfolio says these other outcomes need to come first."

3. Make the sunk cost visible, without blame. If significant time or budget has been invested, name it. "We've invested X in this so far. The question isn't whether that investment was right, it's whether continuing to invest right now delivers more strategic value than redirecting that capacity." This reframes sunk cost from an emotional anchor to a data point.

4. Build the bridge together. Don't just say "not yet." Co-create the interim plan. "If we can't do this right now, what's the lightest-touch way to bridge the gap?" Whether that's temporary resource, a manual workaround, or an MVP experiment, the leader needs to see a path forward that doesn't feel like abandonment.

5. Define the re-entry trigger, and honour it. Agree on specific, measurable conditions for revisiting the initiative. Then, and this is critical, actually revisit it when those conditions are met. Nothing destroys trust faster than a "not yet" that quietly becomes a "never."

Expect to revisit the conversation. This won't land the first time. Or the second. Emotional attachment doesn't dissolve in a single meeting. Be prepared to have the same discussion, with the same empathy, the same data, and the same consistency, multiple times before it sticks.

Tip of the week: Identify your own blind spot.

Before you look for emotional attachment in others, check yourself. Ask honestly:

• "Is there an initiative on my roadmap that I'm protecting because I believe in it, rather than because the data supports it?"

• "If a colleague presented this initiative to me fresh today, with the current data, would I approve it?"

• "What would need to be true for me to park this and am I open to that possibility?"

If the answer to question two is "Probably not", you've found your blind spot. And the willingness to acknowledge it is the most powerful prioritisation behaviour of all.

Next week in Part 5: ROI Isn't a Spreadsheet Exercise, using data to make prioritisation decisions stick.

• 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