Chapter 5
Dani
The complaint arrived on a Thursday morning in a plain department envelope slid under my office door, which told me two things: whoever had written it wanted to be sure it reached me directly, and they'd come to the building after hours to deliver it.
I read it before my coffee was done brewing.
I sat with the envelope and thought about the shape of it. Then I picked up the phone and called Priya.
"I need you to pull the last six months of shift records for Station Seven's support staff," I said. "Pattern of scheduling, who's working with who, any overlap anomalies."
"Good morning to you too," Priya said, and then: "Give me an hour."
I needed to talk to Reid.
This was the part I took my time with. Not because I was uncertain — the process was clear and I knew how to run it — but because I was aware of the specific care required when you were about to involve someone whose department was under scrutiny and whose opinion of you was not entirely professional anymore.
The dinner had been two weeks ago. We had not spoken of it since.
We had been professionally normal in the two meetings we'd had since — a benefits review and a cross-departmental safety briefing — and I had been very good at being professionally normal and I was reasonably sure he had been too and I was also certain that neither of us had stopped thinking about the parking lot.
This was not the context in which I wanted to manage a sensitive personnel situation.
But the situation was the situation, and I had built this HR department on the principle that the work was the work, and I was not going to let my personal complications affect how I did it.
I called Reid at eight forty-five.
"I have a situation at Seven that requires a conversation," I said. "Administrative staff, not ops. Can you come to the HR wing this morning?"
He came at nine-fifteen, which was faster than I expected and which I noted and then set aside. He closed the door behind him — something he'd started doing in our meetings, which I also noted — and sat down across my desk and gave me his full attention.
I briefed him on the situation. I kept it factual and procedural: the complaint, the pattern, the investigation process I was going to run, what I needed from him.
I did not use names yet because I wouldn't until I'd done preliminary interviews, but I gave him enough to understand the interpersonal geography.
When I finished he was quiet for a moment. Then: "I suspected something was off."
"What did you see?"
"Energy change. Last six weeks, the admin team started going quiet when I walked through. Not because of me — I pay attention to that distinction — but because of something among them."
"You didn't escalate it."
"I didn't have evidence. I had a read." He paused. "Was I wrong to wait?"
I considered this honestly rather than reflexively.
"No. A captain escalating 'something feels off' to HR without specifics doesn't help me.
It usually muddies the water. What you're describing — watching and waiting for clarity — is the right instinct as long as it doesn't become patience as an avoidance strategy. " I held his gaze. "Does it?"
"No."
"Good." I pulled the preliminary interview schedule I'd drafted.
"Here's what I need from you. I'm going to run individual interviews over the next three days.
I need you accessible to your staff but not in communication with any of the three parties about the investigation.
I need you to manage any tension that surfaces in the station without acting on information I haven't given you yet.
And I need you to trust that I will tell you what I can, when I can tell it. "
He read the schedule. "You're seeing the coordinator last."
"She filed the complaint. By the time I get to her I want a full picture of the dynamics from the other two sides. She'll see that the process was thorough. It matters for what comes after."
"After?"
"After we resolve it. She still has to work with these people. So do they. How they feel about the process is part of whether the resolution holds."
He was quiet in a way that meant he was sitting with something. Then: "I've seen investigations that were technically correct and practically damaging. The people came out of it more divided."
"I know. I've seen them too. That's what I'm trying to prevent." I paused. "Which is why I need you to be steady in that station for the next three days. Your crew reads you. If you seem tense about this, they will be."
"I'm not tense."
"I know you're not." I looked at him. "I'm telling you anyway because it's my job to say the things that need to be said out loud."
Something shifted at the corner of his mouth. Not quite a smile. "Fair enough."
The three-day investigation process was some of the most technically demanding work I'd done in months, not because the situation was complex in any unusual way but because the three people involved were each individually in pain and each individually trying not to show it, and navigating that required a kind of calibrated attention that I find genuinely exhausting by the end of a day.
I interviewed the first technician on Thursday afternoon.
He was defensive initially — the posture of someone who expected to be found guilty before the facts were in — and I spent the first twenty minutes just giving him room to talk without steering, letting the defensiveness run out naturally.
By the end of the hour he had told me things I don't think he'd intended to say, including the specific incident that had started the whole cascade six months prior: a miscommunication about an equipment order that had been blamed on the wrong person and never corrected.
The second technician on Friday morning.
Her account confirmed the miscommunication and added something the first hadn't mentioned: a pattern of the coordinator being excluded from shared information channels that predated her complaint but had gotten worse in the last two months, which gave me a different picture of the power dynamic than the complaint had suggested.
I debriefed with Priya after each interview.
She pulled the scheduling records I'd asked for and we cross-referenced them with the incident timeline the complainant had described.
The picture that emerged was one of accumulated resentment that had started with a genuine error, been allowed to calcify, and then expressed itself in the petty grinding cruelty of people who had given up on resolving the original problem and were managing their feelings about it sideways.
I wrote this up in my working notes with the neutrality of someone who had seen this particular dynamic before and knew what it needed, and I tried not to think about Reid across the building in the operations wing holding his station steady with whatever the operational equivalent of a poker face was.
He texted me once during the three days. Just: Is there anything I should know that affects shift safety?
I appreciated the precision of the question. It was the right question — it drew a boundary around what he was actually authorized to need to know. I wrote back: No. Station safety is not affected. I'll update you when the process allows.
He replied: Understood. One word. I sat with it for a moment longer than the moment required.
The third interview, with the coordinator, happened Monday morning.
By then I had enough of the full picture to make the conversation productive rather than reactive, and she arrived braced for either an accusation or a dismissal and instead found a room where I already understood most of the story and needed her to help me fill in the edges.
She cried partway through — not from sadness, exactly, but from the specific release of finally being heard by someone who didn't have a stake in the outcome — and I held space for it and didn't rush her and by the end of the hour we had a clear enough picture to move toward resolution.
The resolution took another three days. A facilitated conversation between all three parties, which I ran.
A documented behavioral agreement with three clear commitments and a defined check-in schedule.
A one-on-one between the coordinator and each technician that I framed and monitored.
By the end of the week all three people had agreed on a path forward and the energy in the admin section of Station 7 — which I had stopped by twice under the pretext of unrelated administrative business — had visibly shifted.
I briefed Reid on Thursday afternoon. A full hour, because he deserved the full picture at this point and because I trusted his judgment with it.
When I was done he said: "The original miscommunication. Who was at fault?"
"Both of them, in different ways. The technician made an assumption he didn't verify. The coordinator corrected it internally but didn't communicate the correction to the team."
"Has she been told that?"
"Yes. It was part of the facilitated conversation. She needed to hear it — she'd been carrying a full victim narrative that wasn't entirely accurate, and part of why the resentment had gotten so bad was that the other two felt wrongly blamed for something they'd already tried to address."
He sat with this. "You made her hear something she didn't want to hear."
"That's often the work."
"How did she take it?"
"Better than I expected. She's a fair person.
She needed the full picture and when she had it she adjusted.
" I paused. "The technicians are also fairer people than their recent behavior suggested.
People do worse than their best selves when they feel trapped.
When they have a path out most of them take it. "
He was looking at me with that expression I had stopped trying to categorize — the one that was specifically attentive in a way that felt like more than professional regard — and I was aware of the particular quality of the room: the late afternoon light through the window, both of us at the end of a long week's work, close enough across the desk that the professional distance between us felt, as it increasingly did, like a temporary condition rather than a permanent one.
"You're very good at this," he said.
"I've had practice."
"No," he said. "It's not practice. Some people practice this for twenty years and they're still doing it wrong. You — " he paused. "You actually care about the outcome. Not the process. The outcome."
I held my pen in both hands and looked at the notes I didn't need to look at. "That's the only reason to do it."
He stood. Straightened his jacket. He did this in the efficient way he did most things — no wasted motion. "Thank you for the briefing."
"Of course."
He left.
I sat at my desk for a moment.
Priya appeared in the doorway thirty seconds later with her coffee and an expression of aggressive innocence.
"What," I said.
"Nothing."
"You have a look."
"I have a neutral expression."
"Priya."
"I'm just wondering how long you're going to pretend to have a poker face.
" She looked at me with the particular directness of someone who has worked closely with you for two years and is no longer pretending not to see things.
"Because I work twenty feet from you and it's not as good as you think it is. "
I thought about this. "Noted," I said.
She went back to her desk.
I turned back to my notes. The situation at Station 7 was resolved. The crew was intact. The process had been clean. I had done the work correctly and I was, by any professional measure, satisfied with the outcome.
I was also very sure, sitting in the afternoon light with my resolved case file in front of me, that Reid had noticed.
That he'd been watching me work through the week the same way I'd been watching him, and that what he'd seen had landed in him the same way his particular steadiness had landed in me.
The parking lot had been a beginning. Not a conclusion.
I was beginning to think about what came next.