EC-201a · Module 2
Anticipating Objections in the Structure
4 min read
Every recommendation generates objections. The executive who challenges the data, questions the timeline, or raises a risk you did not mention is not being difficult — they are doing their job. The question is whether you address those objections in the structure of the deck or wait for them to surface in the room. Addressing them in the structure is always better. An objection that is pre-answered in the deck is a validation that you thought carefully. An objection that surprises you in the room is a signal that you did not.
The three objections that appear in almost every executive recommendation: the data objection ("how do we know this will work here?"), the risk objection ("what happens if it does not work?"), and the timing objection ("why now, why not wait?"). Pre-answering all three in the structure of the deck eliminates the most common challenges before they are voiced.
- Identify the three most likely objections before writing What will the most skeptical person in the room challenge? List the three objections most likely to be raised and decide where in the argument each one is best addressed. The data objection belongs in the evidence section. The risk objection belongs adjacent to the recommendation. The timing objection belongs adjacent to the cost of inaction.
- Embed responses in the argument, not in a separate section Address each objection at the point in the argument where it is most likely to arise. If the executive will question the data quality, address that immediately after presenting the data — not in a "limitations" appendix. If the executive will question the timeline, address that immediately after stating the recommendation — not in a "next steps" slide.
- Address concerns without weakening the recommendation Acknowledging a risk is not the same as conceding the recommendation. "The primary risk is data quality in the legacy system. We have addressed this by building a 30-day parallel processing phase into the pilot design." This acknowledges the risk and neutralizes it. It does not soften the recommendation. The recommendation stands. The risk is managed.
Do This
- Identify the three most likely objections before writing a single slide
- Address each objection at the point in the argument where it arises
- Frame objection responses as evidence of rigor, not as concessions
- Distinguish between concerns you have mitigated and risks you are accepting
Avoid This
- Save all objection responses for a "risks and mitigations" slide at the end
- Omit known objections and hope they are not raised
- Respond to objections defensively — it confirms the concern
- Let the 'limitations' section undermine the recommendation rather than contextualizing it