Why the Prime Minister’s Office Runs on Memory — Until It Breaks

The hidden truth of governance by memory.

Most Prime Minister and Executive Offices do not actually run on structure.

They run on memory.

Not documents.

Not dashboards.

Not frameworks.

Memory.

The memory of who handled a crisis last time.

Which ministry “usually fixes this.”

Which officer knows how approvals really work.

Which workaround bypasses a broken process.

This is why PMOs often appear effective only while certain people remain in the room.

Remove those people — retire them, rotate them, replace them — and patterns emerge quickly.

Escalations spike.

Decisions slow down.

Contradictions surface.

The PMO shifts from directing execution to firefighting it.

This is not a leadership failure. It is an anatomy failure.

The Hidden Truth: Most PMOs Don’t Have Insight to Enterprise Anatomy

A PMO is expected to translate national strategy into execution, coordinate across ministries, resolve conflicts, absorb shocks, and maintain momentum.

Yet most PMOs lack the one thing required to do this reliably: an executable enterprise anatomy.

In its absence, substitutes emerge naturally. Experience replaces structure. Memory replaces logic. Escalation replaces architecture.

For a time, this works — especially in stable periods or when experienced individuals remain in place.

But it does not scale. And it does not endure.

What Happens When Memory Replaces Architecture

Across governments — including the United States, Australia, India, and the Middle East — the same execution pattern repeats.

Strategy is announced clearly at the intent level. Ministries interpret that intent independently. Processes diverge. Rules and systems fragment. Implementations multiply. Operations improvise.

The PMO becomes the final escalation point, not because it owns execution, but because no one owns the structure that binds execution together.

This is why PMOs often feel powerful and exhausted at the same time.

The Turning Point: “Explain What You’re Doing So a 15-Year-Old Can Understand”

Earlier this year, the US government issued a direct instruction to major consulting and advisory firms, including Accenture and others: Explain what you are doing in a way that a 15-year-old can understand.

This was not about simplification. It was about exposure.

Because when Enterprise Architecture cannot be explained simply, it usually means it does not control decisions, it does not bind execution, and it does not survive people leaving.

If the PMO cannot clearly explain who owns which rules, how strategy turns into action, or why decisions repeat or stall, then the PMO is not running on architecture.

It is running on memory.

Enterprise Architecture Is the PMO’s Missing Instrument

Real Enterprise Architecture is not IT. It is not documentation.

It is the instrument that allows a PMO to function without relying on personal memory.

When applied properly, it binds strategy (P1) to execution (P6), makes rule ownership explicit (P3), enforces shared logic across ministries, exposes deviations structurally, and survives leadership and staff transitions.

Without this instrument, the PMO cannot direct the State. It can only react to it.

The Diagnostic Questions Every PMO Must Answer

These questions are not theoretical. They surface reality immediately.

Which national outcomes today are not traceable to a clear rule owner?

Which programs were funded before execution logic was fully defined?

Which escalations repeat because no structural fix exists?

Which decisions depend on “who knows how this works”?

What breaks the moment a senior official is rotated out?

If the PMO leadership changed tomorrow, what would silently collapse?

And most importantly:

Can we explain how government execution actually works to a 15-year-old — without relying on names, exceptions, or institutional memory?

If these questions feel uncomfortable, that discomfort is the signal.

The Real Risk Facing PMOs Today

Governments are moving faster. Policy cycles are shorter. Scrutiny is higher.

A memory-driven PMO cannot scale in this environment.

Every new reform, dashboard, or coordination mechanism added without anatomy increases dependence on individuals rather than structure. Over time, this makes execution more fragile, not more resilient.

That is why Enterprise Architecture must become a PMO tool, not an IT function.

What Changes When the PMO Owns Enterprise Anatomy

When Enterprise Anatomy is installed at the center, strategy stops leaking. Escalations reduce structurally. Ministries align without micromanagement.

Knowledge becomes durable. Leadership transitions stop being traumatic.

The PMO becomes an enterprise surgeon again — not a firefighter.