Two halves of the same question
Improvement work in a school district begins in one of three places: strategy, organization, or operations. Most districts start in one and find that the other two were holding the problem.
A comprehensive organization and efficiency review takes on two of the three at the same time. The organizational half asks who owns the work and whether the structure can carry it. The efficiency half asks how the work actually runs once it reaches a department. Districts commission both when the answer to a problem keeps moving between the two.
An instructional scope can be added to either half through a separate module, the Instructional Program Cost and Effectiveness Review, and it changes the unit of analysis from departments to programs. That option is described further down, because the decision to include it belongs at the scoping stage rather than at the end.
The reason to run them together is mechanical. A packaging line produces no more finished product when one stage speeds up, unless the next stage can absorb it. Districts behave the same way. Improve a hiring process inside a department that has no clear ownership of recruiting, and the process gets faster inside a box that still cannot act.
The interesting behavior happens between the stages. Finance holds one part of a story, enrollment holds another, and a principal is hearing something from families that has reached neither report. Responsibility for connecting those observations belongs to nobody in particular. A review that examines departments one at a time will not find it.
The organizational half
This half maps the work the district performs, the position that owns each function, and the functions with no owner. It measures span of control against seven indicators rather than a headcount ratio. It compares job descriptions against job analysis questionnaire returns position by position. It calculates retirement eligibility by department, because that is the fastest-moving capacity risk most districts carry.
The output is a single accurate picture of the organization as it operates today, followed by two or three designed structure options with their span math and their cost.
A fuller description of this half is available in the companion resource, What Should a School District Organizational Review Include.
What a sound structure looks like
Form follows function. Strategy drives structure, processes follow from structure, and the two together shape how people are hired, developed, rewarded, and held accountable. A district that reorganizes without revisiting strategy has moved boxes.
Effective organization design considers five elements: strategy, structure, processes and systems, reward systems, and people practices. Most reorganizations touch one of the five and leave the others alone. That is the usual reason they do not hold.
Before a review evaluates a structure it has to state the principles it is evaluating against, because those principles are the criteria. 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.
There is no single correct structure. Districts run on functional, divisional, matrix, program or team-based, and modular designs, and each one buys something at a price. The review answers a question of fit: which design matches this district's strategy, size, and actual work.
One pitfall is worth naming because it is the most common. Organization design that begins and ends with a structure chart is not design. A chart establishes no governance, creates no accountabilities, and tells nobody how to work differently on Monday.
How value is defined
Value is determined from the perspective of the customer: students, parents, educators, and the community. The department performing the work does not get to decide whether the work was worth doing.
An activity adds value when it is meaningful to that customer, meaning they care whether it is done and how it gets done, or when it changes the product or service they receive. Maintaining the buses that carry children is meaningful to parents whether or not they ever see it happen. A counselor checking a student’s schedule against college requirements changes the service that student receives.
Every activity in a district process falls into one of three classes.
Value-adding. Meaningful to the customer, or it changes the product or service, and it is done correctly the first time.
Non-value-added but required. Neither meaningful to the customer nor changing the product or service, and still required by law, regulation, funding rule, or board policy. A state code requiring a superintendent candidate’s certification to be filed with the probate judge adds nothing a parent would recognize as value, and the district files it. This work gets minimized, simplified, resequenced, or automated. Sometimes the constraint itself can be moved, and naming the constraint is how a district finds out.
Non-value-added waste. Resources consumed by activities that add nothing. Parents do not want to pay more for school lunches so that staff can spend time locating misplaced recipes or producing more food than is needed. Communities do not want weaker teachers because delays in the hiring process let first-choice candidates accept offers somewhere else.
Value is never an expedited action, a temporary fix, a recovery action, or firefighting. Those feel like service from the inside. They are the cost of a process that failed further upstream.
Most districts classify nearly everything as required, and the classification exercise is where the disagreement surfaces. That is the productive part of the engagement. A department leader will argue with a recommendation, and rarely argues with the classification after walking the process alongside their own staff.
Two joined families of waste
Operational waste and organizational waste join to produce inefficiency and lost productivity across a school system while everyone in it is active and working hard. That combination is what makes the problem difficult to see from the top. Effort is visible. Waste is not.
These wastes are usually hidden. They consume revenue and resources, they hold back the people the district serves, they raise staff frustration, and they drive up cost over time. They are commonly defended in three phrases: that is the way it is, it is a personality issue, and that is how we have always done it.
Organizational waste
Organizational waste occurs when leadership fails to identify and maintain focus, provide structure, execute discipline, and motivate ownership. It takes four forms.
Lack of focus. The application of energy and attention to critical objectives. The mission and the message from the top are unclear, accuracy is lost as the message moves down through the levels, and work groups never receive it in a form that applies to what they do daily.
Ineffective structures. The repeatable framework that guides day-to-day work, including processes, expectations, roles, information, and the written and unwritten rules. The structure fails to tell employees what to do and how to do it in a way that reduces waste and keeps it reduced, and it fails to reinforce the behaviors that would.
Lack of process discipline. The checks and balances that keep processes from deteriorating and that address problems accurately and quickly. Leadership responses to problems are unclear, performance and expectations go unreviewed, and groups stop holding their own standard.
Lack of ownership. Taking responsibility for a work area, its processes, and its outputs. Employees stop recognizing operational waste, or they come to accept it, and engagement in improvement fades.
The visible symptoms are familiar in any district carrying them: no strategic plan and no measures, departments functioning as silos, no clear measurement, low or no accountability, poorly defined processes, no document control, unclear expectations, and unclear authority. Every one of those gets reported as a personnel problem. Almost none of them is one.
Operational waste
Operational waste occurs when resources are consumed by activities that do not add value. It falls into four families, and a process walk looks for all four.
People waste. Value lost by failing to capitalize on the knowledge, skills, and abilities of employees and work groups. It appears as assignment, meaning unnecessary or inappropriately assigned tasks; motion, meaning movement that adds nothing, including walking, reaching, and driving; over-processing, where people do not use the better way because training was thin or no standard exists; and waiting, where time is lost on information, a meeting, a signature, or a returned call.
Procedure waste. Problems in how processes are designed and executed. Scattered standardization covers arbitrary or unpredictable processes, steps missed because something was unknown, and competing or duplicative processes. Blind interference covers supervision that produces no sustainable result, arbitrary changes made without full understanding, re-checking original work because it is not trusted, and siloing that meets a department’s internal needs with no consideration of the customer. Unnecessary hurdles cover informal workarounds competing with the official process, uneven flow from backlogs and pinch points, poorly scheduled activities, and steps repeated to correct an error.
Information waste. Value lost to deficiencies in the information available: missing information, irrelevant information, inaccurate information, losses at a handoff, and translation between people or systems.
Asset waste. Human, facility, and material resources used in ways that do not add value. Overburdening taxes people or physical resources beyond safe limits. Fixed assets such as land, buildings, and equipment sit used minimally. Unnecessary transport moves things farther or more often than needed. Inventory and overproduction apply resources before they are required, or produce more output than anyone needs.
These concentrate at the handoffs, particularly where a process crosses from one department into another. Each department can run its own segment well and the transaction between them can still take three weeks, because nobody owns the space between.
Variation
Waste is half of the discipline. Lean removes waste from processes. Six Sigma reduces variation, which is what shows up when a process fails to produce the same result every time.
Stakeholders do not feel averages. Students, parents, and staff expect a predictable outcome from checking a student in and out, changing personal data, hiring a teacher, selecting a bid, or answering a parent’s question. A district can report a strong average and still deliver an experience nobody can count on. A parent does not experience a ninety-nine percent on-time rate. They experience the morning their child’s bus ran thirty minutes late.
A review measures the spread and not only the average, because the spread is what people live with. This is the Lean Six Sigma discipline underneath the engagement, and it is what makes the recommendations defensible, because each one traces back to a step, a class, and a reason.
The efficiency half
This half walks processes. A consultant sits with the people who perform the work, follows a transaction from start to finish, counts the steps and handoffs, and records where the work waits. The people who do the work draw the flow chart. A technical expert drawing it from the outside produces a diagram of the process as it was designed, which is a different thing.
Every district runs an unofficial version of itself alongside the official one. Spreadsheets kept beside the system of record. Email folders serving as a queue. One veteran whose memory makes a process work. This is the hidden factory, and it lives mostly in the handoffs. Finding it is the point of walking the process.
The common pattern is duplicated work. People enter the same information twice because two systems do not talk to each other, or because a report was requested once and never stopped being produced.
Alongside the walk, each department is scored on process and performance maturity across five categories: process documentation, performance measurement, continuous improvement, interdepartmental integration, and software and processes. Each lands at Ad Hoc, Fragmented, Defined, Managed, or Optimizing. Maturity explains why two departments with similar structures and similar budgets perform differently.
Where processes have no measures, the review establishes them. Cycle time, volume, rework, exceptions, and first-pass quality are the usual starting set. A function with no number cannot compete for attention or resources, whatever anyone intends, because a measured accountability wins a resource contest against an unmeasured one by default.
Plan on four to six weeks per function for this work done properly. That figure is the single most useful number for scoping an engagement honestly.
Measuring service from the outside
Every measure described so far is produced by the district or by the review team. Process walks, maturity scoring, span analysis, and cost are all internal evidence. Ask a department how well it serves the rest of the organization and the answer is self-report, and self-report has a predictable direction.
Stakeholder surveys supply the outside measurement. They ask the people on the receiving end of central office work what that service is actually like. The instruments differ by audience.
School leaders rate each central office department on responsiveness, on the contribution that department makes to the work of the school, and on role clarity: who to contact, for what, and what happens next.
Teachers report on the support that reaches the classroom and on the systems and processes they touch directly.
Families report on the interactions they actually have, which are usually with transportation, child nutrition, registration, and the school front office rather than with a central office department by name.
Two constructs are worth measuring separately from service quality. Program value asks whether the people delivering a program believe it produces something worth the effort. Program burden asks what the program costs a school in time, meetings, reporting, and attention. The two move independently. A genuinely valuable program can consume more school capacity than anyone intended, and the schools will know it long before the central office does.
The surveys also locate the seams. When a school leader rates two departments as responsive and still reports that a request involving both of them takes a month, the review has found a handoff problem rather than a department problem. That distinction changes the recommendation entirely.
Where a unit is not rated by anyone outside itself, the report should say so. It happens for legitimate reasons, because the unit is a program rather than a department, or because it serves a population too small to produce a reliable rating. The consequence is the same either way. For that unit the only evidence of service quality is what the unit says about itself, and a superintendent reading the findings deserves to know which conclusions rest on that.
Which functions are in scope
The organizational half covers the whole district. The efficiency half is scoped by choice. The functions most commonly reviewed:
Human resources, including recruiting, onboarding, and position control
Finance, payroll, purchasing, and accounts payable
Transportation
Facilities, maintenance, and custodial services
Child nutrition
Technology services and support
Special education administration
Student services and registration
The operational core is the sound place to start. The work is structured and repetitive, no students sit in the loop, the output can be checked against a known answer, and the failure modes are contained.
The Instructional Program Cost and Effectiveness Review
Non-instructional operations are where most efficiency reviews stop. The Instructional Program Cost and Effectiveness Review is the add-on module that carries the work into instruction, and it changes the unit of analysis. Departments give way to programs.
The question is plain. What does each instructional program cost, what is it producing, and what does the district actually know about the relationship between the two?
Most districts cannot answer that from their own records, for an understandable reason. Program budgets are tracked by funding source. Participation is tracked by program. Outcomes are tracked by student. The three rarely join on a common identifier, because until now nothing required them to.
A program review of this kind runs on three tiers.
Tier 1. A costed profile for every program in the district’s inventory, with the strength of its evidence labeled. Building the inventory is itself a finding in most districts, because the complete list does not exist before the review assembles it.
Tier 2. Cost per participant and cost per stated outcome, calculated only for programs that pass a file test. The file test asks whether participation data, cost data, and outcome data can be joined at the student level. Programs that fail it are reported as failing it, with the specific reason.
Tier 3. A program management score against a fixed rubric. This one examines how the district oversees its portfolio rather than how any single program performs.
Tier 1 depends on the district’s ability to attribute cost to a program, and that ability varies more than most cabinets expect. Central office records often carry the funding source rather than the program. Split positions sit at a percentage nobody has revisited in years. The spending that actually delivers a program frequently lives at the school: a stipend paid at a site, a paraprofessional partially assigned, a coach funded from a school’s own allocation, materials bought locally.
Where that is the case, the cost profile has to be built from the school level up, at least across a sample of schools. That is more work and it is the honest path. A district reporting a program cost of four hundred thousand dollars while its schools carry another two hundred thousand in time and local funds is not comparing its programs on the same basis.
Label the figure with the method that produced it. A cost built from central records alone should say so, and the report should name what it could not see.
Evidence gets graded instead of assumed, and the grade governs what the report is allowed to recommend. A recommendation to discontinue requires both an outcome measure and a cost. A recommendation to scale requires an outcome measure and unmet demand. Where the evidence is thin, the finding is to sustain or redesign with a review requirement attached, and the report says which and why.
Two limits belong in the conversation before the contract. This module rarely produces the savings that an operations review produces, and a district commissioning it in search of a number to cut has commissioned the wrong work. Separately, cost per outcome says nothing about implementation fidelity. Whether a program is delivered as designed is a different question with different methods, and blending the two quietly produces a conclusion neither one supports.
Published work in this area mostly stops short of program-level cost per outcome. Studies report spending, or they report results, and they leave the join to the reader. The difficulty is real. It is also the reason the analysis is worth doing.
The instructional side also changes how the value question gets answered. Central office instructional work can be walked like any other process, and much of it should be. Requisitions, scheduling, assessment administration, materials distribution, and compliance reporting all have steps, handoffs, and waiting, and they carry the same waste as any other process.
That work is usually attached to a program, though, and that is where a process walk by itself stops being enough. A step can be efficient and still exist to serve a program that the community would not choose to fund if it could see the cost beside the result. Classifying the step as value-adding requires knowing what the program is for, who it reaches, what it produces, and what it costs to produce.
That is why the Instructional Program Cost and Effectiveness Review carries its own three tiers instead of riding along on the process work. Deciding whether an activity adds value for students, families, and the community means understanding the program the activity belongs to.
What a review of this kind actually finds
In one school system, the operations review examined a work order system configured with sixty-six crafts against a vendor recommendation of fifteen to twenty. Corrective work orders were printed and re-keyed by hand. Preventative maintenance was tracked outside the system entirely.
None of that was a software failure, and none of it was a staff failure. The system had been configured once, the department had built workarounds for the parts that did not fit, and the workarounds became the process. That is the shape of most findings in this work.
Documentation follows the same pattern. The right order for writing procedures is by risk if the process is not documented, weighed against the number of people who perform it. Each documented procedure gets a single accountable owner. LEAN Frog was teaching districts that method in 2015, and it has not needed revision.
Naming the system state
Findings accumulate, and at some point they have to add up to a statement about the district as a whole. Current LEAN Frog reviews make that statement explicitly rather than leaving the reader to assemble it.
Three states describe where a system sits. Stagnation is a system that has stopped adapting, where outdated structures, assumptions, and routines have stayed in place too long. Chaos is a system reacting without enough clarity, coordination, sequencing, or disciplined decision-making. Balance is the working state between them. Districts move among the three, and most carry different states in different parts of the organization at the same time.
The more useful half of the exercise is direction. A district in balance drifting toward stagnation faces a different agenda from a district in chaos moving toward balance, even when the two findings lists look similar. Direction tells a cabinet whether the work ahead is protective or corrective, and it changes the sequence of what gets done first.
The review states the system state, the evidence behind it, and the direction of travel. That assessment is usually the page a superintendent can hand to a board member who will never open the appendices.
What the district supplies
The data request is the hardest part of the engagement for most districts. Assign one coordinator with authority to chase records across departments.
Organization charts, job descriptions, and the position control roster
Payroll register and department budgets
Existing process documentation, in whatever state it is in
System configurations, standard reports, and transaction data for the functions in scope
Three to five years of enrollment, staffing, and financial history
Access to department leaders and the staff who perform the work
Participation in the stakeholder surveys and job analysis questionnaires
The cost to the district is mostly time, and it is real. Cabinet interviews, department leader sessions, process walks, and questionnaire completion all pull people away from current work during the weeks the review runs.
The sequence
Startup and data request. Scope confirmation, the engagement calendar, the coordinator, and the records list. A startup meeting that produces no named coordinator will cost weeks later.
Discovery. Onsite interviews, process walks, observation, and survey administration. This is where the hidden factory surfaces.
Analysis. Span of control, maturity scoring, peer comparison, retirement eligibility, process measures, and cost. Findings are built from the evidence up.
Workshop. The superintendent and selected cabinet members review the findings and the opportunities before a board-facing report exists. They validate what is accurate, calibrate what belongs in front of the board, and say what the organization can carry this year.
Final report. The board-facing document, with the detailed analysis in appendices and recommendations sequenced rather than listed.
Implementation support. Optional, and the stage districts most often skip. A recommendation with no owner and no date is an observation.
The workshop step is the one worth protecting. A superintendent should see the findings, test them, and shape the board conversation before the report is a public document.
Where the review stops
Scope discipline is what makes the findings defensible.
It does not produce a staffing reduction plan. A reduction decision is also a work-ownership decision, and compliance functions attached to an eliminated position do not leave with the position.
It does not decide school configuration. Square footage per student is a signal worth surfacing, and when it points at a problem the honest recommendation is a dedicated study.
It does not evaluate individuals. The unit of analysis is the position, the process, and the work.
It does not select software. Walk the process first. Automating a poorly designed process makes it run faster and produces more of the same output.
What happens to the findings
Once a process is walked and its steps are classified, a district has five choices for the work: eliminate it, simplify it, automate it, augment it so a person stays in the chair while the machine accelerates the task, or protect it as human judgment. Most near-term value in district operations sits in simplify and augment.
The return is released capacity rather than eliminated positions. That framing matters for what a cabinet is willing to implement, and it is usually the accurate one.
Choosing the scope
A full organization and efficiency review across every function is a large engagement, and few districts should start there. This work comes in several shapes, and the right one depends on what the district already knows about its own problem.
An organizational review on its own. The right choice when the problem is structural: ownership that nobody can name, leaders carrying spans they cannot supervise, functions with no home, or a chart that has drifted away from the work. The companion resource, What Should a School District Organizational Review Include, describes that engagement in full.
A detailed efficiency review of a single department. The right choice when the district already knows which department is under pressure. Child nutrition, transportation, human resources, finance, facilities, and technology are the most common. This engagement goes deeper into one function than a districtwide review can afford to go anywhere.
The combined organization and efficiency review. The right choice when the answer to a problem keeps moving between structure and process, and neither one alone has settled it.
The Instructional Program Cost and Effectiveness Review. Added to any of the above. Add it when the board is asking what the district is getting for its program spending, or when a budget cycle is about to force choices among programs that have never been compared on the same basis.
A Pulse Check first. The right choice when the district cannot yet say where the pressure sits. It runs thirty days from receipt of the district’s data and completion of the virtual interviews, and it converts the scoping question from a guess into a finding.
The efficiency half can also be phased. Run the organizational review across the district, then take functions two or three at a time, in the order the findings justify.
What detailed means in a departmental review
A detailed efficiency review examines how the work is actually done, what systems carry it, and precisely what would have to change to remove the waste and make the system work for everyone it serves. The deliverable describes the current state, the future state, and the path between them at a level a department can act on.
The methods change with the department, and that is the point of running one.
A transportation review examines routing efficiency route by route and bus by bus, with bell schedules, ride times, seat capacity, and the fleet analyzed together. A route recommendation that ignores bell schedules is arithmetic rather than a plan, because the savings move materially when the bells do not.
A child nutrition review includes time and motion study of serving lines across schools. Flow problems appear as queue length, shortened eating time, and lost meal counts, and none of that is visible in a participation report.
A human resources review follows a requisition through to a signed contract, counting approval steps and elapsed days at each stage. A finance review follows a requisition through to a payment. A facilities review follows a work order from request through completion and back into the preventative maintenance schedule.
Those are illustrations. What a department can produce as evidence, the systems it runs on, and the way its work reaches students determine what the review actually does.
Before you commission one
Ask yourself:
Which of our problems have moved between departments more than once without being solved?
Can we name a single owner for each of our core operating processes?
Which of our departments could show us a current process document and a performance measure today?
Who on our team can carry the data request without dropping their current work?
When the findings arrive, who decides, and by when?
The last question is the one that determines whether the engagement produces change or a document. Answer it before the contract, not after the report.
Closing
A district that examines less of its own operation improves more slowly. That holds regardless of budget, size, or state. The value of a comprehensive review is the honest picture it produces and the sequence it puts the work in.
Start by asking which of your operating processes you could describe end to end, with a number attached, in the next cabinet meeting. The answer is the scope.
