The short answer
When a Vice President of Strategy asks your team to execute two massive, enterprise-level analytical workstreams simultaneously within a single month, they are severely misjudging your departmental capacity. A post-merger integration audit and a supply chain restructuring study are both highly complex, data-heavy initiatives that require deep, uninterrupted focus. Attempting to run them concurrently with a standard analyst team guarantees a catastrophic failure of execution on both fronts.
If you agree to this demand, you are setting your analysts up to fail. Your team will be forced to context-switch constantly between disparate datasets, leading to severe analytical errors, missed deadlines, and extreme burnout. The final deliverables will be superficial, lacking the rigorous depth required for executive decision-making. You must intercept this request and dictate a realistic operational reality to your Vice President.
You cannot rely on vague complaints about being busy. You must enforce a rigid project management boundary. You will explicitly reject the concurrent timeline and present a forced choice to the VP. They must either agree to a strict sequential execution plan, prioritizing the merger audit first, or they must authorize the budget to bring in specialized external contractors to absorb the overflow. You must act as the primary governor of your team's analytical velocity.
Why this question is a trap
The trap lies in the casual phrasing of the request. By asking if your team can run them "simultaneously this month," the VP is framing a monumental task as a simple scheduling adjustment. They are testing your willingness to stretch your team's bandwidth to accommodate their aggressive executive timeline. They expect you to say yes to prove your ambition and your team's agility.
If you say yes, you own the inevitable disaster. When the supply chain study contains flawed financial assumptions because your analysts were exhausted from auditing the merger data all night, the VP will not take the blame. They will point the finger at your poor managerial oversight. You will have proven that you cannot accurately forecast your own team's capacity, which destroys your credibility as an operational leader.
Furthermore, agreeing to impossible concurrent timelines trains the VP to treat your department as an infinite resource pool. They will continue to dump massive projects on your desk without any regard for sequencing or prioritization. You must break this habit immediately by forcing the VP to make hard trade-off decisions regarding corporate strategy priorities.
What most people say
Most strategy managers react with an anxious desire to appease the Vice President. They say something like, "That is a massive amount of work for this month, but we will try our absolute best to get both done. I will ask the analysts to work some overtime, but the supply chain study might be a little delayed if the merger data gets complicated."
This response is a complete failure of capacity management. By agreeing to "try your absolute best," you validate the absurd timeline and commit your team to a death march. Offering to have the analysts work overtime proves that you rely on brute force rather than strategic prioritization. Warning that the supply chain study "might be a little delayed" is a weak hedge that the VP will ignore until the deadline is missed. You have surrendered your managerial authority entirely.
What to say instead
"We cannot execute two enterprise-scale workstreams simultaneously without severely degrading the analytical quality of both deliverables. I am enforcing a sequential execution plan, completing the post-merger audit first by the end of the month. If the supply chain restructuring cannot wait until next month, you must authorize immediate budget for external contractors to handle the overflow capacity."
This script is a flawless execution of operational boundary setting. You begin with a direct, uncompromising refusal based on quality. Stating clearly that you cannot execute both simultaneously without "severely degrading the analytical quality" stops the demand instantly. You raise the conversation from a scheduling issue to a risk management issue. You make the VP care about the outcome.
You then immediately deploy the structural solution. You state that you are enforcing a "sequential execution plan." You take control of the timeline and dictate the priority: the post-merger audit happens first. This proves that you are not intimidated by their rank and that your project management is not open for casual negotiation.
Finally, you present the executive alternative that completely neutralizes the threat. You offer them a path to get what they want, but you attach a hard financial cost to it. If the supply chain study truly cannot wait, they must authorize immediate budget for external contractors. By forcing them to spend actual corporate dollars to satisfy their impatience, you make them evaluate the true urgency of the project. You place the burden of proof entirely on their budget.
The phrase to anchor on
Enforcing a sequential execution plan.
How to deliver it
Deliver this response with the absolute, unshakable calm of an air traffic controller. Your tone must project complete professional detachment and total operational control. Do not sound annoyed that they asked, and do not sound intimidated by their title. Treat the interaction as a routine enforcement of project management physics.
Maintain direct, unwavering eye contact with the Strategy VP. When you declare that you are enforcing a sequential execution plan, speak slowly and deliberately. You want the operational weight of that concept to land heavily in the room. When you outline the requirement for contractor budget, keep your voice entirely neutral. You are not challenging them to a fight. You are simply stating the mathematical reality of resource allocation.
Mistakes that cost you the room
The most fatal mistake is offering to split your analysts, putting half on the merger and half on the supply chain. If you divide a small team across two massive projects, you guarantee that neither project has the critical mass required for deep analysis. Both projects will fail slowly. You must keep your resources concentrated to guarantee execution quality.
Another critical error is debating which project is actually more important. Do not say, "I think the merger audit is way more critical than the supply chain study right now." You will lose a subjective argument about corporate priorities with a VP. Anchor entirely on the capacity constraint and the sequential execution plan. Let the VP decide which project goes first, but insist they go one at a time.
Finally, do not ask your analysts if they think they can handle both. You are the Strategy 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.
Practice plan
First, map out the exact hour-by-hour capacity of your analyst team for the current month. You must be able to prove mathematically why two enterprise projects exceed their physical limits. Ensure you have the structural data to back up your words.
Second, practice the transition from the hard refusal to the sequential execution plan. You must sound entirely comfortable telling a senior executive how their projects will be prioritized. Record yourself until the delivery sounds effortless.
Finally, run the drill in the Talk Rightly studio. Focus heavily on keeping your facial expression completely neutral. When a Strategy VP makes an aggressive demand, any sign of anxiety or frustration will invite them to push harder. You must train your body to remain perfectly still under pressure.