Higher Ed Enterprise Model Conceptual model Search
12
Use · Capability overlap

Find redundant capabilities across units

“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.

How to run it
  1. List the services in one area and the unit that runs each.
  2. Group them by the capability they deliver.
  3. For every capability with two or more units, compare who, how and how much.
What you're looking for

The same work for the same students on different systems, separate records about one student, and capabilities nobody owns across units.

The decision

One call per overlap: keep it by design, coordinate it, or consolidate it, each with an owner and a first step.

A worked example

Advising and student support

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:

{{ s.v }}
{{ s.l }}
Show:
Capability
{{ h.name }}
{{ c.svc }} {{ c.app }}

Each cell is a service: what the unit calls it and the application it runs on. Click a row for every dimension.

{{ sel.name }}

{{ sel.why }}

{{ s.v }}
{{ s.l }}
Unit and serviceServesStageStudents a yearStaff (FTE)ApplicationWhere records liveHand-done tasksCost a year
{{ c.unit }}{{ c.svc }} {{ c.pop }} {{ c.stages }} {{ c.volF }} {{ c.fte }} {{ c.app }} {{ c.rec }} {{ c.hand }} {{ c.costF }}
Owner across units

{{ sel.owner }}

Mandates

{{ sel.mandate }}

Outcome at stake

{{ sel.outcome }} →

First step

{{ sel.step }}

By design

Different students, a mandate, or trust that a merger would lose. Keep it, and make sure units refer to each other.

Coordinate

Separate units are right, but intake, records or standards should be shared.

Consolidate

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

Try it: open org units and services →
Step by step
  1. Pick an area. One where students or staff say they get passed around: student support, research administration, IT help.
  2. List every service and its unit. Include services run from spreadsheets and inboxes; they're usually where the overlap is.
  3. Map each to a capability. Use HERM, then split broad capabilities like Student Support into the activities students see: intake, tutoring, alerts, funding.
  4. Fill in the dimensions. Who it serves, at which stage, how many, how many staff, which application, where records live and what's done by hand.
  5. Check ownership and mandates. Find out who is accountable across units, and which separations a grant, regulation or privacy rule requires.
  6. Make the call. By design, coordinate or consolidate, with the outcome at stake and a first step that one person owns.
Who’s at the table
Vice presidents or deansSponsor the review and own decisions that cross divisions.
Unit directorsDescribe their services, students and mandates.
Enterprise architectMaps services to capabilities and applications.
StudentsSay where they get sent around. Their journeys check the findings.
Pitfalls
Treating all overlap as waste. Services for specific students often work because they're separate.
Leading with headcount. If the review reads as a staffing cut, units stop sharing what they do.
Mapping too broadly. At the HERM level, everything is Student Support. Map to what students actually ask for.
Skipping the records. Shared records usually help students more than merging units.
How you know it worked
  • Fewer offices a student contacts to resolve one need.
  • Fewer applications and record stores per capability.
  • Every overlapping capability has an owner across units.
  • Hand-done tasks fall, and freed staff time is reported.
Where the data comes from
Related: Find operational efficiencies → Rationalize the portfolio → First-gen playbook →
← All uses ← Find operational efficiencies