That phrase lived in my head for a long time. It didn't feel like a description. It felt like an accusation.

Army aviator. Instructor pilot. Program manager at the National Guard Bureau, building a resource allocation model across 54 states and territories that's still in use a decade later. National Guard liaison at the White House, working national drug policy across the FBI, DEA, and DHS. Management consultant leading change teams at federal agencies. Nonprofit board chairman who scaled a startup charity to national reach. Commercial pilot. Author.

Read that as a resume and it looks like someone who couldn't sit still. Someone who never figured out what they wanted to be. I read it that way myself for years. Every transition felt like proof I still hadn't found the thing. The specialists around me had a clean answer for "what do you do?" I had a paragraph. And I could see the other person's eyes glaze about halfway through.

I’ve often said I have a plan, not a script for my career. I’ve been open to assignments, opportunities that were interesting at the time and have unlocked doors later on. With any new role, I dive deep quickly to learn as much as I can. When I have it figured out and see the patterns, I begin my search for a new challenge.

Then I came across Charlie Munger's idea of the expert-generalist. Munger called it "worldly wisdom." Carry models from several fields. Use them where the specialists can't, because the specialists never left their lane. Looking across domains and bringing what works from one into another is what makes my perspective unique and insightful.

That reframe didn't happen overnight. But it changed how I saw my own career. I wasn't scattered. I was reading widely and applying specifically. I just hadn't learned to see it yet.

At some point I stopped reading my career as a resume and started reading it as a book. Each role is a chapter. The chapters look different on the surface. Different settings, different stakes, different groups of people. But underneath, the same things keep showing up. The through-line isn't the subject matter. It's me.

I build coalitions. Every role came down to aligning people who don't naturally agree. Military units and civilian agencies. Federal bureaucracies and White House staff. Consultants and the government employees who never asked for them. Nonprofit donors and the communities they'd never visited. The work was always the same: find the shared interest, build the table, keep people in the room long enough to produce something real. That's harder than it sounds, and I've gotten it wrong more than a few times. But the pattern kept repeating.

I import models across domains. The resource allocation framework I built at the National Guard Bureau drew on principles I learned as an instructor pilot. In federal consulting, I used the military's approach to operating without full information. The advisory work I do now in aviation applies patterns I first saw in IT and government contracting. The acronyms change. The problems don't. That's what the expert-generalist looks like in practice. Take a model that worked somewhere else. Test whether it holds in a completely different environment.

I build things that outlast me. Every chapter ended with something still running after I left. The allocation model is still in use. The nonprofit grew past my involvement. I built systems the agencies kept after the contract ended. I care about that more than I probably should. Legacy over credit. If the work stops when I leave, I haven't finished building it yet.

Those three showed up in every chapter regardless of the title on the door. The subjects changed. The constants never did. I think that's what makes it a book and not a pile of disconnected jobs.

There's a concept I see in my LinkedIn feed right now about stepping away for 30 days to see if the work breaks. I'm not going to repackage it as a framework. I lived it before it was a hashtag.

Years ago I left for a 30-day executive program. Before I went, I set my team up. Delegated authority. Documented the decisions that would come up while I was gone. Made sure the systems could hold.

I came back and nothing had broken. Nobody had needed me. Client was pleased and the team was supported.

That silence could have felt like failure. Like I didn't matter. It didn't. It felt like completion. The thing I'd built could run on its own. Staying would have been comfortable. It also would have been the wrong call. The work was done. Time to write the next chapter.

That experience taught me two things I still carry.

Build things that run without you. If the work stops when you leave, you haven't finished building it. You're still a dependency, not a builder. The goal of every chapter is to make yourself unnecessary to the thing you created. I know that sounds backwards. Most people measure their value by how much they're needed, how full their calendar is, how many Slack messages they receive. I've started measuring mine by how well things work when I'm not there.

Run toward something, not away from something. I've caught myself running "from" more times than I'd like to admit. Away from a role that felt stale. Away from politics I was tired of. Those moves always felt productive. But the good moves, the ones I don't second-guess, were always "to." Toward a problem I wanted to solve. Toward a skill I wanted to build. Toward a chapter I was drawn to write.

Running from feels like progress. Running to feels like intention. The difference shows up in what you build on the other side.

I'm still writing chapters. The through-line hasn't changed. I still build coalitions, import models from one field into another, and try to leave things that work after I'm gone. The settings will keep changing. The method won't.

A varied career isn't scattered when it has a through-line. It's a book. Mine's still being written.

If this resonated with how you think about your own career, reply to this email. I'd like to hear your version.

Written by Travis Wright | ETL Advisory

Aviation intelligence for operators, buyers, and founders in the $5–10M segment.

Follow on LinkedIn: | Reply to this email anytime — I read every response.