Organizational Design Principles

Definition

The problem it addresses

Most district structures were never designed. They were adjusted, one defensible decision at a time, until the chart described a set of historical circumstances instead of a current strategy.

When the structure finally comes under review, the district discovers it has no criteria. Cabinet members argue from experience and preference, the loudest analogy wins, and the resulting chart is a political compromise that finds a place for everyone currently employed. That structure will need revisiting within a few years.

Stating the design principles first changes what the conversation is about. The question becomes whether a proposed structure satisfies the criteria, and that is a question evidence can settle.

How it works

Form follows function

Strategy drives structure. Processes are built on structure. Structure and process together determine how people are hired, developed, rewarded, and held accountable. A district that reorganizes without revisiting strategy has moved boxes.

Five elements, and structure is one of them

Effective organization design considers five elements together.

• Strategy
• Structure
• Processes and systems
• Reward systems
• People practices

Most reorganizations touch one element and leave the other four alone. That is the usual reason they do not hold. A new chart that leaves the old approval process, the old measures, and the old pay structure in place will be absorbed by them.

Six criteria

LEAN Frog evaluates a district structure, its processes, and its people practices against six design criteria. Together they are the standard the review measures against.

• Deliver a high level of satisfaction across all stakeholder groups
• Establish accountability and responsibility throughout the organization
• Hold strategic direction consistent
• Promote strategic leadership
• Encourage horizontal integration and collaboration across the organization
• Create solutions that support staff in serving the district's students, families, and community

Two further tests sit underneath the six. An organization is effective when it is doing the right things to achieve its mandate. It is efficient when it does them in a way that makes the best use of the capacity it has. A sound design answers to both, and to the performance measures the district has chosen for itself.

What good design looks like in practice

Structure. The fewest layers that work. Spans that fit the work being supervised. Similar capabilities grouped together. An organization designed around strategy and process rather than around the individuals currently in the seats.

Process. No single point of failure or bottleneck. Minimal handoffs. Resources concentrated on value within the value stream. Tasks aligned to the correct line of support.

People. Clear responsibilities and accountabilities for every role, and a visible line of sight from district strategy to an individual's objectives. Right behaviors encouraged and unacceptable behaviors discouraged.

Governance and systems. Communication that is effective and efficient, with the right information reaching the right people in time to make the decision.

The five structure types

There is no single correct structure. Districts run on five broad designs, and each one buys something at a price.

Functional. Groups specialists by discipline and gains depth and operational efficiency. As the organization grows it drifts toward silos, tunnel vision, and weak horizontal integration.

Divisional. Groups each function into a division built around a service line or a geography, with its own resources. Failure in one division does not directly threaten the others. The cost is duplicated specialist capacity.

Matrix. Groups people on two dimensions at once, which suits large organizations spanning different work types. It complicates the chain of command, raises the manager-to-worker ratio, and can produce conflicting loyalties and diffuse accountability.

Program or team based. Organizes around what the district delivers, with cross-functional teams that can change over time. It improves horizontal integration and can duplicate specialist capacity.

Modular. Divides the organization into small, tightly focused units with weak interdependence and high flexibility. It restructures easily and gives up some of the communication and creative gain that tighter coupling produces.

The review answers a question of fit. Which design matches this district's strategy, size, and actual work, and what is the district willing to pay for it?

Evidence required

• The current strategic plan, and whatever the district treats as strategy in practice
• Organizational charts by department and the employee list behind them
• Job descriptions, job analysis questionnaires, and position control records
• Board policy and documented delegations of authority
• The district's own performance measures and how they are reported
• Process documentation for core district transactions
• Interviews establishing where decisions actually get made

Indicators and measures

• Layers between the superintendent and the front line
• Spans of control against the seven indicators
• Functions with no owner of record
• Decisions requiring approval above the level accountable for the result
• Handoffs per core process, and single points of failure
• Capabilities duplicated across two or more units
• Positions whose responsibilities were assembled around a specific individual

Appropriate uses

• To establish the criteria before structure options are designed
• To evaluate a structure the district has already proposed on its own
• During a superintendent transition, to separate inherited design from inherited habit
• When a reorganization has failed and the district wants to know why
• As the framing for a cabinet conversation about what the structure is supposed to do

Inappropriate uses

• As a template. The principles are criteria, and the structure that satisfies them varies by district.
• To justify a decision already made. Principles chosen after the chart are advocacy.
• As a substitute for the work and ownership map. Design criteria cannot be applied to functions nobody has inventoried.
• To settle questions about individuals. Design operates at the level of the role.

Limitations

The six criteria can pull against each other. Horizontal integration and functional depth compete, and so do minimal layers and appropriate spans. Design is the act of choosing which tension to carry, and a review that presents the criteria as a checklist has misunderstood them.

The principles also say nothing about sequencing or capacity to absorb change. A structure that satisfies every criterion and asks more of the organization than it can carry this year is a design that will not survive implementation.

Local conditions matter. Board composition, state law, collective agreements, community expectation, and the calendar all constrain what is available, and an honest design names those constraints rather than designing past them.

Five common design pitfalls

• Design that begins and ends with a structure chart. A chart establishes no governance, creates no accountabilities, and tells nobody how to work differently on Monday.
• Evolution without conscious design. Piecemeal adjustment over years produces unclear accountabilities and working relationships nobody chose.
• Assuming a lean organization happens by itself. Focusing an organization on its primary outputs and reducing non-value-added activity is deliberate work.
• Designing once. Conditions change, and structures that are never revisited are structures carrying an expired forecast.
• Design as political compromise, undertaken to find jobs for existing people. Senior teams need permission to work outside current conventions long enough to ask what the design should be.

An example

In one district, the review recommended a new layer of four executive directors beneath the superintendent's cabinet. Three months after the report, the district's own revised structure kept the program groupings and dropped the layer, using two assistant superintendents instead.

Both versions satisfied the same design criteria. They reached the same span math and grouped similar capabilities the same way, and the district's version asked the organization to absorb less. That is the pattern worth designing for: options that meet the criteria at different levels of disruption, so the cabinet has a real choice rather than a single recommendation to accept or refuse.