For most of my career, I didn’t have a clean label for the kind of work I kept gravitating toward.
I moved across roles—technical writing, development, marketing, executive communications, even recruiting. But in each one, the work I cared about most wasn’t what was in the job description. It was the work between roles: coordinating across teams that didn’t quite line up, translating complexity into something people could act on, and keeping things moving when ownership was spread out and timelines were real.
At the time, I didn’t call that program management. I called it meta work because it was the work required to make the main work possible.
Looking back across the arc of my career, that other stuff is the through‑line. All of it converges here. The technical, operational, communication, and strategic lines in my career all converge here.
The Accidental Résumé
When I eventually mapped my experience to technical program management, the alignment was obvious. It had just gone unlabeled for a long time.
Years spent writing technical documentation taught me how to internalize complex systems and explain them clearly. Not just to end users, but across engineering, product, and support teams. Each needed something different from the same material.
Time spent as a developer gave me enough technical fluency to sit credibly with engineers. I could follow what they were building and understand the constraints behind their decisions.
Over a decade in marketing—managing a multi-language web portfolio, agency relationships, and major launches—was program management in everything but name. I was coordinating dependencies, aligning across teams and time zones, and tracking work against business outcomes. In the end, the title didn’t change what the work required.
Seven years in executive communications added a different dimension. I was operating at senior altitude, shaping messages under pressure, and synthesizing complex context into something that had to land cleanly, often with no room for iteration.
That work demanded judgment about timing, audience, and tradeoffs. The same kinds of calls program managers make every day.
Even work that sat far outside technology followed the same pattern. Navy recruiting required building relationships from scratch, managing against hard targets, and operating autonomously without a shared playbook. And long before that, standing watch as a nuclear‑trained operator at sea was where I first learned to qualify on complex systems, manage risk in real time, and take responsibility for outcomes that couldn’t be undone.
None of those roles carried a program management title. All of them required program management discipline.
Closing the Formal Gap
I’m not assuming experience alone is enough for this transition. Pattern recognition matters, but so does shared language—especially when stepping into a discipline with its own frameworks and expectations.
That’s why I’m working through formal coursework now, including the Microsoft Program Management Professional Certificate and additional third‑party coursework focused on technical program management.
This isn’t box-checking. It’s how I’ve always closed gaps—pairing lived experience with structured understanding. Much of the material maps directly to work I’ve already done. But having shared vocabulary matters. Concepts like RACI matrices, risk registers, and stakeholder mapping aren’t new practices for me; they’re names for patterns I’ve been executing without formal labels.
What the coursework adds isn’t speed. It’s precision. It gives me language the discipline recognizes, and a common frame for working inside a professional community I’m deliberately choosing to enter.
What I’m Choosing Next
The first four articles look backward. This one is about where I’m heading.
I’m looking for a role in program management, technical program management, or related operational functions. Ideally, the kinds of problems I’ve described here shouldn’t be edge cases. I want to be in environments where cross‑functional coordination, stakeholder alignment, and forward motion under ambiguity are the job, not side effects of it.
I work best in organizations with real infrastructure. It’s not because I need someone else to define the process, but because effective program management requires something solid to manage against. I’ve learned, sometimes the hard way, what happens when decision authority is fragmented and organizational scaffolding is thin.
I’m also more deliberate now about transition risk. I’m changing function, and that means being thoughtful about keeping other variables stable: a work environment where I can build context and relationships in person, organizations where I can observe how decisions actually move, and teams where trust is built through proximity as much as output.
What Compounds
I want to be clear about what I bring, without overstating it.
I’m comfortable communicating across levels. I’ve had to be.
I’ve worked with developers, marketers, executives, vendors, customers, and partners for most of my career—often translating between groups that don’t naturally speak the same language. In program management, that range isn’t ancillary; it’s essential.
I’ve operated under real pressure, in environments where decisions mattered and couldn’t be walked back. That shapes how I think about risk, prioritization, and communication when stakes are high.
I know what I don’t know, and I have a long track record of closing those gaps quickly. Every major role I’ve taken on was one I hadn’t done before. The pattern isn’t recklessness. It’s learning in motion, grounding decisions in evidence, and earning trust through follow‑through rather than credentials.
And I’ve also learned to recognize when conditions aren’t right: when effort won’t compound, when misalignment is structural, and when recalibration is the responsible call. That kind of judgment is harder to teach than any framework.
Not a Final Chapter
I’m aware this series could read like a capstone, a retrospective from someone getting ready to wind things down. That’s not how it feels from here.
I still have meaningful working years ahead of me, and I want them to be the most focused of my career. The earlier decades gave me range. What I’m choosing now is direction.
The technical, operational, communication, and strategic lines in my career all converge here. I didn’t plan it this way. The work just kept pointing me in this direction.
I’m not starting over. I’m starting from everything.