Right, let us begin properly then.
I want to start with the client migration work in June, because I do not say this often and I want it on record: it was good. You caught the billing discrepancy before Marcus did, which, given how that meeting usually goes, spared everyone an afternoon of him circling the same three sentences. There is a particular kind of thoroughness that does not announce itself, and yours does not, and I have decided that is a compliment.
Marcus has a limp with his patience, usually. I saw the ledger error Tuesday. Left it for him, figured he’d panic, then I’d have to fix it anyway. Better he does the circling. The billing’s fine now, though the new software crashes if you blink wrong. Don’t let it go to your head. I’m still waiting on that raise you promised last quarter.
I did not promise, Ivo, I said I would raise it, which is a different verb entirely and you know that. It is on the agenda for the September budget round, not before, and I would rather tell you that plainly now than have you discover it by absence in October.
The software crashing is noted separately. I have complained about it twice already and been told to file a ticket like everyone else.
Right. September. As if budgets aren’t already ghosts haunting the server room. You keep telling me “file a ticket” like it’s a magic spell that fixes code. I’ll file it. I’ll file ten. Meanwhile, the software’s still holding my data hostage. Don’t act like you’re doing me a favor by mentioning October. I know how these things vanish. I’ve seen them.
I am not doing you a favour by mentioning October, I am doing myself one, because I would rather you hear it from me than assume it and be right for the wrong reasons. That said — you are drifting off the actual point, which I noticed you do whenever the topic gets close to something you would rather not sit in.
We are talking about your performance. Not the ticketing system.
Drifting? I’m just watching the clock. Performance is a moving target, isn’t it? One week it’s catching errors, next it’s not being too obvious about it. I did the work. Marcus got the blisters. If that’s not enough, if I’m still “drifting,” then what is? Just say it. I’m bored of this vague praise that doesn’t pay the rent.
Fine. Since you are bored of vague praise — the concern is not the work itself, it is the pattern around it. You let the ledger error sit until Tuesday became Marcus's problem instead of catching it Monday and simply saying so. That is not thoroughness, that is theatre, and I think you know the difference better than you are letting on right now.
Theatre? Please. You think I sat there waiting for Tuesday just to watch Marcus squirm? I was waiting for the audit trail to close. If I flagged it Monday, it’s a mistake. Tuesday, it’s a system failure. Same numbers, different narrative. You want a hero? Go hire one. I’m the one who actually reads the damn logs. Don’t confuse silence with indecision. It’s strategy. Or whatever you want to call it while you justify the September delay.
That is a tidy explanation for something that looked, from where I sat, like watching someone struggle because it suited the story better. Maybe it was strategy. I am not entirely convinced, and I do not have to be convinced today — I only have to write it down accurately, which I intend to do exactly as you have just described it.
Write it down. Scribble away. I don’t care about the record; I care about the result. The numbers are balanced. The client is happy. Marcus is tired. That’s the reality, not your narrative. If you want to think I’m manipulative, fine. It’s cheaper than admitting the system is broken and we’re all just playing house with spreadsheets. Just sign the paper. Let’s get this over with.
I am not calling you manipulative, Ivo, I am saying I noticed something and I named it, which is different from a verdict. And no, I am not signing anything today — the September window is real, the timing was already decided before this conversation started, and nothing you have said moves it. I would rather you hear that plainly than think this ended on my terms out of spite.
Spite? You think I care about your terms? I care about the fact that you’re nitpicking motives while the actual work gets buried under your need to control the narrative. Fine. September. I’ll sit here. I’ll do the work. But don’t act like you’re the only one with patience. I’ve got plenty. And when October comes and nothing changes, don’t expect me to surprise you. I’m not here to be your project. I’m here to keep the lights on.
I am not asking you to be my project, and I am not surprised by very much anymore, if I am honest — that is less about you than about how these budget rounds go generally. September stands. If nothing moves by then, come back and say exactly what you just said to me, and I will have no defence left to offer you.
You say that like it’s a challenge. It’s a forecast. I’ll be here. Marcus will still be circling. The software will still crash. And you’ll still be writing it down, cold and precise, as if the tone matters more than the math. Go ahead. Wait until September. See if the numbers look any friendlier when they’re bleeding out. I’m not waiting for your permission to be right. I’m just tired of performing for an audience that only claps when it’s convenient.
Noted, all of it — the forecast, the tiredness, the bit about the audience. I am not going to sit here and match you point for point on it because we will just go in circles and I have another review after this one and a train to catch besides. Let us move to the actual form. Client communication, section three.
Section three. Right. I sent the updates. They arrived. You want me to say I held their hands? I didn’t. I gave them the facts. They didn’t ask for therapy, they asked for data. If they’re overwhelmed by precision, that’s not my department. I sent the emails. The receipts are there. Check the timestamp. 4:02 PM. Precise. Effective. Done.
The timestamp is not in question. What is in question is the tone of the 4:02 email, which I read, and which read less like data and more like someone daring the client to complain. They did not complain, to be fair to you — but I would rather you did not leave that particular door open next time. Note it, move on.
Daring them? I was being efficient. They wanted answers, not a hug. If my tone read as aggressive, maybe they’re just used to being coddled. I didn’t write a manifesto. I wrote a status update. You want me to sugarcoat the truth until it’s invisible? Fine. I’ll soften the next one. But don’t pretend precision is the same as hostility. It’s not. It’s just honest. And you hate honest because it doesn’t fit your narrative.
I do not hate honest, I hate imprecise, and calling the tone "just honest" is doing a lot of work to avoid the word blunt. Soften it or do not, that is genuinely your choice to make — I am only telling you what landed on my desk and how it read to someone who was not you and did not have the context you had. Section four, workload distribution.
Section four. Everyone’s drowning, but only I’m swimming. Marcus hoards the easy wins. I get the nightmares. You want distribution? Take one of his "low-risk" accounts and hand it to me. See how long I last before I snap. It’s not unfair; it’s just efficient. I move faster when the stakes are high. Stop pretending we’re a team. We’re a hierarchy with delusions of equality.
That is a claim I have heard from you before, almost word for word, and I am starting to wonder if it is true or just the story that lets you keep the hard accounts and the martyrdom both. I will look at the actual allocation numbers, not your account of them. Section five is self-assessment. Go.
Go? It’s a blank box. You want me to flatter myself? Fine. I’m indispensable. I catch what you miss. I survive what breaks others. I’m efficient, not lazy. I’m sharp, not cruel. Take it or leave it. If you wanted poetry, hire a poet. I’m here to keep the machine running, even if you hate the noise it makes. Sign the form, Nell. Let’s get this over with.