One of the leaders I was coaching was dealing with a challenge that will sound familiar to many senior leaders. The expectations were continuing to increase, resources were constrained, timelines were not moving, and the message from above was the usual “find a way to do more with less”.
This leader was not only responsible for their own work. They were leading other leaders, which meant every new expectation had a ripple effect across multiple teams. A change in priority at the top that will create additional pressure several levels down.
They were trying to protect delivery, maintain quality, support their leaders, and remain responsive to senior stakeholders. At the same time, they were becoming increasingly aware that simply absorbing more work was not a sustainable answer.
As we talked, I was reminded of something I had learned many years earlier in project management training: the project management triangle. The traditional triangle connects three constraints: scope, time, and cost or resources. The basic idea is simple. When one side changes, at least one of the others usually needs to change as well.
If the scope increases, the project may need more time or more resources. If the deadline moves forward, the scope may need to narrow or additional capacity may be required. If the budget or team size is reduced, then expectations around scope, timing, quality, or risk may also need to be reconsidered.
It is a familiar project management concept, but I had not thought about it in a while. In that coaching conversation, however, it became immediately relevant.
I drew a triangle and asked the leader to map their current situation against it.
The scope of work was growing. The timelines were becoming more aggressive. The resources available to deliver the work were staying the same and, in some areas, decreasing. At the same time, the expectation was that the quality of the outcome would remain unchanged.
Once we put it on paper, things started to open up.
We talked about the triangle as though it represented a fixed area. If one side became longer, the other sides would need to adjust if the area of the triangle was going to remain the same. It was not a perfect technical interpretation of the model, but it gave the leader a simple and useful way to visualize the problem.
The organization could increase the scope, but that would likely require more time, more capacity, or a change in the expected quality or level of risk. It could hold the deadline, but then it might need to reduce what was being delivered or provide more resources. It could keep resources fixed, but then not every priority could remain equally important.
The triangle helped shift the conversation away from exasperation and toward choice. Instead of simply repeating that the team was overloaded, the leader had a way to show which constraint had changed and which trade-offs now needed a decision.
Many leaders respond to increasing expectations by trying to make everything fit. They work longer hours, become more involved in the details, ask their teams to stretch, and delay difficult conversations about capacity. That can work for a short period. But over time it is not sustainable and the impact shows up in other places, usually the ones you don’t want it to be!
For leaders of leaders, the hidden cost is even greater. When senior leaders absorb more and more work themselves, they may unintentionally reduce the space their own leaders have to make decisions, build judgment, and take ownership. The organization may still appear to be delivering, but it becomes increasingly dependent on a small number of people holding everything together.
The triangle gave this leader a more neutral way to talk about the situation. A couple of things came up, instead of pushing back on a new request, they could ask, “If this becomes the new priority, what should move down the list?”
Or they could ask, “What level of quality or risk are we prepared to accept if we deliver within this timeframe?”
That helped them reframe the request in front of them.
The triangle also helped the leader separate constraints that were genuinely fixed from those that were simply being treated as fixed.
Sometimes a deadline truly cannot move. Sometimes the scope is tied to a regulatory, client, or business requirement. Sometimes additional resources are not available. But it is rare that every element is completely immovable.
The coaching conversation became more about options: Could the work be phased? Could a lower-value deliverable be delayed? Could they clarify what “good enough” looked like for an interim release? Could another initiative be paused to create capacity?
After the session, the leader continued to use the triangle as a practical tool for new requests and difficult priority conversations.
They used it with senior stakeholders to make trade-offs more visible, but they also used it with the leaders who reported to them. Instead of passing pressure directly down the organization, they could help their leaders think through what had changed and what needed to adjust as a result.
A leader of leaders is not only responsible for making trade-offs at their own level. They also shape how those trade-offs are understood and managed throughout the organization.
When senior leaders do not make choices clearly, teams are often left to make them informally. Different groups start protecting their own priorities. Work gets delayed without being officially deprioritized. Quality standards vary. People work around capacity constraints instead of discussing them directly.
The trade-offs still happen, but they happen inconsistently and often without the right people being involved. A simple visual can help bring those choices back into the open.
The project management triangle worked because it helped to visualize the issue and bring it back to basics. It helped give a clear way to explain that increasing expectations without adjusting time, resources, scope, quality, or risk was still a choice.
It is easy to become the messenger who tells others that the team is overloaded. It is more effective to help stakeholders understand the options, implications, and decisions required.
For example, rather than saying, “We cannot deliver this,” a leader might say:
“We can deliver the full scope by the current deadline, but it will require additional capacity.”
“We can meet the deadline with the current team, but we will need to reduce or phase the scope.”
“We can keep the scope and resources as they are, but the timeline will need to move.”
“We can attempt to hold all three, but we should be explicit about the quality, execution, and sustainability risks.”
These are all more clear and give your stakeholders something they can respond to.
That was what made the triangle so useful in this coaching engagement. It gave the leader a straightforward way to articulate what they were already experiencing but had found difficult to explain.
More scope, less time, and fewer resources may all be possible for a period. But something will adjust. The question is whether leaders choose what adjusts, or whether the impact eventually appears somewhere they did not intend.
Sometimes the most useful coaching tools are not new. They are simple ideas we return to at the right moment and apply in a different way.