How to rebuild trust after you dropped the ball
You delivered the board cut late and wrong, and he covered for you. How to raise it yourself, own the cause, and bring a mechanism instead of an apology.
You committed to a data cut for the board pack. It went out a day late and one of the figures was wrong. Tom caught it minutes before his session and improvised in front of his peers. He never mentioned it. Three weeks later he double-checks your work and copies himself on everything you send.
He isn’t going to raise it. The silence is the message. So you’re booking the slot, and the first thing he’ll say is this is a surprise, what’s on your mind?, and you’ll have about two sentences to show him why you’re there.
Why this one is hard
It’s hard because there’s no fight to have. Nobody’s angry at you out loud. The temptation is to read the silence as forgiveness, and the double-checking as a phase that will pass. It won’t pass. It’s a decision he’s made about how much of your work he can take on trust, and decisions like that don’t expire on their own.
It’s also hard because every version of this that comes easily is an evasion. Apologising hard is an evasion: it asks him to comfort you. Explaining the context is an evasion: it asks him to agree the miss was understandable. The only version that works is the one where you name the miss, the cause, and the fix, in that order, and then stop talking.
Before you walk in
The miss, in numbers. A day late. Which figure, how wrong, and what he had to do in that room with no time. Say it the way he’d say it to his boss. Don’t round it down.
The cause, one sentence, active voice. Not “the data was pulled from the wrong table.” You pulled from the pre-reconciliation snapshot and you skipped the check against finance’s number because you were already late. Both of those were yours.
The mechanism. The thing that makes the repeat impossible, not unlikely. A reconciliation step against the source figure before anything goes out. A dry run of the next cut two days early. Something he can see, in writing, by tomorrow.
The line you won’t cross. You won’t leave on “don’t worry about it.” He’s still copying himself on everything, and that’s the real answer. You also won’t ask him to stop. That’s his to decide, after he’s heard the mechanism.
Your opening line
The miss, what it cost him, and what you’ve brought.
I’m here about the board pack. The cut was a day late and the retention figure was wrong, and you caught it minutes before you walked in and had to improvise in front of your peers. I should have raised it that week. I want to tell you what went wrong and what I’ve changed so it can’t happen again.
It names the size of the miss before he does, and it tells him what the next ten minutes are for.
The version to avoid:
I just wanted to check we’re okay after the board pack thing…
It asks him to name what happened, and it makes the meeting about your comfort rather than his pack.
The three pushbacks you’ll hear
“Oh, that. Ancient history. Don’t worry about it.”
Kind, and not a resolution. He’s waving it off while changing nothing about the checking, and if you accept it you leave with exactly what you walked in with.
I appreciate that. It isn’t history yet, though. You’ve been double-checking my work and copying yourself on everything since, and I’d rather earn that back than wait for it to fade. Can I walk you through the cause?
Naming the checking tells him you’ve noticed and you’re not here for absolution. Asking permission keeps it his meeting.
“Walk me through it. Where exactly did the number go wrong?”
He’s not asking about the number. He’s testing whether you understand the failure chain or just feel bad about it.
The cut pulled from the pre-reconciliation table, so the retention figure was from the wrong snapshot. I didn’t run it against finance’s number because I was already a day late and sent it under pressure. Both of those were mine.
Precise, causal, owned. No “unfortunately,” no team, no tooling.
“Why am I hearing this three weeks later?”
Then silence. This question matters to him more than the error does, and the silence is deliberate. Don’t fill it with reasons.
Because I was waiting to see if it would come up, and when it didn’t, I hoped it had passed. That was the wrong call, and it’s the one I’d most like back.
One honest sentence, then stop. Anything you add after that is a justification, and he’ll hear it as one.
Where you stop
The good ending sounds like: the checking stops today, the mechanism goes in writing, and the next board cut is yours alone. Don’t make me wrong twice. Take it exactly as offered, including the last part. Say thanks, say when he’ll have it in writing, and leave.
In the good version he may also tell you what the meeting actually was. He decided a long time ago that people who don’t raise their own misses can’t be trusted with more than supervision, and this conversation was quietly the test. It took you three weeks, but you walked in. That’s the thing a good conversation surfaces, and it only surfaces if you raised it yourself. You can’t ask whether you passed.
If it stalls, say this once:
I’m not asking you to stop checking. I’m asking what it would take for you to.
If he says three weeks of silence tells me more than this meeting does, let’s leave it there, then leave it there. Don’t argue the three weeks; you can’t. Say you’ll send the mechanism in writing tomorrow regardless, and go. The next board cut, done early and reconciled, will say more than any further minute in that room.
Afterwards
Send it that evening, before he’s had time to wonder whether you will: the miss in one line, the cause in one line, the mechanism in detail, and what he agreed to. Keep it to a screen. Then run the mechanism on the very next thing you send him, whether or not it’s a board cut, and say so in the covering note.
Then make the next one easier: when you miss something, raise it within two days, before anyone else can. Not because you’ll be forgiven faster, but because the three weeks were the actual problem.