325: Why Public Sector Projects Really Fail with Matthew Oleniuk

September 17, 2025·49 min·4 clips

Matthew Aleniak reveals how public sector systems become a 'cohesive goo' that slows down projects instead of accelerating them.

This episode features host Laura Bernard and guest Matthew Aleniak, a former senior public servant with 15 years of experience overseeing complex government projects. They examine the underlying causes of project failures in public sector environments beyond mere process issues. Aleniak argues that public sector structures, comprising numerous non-interoperable agencies and departments, create a slow, "cohesive goo" that hinders systems. He cites the scale of these organizations, like the 3-million-strong U.S. federal workforce, to illustrate why individual leaders feel powerless. The discussion identifies a core issue: infrastructure is designed to protect against failure rather than achieve ambitious outcomes. This leads to excessive oversight layers, including multiple steering committees and reporting requirements, which foster a risk-averse culture. Projects often operate under public, politically-set expectations from the start, unlike private sector products developed in secrecy like the iPhone. A significant insight is that success metrics in government are inherently vague and difficult to quantify compared to private-sector profit measures. Aleniak notes that risk management systems are typically built for steady-state operations, not for time-bound projects, making them misaligned. He emphasizes that project leaders can create their own "mini culture" of achievement and innovation within their teams to counteract the broader environment. Leaders are advised to transform oversight meetings from interrogations into exchanges by anticipating challenges and preparing proactive responses. A memorable suggestion is to reframe risk conversations by asking, "What will prevent you from achieving your outcomes?" instead of relying on standardized risk registers. Aleniak points out that the most critical risks, like a disengaged key stakeholder, often remain unspoken because they don't fit formal categories. He uses the vivid analogy that every day in a project's fixed timeline is "expiring," underscoring the need for purpose-driven action. The conversation stresses that true project ownership requires leaders to operate with their "eyes wide open" about potential obstacles. The tone is candid and educational, blending personal experience with practical coaching advice for practitioners. The style is conversational, with the host and guest exploring systemic challenges while offering actionable strategies. This episode is ideal for public sector project managers, PMO leaders, and anyone frustrated by bureaucratic inertia seeking ways to drive delivery. Listeners who prefer discussions solely about technical project management processes might find the focus on organizational behavior and politics less relevant.

As heard by us

A blunt look at why public projects fail when oversight protects the wrong things.

The episode lands on a hard truth: public sector projects often fail less because the process is wrong and more because people will not name the behaviors driving the failure.

Read the full review in PlayNext →

Why you'd press play

When projects look busy but still drift, this gives you the hard questions to ask.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from PMO Strategies