For a long time, I thought being a good program manager meant making sure everything happened.
The right people were informed, the schedule was on track, the details were accounted for, problems were solved, and the program was delivered.
And, of course, those things matter.
But over the course of my career, I’ve realized there is an important distinction between managing a program and making a program better.
The first is about keeping things moving.
The second is about asking whether they could move better.
The Work Behind the Work
Program management can look straightforward from the outside. There is a plan, a timeline, a budget, a group of people, and a set of goals.
Programs are living systems. People change. Priorities shift. Information gets lost between teams. Processes that once made sense become cumbersome. A solution that worked for a program of 20 participants may not work for 200.
And sometimes, the biggest challenges aren’t the ones anyone planned for.
That’s where I’ve found that I enjoy program operations most. I like looking at the things that happen between the obvious responsibilities and asking questions such as:
Why are we doing this step?
Does everyone actually need to do it?
Could this process be simpler?
Are we collecting information that we’re not using?
Is there a better way for two teams to communicate?
Could technology eliminate a repetitive task?
What would make this experience better for the person participating in the program?
These questions may not appear in a job description, but they can have an enormous impact on how effectively a program operates.
Good Systems Create Room for Good Work
One of the things I’ve come to appreciate about operations is that good systems are often invisible. When things work well, people don’t necessarily notice the process behind them. They simply have what they need when they need it.
A participant receives clear communication. A colleague knows exactly where to find a resource. A team isn’t spending hours manually completing a task that could be automated. The deadline isn’t missed because someone didn’t know who was responsible. A program manager can spend more time thinking strategically because they’re not constantly putting out the same operational fires.
That’s the kind of improvement I find rewarding.
It’s not about introducing technology or creating processes simply for the sake of doing something new. It’s about making the work easier, clearer, and more effective so people can spend more time doing the things that actually matter.
Technology Is a Tool, Not the Solution
This way of thinking has also shaped how I approach technology.
I’m increasingly interested in how tools like automation, data, and technology can help organizations work more effectively. But technology alone doesn’t improve programs. A poorly designed process that’s been automated is still a poorly designed process.
The first question should always be: What problem are we trying to solve?
From there, the answer might be technology. It might be a new process, better communication, or simply eliminating a step that no longer serves a purpose.
The goal isn’t to use more technology. It’s to use the right tools to create better outcomes.
From Managing to Improving
This way of thinking has changed how I approach my work.
I still care deeply about delivering programs successfully. Deadlines matter. Details matter. People matter.
But I’m increasingly interested in what comes next:
How can we take something that works and make it work better?
How can we make a program more scalable without losing what makes it meaningful?
How can we reduce administrative burden without sacrificing quality?
How can we build systems that support people rather than create more work for them?
How can we use data and technology to make better decisions?
Those questions are increasingly at the center of where I want my career to go.
I don’t think program management and operations are separate from mission-driven work. They’re part of how a mission becomes reality.
A great idea needs a great program. A great program needs great people. And great people need systems that allow them to do their best work.
That’s the kind of work I want to keep doing: not just managing programs, but helping to make them better.
Field Note
The best operational improvements I’ve made usually started with a simple question: Why are we doing it this way?
Leave a comment