Skip to content
Get started

How to say it

How to handle tough questions in a presentation

Buy time calmly, clarify assumptions, and commit to follow up with precision.

  • Presentations
  • Disagreement
How to handle tough questions in a presentation

Direct Answer & Key Takeaway

Buy time calmly, clarify assumptions, and commit to follow up with precision. Never invent numbers. Validate the relevance of the question, give your best high-level framing, and commit to delivering precise metrics via follow-up.

The moment

During your Q&A session, a senior stakeholder asks a challenging technical question about system limits that you do not have exact data for on your slides.

General advice

Never invent numbers. Validate the relevance of the question, give your best high-level framing, and commit to delivering precise metrics via follow-up.

The full technique is in the app

Step by step, with practice in four formats and a review of your own answer by the AI coach.

Open the technique

Phrases that work

  • That is an important question. Let me unpack the trade-off.

    Це важливе питання. Дозвольте пояснити головний компроміс тут.

    Buys a 3-second thinking window while acknowledging the stakeholder.

  • I do not have the exact latency numbers on hand, but I will pull them right after the call.

    У мене немає точних цифр затримки під рукою, але я вивантажу їх одразу після дзвінка.

  • To make sure I address your core concern, are you asking about peak load or steady state?

    Щоб відповісти точно по суті: ви маєте на увазі пікове навантаження чи стабільний режим?

  • We intentionally chose to optimize for consistency first, with caching layered in phase two.

    Ми свідомо вирішили спершу оптимізувати консистентність, а кешування додати на другому етапі.

In a real conversation

StakeholderWill this microservice architecture handle a tenfold traffic surge on Black Friday?

YouThat is an important question. The stateless workers scale automatically, but database connections remain the bottleneck. I do not have the exact saturation numbers on hand, but I will pull our load test report and send it over this afternoon.

StakeholderFair enough. Looking forward to the data.

Common mistakes

  • Instead ofYes, of course, absolutely no problems at all, 100 percent sure.

    SayThat is an important question. Let me unpack the trade-off.

    Bluffing on architecture destroys credibility when systems degrade under real traffic.

  • Instead ofI do not know, somebody else built that part.

    SayI do not have the exact latency numbers on hand, but I will pull them right after the call.

    Deflecting responsibility sounds defensive and junior.

Handling Q&A effectively is about poise and honesty. Acknowledging boundaries and committing to follow up with verified evidence shows genuine seniority.

Terms in this article

Related articles