“How many offices are doing the same thing for our students?”
Every service belongs to a unit and delivers a capability. When several units deliver the same capability, you can see who serves whom, on which systems and at what cost, and decide whether the overlap is by design, needs coordinating, or should be consolidated.
The same work for the same students on different systems, separate records about one student, and capabilities nobody owns across units.
One call per overlap: keep it by design, coordinate it, or consolidate it, each with an owner and a first step.
The vice presidents ask why students say they get sent from office to office. Grouping the support services at Example State University by capability gives this picture:
Each cell is a service: what the unit calls it and the application it runs on. Click a row for every dimension.
| Unit and service | Serves | Stage | Students a year | Staff (FTE) | Application | Where records live | Hand-done tasks | Cost a year |
|---|---|---|---|---|---|---|---|---|
| {{ c.unit }}{{ c.svc }} | {{ c.pop }} | {{ c.stages }} | {{ c.volF }} | {{ c.fte }} | {{ c.app }} | {{ c.rec }} | {{ c.hand }} | {{ c.costF }} |
{{ sel.owner }}
{{ sel.mandate }}
{{ sel.step }}
Different students, a mandate, or trust that a merger would lose. Keep it, and make sure units refer to each other.
Separate units are right, but intake, records or standards should be shared.
The same work for the same students on separate systems. Move it to one unit or one application.
Sample data for a fictional campus. Cost is staff time at $110k per FTE plus hand-done tasks at 60 hours a year and $55 an hour. Data