The structure you have is a forecast
Every organizational structure carries a forecast. It assumes an enrollment range, a revenue picture, a volume of work, and a set of people available to carry it. Those assumptions were sound on the day the structure was built. Most districts never go back to check whether they still hold.
Structures accumulate. A coordinator position is created when a grant arrives. A vacancy is held open through a tight budget year. A department absorbs a new mandate because someone there said yes.
Each decision is defensible on the day it is made. Together they produce a chart no one would have drawn on purpose.
An organizational review puts that structure back under examination while the district still controls the calendar. Work that begins under a deficit turns a design decision into a reduction decision. That difference is mostly a matter of timing.
This guide describes what a defensible organizational review includes, what evidence it requires, what it measures, and where it should stop.
The questions a review has to answer
A review earns its cost by answering questions a district cannot answer from its own records.
- What work does the district actually perform, and who owns each piece of it?
- Where does decision authority sit relative to accountability?
- Which leaders carry a span they cannot supervise well, and why?
- Which functions have no clear owner at all?
- What will this structure be unable to absorb over the next three to five years?
The last question is the one most often skipped. A structure can work today and still rest on assumptions with an expiration date.
Start with the work
The most common finding in the organizational reviews LEAN Frog conducts is a structure answering a question the district stopped asking years ago. Over and understaffing show up less often than that.
A sound review begins with the work and follows it back. Work leads to ownership. Ownership leads to authority. Authority leads to capacity, and capacity leads to cost. The boxes come last.
That order matters most for cross-functional mandates. State laws are assigning districts responsibilities for technology use, data governance, and disclosure that appear on almost no org chart. The first requirement is a decision about ownership and authority. A new coordinator box is a second-order question, and sometimes an expensive way to avoid the first one.
What the review includes
- Similar experience, knowledge, and skills among those supervised
- Mastery employees
- Related activities
- Results identifiable by metrics
- Work that is routine
- Standardized processes
- A leadership role that is mostly managing
What the measures actually show
The numbers from this work are usually quieter than the reaction to them.
One city district's review counted thirteen positions reporting directly to the superintendent, against five to eight functional leaders in similarly sized peers, with no administrative support for the superintendent's office. Another counted twenty-three direct reports and no established levels of hierarchy, so a coordinator could supervise a coordinator. Neither district was poorly run. Both had grown a structure one reasonable decision at a time.
In another school system, a single position carried five different titles across the district website, its job analysis questionnaire, two job descriptions, and the employee list. Supervisor job descriptions assigning no supervision sat beside questionnaire returns reporting anywhere from zero to more than two hundred direct reports. The district held several competing records of itself, and the org chart was only one of them.
Where the records disagree like that, the first product of the review is a single accurate picture of the organization as it operates today.
Structure and pay are connected more tightly than most districts expect. One compensation study reached the structural conclusion from the pay side and said so in its own closing recommendation. That district carried eighty-seven salary schedules, twenty of them with no employees on them, and one undifferentiated grade covering both supervisors and coordinators.
The cost projections priced the consequence. Twenty-nine of those employees showed a zero projected increase. No amount of money moved them until the schedule was split by responsibility level. Structure had to change before pay could.
What districts actually adopt
Two outcomes are worth knowing before commissioning a review.
In one district, four structural options were presented. Within a year the district had acted on the two that added capacity, creating an academic leadership role and adding administrative support for the superintendent. The two that moved or consolidated existing functions were left alone.
In another, the recommendation rested on a new layer of four executive directors placed 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. The superintendent's direct reports fell from twenty-three to six plus the principal group under either version.
That is two engagements, so treat it as a working hypothesis. It is enough to design for. Additive change is easier for an organization to carry than reallocative change, and a recommendation that reaches the same span math with less disruption tends to survive contact with the cabinet. Build the options so the district has a real choice among them.
Additive change is easier for an organization to carry than reallocative change.
Where an organizational review should stop
A review that tries to answer everything answers nothing defensibly.
It is not a staffing reduction plan. A reduction decision is also a work-ownership decision. Compliance functions attached to an eliminated position do not disappear with the position. The cabinet question is which functions still have to be performed next year and who owns them now.
It is not a facility study. Square footage per student is a useful signal inside a review, and a signal is all it is. When the numbers suggest a configuration problem, the honest recommendation is that the district commission a dedicated study. An organizational review should stay out of consolidating, reconfiguring, or closing schools.
It is not an evaluation of individuals. The unit of analysis is the position and the work, and the report should read that way.
It is not a compensation study, though it frequently triggers one. Titles, grades, and responsibility levels are where the two meet.
Before you commission one
A provider should be able to tell you what evidence they need from you, what they will measure, what the report will contain, and what they will decline to answer. Ask for all four before the contract.
Closing
The structure you operate next year is being set now, by the vacancies you hold and the mandates you absorb. Write down the forecast your current chart assumes. Set it beside the one your finance office is using. The distance between them is the agenda for the review.
