Back to Services

Project, Program & Portfolio Management

Deliver transformational change at scale. From setting up a PMO to executing complex multi-stakeholder programs, I bring disciplined execution methodology, governance clarity, and—most critically—structured change management to ensure transformations stick.

Three Pillars of Program Success

Portfolio Management

Manage your organization's full portfolio of strategic initiatives. Prioritize by impact, sequence by dependencies, and optimize resource allocation across competing programs.

  • Strategic portfolio alignment
  • Prioritization frameworks
  • Resource and capacity planning
  • Risk and dependency mapping
  • Executive-level governance

Program Management

Coordinate multiple integrated projects toward a single strategic outcome. Establish PMO structure, build governance frameworks, and deliver end-to-end program execution with discipline.

  • PMO design and charter
  • Program governance structures
  • Schedule and budget integration
  • Cross-functional alignment
  • Benefits realization tracking

Change Management

Transform how people work. Surface resistance, build stakeholder commitment, and drive adoption of new processes, systems, and ways of working. This is where most programs fail—and where we focus relentlessly.

  • Stakeholder impact analysis
  • Resistance management
  • Sponsor activation
  • Communication strategies
  • Adoption metrics and reinforcement

Why Transformations Fail

The harsh reality: 60–70% of transformations miss their benefits targets. Not because the plan is wrong, but because people don't change. Programs get delayed, scope creeps, stakeholders resist, and you end up back where you started—just with more process overhead and burned-out teams.

Execution Without Adoption

Great project plans, poor change strategy. The new system goes live on time, but people go back to old ways. Benefits evaporate.

Hidden Resistance

Stakeholders nod in meetings and undermine change behind closed doors. Resistance surfaces late, derailing the timeline and morale.

Leadership Misalignment

Sponsors aren't visibly committed. When teams see leadership indifference, adoption becomes voluntary—and people choose the familiar.

No Adoption Roadmap

Communication happens ad-hoc. Training is generic. You have no mechanism to surface adoption barriers or measure whether change actually stuck.

Governance Gaps

Multiple programs step on each other. Resource conflicts arise. There's no single source of truth for status, dependencies, or trade-offs.

Burnout and Churn

Change fatigue without visible progress. Talented people leave. You lose institutional knowledge during transformation when you can least afford to.

Why Change Management is the Difference

Here's what I see across organizations: The technical work is usually done well. The schedule is solid. But change management—understanding who's affected, why they resist, how to move them—gets treated as an afterthought. That's where 70% of failure lives. I flip that: change management is the program strategy, and the technical work is one component of it.

Stakeholder Clarity

Map who's affected, how they'll be affected, and what success means to them. Not all stakeholders change at the same rate. Understanding this drives targeted communication and support.

Resistance as Data

When people resist, they're telling you something important—usually that they don't believe in the why or don't feel confident in the how. Surface it early. Address it directly.

Visible Sponsor Commitment

Active, visible leadership support is the #1 predictor of change success. We activate sponsors to model the change, communicate the why, and reinforce adoption publicly.

Adoption as Measurable

Define what adoption looks like—specific behaviors, frequency, proficiency. Measure it. Identify who's lagging and why. Intervene with precision, not broadcast communication.

Momentum Through Wins

Find quick wins early. Build momentum. Show that change is possible and leads to better ways of working. Reinforce with stories of people who've embraced it successfully.

Sustain the Change

Most programs end and people drift back. We build capability transfer, role modeling, and reinforcement mechanisms to ensure the change sticks after you leave.

Change Management Framework

I use a structured approach to move people through change. This isn't feel-good communication—it's behavioral psychology applied to organizational transformation:

1. Awareness

Stakeholders understand the why. Why are we changing? What happens if we don't? Why now? This is emotional as much as rational.

2. Desire

People want to support the change. You've shown them what's in it for them, addressed their concerns, and created social proof (sponsors modeling it first).

3. Knowledge

People know how to operate the new way. Not generic training—targeted, role-specific, hands-on. Reinforced multiple times. Easily accessible.

4. Ability

People can execute the new way. They've practiced. They've received coaching. They've solved problems that came up. They feel confident.

5. Reinforcement

New behaviors are reinforced through systems, metrics, processes, and leadership. People see consequences for going back to old ways. Change becomes "how we work here."

How We Work Together

1

Portfolio Assessment

Understand your portfolio of programs, dependencies, resource constraints, and strategic alignment. Identify where governance gaps exist.

2

Stakeholder & Change Analysis

Map affected stakeholders. Assess readiness for change. Identify early resistors and champions. Surface what drives adoption and what blocks it.

3

PMO & Governance Design

Establish program structure, decision rights, and communication cadences. Build the infrastructure for disciplined program delivery at scale.

4

Change Strategy Execution

Activate sponsors. Drive communication campaigns. Build training and adoption support. Surface resistance and address it directly.

5

Adoption & Reinforcement

Measure adoption. Course-correct. Reinforce through systems and leadership. Build capability so change sticks long after we hand off.

Expected Outcomes

Based on 25+ years leading transformational programs across Fortune 500 organizations and high-growth companies:

30–40%
Faster program delivery through structured governance
80%+
Adoption rate through targeted change management
4–6 mo
Time to sustained behavior change
90%+
Stakeholder alignment and buy-in

My Approach

Change First, Process Second

Your project plan is important, but adoption is everything. I design the program around what drives people to change, then build the project management infrastructure to support it.

Resistance is Valuable

When someone says "this won't work," I listen. Resistance often surfaces the real constraints: people don't understand, they're not equipped, or leadership isn't truly committed. Address it there.

Sponsor Activation, Not Communication

Sending emails doesn't drive change. Visible, active leaders modeling the new behavior does. I hold sponsors accountable for change, not just the project team.

Transparency on Progress

Real dashboards. Real metrics. You'll know exactly which initiatives are on track, where resistance is happening, and what it will take to get back on course.

Capability Transfer

When I leave, your organization knows how to sustain the change. I build the PMO, transfer the methodology, and coach your team to operate the program independently.

Peer Leadership

I work with you as a peer, not a vendor. I'll challenge assumptions, speak directly about obstacles, and help you make better decisions—especially about change.

Frequently Asked Questions

Why is change management so critical?
Studies consistently show 60–70% of transformations fail to achieve their intended benefits. The reason? Not the technical work, but adoption. Great plans fail because people don't change. I've seen organizations execute flawlessly on project schedules while adoption rates stayed below 30%. That's like building a highway nobody uses. Change management turns project success into business outcomes.
How do you measure adoption?
Adoption isn't a feeling—it's measurable behavior. For a new system, I define: what percentage of users are actively using core functionality at target frequency? For a new process, what percentage of transactions flow through it correctly? For a cultural change, what behaviors are we seeing at all levels? We track metrics by role, by location, over time. When someone's lagging, we know it and can intervene—not broadcast another email.
What if leadership isn't aligned on the change?
That's a blocker I surface immediately. You can't drive organizational change with mixed signals from the top. In that case, the first work is sponsor alignment—getting leadership aligned on the why, the vision, and what they personally need to do. Sometimes that means delaying program execution until alignment is real. Better to delay a few weeks than execute for six months with leadership working at cross purposes.
How long does change management take?
Depends on the scope and complexity of change. Simple process changes might take 3–6 months to reach sustained adoption. Major organizational transformations might take 12–18 months. The key: don't declare victory when the system goes live. That's when adoption work really begins. I stay engaged through the adoption phase to reinforce, measure, and adjust.
What's the difference between this and a traditional project manager?
A project manager owns schedule, budget, scope, and deliverables. I own those—plus adoption and sustained behavior change. If your initiative is 40% technical work and 60% change work, a traditional PM will get the 40% right and leave the 60% undone. I flip the priorities: change is the strategy, and project management enables it.
What if people just refuse to change?
In my experience, people don't refuse to change—they refuse to be changed without understanding why or feeling equipped. When resistance is real and persistent, it's almost always pointing to one of these: (1) They don't believe in the why, (2) They're not convinced leadership is actually committed, (3) They lack confidence in their ability to work the new way, (4) The change disadvantages them and nobody's acknowledged that. Address the root cause, and resistance often softens. Sometimes you do need to make firm decisions about people who won't move, but that's rare when the above is handled well.

Ready to Transform?

If you have a program that needs delivery discipline and a change management foundation that actually works, let's talk. The first conversation is free and no-pressure.