My Approach to Complex Project Management

Learnings from Leading a 25-Team Migration

In my first 30 days at a healthcare company, I was handed the largest project I’d ever worked on: migrating all company payment operations to a new payment processor. The scope was massive, the stakeholder map was unclear, and I was still learning internal acronyms and team dynamics. It was equal parts overwhelming and energizing.

Here are the core principles that helped me successfully lead a project spanning 25 teams.

1. Identify Your True Stakeholders—and Earn Their Buy-In

As a newcomer, my first priority wasn’t execution, it was understanding. I invested early in learning who the true decision-makers and day-to-day operators were across engineering, product, ops, and support.

I knew I was asking people for their time, attention, and care, so I made it worth it. Every conversation focused on how this migration would make their lives easier: fewer payment failures, less chaos on autopay days, clearer escalation paths, and more predictable workflows. I also made space for concerns and friction points, positioning myself as a partner rather than a task-driver.

I learned that people don’t invest in projects,  they invest in outcomes that matter to them.

2. Create a Living Project Plan That Becomes the Source of Truth

To manage the complexity, I worked closely with engineers to understand the technical lift and translated that work into a project plan that both technical and non-technical stakeholders could understand.

Rather than trying to design a “perfect” plan upfront, I made it explicit that this document was living and flexible—allowed to evolve as we learned more. The one non-negotiable was accuracy. At any given moment, the plan reflected our true status, risks, and dependencies.

This emphasis on accuracy was about building trust. And yes, it also dramatically reduced inbound Slack messages asking for updates. The answer was always the same: check the plan.

3. Expect Curveballs—and Respond with Calm, Transparent Leadership

A project of this scale will never go exactly as planned. We hit delays, unexpected dependencies, and issues outside our control. When that happened, my role shifted from planner to stabilizer.

I communicated candidly with stakeholders about what was happening, what it meant, and how we were adjusting. Internally, I partnered with engineers to re-sequence work and identify where we could regain momentum. The goal was not perfect adherence to a plan, but reacting with agility and maintaining steady progress.

Running large, cross-functional projects requires resilience, adaptability, and the ability to keep teams grounded when things get messy.

The Result

With grit, flexibility, and strong cross-functional partnerships, we successfully delivered the migration—unlocking meaningful operational and financial benefits for the company.

More importantly, the project reinforced my belief that complex programs don’t succeed because of flawless plans, they succeed because of clear ownership, shared trust, and steady leadership under pressure.