These are the things I do consistently, regardless of the industry, the tooling, or the size of the team.
Most of the work I inherit doesn’t arrive as a clearly defined problem. It usually starts as frustration, a missed deadline, or a process that isn’t working the way people expected. Before proposing solutions, I spend time understanding what is actually happening, who is involved, and where the work is breaking down. Once everyone shares the same understanding of the problem, the right path forward becomes much easier to see.
Most escalations don’t come out of nowhere. They usually start as small patterns: an increasing backlog, a growing number of workarounds, or questions that keep coming up. I pay attention to those early signals because they’re often the best opportunity to solve a problem before it becomes urgent, expensive, or highly visible.
Most processes start with good intentions. Over time, people add steps to solve individual problems until the workflow becomes harder than the problem itself. I look for the decisions that were never made, because once those are resolved, many of the extra steps can simply disappear. A successful outcome usually leaves the work simpler than I found it.
Finishing a project isn’t always the right outcome. Sometimes the original business need has changed, adoption never materialized, or the expected value simply isn’t there anymore. If the data no longer supports moving forward, I’m comfortable recommending that we stop, along with a practical plan for closing the work responsibly.
Documentation isn’t valuable because it exists. It’s valuable because someone can use it when they need it. I write documentation that explains the work, the decisions behind it, and how to keep it current so it doesn’t become another outdated document people stop trusting.
When something keeps breaking, my first question isn’t, “What process are we missing?” It’s, “Who owns the outcome?” Until ownership is clear, adding meetings, documentation, or approvals usually creates more work without solving the real problem. Clear ownership makes better decisions possible.
Even the best solution won’t succeed if people can’t realistically adopt it. I look for ways to introduce change that fit how teams already work, balancing business goals with day-to-day operations. The goal isn’t simply to launch something new. It’s to build something people will actually use and sustain over time.
What the first month looks like
Every engagement is different, but my approach is consistent. Here’s what the first month typically looks like.
Week one
Read, listen, and follow one piece of work from beginning to end. No recommendations yet.
Weeks two to three
Define the problem, clarify ownership, and agree on what is in scope and what isn’t.
Ongoing
One clear plan, a regular review rhythm, and escalations only when they’re needed.
Seven case studies covering program management, risk, fraud, compliance, and process improvement.
Read the case studies