Chapter 3
Dani
I was pleased about this. Professionally pleased. In the way you are pleased when a system you built is functioning as intended.
I was less pleased about the fact that I had begun marking, in my private mental calendar, which days Reid stopped by the administrative wing and which days he didn't.
This was not something I intended to be doing.
I noticed it the way you notice an unfamiliar sound in a room that's supposed to be quiet — with the specific discomfort of something that shouldn't be there.
I had never tracked a colleague's presence before.
I was not tracking it now in any actionable sense.
I was simply aware, in a way I could not turn off, of his particular footstep pattern in the corridor — unhurried, even, the walk of someone who knows where they're going and isn't performing urgency about it — and on the days I heard it, something in my shoulders that I had not noticed was tense quietly released.
This was information I was managing very carefully.
The professional interactions gave me structure, which I appreciated.
We had a scheduled monthly one-on-one for HR advisory purposes — standard for all department heads — and in between there were the organic touchpoints: policy questions he routed through me rather than going directly to Bauer, which told me he understood the value of building the HR relationship correctly.
A compensation equity question. A question about the investigation protocol when a personnel complaint came in from his team.
The complaint was the first real test.
One of the Station 7 firefighters — a six-year veteran, well-regarded — had been escalated against by a newer hire over a comment made during a training drill.
The newer hire felt the comment had been dismissive and undermining.
The veteran maintained it was direct feedback on a performance issue.
Neither position was wrong, exactly, which made it the kind of situation that goes sideways when people try to resolve it through position rather than through understanding.
I received the complaint on a Tuesday and had a conversation with Reid by Wednesday morning.
He came to me rather than waiting for me to come to him, which I noted.
He'd already spoken to both firefighters separately — not to gather information for the complaint process, but to check in on the interpersonal temperature.
"I wanted to know if this was a conflict or a misunderstanding," he said, "before we decided which process it needed. "
I looked at him. "That's exactly the right distinction to make."
"You sound surprised."
"I'm not surprised," I said, and was aware even as I said it that I was slightly surprised. "I'm glad. Most captains want to resolve it as fast as possible and resolution speed isn't the same as resolution quality."
"No. It isn't." He put his hands flat on my desk and looked at the file I had open. "What do you need from me?"
What I needed from him was cooperation, transparency, and to stay out of the active investigation while remaining accessible to his crew.
I said all of this. He said he understood.
He asked three questions — each one the right question, the one that got at what the process was actually designed to protect — and then he left me to it.
I ran the investigation. Took five days.
The outcome was a documented conversation between both parties with a clear behavioral agreement and a sixty-day follow-up check-in.
No formal discipline. Both firefighters shook hands.
Neither of them liked it especially but both of them accepted it, which is usually the best outcome available in situations like this.
When I briefed Reid on the resolution he said, "Good.
" One word. No embellishment. I understood that the one word meant: you handled it correctly and I'm not going to perform enthusiasm about it, and somehow the absence of performance made the word feel more complete than a full sentence would have.
"Your crew is going to come to you about this," I said. "They're going to want to know what happened."
"I'll tell them it was managed and that both people are still on the team and that if they have concerns they should come to me directly."
"That's the right answer."
"I know." Not arrogant. Just matter-of-fact. He looked at me with the focused, unhurried attention I had been cataloguing for a month. "How did you know it would resolve that way? You called it before the process started."
"I've run a lot of these. The complaint language told me where the real wound was.
He used the word dismissed three times. That's not about the comment.
That's about feeling invisible." I paused.
"The veteran didn't know the newer guy was struggling.
He thought he was just giving feedback. Once they understood each other's position the conflict didn't have anywhere to stand. "
Reid was quiet for a moment. "You like this work."
It wasn't a question.
"Yes," I said.
"Not the administration side. The people side."
"They're the same side." I closed the file. "The administration exists to protect the people. If it doesn't do that it's just paperwork."
He left shortly after. I sat at my desk for a long moment with the closed file in front of me, and I thought: this is what I meant about conversations opening.
The policy disagreement came in the third week.
Reid had submitted a memo — he submitted memos, formal ones, which I found out was somewhat unusual for captains who typically called or stopped by — proposing a modification to the shift-change communication protocol.
The current protocol required a written handoff log to be submitted to both the incoming captain and the administrative office within one hour of shift change.
Reid's argument was that the one-hour window created a rush documentation scenario that compromised log quality, and that a two-hour window with a templated format would produce more accurate records.
It was a reasonable argument. I told him so when I replied to his memo. I also told him the protocol existed because of a specific incident three years prior.
He stopped by the following morning to ask about the incident.
"There isn't a version of this I can read?" he asked.
"There is." I pulled the incident report from the filing system — physical copy, because some things I kept in paper. I slid it across the desk. "Take your time."
He read it. I watched him read it, which was something I apparently did now.
The incident was a three-year-old miscommunication between an outgoing crew and an incoming one during a shift change that had no formal handoff log.
An exposure risk for one of the incoming firefighters hadn't been communicated.
The firefighter caught it himself hours later; no lasting harm, but close enough that the department had convened a full review.
The one-hour protocol had come directly out of that review.
Reid finished reading. He looked up. He said: "Fair point."
I blinked.
Not because it was an unreasonable thing to say — it was exactly the right thing to say.
I was surprised because in three years I had brought that incident report to four captains and none of them had said fair point.
Two had argued that their situation was different.
One had asked if the protocol could have a carve-out for his station specifically.
One had agreed with visible reluctance and immediately moved on.
"Most captains push back on this," I said.
"Most captains haven't read the incident that generated it." He slid the report back across my desk. "The two-hour window was a bad idea. Can I suggest the template instead?"
"Send me a draft. I'll review it for compliance with the reporting requirements and if it works we'll pilot it at Station Seven."
He nodded. The template memo arrived in my inbox by end of day. It was good. We piloted it. The log quality improved in the first month and I updated the protocol departmentwide.
The retirement dinner was the week before the six-week mark.
Deputy Chief Hernandez — twenty-two years on the job, the last eight as deputy, known for his terrible puns and his encyclopedic knowledge of every structural anomaly in every building in Redwood Falls — was retiring at the end of the month, and the department threw him the kind of dinner that a twenty-two-year career earns: rented out the back room at Caruso's, full department invitation, the kind of evening where toasts run long and nobody minds.
I attended as a matter of course. I sit at department events because the relationships I build there are part of how the work functions.
I was at a round table in the middle of the room with Priya and the dispatch supervisor and two people from EMS administration, and I was fine, and I was having a professional evening.
Reid arrived with the Station 7 crew and sat two tables away.
For the first hour of the dinner this was entirely unremarkable.
The toasts were warm and funny and Deputy Chief Hernandez cried a little and made a terrible pun in the middle of his own retirement speech and the room groaned and then laughed and it was the specific warmth of a department event done right.
I talked to my tablemates. I refilled my wine.
I was present and engaged and thinking about nothing in particular.
Somewhere in the second hour, the seating rearranged the way it does at long events — people get up, conversations migrate, chairs pull toward whoever is telling the best story.
Priya got pulled into a long conversation with the EMS team on the other side of the room.
The dispatch supervisor went to find the dessert table.
I was at my table with a half-glass of wine and no particular obligation, and when I looked up Reid was at the empty chair across from me.
"Is this taken?" he asked.
It was such an ordinary question.
"Help yourself," I said.
He sat down. He had a glass of whiskey — I'd had him clocked as a whiskey person for weeks. He set it down. He looked at the room and then at me.
"Good dinner," he said.
"Hernandez deserves it. He's the institutional memory of this department. When he walks out at the end of the month we lose things we didn't know we had."
"You worked closely with him?"
"Closely enough. He was the one who told me — when I first proposed the HR infrastructure expansion — that it would work if I built it around trust rather than enforcement. He said the department would follow the policy if they believed the policy was on their side."
Reid turned his glass slowly. "Good advice."
"It was the right advice. It took me six months to fully understand it."
"How did you get there?"
I looked at him. "Why?"
"Because it's an unusual thing to build. Most people in your role build enforcement mechanisms. You built something that functions more like infrastructure. Like the department runs on it without noticing."
Nobody had said it to me quite that way. I was aware of something in my chest doing something I set carefully aside.
"I grew up in this town," I said. "I know these people.
My father's cousin is a dispatcher. Two people I went to school with are on the EMS side.
When you know the people you're building for, you build differently.
" I paused. "I also know what happens when institutions fail the people inside them. I've seen it from both sides."
"What does the other side look like?"
I took a breath and told him about Marcus — not the name I would normally use in professional conversation, but we were past professional conversation, had been for a while.
A long relationship, a supervisor at my previous role, an ending that was complicated by the institution's failure to have any process for navigating it.
Not scandal — just mess. The kind of mess that happens when there are no structures and nobody wants to be the one to build them.
He listened to the whole thing without interrupting. When I finished he said, "That's why you wrote Rule One."
"That's why I wrote all of it."
We talked for another hour. He told me about Sacramento — not the restructuring, but the years before.
A major fire in his third year as a captain that he still thought about.
A crew member he'd mentored who'd gone on to run her own station in the Bay Area.
The way the job could take up your entire identity if you let it and why he'd tried not to let it.
"Did you succeed?" I asked.
"Partially." He looked at me. "I'm still working on it."
The restaurant began clearing. Servers were stacking chairs at empty tables. Most of the department had filtered out in the last twenty minutes, including Priya, who had sent me a text saying don't stay too late! with a winking emoji that I had not responded to.
Reid and I sat at our table until a server politely indicated they needed to reset it.
We stood in the parking lot, the October air clean and cold after the warm room.
The station crew had a knot of people doing the slow goodbye near the far side of the lot.
Reid and I were standing near the restaurant door with six feet of autumn night between us and both of us knowing, without saying it, what the six feet was for.
"I don't usually talk this much," he said. "At these things."
"I noticed." I held his gaze in the dark. "I liked it."
He said goodnight. I said goodnight.
I drove home with the windows down and the cold air coming through and the conversation still turning in my mind, and I thought: this is going to require a policy review.
Not because I'd done anything wrong. Because I was standing at the exact edge of everything I'd built my professional life around, and I needed to know what the view looked like before I decided whether to step across.