The project plan was sound.

The milestones were clear.

And still, the project struggled.

It was the kind of project most project managers would feel confident presenting. The schedule was realistic, risks were documented, stakeholders were identified, and governance was in place. On paper, it looked like a model initiative—well-structured and well-managed.

Yet despite all of that, momentum slowed. Decisions lagged. Resistance emerged in unexpected places. And what initially appeared to be isolated issues began to reveal a deeper pattern.

With experience comes a difficult truth: many project challenges do not originate in poor planning. They originate in untested assumptions.

A Lesson Learned the Hard Way

Early in my career, I led a complex initiative that checked every procedural box. The project team was capable and engaged. Leadership had approved the plan. Dependencies were mapped and change impacts were considered.
What we assumed—incorrectly—was that alignment equaled commitment.

Stakeholders had nodded in meetings, but ownership of key decisions was unclear. We assumed capacity existed because no one raised concerns. We assumed priorities would hold because they always had before. None of these assumptions felt unreasonable at the time.

But as the project progressed, those assumptions surfaced as friction. Decisions stalled. Competing initiatives quietly took precedence. The team worked harder, but progress slowed.

The plan hadn’t failed. Our understanding of the environment had.

That experience fundamentally changed how I approach projects—not as static plans to be executed, but as dynamic systems to be continually understood.

The Risk We Rarely Name

Assumptions are the quiet drivers of project outcomes. They influence timelines, resource models, and governance structures—often without being explicitly acknowledged. We assume alignment because meetings were held. We assume readiness because similar work has been done before. We assume stability because no one has challenged it.

These assumptions rarely appear in status reports, yet they often carry more risk than the items formally logged in a risk register.
In complex organizational environments, what remains unspoken frequently matters more than what is documented.

From Execution to Leadership

Earlier in my career, I believed strong project management meant tighter control—more detailed plans, more frequent reporting, more precision. Those disciplines are important. They create structure and clarity. But they are not sufficient on their own.

Leadership in project management begins when we move beyond managing tasks and start shaping decision environments.

This shift requires us to ask questions that may feel uncomfortable, especially in fast-moving or politically complex settings:

• Who truly owns the decisions this project depends on?
• What are we assuming about capacity, readiness, and tolerance for change?
• How aligned are we on what success actually means—and who defines it?

These questions elevate our role. They move us from execution to influence, and from delivery to outcomes.

Making the Invisible Visible

Assumptions are not failures. They are unavoidable. Every project operates with incomplete information. The risk lies not in having assumptions, but in failing to surface and test them early.

Some of the most meaningful turning points in my projects have come not from revising schedules, but from creating space for candid dialogue—conversations where teams could challenge what was being taken for granted.

When assumptions are named, they can be validated, adjusted, or retired altogether. When they remain hidden, they quietly undermine even the strongest plans.

Creating this visibility requires leadership presence. It requires psychological safety, trust, and the confidence to slow down briefly in order to move forward more effectively.

The Executive Perspective Projects Require

As projects increase in scale and complexity, success is shaped less by task-level execution and more by organizational dynamics. Strategy, culture, governance, and readiness play a decisive role.

At senior levels, projects rarely fail in isolation. They falter within systems that were not fully understood—or were assumed to be more stable, aligned, or prepared than they actually were.

Project leaders who recognize this expand their impact. They do more than deliver initiatives; they help organizations see clearly, decide deliberately, and adapt intelligently.

This is where project management intersects with leadership.

Shifting the Conversation

One of the most impactful changes we can make is shifting conversations from what we are doing to why we believe it will work. This reframing invites challenge, strengthens alignment, and encourages shared ownership.

When teams understand not just the plan, but the thinking behind it, they are better equipped to respond when conditions change—as they inevitably do.

In today’s environment, adaptability is not a soft skill. It is a leadership capability.

A Challenge to Reflect

If a project you are working on feels harder than it should, pause and consider what assumptions may be operating beneath the surface—not just about scope or timelines, but about people, priorities, influence, and readiness

As project professionals, our value extends beyond execution. It lies in our ability to surface truth, enable clarity, and guide organizations through complexity.

A Call to PMI Members

PMI Manitoba represents a community of professionals committed to advancing the practice of project management. I invite you to reflect on the assumptions shaping your current work—and the conversations you may need to initiate as a result.

Elevating our profession does not always require new tools or frameworks. Sometimes, it requires the courage to ask better questions.

Because sometimes, the project plan didn’t fail.

Our assumptions went unchallenged.

 

---

 

Article written by:

Sandra Rydz – PMP, Prince2, MSP, ITIL v3, MoP

Director, Consulting Services

Paradigm Consulting Group