The short answer
When a Department Director demands that you absorb a massive, high-visibility event like a regional summit into an already saturated project portfolio, they are asking you to violate the basic laws of operational physics. Program management bandwidth is a finite corporate resource. You cannot magically generate additional capacity by simply ordering your team to work harder. The Director is attempting to solve their resourcing crisis by dumping the problem entirely onto your desk.
As a Program Manager, your absolute mandate is to guarantee the flawless execution of committed deliverables. If you accept a massive new project without shedding an equal amount of existing work, you mathematically guarantee failure across the entire board. Your team will burn out, deadlines will slip on core projects, and the regional summit will be executed poorly. You cannot allow executive convenience to destroy your department's reliability.
You must firmly reject the premise of infinite capacity. You will aggressively defend your team's operational boundaries by forcing the Director to confront the data. By presenting your current utilization charts and demanding that they explicitly pause an active workstream, you transition the conversation from a dictatorial mandate into a structured corporate trade-off. You must force the Director to manage the portfolio rather than just throwing tasks over the wall.
Why this question is a trap
The trap relies entirely on hierarchical intimidation and the illusion of "synergy." The Department Director is using their senior title to force compliance. They are framing the regional summit as an urgent corporate necessity, implying that any resistance from you indicates a lack of dedication to the company's success. They expect you to eagerly accept the challenge to prove that your program management team is agile and highly capable.
If you agree to absorb the summit without dropping other projects, you assume total liability for the inevitable disaster. When your team starts missing critical milestones on the ERP migration because they are busy booking hotel blocks for the summit, the Director will not accept the blame. They will claim that you should have managed your time better or raised a flag earlier. You will be penalized for failing to deliver the impossible.
Furthermore, capitulating to this demand trains the Director that your capacity planning is entirely fake. They will learn that your baseline portfolio is just a suggestion and that applying enough executive pressure will always open up more free labor. Your team will become a dumping ground for every abandoned project in the department. You must establish an unbreakable mathematical boundary to protect your staff from chronic exploitation.
What most people say
Most program managers panic when confronted by a director's direct order. They try to find a dangerous compromise to avoid saying no. They say something like, "We are already at maximum capacity with the Q3 portfolio, but I know the summit is really important. Let me ask the team to put in some overtime this month, and we will try to juggle the logistics alongside our other deliverables, but some things might slip a little bit."
This response is an absolute failure of operational leadership. By agreeing to "juggle" the work, you validate their reckless demand. Asking your team to work overtime proves that you manage by brute force rather than strategic prioritization. Warning that things "might slip a little bit" is a weak, useless hedge. When a critical project fails, the Director will hold you accountable, ignoring your vague warning. You have surrendered your authority and doomed your team's morale for absolutely nothing.
What to say instead
"We cannot absorb the regional summit without compromising our core operational bandwidth. My team is currently operating at ninety-five percent utilization across four critical Q3 deliverables. If you want us to execute the summit logistics, you must formally authorize pausing the internal software migration project today, freeing up the required three hundred hours of program management capacity."
This script is a flawless execution of capacity defense. You begin with a direct, uncompromising refusal based on physics. Stating clearly that you cannot absorb the summit stops the demand instantly. You do not ask for permission to hold the line. You correctly define the consequence: compromising your core operational bandwidth. You raise the conversation from a simple scheduling issue to a severe risk management warning.
You then immediately deploy the objective data. By citing "ninety-five percent utilization" across "four critical Q3 deliverables," you prove that your refusal is based on math, not laziness. You show the Director that you know exactly what your team is doing at all times. You strip away their ability to argue that your team just needs to work faster.
Finally, you deliver the executive solution that completely neutralizes the threat. You do not just say no. You dictate the exact process required to get to yes. By identifying a specific project (the internal software migration) and quantifying the exact time required (three hundred hours), you force the Director to make a hard trade-off. You make them own the decision. If they want the summit, they must officially sign off on delaying another project. You replace their dictatorial demand with a structured business choice.
The phrase to anchor on
Compromising our core operational bandwidth.
How to deliver it
Deliver this response with the absolute, unshakable calm of a flight controller denying a landing clearance. Your tone must project complete professional detachment and total operational control. Do not sound angry that they tried to dump a massive project on you, and do not sound intimidated by their title. Treat the interaction as a routine enforcement of project management mathematics.
Maintain direct, unwavering eye contact with the Department Director. When you cite the ninety-five percent utilization rate, speak slowly and deliberately. You want the operational weight of that metric to land heavily in the room. When you outline the requirement to pause the software migration, keep your voice entirely neutral. You are not challenging them to a fight. You are simply stating the physical reality of resource allocation.
Mistakes that cost you the room
The most fatal mistake is offering to do the summit logistics yourself to spare your team. Throwing yourself into the trenches to book caterers and manage event schedules proves that you are a tactical coordinator, not a strategic program manager. You must protect your own executive bandwidth just as fiercely as you protect your team's bandwidth. A manager who does the work of three people is failing to manage the portfolio.
Another critical error is debating the actual importance of the summit. Do not say, "I really don't think this summit is as important as our current projects." You will lose a subjective argument about corporate priorities with a senior director. Anchor entirely on the capacity constraint and the required trade-off alignment. Let the Director decide which project is more important, but insist they only pick one.
Finally, do not ask your team if they think they can handle it. You are the Program Manager. You own the capacity model. Asking the team proves you have no control over your own workstreams and opens the door for junior staff to volunteer for burnout just to please a senior leader. You must be the ultimate authority on what your team can deliver safely.
Practice plan
First, meticulously update your department's resource utilization dashboard today. You cannot enforce a capacity boundary if you do not have a documented system that tracks exactly how many hours are committed to each project. Ensure you have the structural data to back up your words instantly.
Second, practice the transition from the hard refusal to the required trade-off. You must sound entirely comfortable telling a senior director that their new idea kills an old idea. Record yourself delivering the script until the cadence sounds effortless and entirely devoid of emotional friction.
Finally, run the drill in the Talk Rightly studio. Focus heavily on keeping your facial expression completely neutral. When a Director makes an aggressive demand for free labor, any sign of anxiety or frustration will invite them to push harder. You must train your body to remain perfectly still under pressure, projecting absolute certainty in your departmental boundaries.