The Question You Didn't Prepare For

 

The Question You Didn't Prepare For

I've already written about how nobody ever gave me a stable rule for reporting — lead with the conclusion, no wait, walk me through it first. That was one kind of stress. This is a different one, and it never really went away no matter how many years I put in.

It's the moment in a report to a vice president, or any senior executive really, when the question that comes back isn't the one you built your slides around.

You can prepare for the questions you expect

Most of a report is not the report itself. It's the night before, or several nights before, trying to guess what will get asked.

I always did this alone. Not with the team, not with a junior colleague reading questions off a list at me — just me, going through the deck line by line, asking myself where I would attack it if I were the one sitting across the table. Where are the numbers soft. Where did I make an assumption I can't fully defend. Where is the gap between what I actually know and what the slide implies I know.

You can get quite good at this over time. I'd guess I caught maybe seventy, eighty percent of what actually came up, just from doing that alone every single time.

Then there's the other thirty percent

The question you didn't see coming is a different kind of stress entirely, and I don't think it gets easier with experience, not really. What gets better is how you handle the two or three seconds right after it lands.

I decided a long time ago that there was exactly one wrong way to answer something I didn't fully know: pretending I did. Guessing with confidence, dressing up a half-answer to sound like a full one, hoping nobody would check. I've watched other people do that in a report, and I've watched it go badly almost every time — not immediately, sometimes weeks later, when the number turns out to have been wrong and now it's not just a mistake, it's a mistake someone tried to hide.

So my actual rule, the one I held onto through every company, was smaller and less impressive than it sounds: answer with what I actually know, say plainly when I don't know something, and never invent the rest to fill the silence. It doesn't feel like a strategy in the moment. It just feels like the only option that doesn't get worse later.

What "I don't know" actually costs you

I won't pretend saying it is free. In a Korean office, in front of a room, admitting a gap in your own report can read as unprepared, and for a second the temperature in the room does change. Nobody claps for honesty.

But the alternative has a bill that comes due later, and it's always bigger. A wrong answer stated with confidence gets written down as a fact by whoever's taking notes. Then it moves. It ends up in someone else's summary, then in a decision, and eventually someone traces it back and finds it started with you, in that room, making something up under pressure. I've seen careers take a real hit from that, more than one.

So I'd rather take the smaller, immediate cost — looking slightly less sharp for thirty seconds — than the larger one that shows up a month later with your name attached to it.

The nights that didn't end when the deck was done

There were times the deck itself wasn't the problem. It was the wording.

I remember more than one night going back over a single slide, or sometimes a single sentence on a single slide, past midnight, because I couldn't get the phrasing right in my head. Not the data — the data was fine. It was how a particular line would land, whether it sounded like I was making an excuse or stating a fact, whether one word made it sound like I was blaming another department when I wasn't trying to. In a Korean report, how something is said carries almost as much weight as what's actually being said, and you learn that the hard way, usually after getting a sentence wrong in front of the wrong person once.

So I'd rewrite it. Then rewrite it again. Sometimes I'd go to bed still not happy with it and wake up and change it one more time before the meeting. I don't think anyone ever noticed the difference between version four and version seven of a single sentence. I noticed. That was usually enough to keep me up.

What actually got easier, and what didn't

The mechanics got easier over the years — building a deck fast, anticipating the obvious questions, reading a room's mood before I even opened my mouth. All of that is a skill, and skills improve with repetition.

The part that never got easier was the specific two or three seconds after an unexpected question, when you have to decide, right there, whether you're going to be honest about what you don't know or paper over it. I don't think that gets easier because I don't think it's supposed to. If it ever stopped feeling like a small risk, I'd probably start taking the easier, worse option more often.

Twenty-three years in, I still do the same thing I did in my first company. I rehearse alone, the night before, going after my own numbers as hard as I can. And when something still gets through anyway — because something always does — I say what I actually know, and I say plainly when I don't. It's not a clever answer. It's just the one I've never regretted afterward.