Compromise is unavoidable in project and operations management , but unmanaged compromise destroys trust, burns out teams, and derails delivery. The difference between high-performing organisations and struggling ones is not fewer trade-offs, but better trade-offs and better communication around them.

I call this the Doughnut Rule.

The Doughnut Rule is a practical framework for making trade-offs visible, intentional, and value-driven across delivery, stakeholders, and team capacity. It helps you find the “sweet spot” where outcomes are maximised without quietly overloading teams or constantly disappointing sponsors.

For project managers, operations leaders, and executives, this is how you turn compromise from a hidden liability into a repeatable management practice.

Why Trade-Offs Hurt More Than They Should

Most organisations already live inside a permanent trade-off: limited time, limited budget, and unlimited expectations. The pain comes from how these constraints are handled.[wcu]

Common failure patterns:

Silent trade-offs

Work is quietly de-scoped, quality is cut, or teams stretch evenings and weekends to hit dates. Leadership sees green status reports until something breaks.

Negative framing

Trade-offs are communicated as loss: “We have to drop this”, “We can’t do that”, “We don’t have capacity.” Stakeholders feel blocked or short-changed.

Capacity denial

Planning assumes 100% availability, ignoring meetings, support, and context switching, even though sustainable capacity for knowledge work is closer to 60–70% of nominal hours.

Silent trade-offs
Work is quietly de-scoped, quality is cut, or teams stretch evenings and weekends to hit dates. Leadership sees green status reports until something breaks.
Negative framing
Trade-offs are communicated as loss: “We have to drop this”, “We can’t do that”, “We don’t have capacity.” Stakeholders feel blocked or short-changed.
Capacity denial
Planning assumes 100% availability, ignoring meetings, support, and context switching, even though sustainable capacity for knowledge work is closer to 60–70% of nominal hours.

When trade-offs are invisible or framed as defeat, you get resentment, disengagement, and eventually burnout. The Doughnut Rule exists to prevent exactly that.

The Doughnut Rule, Explained

The Doughnut Rule reframes compromise from “what we are losing” to “what we are optimising for right now.”

A better question

Instead of asking

“What are we cutting?”

→

You ask

“Which outcome are we optimising in this phase — speed, scope, quality, learning, or risk?”

The framework has three layers: delivery fundamentals, stakeholder priorities, and communication and perception.

IThe framework has three layers:

Core (the dough) – Delivery fundamentals
Scope, timeline, budget, resources, and quality standards. This is the classic project triangle, but explicit, not assumed.
Ring – Stakeholder expectations and business priorities
What matters most to whom: revenue, time-to-market, risk reduction, compliance, customer satisfaction, internal efficiency.
Glaze – Communication and perception
How decisions are framed, how trade-offs are explained, and how people feel about the process.

Most teams live only in the core. Good project managers manage the ring. The best leaders actively design the glaze, they understand that the same decision can either damage trust or deepen it, depending on how it is communicated.

How to Use the Doughnut Rule (Step by Step)

Here is where we add real value: a concrete way to apply this in your next project or steering meeting.

1. Make the trade-offs explicit

Before you talk tasks, talk priorities.

Ask stakeholders:

“If we have to optimise for one thing in this phase, what is it, time, scope, quality, or risk?”
“What is non-negotiable, and what is flexible?”

You can borrow a simple technique from trade-off workshops: list key dimensions (scope, schedule, cost, quality, risk) and ask stakeholders to rate each from 1 (most flexible) to 5 (least flexible). Misalignment shows up very quickly when one person puts “scope” as a 5 and another puts it as a 1.

2. Model capacity honestly

Then bring in reality.

Map planned work against sustainable capacity, not theoretical capacity. Sustainable capacity for knowledge workers is often closer to 25–30 hours of focused work per week once meetings and overhead are included.
Visualise this: show the team’s real weekly hours, then show how much is already reserved for BAU, support, and meetings.

This is where the Doughnut Rule adds “bite”, you are not just saying “we’re busy”; you are demonstrating the trade-off surface: “Here is what we can genuinely do without degrading quality or burning people out.”

3. Reframe constraint as optimisation

Now you connect the two: priorities and capacity.

For example, instead of saying:

“We can’t deliver all features by end of quarter.”

Use Doughnut framing:

“Given we are optimising for time-to-market this quarter, we will deliver the 5 highest-value features by end of quarter, and schedule the remaining 3 for the next release.”

You are not apologising for constraints; you are showing how you are using constraints to optimise for agreed priorities.

Concrete scripts you can use:

Scope vs timeline:
“To keep the deadline, we will keep features A, B, and C which drive 80% of the value, and move D and E to the next phase. Does that match what we said we’re optimising for?”
Capacity vs quality:
“At current staffing, we can either keep the date and accept higher defect risk, or push the date by two weeks and maintain our quality standard. Which outcome are we optimising for?”
New request mid-sprint:
“We can absolutely do this, but it means dropping X or Y from this sprint. Which one is less critical to our current objective?”

This gives PMs and ops leaders real language they can deploy tomorrow.

4. Communicate decisions in context, not isolation

Every decision should answer three implicit questions for stakeholders:

What did we optimise for?
What did we consciously trade off?
How does this protect or increase value?

For example:

“We optimised for regulatory compliance for this release, which meant trading off two UI enhancements. This protects us from delay penalties and keeps the go-live on track.”

You are teaching your stakeholders to see decisions through a value lens, not a feature list.

What Executives Get Out of This

For C-level leaders, the Doughnut Rule is not a soft skill; it is a governance and risk tool.

When applied systematically, it:

Reduces hidden risk
Trade-offs are documented, not buried in late nights, quiet scope cuts, or “heroic” efforts.
Improves predictability
Capacity is treated as a hard constraint, not an endless buffer. That leads to more realistic plans and fewer last-minute surprises.
Strengthens stakeholder trust
Decisions are framed transparently: “We chose X over Y for these reasons.” That reduces political tension and alignment noise across departments.
Protects talent
By challenging the planning fiction of 100% utilisation, you actively design for sustainable performance instead of running teams into the ground.

In other words, you get better delivery, fewer crises, and teams that don’t burn out simply because nobody would admit the trade-offs early.

The Human Side (Plus Actual Doughnuts)

At the end of the day, this is about people.

Anyone can present a Gantt chart.
A competent project manager explains the “why” behind changes.
An effective leader co-creates the trade-offs with stakeholders and protects their teams while delivering on what matters most.

And sometimes, yes, bringing actual doughnuts to a difficult prioritisation meeting helps. It signals: “We’re in this together, we’re going to have hard conversations, and we still respect each other.”

If you want to build this kind of trade-off discipline into your projects or operations, from the way you plan capacity to how you communicate with stakeholders, you can learn more or get in touch at hiliconsulting.eu.

The Doughnut Rule: Turning Compromise into a Strategic Advantage