Support Is a Structure, Not a Feeling

Part one was about what broke and what shifted. This is about what I actually did.

I want to be specific, because “I did the work on myself” is the least useful sentence in the leadership vocabulary. It signals virtue without conveying information. What follows is the actual inventory: the people, the practices, and the tools that helped me get from where I was to somewhere more functional.

TribalNet and the Ceiling Question

One of the things I was sitting with was a question I kept circling without naming directly: is there a ceiling here, and if so, is it structural or is it me?

Robert Castle writes about a tech ceiling that exists at the director level, where technical credibility stops being the primary currency and political and relational fluency take over. I had read his work before. I read it again with different eyes. The distinction he draws is not that technical leaders lack the capacity to lead at higher levels. It’s that the game changes in ways that aren’t always made visible, and many people hit the ceiling without ever being told the rules shifted.

TribalNet gave me a different kind of data. Being in a room with peers across tribal governments doing serious technology leadership work recalibrated my sense of what’s possible in this sector. It reminded me that the ceiling I was bumping against was contextual, not permanent. That matters. Despair is often a failure of context.

Over-Functioning Is a Choice. A Bad One.

My friend’s question stayed with me longer than almost anything else from those months: why are you over-functioning to hold this together?

The honest answer was that I had confused effort with agency. If I worked hard enough, stayed late enough, carried enough of the load, I could offset structural constraints. That is not how organizations work. Systems are designed a certain way, for reasons that accumulated long before I arrived, and the design doesn’t bend because one person pushes harder. What actually happens is that the over-functioner absorbs the cost of a broken system and makes it invisible to the people who could fix it.

I stopped. Not all at once, but deliberately. I let the system show its own constraints instead of buffering them. That was uncomfortable. It was also the right call.

The People Who Showed Up

Support is a structure, not a feeling. I had to build it deliberately, and I want to name what it actually looked like.

The foundation was my wife. Before any framework, any mentor, any peer conversation, there was someone at home who was willing to hear me out without an agenda. She listened when I needed to say things out loud before I knew what I actually thought. She kept me grounded when my perspective was drifting, and real when I was at risk of either catastrophizing or minimizing. That combination, genuine presence and honest calibration, is not something you can replicate anywhere else in a support network. Everything else I’m about to describe was built on top of that.

The next layer was a former military colleague, someone who served alongside me when I was a Signal Officer through the kind of shared experience that doesn’t require explanation later. There is a particular kind of trust that comes from having been in difficult circumstances together, and that trust doesn’t expire. I could be completely honest with them in ways that required no framing or context-setting. Bringing deep experience, real perspective, and the kind of grounded Christian character that makes someone a reliable voice when the noise is loudest. They have seen enough of life and leadership to know the difference between a hard moment and a defining one.

The third layer was a former boss who became something more durable than a professional reference. The transition from reporting relationship to genuine mentorship doesn’t happen automatically. It requires the other person to stay invested after the org chart stops requiring it, and it requires you to be willing to be known rather than just managed. I was fortunate to have that. Someone who had seen me work, understood my strengths clearly, and had enough history with me to call things accurately when I couldn’t. They knew the difference between a hard season and a pattern worth worrying about, and they helped me tell the difference too. That grounded, longitudinal perspective is something you cannot manufacture. You earn it over time with someone who chooses to stay in the conversation.

The fourth layer was an external mentor with no connection to my sector, my organization, or the specific dynamics I was navigating. A senior executive with decades of experience across a very different field, which turned out to matter more than I anticipated. The distance was the point. They had no stake in the politics, no history with the personalities, no reason to manage what they said to protect a relationship inside the system. They could be a genuine sounding board in a way that proximity makes impossible. When you are in the middle of simultaneous personal and professional turmoil, that kind of external anchor is not a luxury. It’s load-bearing. They brought pattern recognition at a level I couldn’t access from inside the situation, and they did it without rushing me toward a conclusion.

The fifth layer was peers. I want to be precise here, because my experience with peers during this period was genuinely good, and I don’t want to frame it as something it wasn’t. I’m not wired for competitive peer dynamics. West Point has a phrase for it: cooperate and graduate. That ethos was serious, and it stayed with me. What I recognized during this season was how precious that absence of competition actually is. Peers made time. They shared what they were actually carrying. The exchange was honest and mutual in a way I didn’t take for granted, because I know enough to know that isn’t universal.

Voices Worth Following

Several names appear in my notes because they showed up at the right time.

Christopher Voss on negotiation gave me language for what was happening in conversations where I felt unheard. His framing, that being heard is a precondition for being understood, helped me stop trying to win arguments and start trying to create the conditions where real communication could happen. It’s a subtle shift with significant operational consequences.

Jefferson Fisher on communication did something different. Where Voss gave me strategy, Fisher gave me the moment-level mechanics: how to slow down inside a hard conversation, how to respond instead of react, how to hold your ground without escalating. His core argument is that the person who controls the pace controls the conversation. That landed for me as a leader who was, at the time, letting urgency dictate my register in situations that required steadiness. The practical application is unglamorous. Pause longer than feels natural. Say less than feels necessary. Let silence do work you’ve been trying to do with words.

Mel Robbins advice on “Let them” gave me something more basic but no less useful: a way to move when the emotional weather was bad and movement felt impossible. The framework is almost embarrassingly simple. It works anyway.

Vanessa Van Edwards on human behavior helped me read the room more accurately. When you’re under sustained stress, your pattern recognition degrades. Having a more structured framework for reading people helped me stay calibrated in situations where I was most likely to misread them.

Writing as Processing

I started writing not to publish, but to think. There’s a difference, and it matters.

When I’m working through something difficult, my interior monologue is fast and circular. Writing forces linearity. It requires me to put one thought after another in sequence, which means I have to figure out what actually comes first. That discipline surfaces things that looping internal dialogue never does.

I also started naming emotions specifically, as a practice rather than an instinct. Not “I’m stressed” but something more precise: I’m anxious about a decision I can’t influence. I’m angry about something that already happened. I’m grieving a path that closed. The specificity matters because the response to each of those is different. Treating all of them as “stress” and pushing through is how you end up in the police station with Jeanie Bueller.

The gratitude journal is the piece of this that sounds most like a self-help cliche. I’m including it anyway because it worked. Not in a motivational-poster way. In a neurological-recalibration way. The brain under sustained pressure filters for threat by default. Deliberately naming what is working, what is good, what is present, counteracts that filter. You don’t have to believe in the mechanism for the mechanism to function.

What This Actually Adds Up To

None of these tools is sufficient on its own. That’s the point. What held me together was a system, not a single intervention. Scripture and Stoicism gave me a philosophical frame. Honest peers gave me accurate feedback. Specific thinkers gave me operational vocabulary for specific problems. Writing gave me a processing practice. The journal gave me a counterweight to threat-filtered thinking.

The combination is not a program you can package. It’s a set of deliberate choices made under pressure about what to pay attention to and what to put down.

I’m still inside the organization I was inside when this started. The constraints haven’t changed. What changed is that I’m no longer paying an emotional tax on things I cannot move, and I’m no longer absorbing the cost of structural problems to keep them invisible.

That is not a small thing.