The Issue: Individual discipline is powerful. But it's not enough to protect your roadmap at scale.

Last week, I shared a post about Steve Jobs and his belief that focus is about saying "no." It resonated, 30k impressions and counting. But the comments were just as revealing as the engagement. One commenter argued that Apple and Google have sometimes said "no" too aggressively, killing promising directions and frustrating developers and consumers. Another raised AWS as a counterpoint, a bold "yes" that didn't fit Amazon's core business but became one of the most transformative technology decisions in history.

Both points are valid. And both prove something I've been building toward over the last six weeks of this newsletter: the behaviour of saying "no" is essential, but without a system and supporting behaviours around it, it's inconsistent, personality-dependent, and fragile.

If you've been following my 6-part series, Frameworks Don't Prioritise. Behaviours Do. , you'll know I've spent the last six weeks unpacking the human behaviours that make prioritisation stick: the confidence to say "not yet," filtering urgency from importance, challenging drift, navigating emotional attachment, reframing ROI, and getting creative with delivery. Link to series.

Those behaviours are the foundation. But here's the question I want to pose this week: what happens to those behaviours when the person driving them is on holiday, in a different meeting, or moves on from the business?

That's where governance comes in. Not governance as bureaucracy. Governance as the system that makes good prioritisation behaviours sustainable at scale.

What I see everyday: Strong leaders holding the line... Alone.

The pattern is common. A strong COO or a confident Head of IT learns to say "no" with data. They filter urgency brilliantly. They challenge drift in real time. The roadmap holds. Delivery accelerates. Everyone benefits.

Then they step out of the room.

And within a week, a senior stakeholder has reopened a parked initiative. A "quick win" has jumped the queue without anyone asking what it displaces. A vendor has quietly shifted the roadmap to suit their release cycle. The behaviours that were protecting the plan were tied to a person, not embedded in a system.

In that sense, individual discipline without organisational governance is a single point of failure. It works brilliantly until it doesn't. And scaling businesses cannot afford to have their strategic delivery dependent on one person being in every room.

The AWS lesson: Even bold "yes" decisions require disciplined "no" decisions elsewhere.

The AWS counterpoint from my post is worth examining. Yes, AWS was a bold bet. Yes, the ROI wasn't shaped when it was first prioritised. But here's what's often overlooked: AWS could only be delivered because Amazon was saying "no" elsewhere. The capacity, focus, and strategic bandwidth to pursue something that ambitious only existed because other initiatives weren't competing for the same resources.

And here's the question nobody asks: had someone said "no" to AWS earlier in the pipeline, is there another programme that could have been approved and yielded an even greater return? We'll never know. That's the inherent tension of prioritisation, every "yes" carries an opportunity cost. The goal isn't perfect decisions. It's disciplined ones.

Even more revealing, a commenter shared that at Amazon, a manager reportedly cannot say "no" to an initiative unless they write a paper explaining why. That's governance. Not a committee. Not a 40-slide approval process. A simple, disciplined mechanism that forces rigour around the decisions that matter. It doesn't kill innovation, it ensures that every "no" is evidence-based and every "yes" has earned its place.

But, and this is critical, needing to provide a reason to say "no" or "yes" and document it only works if it's supported by the right prioritisation behaviours and culture. And the people providing those reasons must have the capacity to do so. A governance mechanism that requires thoughtful documentation becomes another ignored task if leadership is too stretched to engage with it.

That's the kind of system I'm talking about. Lightweight. Configurable. But deliberate.

What needs to happen: Build the escalation paths that protect your behaviours at scale.

When I bridge prioritisation behaviours into governance, the first thing most businesses notice is missing is a clear escalation path. They've learned to say "not yet." They can challenge drift. But when two legitimate priorities genuinely compete, and the data supports both, there's no defined route for making the call.

Without an escalation path:

• Contested priorities linger in limbo while leaders avoid the uncomfortable conversation.

• The loudest voice or the most senior title wins by default, regardless of strategic alignment.

• Teams lose confidence in the process because they can see that "political" decisions still override "data-driven" ones.

Here's what a lightweight governance system looks like when it's designed to protect, not slow down, your prioritisation behaviours:

• Clear decision rights. For every level of priority decision, someone is named as the owner. Not a committee. A person. With a defined timeframe to make the call. If they don't, it escalates automatically.

• A visible escalation path. When two priorities compete and the data supports both, where does the decision go? This needs to be defined before the conflict arises, not negotiated in the heat of the moment. A simple, two-step escalation (initiative owner → executive sponsor → COO/CEO) covers 90% of cases.

• A decision log with rationale and expiry. Every significant prioritisation decision, "yes," "no," or "not yet", gets logged with a one-line rationale. This does two things: it creates accountability, and it prevents the same decision from being relitigated every fortnight. Decisions that are time-bound get an expiry date for review.

• Scale governance to the stage of the pipeline. Not every decision needs the same level of rigour. An early-stage idea that doesn't align to business strategy should be filtered quickly, a lightweight "does this fit?" check that takes minutes, not hours. A large programme midway through delivery with significant sunk costs needs a deeper review before it's stopped or continued. Where a request sits on the demand-to-delivery pipeline should determine how much detail is required. This prevents two equally damaging problems: wasting senior time documenting reasons to reject ideas that were never viable, and failing to stop a costly programme because nobody had the governance mechanism to challenge it.

• A cadence that doesn't add meetings. Governance doesn't need a new meeting. It needs a rhythm embedded into existing forums. A 15-minute prioritisation check at the start of your existing leadership meeting. A monthly portfolio review added to an existing SteerCo. The system fits into your pace, your pace doesn't bend to the system.

• Protection that outlasts any individual. The ultimate test of governance is this: if the person who's been driving your prioritisation discipline left tomorrow, would the system hold? If the answer is no, you don't have governance. You have a strong individual carrying the load.

Tip of the week: Map your escalation path for contested priorities.

Before your next leadership meeting, draw a simple two-step escalation map:

1. When two priorities compete, who makes the call at initiative level?

2. If that person can't resolve it within 48 hours, who does it escalate to?

3. What data must accompany the escalation? (Portfolio view, ROI comparison, capacity impact)

4. What's the maximum time allowed before a decision is made?

Pin it to the wall. Share it with your leadership team. And the next time a contested priority arises, use it. If the path feels clunky, refine it. If it works, you've just built the first piece of governance that protects your prioritisation behaviours at scale.

Lesson learned: Steve Jobs was right, focus is about saying "no." But Jobs didn't say "no" alone. He built a culture, a system, and a set of decision-making structures that made "no" sustainable across an entire organisation. That's the difference between individual discipline and organisational governance. And it's the difference between a roadmap that holds when you're in the room and one that holds when you're not.

I work directly with leadership teams to facilitate alignment, challenge the behaviours that undermine good prioritisation, and build governance structures that fit a fast-moving business, not a corporate playbook. My approach is embedded, not advisory-from-a-distance.

Curious how your business scores on prioritisation and governance? Take my 3-minute leadership quiz to find out where your strengths are and where the blind spots might be hiding. Take the quiz here.

• 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