Five preambles that cost you authority in meetings, and what to open with instead

You already hold the answer in Columbus. You have been carrying this since the fourth slide. You open your mouth and what comes out is "This might be a dumb question, but." Eleven words of apology in front of the sharpest sentence anyone will say in that room. The idea lands, eventually. Looking back, what stuck with everyone was the apology that came first, not the substance that followed it.

The lead-in seems polite, like courtesy. It sounds like asking permission. By speaking that way you hand the audience a rulebook for discounting your next remark, and the rulebook says to discount it a little. Nobody requested your judgment of yourself. You offered that judgment unprompted, and then you were puzzled when the colleague from Dublin who raised the identical point at 10:19 received the nod instead. That pattern shows up in boardrooms along the Columbus skyline and in planning sessions across Central Ohio alike.

Rule A. Raising a query in a senior session

The tempting version runs: "This might be a dumb question, but how are we funding the second phase?"

The stronger version runs: "How are we funding the second phase?"

Reason: the query was never foolish. If nobody has an answer, you found the gap. Should anyone think otherwise, you still gained the facts. The preamble simply adds a self-rating that the question had no need for.

Rule B. Sharing your take once the leaders have weighed in

The tempting version runs: "I'm not sure if this makes sense, but I wonder if we're underestimating the churn."

The stronger version runs: "I think we're underestimating the churn. Here's why."

Because "I think" already flags uncertainty, and it does so truthfully. Stacking a second hedge on top turns a view into a wobble, and a room deciding what to do skips past wobbles.

Rule C. Pushing back on a number

The tempting version runs: "Sorry, I could be wrong about this, but I had the margin at 22, not 26."

The stronger version runs: "I had the margin at 22, not 26. Can we check?"

One of those two figures is mistaken, and an advance apology from you will not change which one it is. Saying "Can we check" reframes the correction as a joint task rather than a confrontation over who is right.

Rule D. Reclaiming the conversation after being cut off

The tempting version runs: "Sorry, can I just finish quickly?"

The stronger version runs: "Let me finish the thought." Then complete it at an ordinary pace.

The word "quickly" signals that you will be brief about a point that merited the floor in the first place. "Sorry" apologizes for owning it. Neither is a crime. Both versions spend the room's attention at the very moment you most need to hold it.

Rule E. Presenting work you are proud of

The tempting version runs: "This is still rough, and I didn't have much time, so bear with me."

Stronger: "Here's the outcome we reached. Three things to look at."

Once you have called it "rough," the room cannot forget that you did. Each chart that follows will be judged against the standard you just set for it. The work was probably fine. Allow them to discover the quality of the work on their own.

The principle that ties all five together

State the line, then let it sit. Each preamble is a line about yourself set ahead of a line about the work, and the audience reads the first as a guide to interpreting the second. The impulse to hedge is not a personal failing of yours. It was learned in rooms that punished women for sounding certain, a point Tulshyan and Burey made in HBR in 2021: the "imposter" label takes a systemic problem and hangs it on the individual. You cannot fix the room this week. You can drop eleven words.

Remember this one well. Reread this in the elevator before your next meeting.