Melissa McLean

I’ve always gravitated toward both big-picture thinking and practical details, which is probably why this kind of work fits. I started out in construction and electrical environments, where things move quickly and you feel it if something doesn’t come together the way it should. That’s still how I think about delivery.

Since then, I’ve worked in complex technical environments including advanced manufacturing, automation, R&D, and defense-adjacent programs, where timelines are tight and expectations are high. Where things are constantly changing and rarely clean.

I’ve stepped into programs that were already in motion and needed clarity, and helped get them to a place where people know what they’re working toward and how to get there. Alongside delivery, I’ve also supported customer and leadership conversations around shaping new work, often under tight timelines — giving me a good understanding of how decisions are made and how important it is that what gets promised can actually be delivered.

In practice, I move between levels — supporting direction with leadership, working through details with teams, and stepping in where needed to keep things on track. I focus on bringing structure that supports the work, not just structure for the sake of it. That usually means being honest about what’s realistic and helping teams move forward in a way that’s steady and sustainable.

I’m not overly attached to frameworks. If something works, I’ll use it. If it doesn’t, I’ll adjust. What matters to me is that the work actually works — not just in a plan or a report, but day to day for the people doing it. And if something needs to be talked through, I’m probably going to suggest a quick walk and talk, coffee in hand. It’s usually where the best decisions get made.