The short answer
You are a highly disciplined Business Analyst responsible for the empirical truth of the organization. You do not fabricate fantasy numbers or bake unbacked optimism into business cases simply to help a project leader secure capital funding. When a Project Lead aggressively demands inserting a guaranteed twenty percent efficiency gain projection that lacks any grounding in historical performance or pilot data, they are asking you to corrupt the analysis. You must reject this demand immediately and unconditionally. State clearly that the core business case must reflect actual baseline capability and proven metrics. Inform them that while aggressive targets can be presented as the ultimate goal, they absolutely cannot compromise the integrity of the financial request. Protect the committee's trust with absolute, unyielding professional discipline. You predict based on facts, not wishes.
Why this question is a trap
The Project Lead is actively weaponizing funding presentation optics to mask a weak business case or appease executive leadership. They want the analysis to reflect their ambitions rather than reality, hoping that magical thinking will somehow convert into approved budget. This is a severe, unacceptable threat to your professional credibility and the company's strategic planning.
If you yield to their pressure and bake an unsupported twenty percent efficiency guarantee into the core forecast, you set the organization up for a catastrophic public miss. When actual efficiency inevitably falls short of the inflated model, the funding committee will examine the financial assumptions and demand to know why an unrealistic growth rate was approved. The Project Lead will claim that the analyst vetted and built the model, shifting the entire blame onto your spreadsheets. You will lose the trust of the CFO and the executive team. Business analysis is governed by empirical data and historical run-rates, not operational optimism. Do not trade your analytical reputation for a temporary board room ego boost.
What most people say
Most junior business analysts feel intimidated by aggressive operational leaders who control large teams and speak with absolute corporate confidence. They worry about being labeled as unsupportive of innovation or difficult to work with.
They reply with weak, highly destructive hedging language. They say things like, "Well, if the software integration goes perfectly, maybe we can get close to twenty percent, so I'll adjust the formula in the deck." This approach is completely fatal. It signals to the operational organization that analytical models are subjective toys that can be stretched to fit any narrative. When the pilot fails to deliver the promised efficiency, the analyst takes the blame for bad math. You must never compromise model integrity for political storytelling.
What to say instead
You must respond with cold, unshakeable analytical authority. You are the guardian of operational reality. You define the math.
Tell the Project Lead plainly that business cases are predictive tools built on empirical data, not motivational posters. State that our historical performance baseline across the last four quarters shows a consistent variance that makes guarantees impossible. Inform them that you are fully willing to model their twenty percent target, but it will be explicitly isolated and labeled as an "Unverified Hypothesis" with a detailed sensitivity analysis showing the required operational changes and headcount reductions needed to achieve it. Make it clear that the core funding deck will retain the realistic, data-backed baseline as the primary metric. Offer no compromise on the integrity of the primary forecast.
The phrase to anchor on
The exact, non-negotiable phrase to deploy is empirical performance data.
This specific terminology forcefully removes the conflict from the personal realm. You are not refusing their request because you lack ambition or enterprise vision. You are strictly tethering the forecast to verifiable empirical performance data. It reminds the project leader that business analysis is a quantitative science governed by past performance and measurable velocity, not executive wishful thinking.
How to deliver it
Deliver your response with absolute, chilling analytical calm. Do not raise your voice, do not look away, and do not apologize for being conservative.
Use short, declarative sentences. When the Project Lead argues that we need to fake it till we make it for the committee, state flatly that institutional investors and finance leaders perform variance analyses and spot unsupported hockey-stick projections immediately. Maintain unyielding eye contact. If they threaten to escalate to the sponsor to get an override, encourage them to do so, noting that you will gladly present both the realistic baseline model and their unconstrained hypothesis scenario to executive leadership. Your total emotional detachment in the face of their funding panic is your ultimate protective shield.
Mistakes that cost you the room
The absolute most damaging mistake is agreeing to split the difference and plug an arbitrary ten percent efficiency gain into the model without any supporting data. Arbitrary numbers destroy the entire predictive value of a business case.
Another fatal error is modifying the model in the meeting while the project leader watches over your shoulder. Never alter core financial assumptions under live interpersonal pressure. Always take the request back to your workbench, run the data models objectively, and present them through formal channels.
Practice plan
This drill requires intense psychological preparation for standing up to dominant operational leaders during budget season. Record yourself stating the refusal on camera. Review your posture to ensure you are holding a level, deep vocal tone.
Practice the delivery of the phrase empirical performance data until it sounds entirely automatic and emotionless. Rehearse your response to their committee room optics arguments. Drill this scenario repeatedly until the fear of upsetting a project lead is completely replaced by the fierce pride of protecting analytical integrity. Please note that this guide serves strictly as a rehearsal tool for communication scenarios. Talk Rightly does not offer formal financial, legal, or accounting directives.