The short answer
When an executive defends shadow AI by blaming your delivery speed, acknowledge the business goal while enforcing legal boundaries immediately. Say: "Using public tools on client data violates our strict data security covenants. That practice exposes the company to severe regulatory fines. We will onboard marketing to our secure private model by this afternoon. I will review team workflows tomorrow to confirm complete compliance."
Why this question is a trap
Executive peers do not confess to using shadow AI by accident. When an Executive Vice President tells you their team went around you, they are making a power move. They are framing your data team as an operational roadblock and positioning their unauthorized tool selection as pure initiative. They want you to apologize for being slow.
If you apologize, you accept blame for their breach. You establish a precedent where any team that feels delayed can pipe proprietary records into unvetted public software. That destroys data governance across the entire enterprise.
If you react with corporate policy quotes, you lose the room. The room hears a bureaucrat whining about red tape while marketing chases revenue. Other executives will rally behind the peer who gets things done, even if that peer broke every cybersecurity rule on the books.
The real danger is legal exposure. Public generative models routinely retain input data to train future model iterations. When marketing pastes customer contact lists, sales transcripts, or proprietary brand strategies into consumer-grade tools, that data leaves your perimeter. It breaches Master Services Agreements. It breaks GDPR, CCPA, and industry compliance standards. The EVP knows you cannot allow this, but they are betting you lack the spine to shut it down in front of company leadership.
They are testing your executive presence under pressure. Do you fold and promise to speed up? Do you lose your temper and sound like a hall monitor? Or do you take control of the risk, protect customer data, and deliver a clean operational path forward within the hour?
What most people say
Most data and engineering leaders react defensively when accused of moving too slow. They feel their technical integrity attacked, so they push back with anger or procedural whining.
"You can't do that! It violates IT rules and our team is working as fast as we can, so you need to stop right now."
This response fails on every level.
First, it sounds childish. Starting with "You can't do that" invites an immediate challenge. The EVP just told you they are already doing it. Telling them they cannot do something they just admitted to doing makes you look completely disconnected from operational reality.
Second, citing generic IT rules sounds weak. Business executives view internal IT policies as guidelines meant to be bent for commercial gain. When you hide behind generic rules, you sound like someone hiding behind paperwork because you lack real authority. You signal that the rules exist to protect IT convenience rather than company solvency.
Third, defending your team speed with "we are working as fast as we can" concedes the argument. You just admitted your team is slow. You confirmed marketing's narrative. Now the meeting shifts from an urgent corporate security breach to a debate about your data team ticket backlog and staffing ratios. You put yourself on trial while the person breaking the law walks away looking like an operational hero.
What to say instead
Take control of the room by anchoring the issue to enterprise risk and commercial commitments. Never defend your team speed in the opening sentence. Fix the breach first.
"Using public tools on client data violates our strict data security covenants. That practice exposes the company to severe regulatory fines. We will onboard marketing to our secure private model by this afternoon. I will review team workflows tomorrow to confirm complete compliance."
Here is why this structure works.
Sentence one shifts the ground beneath their feet: "Using public tools on client data violates our strict data security covenants."
You do not talk about internal IT guidelines. You talk about external obligations to clients. The phrase raises the stakes immediately. You make it clear that this is not an internal disagreement between marketing and engineering. It is a contractual violation against the people who pay the company revenue.
Sentence two quantifies the consequence: "That practice exposes the company to severe regulatory fines."
You state the direct business risk in plain terms. Regulators do not care if marketing had a deadline. Enterprise customers do not care if content creation felt slow. A fine hits the bottom line and lands on the board audit committee. By stating this plainly, you reframe the EVP actions from clever initiative to reckless financial exposure.
Sentence three eliminates their excuse: "We will onboard marketing to our secure private model by this afternoon."
You take away their operational complaint without lingering on past delays. You do not explain why the centralized model took time to stand up. You provide a solution with a concrete deadline. By giving them enterprise-grade access within hours, you prove your team can move at market speed while keeping the company safe.
Sentence four establishes operational authority: "I will review team workflows tomorrow to confirm complete compliance."
You set up direct oversight. You do not ask the EVP to police their own staff. You tell them you will verify the fix yourself. This closes the loop and ensures unauthorized access actually stops.
The phrase to anchor on
The phrase that wins this exchange is "data security covenants."
Internal policies carry zero weight in a turf war between executives. Covenants carry legal, binding weight. A covenant is an explicit promise made to clients, investors, or insurers. Breaking a covenant triggers audits, lawsuits, customer churn, and executive termination.
When you use this phrase, the entire room understands the gravity. You are no longer talking about tech preferences or architecture roadmaps. You are defining the legal boundary of the enterprise.
You can adapt this anchor across other difficult scenarios.
If a sales leader wants to share unredacted pipeline figures with an external vendor, use this variation: "Sharing raw pipeline data violates our client confidentiality covenants. It exposes us to vendor liabilities. I will provide a masked reporting view by noon."
If a product manager attempts to train internal features on customer code repositories without opt-in consent, pivot to this version: "Ingesting tenant repositories breaches our customer licensing covenants. That creates severe intellectual property exposure. We will restrict the training set to internal synthetic data today."
In every case, you pair external legal reality with an immediate technical alternative.
How to deliver it
Your vocal delivery determines whether this script sounds authoritative or combative. Deliver these lines with zero defensive heat.
Pace yourself deliberately. When someone attacks your team speed, your natural reflex is to talk faster to match their urgency. Resist that impulse. Speaking fast signals panic. Drop your speaking rate to about 130 words per minute. A measured pace demonstrates that you are not rattled by the confrontation.
Insert a distinct pause before you start. Let two full seconds of silence hang after the EVP finishes speaking. That pause forces the room to absorb what the EVP just confessed to. It frames your response as a deliberate executive determination rather than an emotional snap.
Drop your pitch at the end of every sentence. Upward inflection turns an executive directive into a question, making you sound like you are begging for approval. Keep your vocal tone flat and resolve downward. Period. End of statement.
Lock your eye line squarely on the EVP. Do not look down at your notes or glance around the table to see how other executives are reacting. Looking away makes you appear uncertain of your standing. Keep your shoulders square, rest your hands flat on the table, and speak directly across the room. You are not asking them to stop. You are stating the reality of enterprise risk.
Mistakes that cost you the room
- Apologizing for centralized data timelines. The moment you say "I am sorry we have been slow," you accept responsibility for their unauthorized actions and validate their breach.
- Quoting IT policy numbers or internal rulebooks. Citing internal wikis makes you sound like a minor clerk rather than an executive peer protecting the balance sheet.
- Debating tool quality. Never argue about whether the public tool writes better copy than your internal setup. The quality of the copy is irrelevant if the tool leaks company data.
- Threatening to report them to Human Resources. Bringing in HR or compliance as an empty threat signals that you lack the personal standing to handle executive friction.
- Over-explaining model infrastructure. Do not explain tokenization, private tenants, or API endpoints. Keep your answer focused strictly on legal exposure and onboarding deadlines.
Practice plan
Reading these words is easy. Saying them with an even pulse while an executive peer stares you down in a leadership meeting requires muscle memory. Follow this three-step preparation routine.
Step 1: Write down your company specific compliance risks. Know the exact names of your major client commitments, data residency covenants, or regulatory frameworks. When the moment comes, you must speak these terms without hesitation.
Step 2: Practice the hard stop. Stand in front of a mirror and deliver the four-sentence script. Cut out every filler sound. Focus on dropping your pitch at the end of "security covenants" and "regulatory fines." Ensure you do not add defensive qualifiers like "you have to understand" or "as you know."
Step 3: Rehearse out loud under simulated pressure. Open the Talk Rightly app, face the camera, and read the prompt on the teleprompter. Rehearse the script at 130 words per minute, hold steady eye contact, and inspect your five-pillar delivery score to make sure your pacing and downward inflection convey complete control.