Why Whole-of-Government frameworks often struggle at the delivery level

If you’ve been asked to align to a Whole-of-Government (WofG) framework, there’s a good chance your first reaction was:

“I understand what this is asking for… I just don’t know how to make it work here.”

Or maybe:

“This is fantastic! There’s no way I have budget to make it happen.”

That doesn’t mean you don’t support the intent – it usually means you’re already carrying too much, and now you’ve been given something else to fit in.

You’re probably dealing with delivery milestones to hit, stretched staff with mixed levels of maturity and experience, and competing priorities. Now you’re being asked to show progress against a framework that makes sense in principle, but not yet in practice.

The first thing you do is try to align. You map your current work to the framework, you set up the governance group it suggests, you adopt the role titles and start assessing your coverage, because those are the easiest parts to implement. Those things are visible and look like action.

The harder parts are the ones the framework can’t do for you:

• Deciding which parts of the framework matter most for your risks and priorities
• Agreeing what “alignment” actually means in practice
• Figuring out how to make trade-offs
• Fitting it into business-as-usual ways of working

Those take time, conflict, and executive attention, so they tend to come later, if they come at all…

When alignment becomes the job

In high-scrutiny environments, alignment feels like the least risky move.

If someone asks if you’re aligned to the framework, you can point to a document, the governance and a set of domains you’ve covered – this gives you breathing room.

However, it doesn’t necessarily help you decide what to fix first, what can wait, or what’s actually within your control.

Without this clarity, the framework gradually stops being something you use to decide what to change, and becomes something you have to keep up to date. Not because you want to, but because that’s what’s easiest to demonstrate.

 

What this turns into

---

A better approach – start with strategic framing questions, not the framework itself

We’ve seen frameworks work when teams stop starting with the framework itself. Instead, they start with a set of questions:

• What do we genuinely control?
• What decisions do we actually need to make, or what behaviours do we actually need to change?
• How will someone actually use this when they’re under time pressure and constraints?
• When would “good enough” actually be good enough for our context and risks?
• Where would a small investment in capability make the biggest difference?
• Which domains are worth doing properly, and which can wait?

What would be considered “aligned enough” for assurance purposes?

Then they shape the framework around that.

This usually means:

• Explicitly scoping what’s in and out – E.g. “We will assess and improve data governance processes and note technology considerations as a dependency on the IT department”
• Redesigning the framework outputs to answer specific questions – E.g. “This will only be used to decide our top three investment priorities”
• Simplifying the criteria to respect constrained time and capability, and so people can answer honestly and not defensively – E.g. Cutting a 60-question assessment framework down to 15
• Translating framework language into the terms people use in their day-to-day work – E.g. Changing “formalised data stewardship practices” into “data owners oversee data quality on a monthly basis”
• Weighting or sequencing domains based on real decision needs, not equal coverage – E.g. “This quarter we focus on data quality to support core operations; architecture and metadata come later”
• Adding emphasis where local strategic objectives matter – E.g. Including “supporting frontline reporting” as an explicit focus area

The trade-off is less theoretical coverage, and what they get instead is clearer priorities, more honest engagement, and outputs that tell a leader what to do next.

It doesn’t look as neat, but it gets used, and supports alignment as a by-product of good use.

Choose the right time to align

Sometimes alignment is mandated. You can’t ignore the framework.

However, there are times where starting with alignment makes delivery harder. These are particularly when:

• Your team is already stretched and under pressure
• Foundational capability is uneven
• Roles accountabilities are unresolved or aren’t clear
• People are exhausted by change

In those situations, leading with alignment usually creates rework later. Stabilising delivery first is often what makes alignment meaningful rather than performative.

A final note

Not every delivery challenge can be solved by better framework use. Some constraints are structural, political, or fiscal, and in other cases the limiting factor is delivery or technical capability rather than strategic alignment. In those situations, progress depends less on refining guidance and more on strengthening execution.

Frameworks don’t fail because people ignore them – they fail when teams work so hard to align to them that it stops helping them decide what to do. Start with making the parts that matter useful, and let alignment follow.