Government vs Private Sector Structure — Different Owners, Different Design Rules

When people compare government and private organizational structures, they usually land on the same contrast: the public sector is hierarchical and slow, the private sector flat and fast. That contrast describes the symptoms. The real differences sit underneath, in three design constraints that the private sector controls internally and a government entity does not: what the organization is for, where its authority comes from, and who has to approve changes to the structure itself. Design around those three anchors and the rest follows. Ignore them and you get the most common failure in this space, a semi-government entity that inherits the slowest parts of both worlds.

We do a growing share of our structure work in Saudi Arabia with entities somewhere on the public side of the line: ministries and authorities, companies spun out of them, and private firms whose largest customer is government. The Vision 2030 agenda of moving services into commercial entities has made the hybrid case much more common, and it is the case where the design choices matter most.

"We built a company with a ministry's spine"

A semi-government company in Saudi Arabia was created to commercialise a service that had previously been run by a government department. The leadership team was a mix of people from that department and commercial hires from the private sector, and the first structure was, understandably, a copy of the one everyone from the department knew: directorates, general managers, deputyships, and an approval chain that ran every commercial commitment up four levels.

Within a year the commercial team had built a parallel, informal structure to get anything done. A discount for a large client needed four signatures, one of them from a committee that met monthly. The commercial director described the problem in a sentence we have borrowed ever since: "We built a company with a ministry's spine. It stands up straight and it can't turn."

The entity had kept the approval anchor of its parent and taken on the mandate of a company. The two did not fit together, and no amount of goodwill in the commercial team could make them.

The Three Design Anchors

Every organizational structure answers to three anchors. In a private company they are internal and relatively easy to move. In a government entity they are external and fixed. Semi-government entities sit in between, and designing one means deciding, anchor by anchor, which side it should borrow from.

The practical consequences follow from the table. In a government entity, the structure is tied to budget lines and approved positions, so organizational design is partly a negotiation with whoever approves them, and it has to be justified in terms of the mandate. In a private company, structure is a management tool and can change as fast as strategy does. In a semi-government company, the most important design decision is which anchor to take from which side: typically a public mandate and public-style accountability at board level, combined with private-style authority and approval inside management.

Here's the contrarian part

The instinct in public-sector transformation is to make government entities look more like startups: flatter, faster, less formal. We think the goal is clarity, not flexibility. Much of the formality in a well-designed government structure exists for good reasons. Written procedures make public decisions auditable, defined positions keep services running when leaders change, and a clear chain of authority lets citizens and oversight bodies know who answers for what. Stripping that out in the name of agility often produces an entity that is neither accountable nor fast.

The second point is about churn. Public entities restructure far too often, usually when leadership changes, and each new structure reflects the preferences of the person at the top rather than a change in the mandate. That is expensive in ways that rarely show up in a budget: people spend a year learning the new boxes, informal networks do the actual work in the meantime, and the entity's memory thins with every reshuffle. Anchor each restructuring to the mandate, and treat a change of leader as a reason to review the structure, not to redraw it.

Why it works

Max Weber's account of bureaucracy is still the right place to start, because it explains that the formality of public organizations was designed as a feature: rules, written records and defined offices exist so that authority is exercised predictably and impersonally, not according to who you know. Henry Mintzberg's configurations in The Structuring of Organizations add the design vocabulary. Much of government resembles what he called the machine bureaucracy, which works well for standardised, high-volume services and badly for novel problems, and knowing which of your units is which is half of good public-sector design.

Mark Moore's Creating Public Value explains why the private-sector template does not transfer directly. His strategic triangle asks public managers to align three things: the public value they are trying to create, the legitimacy and support they need from their authorising environment, and the operational capacity to deliver. A private company's structure only has to serve the first and third. A public entity's structure has to serve all three, which is exactly why approval and authority carry so much more weight. The New Public Management wave of the 1980s and 1990s, which imported private-sector tools into government, left a mixed record for this reason, and much of the later critique argued that borrowing the tools without the conditions produced the formality of one sector and the accountability gaps of the other.

In our own work the pattern is the one in the story above. Hybrid entities succeed when they are designed as hybrids on purpose, with written corporate governance at the board and real commercial authority in management. They struggle when they inherit a parent's structure by default, which is a close cousin of the problem we describe for holding company structures that copy one org chart across very different businesses.

A practical checklist

• Write down the three anchors for your entity: the mandate as it is legally defined, the source of each major decision right, and who must approve structural change.
• For a semi-government entity, choose each anchor's side deliberately. Public-style accountability at board level and private-style authority in management is the usual answer; write down the exceptions.
• Separate standardised services from novel work. Keep the first in formal, procedure-driven units and give the second cross-functional teams with clear boundaries.
• Map every approval chain for commercial decisions and remove each step that exists by inheritance rather than by rule.
• Tie every restructuring proposal to the mandate, and write the mandate-based reason at the top of the proposal.
• Keep a record of every structural change, including what changed, why and who approved it. In the public sector this is not overhead; it is accountability, and it makes the next change easier to justify. Our piece on change management covers the people side of carrying that change through the middle.

Ask yourself

• Could we state, in one sentence each, our mandate, the source of our authority, and who approves changes to our structure?
• Which of our approval steps exist because a rule requires them, and which because the previous structure had them?
• If we are semi-government, which parts of our parent's structure did we inherit without deciding to?
• Did our last restructuring follow a change in mandate, or a change in leadership?
• Which of our units deliver standardised services and which face new problems, and are they designed differently?

The takeaway

Government and private structures differ less in style than in their anchors: who sets the mandate, where authority comes from, and who approves the structure itself. Design from those anchors rather than from the org chart, choose each anchor's side deliberately when you are a hybrid, and tie every restructuring to the mandate rather than to the leader. The goal in the public sector is not to look like a startup. It is to be clear about who answers for what, which is also why the org chart and the organizational structure are worth keeping distinct.