Chapter 2
Reid
I came to Redwood Falls because I was done with Sacramento.
That's the simple version. The longer version involves fourteen years, a restructuring I didn't see coming, and a moment in the Fire Chief's office when I was offered a lateral move into administration and I sat there listening to the language of it — career continuity, institutional knowledge, a role that leverages your experience — and understood, with the specific clarity that comes from exhaustion, that I was being offered a graceful off-ramp.
That the department had decided I was more useful as a symbol than a captain.
That after fourteen years of doing the work, I was being invited to stop doing it and start talking about it.
I said thank you, and I asked for a week to think about it, and I spent that week applying to six departments and accepted the Redwood Falls offer before the week was up.
Redwood Falls is smaller. Quieter. The call volume is lower and the structural complexity of the department is a fraction of what I'd been managing in Sacramento.
Some people would find that a step down.
I found it a clarification. I wanted to run a good crew in a place where the work was still the point.
I wanted to show up on Monday knowing why I was there.
What I did not anticipate — and I had done thorough anticipation, because I am a person who does thorough anticipation — was the HR director.
I want to be precise about this because I am a precise person and vagueness in situations like this has a way of becoming an excuse for sloppy thinking.
What I mean is: I expected a competent departmental HR professional.
I expected someone organized and policy-literate who would facilitate my onboarding efficiently and whom I would interact with periodically on administrative matters.
I expected to find her unexceptional in the specific way that most institutional roles are unexceptional — not incompetent, just defined by function.
What I found was Dani Cruz.
The distinction presented itself on the first day, in the first ten minutes.
She came into the meeting room already in motion — not rushed, there's a difference — and the color-coded folder under her arm was either a very specific joke or a genuine reflection of how she organized her thinking, and within sixty seconds of conversation I knew it was the latter.
She had built the program herself. She knew every policy in it by memory but more importantly she knew why each one existed, the incident or pattern it was responding to, the human situation underneath the procedural language.
When I asked about the incident command structure she answered without consulting anything, and the answer was layered — not just what the structure was but why it had developed that way, where the friction points were, where she'd personally intervened to smooth them.
I have worked with a lot of HR people. Most of them know the rules. Dani Cruz understood the system.
I filed this in the category of professional observations: Dani Cruz is unusually good at her job.
This was useful information. She was a key operational relationship for any senior leader in this department and I was new and needed to understand how the department worked.
Knowing who was worth talking to was part of that.
This was a complete and sufficient explanation that I accepted entirely and thought about for approximately the rest of the week.
The first month at Station 7 was what I'd expected in some ways and not in others.
The crew was good — experienced, tight, the kind of team loyalty that takes years to build and is worth protecting once you have it.
They were also testing me, which Dani had predicted on my first Friday and which I appreciated knowing, because it meant I was watching for it correctly rather than misreading what I was seeing.
The test wasn't insubordination or friction — it was the more interesting kind, the kind where they were watching how I handled situations that didn't have clean answers.
What I did when the call was ambiguous. Whether I'd back my crew when an outside assessment disagreed with their read.
Three weeks in, a structure fire that started as a routine residential call developed into something more complicated when the building's configuration didn't match the permit records on file.
My crew made a call in the field that deviated from standard protocol — not recklessly, but deliberately, because the lead firefighter read the building correctly when the documentation hadn't.
I backed the call in the debrief. I explained my reasoning clearly, and I also made it clear that I needed to know when field deviations happened so I could support them, not just discover them after.
The crew didn't say much. But something shifted.
I reported the incident to Chief Bauer, who nodded and said, "Good call.
" I also had a conversation with Dani about the documentation side of it — the incident reporting protocols and how the deviation would need to be logged — which was procedurally routine and lasted twenty-five minutes and ranged considerably off-topic by the end.
This was a pattern I was noticing. We would start with a specific professional matter and the conversation would open.
Not wander — open is the right word. Like a window that was cracked and then somebody pushed it wider to let in the air.
She was rigorous about the professional subject and then curious about everything adjacent to it, and her curiosity was the direct kind: she asked what she wanted to know, she listened to the answer, and then she asked the thing underneath the answer.
"Why did you back the field deviation instead of citing protocol and doing a full incident review?" she asked, during the documentation conversation, which had been going on long enough that we'd both gotten a second coffee.
"Because protocol exists to generate good outcomes and in this case the deviation generated a better outcome than the protocol would have. If I undermine the crew's field judgment when it's correct, I don't get their field judgment when I need it."
She was quiet for a moment. "Most captains don't think about it that way. They think about it as: did you follow the protocol or not."
"Protocol is a tool. It's a very good tool but it's a tool." I paused. "You think that way about policy."
She looked at me sharply, like she hadn't expected to be reflected back.
"The fraternization policy has a specific scope," I said. "You built it around power dynamics and supervisory relationships. Not broad-category restriction. I read it."
"I know you read it. You mentioned it."
"I mentioned it because most people read policies to find the edges. You wrote that one to protect people."
She held my gaze for a long moment. Then she said: "Yes," and it was the measured kind of yes that meant she'd heard the full thing I was saying and was not prepared to respond to all of it yet.
I took my coffee back to the operations wing.
The file, as I had come to think of it — the mental folder labeled professional observation: Dani Cruz — had started developing subsections.
This was not the kind of thing I was in the habit of, particularly.
I had not thought about a professional colleague this persistently since my early years on the job when everything was new and every person I worked with was someone I was studying, trying to understand the field through.
I had thought I was past the phase of finding people surprising.
Dani Cruz kept surprising me.
At the monthly leadership meeting she was the only person in the room who disagreed with the Fire Chief and explained her reasoning with the specific confidence of someone who had done the analysis and stood behind it and was not performing certainty she didn't have.
Bauer considered her position. He didn't cave to it, but he modified his.
Dani noted the modification and moved on without making it a victory lap.
I noticed she had been careful not to embarrass him, which was a different skill from being right.
On a Wednesday when I came into the administrative wing to deal with a benefits enrollment issue, she was on the phone managing what sounded like a very difficult personnel situation — I could only hear her end of it — and she was doing that thing I had started specifically watching for: the firmness that didn't harden into coldness.
She was direct about consequences and simultaneously, genuinely, concerned about the person.
She finished the call, looked up at me in the doorway, and said, "Sorry, two minutes" — not apologetically, just factually — and then she was at her desk with the benefits portal open before I'd sat down.
"You're good at that," I said, when we were done.
"The portal? Nobody's good at the portal. It's terrible."
"The phone call."
She paused. "It's a hard situation. The easy thing would be to make it procedural and process the person out." She straightened a stack of papers that didn't need straightening. "That's not why I built this department."
I thought about this on the way back to the operations wing.
I thought about it through the afternoon.
I thought, with a clarity I had been mostly avoiding, that I had been in Redwood Falls for just under a month and the most interesting conversations I'd had were with the woman whose job it was to make sure I didn't make them personal.
I also thought — with the precision that I applied to things I needed to be honest about — that she was aware of it too.
That the conversations that opened were opening in both directions.
That the moment on Friday, first week, when I'd said Reid instead of the formal and she'd repeated it back to me the way she did — that was not a professional exchange.
I was not in the habit of letting files like this stay open without acting on them eventually.
I was also not reckless. There was a right way to do this and a wrong way to do this and Dani Cruz had built the framework that described the difference. I had read it. I would read it again.
But the file was open. And I was done pretending otherwise.