Passion · Week 2 · Tuesday
She’s thirty-four and four months into a new team, still at the stage where she reads the room more carefully than she’d like to admit. On Thursday a colleague walked the leadership group through an approach — the approach she had built, over three weeks, mostly alone — and described it without saying her name.
Maybe he took it. Maybe he was summarizing team output the way people summarize team output, and it never occurred to him that attribution was the point. She has watched the moment back in her head enough times that the tape is worn through and she genuinely cannot tell anymore.
What she has done since Thursday is build.
She has the timestamps on the original document. She found an old thread where he asked her a question that proves he didn’t know the answer three weeks ago. She took a screenshot of something on Friday that she will never need and cannot explain wanting. It’s Tuesday morning now and there is a draft in her outbox, carefully worded, not shrill — she’s proud of how not-shrill it is — with her manager copied.
Building a case and addressing a problem are opposite moves.
That’s the thing that took me a long time to see. They feel like the same activity. Both of them are about the wrong. Both of them feel responsible, even diligent. But one of them ends and the other one compounds, and you can tell which is which by asking a simple question: does this activity require the other person?
Addressing it requires him. You have to go to him, you have to be wrong-footed for a minute, you have to risk finding out it was nothing and feeling foolish. Building the case requires nobody. You can do it forever, alone, at your desk, getting stronger the whole time.
Notice what that verse does not say. It does not say his weakness is to overlook an offense. It does not say his exhaustion, or his cowardice, or his conflict-avoidance. It says his virtue, and it puts insight at the front of the sentence as the thing that makes it possible.
Overlooking is not the same as swallowing. Swallowing is what you do when you’re afraid, and it doesn’t overlook anything — it files it somewhere you’ll find it again in eight months. Overlooking is a decision made from strength by someone who could pursue it and has looked at it clearly and concluded it does not need a verdict.
The Cursor
It’s 8:40 and the draft is open and the cursor is over send.
She can file it. It’s accurate, it’s measured, it will be taken seriously, and it will do exactly what filing does — it will move the question from between two people to above them, where it becomes permanent and someone else’s to adjudicate.
Or she can close the laptop and go find him at eleven, when he gets coffee, and ask him a plain question with nothing loaded behind it. Hey — Thursday, in the leadership walkthrough. Was that the piece I put together? No case. No timestamps in her back pocket. Just the question, asked once, of the actual person.
The cost is specific and worth naming: she gives up the protection. Right now she has documentation, and documentation feels like safety when you’re four months in and don’t yet know who has your back. Walking over with a question means standing there with nothing in her hands.
What To Do Today
Delete the file you’ve been building. Not the work — the file. The screenshots, the thread you saved, the running mental list.
Then ask the question out loud, of the person, today.
And understand what this is not: it is not a guarantee. He may say something that makes it clear he knew exactly what he was doing. That happens. If it does, you’ll deal with the actual thing instead of the version you’ve been feeding for four days, and you’ll deal with it from a position where you are not already three days into a war he doesn’t know he’s in.
Leave a Reply