The short answer
When executive peers lock horns over software ownership and freeze delivery, do not referee their emotions or take sides. State the enterprise risk plainly. Present the documented technical and operational trade-offs without bias. Escalate the decision authority cleanly to the chief executive officer, and establish an immovable deadline for binding ownership.
Why this question is a trap
Two executive vice presidents reach an impasse. The Executive Vice President of Operations wants control over workflow software because their team handles customer fulfillment. The Executive Vice President of Technology wants exclusive control because their team manages system architecture, security, and code maintainability. Neither will yield. Delivery stops. Sprints stall. Corporate milestones fall behind schedule.
You are caught in the middle. You need the stalemate broken to move work forward. This is where most senior leaders fail.
The trap is political and procedural. First, lateral C-level executives often use operational standoffs to wage proxy wars over enterprise territory. If you take a side, you make an immediate enemy out of the other leader. Back Operations, and Technology will delay code reviews, withhold engineering resources, and cite compliance violations. Back Technology, and Operations will claim the tool does not meet business requirements, refuse user acceptance testing, and blame your program for customer churn.
Second, the trap tests your maturity under political friction. Executive peers watch how you handle their gridlock. If you show irritation, you appear overwhelmed by senior management conflict. If you shrink back and wait for them to sort it out, you appear passive and ineffective. If you try to split the difference with a sloppy compromise, you create a shared-ownership nightmare where no one is accountable and systems fail quietly months later.
Third, people assume their job is to smooth things over. That instinct ruins projects. Stalemates do not dissolve because people decide to be nice. They dissolve when someone changes the playing field from subjective territory to objective business impact, outlines the cost of inaction, and forces a structured governance decision.
What most people say
"Both of you are being stubborn and it's making it impossible for the project team to get any real work done."
This response destroys your standing in seconds. It attacks the character of two senior officers instead of addressing the structural defect in the operating model.
Calling executive vice presidents stubborn strips away their professional dignity. The moment you insult them, their focus shifts from resolving software ownership to punishing your lack of deference. They will unite against your tone. Instead of defending their architectural or operational logic, they will correct your conduct. You will spend the rest of the quarter apologizing for your lack of executive presence rather than delivering product features.
This statement also betrays victimhood. When you say "it is making it impossible for the project team to get any real work done," you sound like a helpless middle manager begging parents to stop fighting. Senior management does not respect complaints about how hard work has become. They expect operators to manage conflict, isolate technical trade-offs, and surface clear paths to resolution.
Worst of all, it offers zero path forward. You named the friction, insulted the decision makers, and provided no mechanism to settle the dispute. Delivery remains frozen.
What to say instead
"This executive gridlock is freezing critical delivery across all our corporate milestones. I documented the architectural trade-offs and operational costs for both divisions. We will review the boundary options with the chief executive officer on Thursday. I will confirm binding ownership before the end of the week."
This response works because it is clinical, objective, and structurally decisive. Break it down phrase by phrase:
"This executive gridlock is freezing critical delivery across all our corporate milestones."
You name the reality without softening it. You do not say people are arguing. You call it executive gridlock. You immediately tie that gridlock to the single metric that matters: critical delivery across corporate milestones. This shifts the stakes from departmental pride to board-level execution.
"I documented the architectural trade-offs and operational costs for both divisions."
You position yourself as an impartial operator of enterprise facts. You did not write an opinion memo. You documented technical realities on one side and operational expenses on the other. Both EVPs see their core concerns reflected in the data. You remove subjective emotion and replace it with concrete architectural and fiscal boundaries.
"We will review the boundary options with the chief executive officer on Thursday."
You remove the deadlock from their private vacuum without threatening them. You do not run to the CEO as a tattletale; you schedule a structured decision review regarding system boundary options. When peers realize their dispute will be evaluated directly by the chief executive officer under an objective trade-off lens, posturing stops. Nobody wants to defend a territorial turf war in front of the CEO without data.
"I will confirm binding ownership before the end of the week."
You establish an aggressive, definitive timeline. You are not waiting for consensus to emerge from thin air. You take accountability for driving the loop to closure. By Friday, the ambiguity disappears.
The phrase to anchor on
The phrase to anchor on is "binding ownership."
Loose terms like "alignment," "partnership," or "shared responsibility" allow executive standoffs to fester. Shared ownership means zero ownership. When systems break or roadmaps slip, shared owners point fingers across the hallway.
Binding ownership is absolute. It means one leader holds the budget, the operational sign-off, and the technical accountability. It signals to both EVPs that this meeting will not end in a polite handshake and continued paralysis. The organization requires a single throat to choke, and that decision will be locked down permanently.
Here are two variations for different high-stakes standoffs:
If you face an executive conflict between Product and Sales over custom client engineering:
"This product disagreement is holding up our core platform release. I documented the revenue upside against the engineering debt for both units. We will review the client commitments with the chief revenue officer on Tuesday. I will establish binding ownership over custom code requests by Wednesday afternoon."
If you face a territorial dispute between Security and Infrastructure over cloud deployment gates:
"This operational friction is delaying infrastructure provisioning for three product lines. I gathered the security compliance controls and the release velocity benchmarks. We will present these two operating models to the chief operating officer tomorrow. I will enforce binding ownership on deployment approvals before our sprint planning on Monday."
How to deliver it
Your vocal mechanics determine whether this script commands the room or triggers an executive explosion. If your voice shakes, you will sound like an insubordinate employee overstepping your rank. If your tone is cold, measured, and neutral, you will sound like the only adult in the room.
Speak at a deliberate, controlled tempo. Slow down to roughly 130 words per minute. When people step into C-suite cross-fire, their heart rate spikes and their speech speeds up. Rapid speech signals panic. Force yourself to slow down. Give every syllable equal weight. Let the weight of each sentence register before moving to the next.
Insert intentional silences. After you say, "This executive gridlock is freezing critical delivery across all our corporate milestones," pause for a full two seconds. Let the room absorb that statement. Do not rush to soften it. When you name the review with the chief executive officer, pause again. Silence projects authority. It demonstrates that you are comfortable standing in the tension you just highlighted.
Keep your pitch completely flat and end on a downward inflection. Do not let your voice rise at the end of the sentence. A rising pitch turns a strategic directive into a question, signaling that you are asking for their permission to escalate. A falling pitch makes it an administrative fact. You are not asking if Thursday works for them; you are stating that the review is on the calendar.
Fix your eye line. Do not ping-pong your gaze between the two executive vice presidents like an anxious spectator at a tennis match. Look directly at the Executive Vice President of Operations for the first sentence. Turn calmly to the Executive Vice President of Technology for the second sentence. Look straight ahead, commanding the entire room, when you deliver the escalation to the CEO and the deadline for binding ownership. Hold your chin level. Keep your hands flat on the table or resting still. Zero fidgeting.
Mistakes that cost you the room
- Adopting shared custody models. Splitting the difference to keep both EVPs happy always fails. Making Operations own the frontend and Technology own the backend without clear boundary governance simply guarantees future conflict.
- Blaming personal attitudes. Calling executives stubborn, childish, or political turns an operational issue into an interpersonal fight you will lose.
- Back-channeling behind their backs. If you set up a meeting with the CEO without informing both EVPs first, you become an untrustworthy operator. State your escalation directly to their faces in the room.
- Leaving the meeting without an explicit date. Agreeing to "revisit the conversation next week" lets the gridlock continue. State the exact day and time the decision will be finalized.
- Over-apologizing for the escalation. Saying "I hate to bother the CEO with this" signals weakness. Escalating unresolved strategic trade-offs to the executive office is proper governance, not an operational failure.
- Focusing on team frustration instead of enterprise metrics. EVPs do not move because developers or managers are stressed. They move because corporate milestones, quarterly commitments, and capital allocations are frozen.
Practice plan
1. Map the neutral trade-offs. Write down the exact operational costs and technical risks on a single sheet of paper. Remove all emotional adjectives, blame, and speculation. If you cannot describe the Technology EVP's concern in terms that they would agree with, you are not ready to speak.
2. Rehearse the downward inflection. Read the four-sentence response aloud five times in front of a mirror. Focus on ending every single sentence with a dropping tone. Cut out any upward lilt at the word "Thursday" or "week." Ensure your head does not tilt or nod when stating the escalation.
3. Record your delivery under pressure. Open Talk Rightly, launch the camera rehearsal, and read this exact response into the teleprompter without looking away. Review your five-pillar delivery score. Pay strict attention to your pace and composure metrics. Repeat the drill until your voice sounds completely detached, authoritative, and steady.
