I’ve written a series of articles about my career and the roles I’ve moved through over time. Call it a work version of the examined-life idea: if I’m not examining the work, I’m not really choosing how I do it.
It’s a non-linear path: naval nuclear power, recruiting, technical writing, software and web development, marketing, executive communications, and now perhaps a shift toward program management.
These reflections are drawn from my own experience in specific roles and environments. They’re not meant to generalize or serve as a complete account. They reflect how I experienced the work at the time, which rarely fits neatly into a clean narrative.
The point isn’t to document everything. It’s to show how I think through work that doesn’t come fully defined.
Across roles, a few patterns show up repeatedly: responsibility before readiness, learning while doing, making decisions with incomplete information, and learning where effort compounds and where it doesn’t.
Looking back, the pattern is clearer than it was while I was in it.
If your work involves program management, operations, or moving things forward across teams and imperfect systems, some of this may feel familiar.
If you happen to be hiring for that kind of work, this is how I tend to show up.
- Starting Late, Learning Fast, and Earning Trust
- Access Before Readiness
- Operating in Ambiguity
- When Judgment Isn’t Enough
- Where the Lines Converge
Photo by Christy Ash on Unsplash