Higher Ed Enterprise Model Conceptual model Search
Step 5 · Act

The model exists for action

“We can see the problem. Now what?”

The views surface findings: gaps, overlaps, blocked processes, unclear ownership, low adoption and weak links. Each kind of finding has a lever that fixes it. Pick the lever that matches the cause, pull it, then record the change in the catalog so the next reading starts from the new state.

5Step 5 of 5 · Act — levers
Six levers

Match the lever to the cause

Lever
Fund

When the finding is a gap: a capability with no system, no owner or not enough capacity.

Views that show it: Coverage map, by capability, drivers with a gap status
Who pulls it: Budget owner, cabinet
Watch out for: Funding a system without funding the people and process changes around it.
Lever
Consolidate

When the finding is an overlap: two or more systems doing the same job.

Views that show it: By system, application type, coverage map
Who pulls it: CIO with the owning units
Watch out for: Counting licence savings and missing the migration and retraining cost.
Lever
Change policy

When the finding is a blocked process: a rule that slows or stops the work.

Views that show it: Policy refs, workflows with hand-offs, by decision owner
Who pulls it: Policy owner through its governance body
Watch out for: Changing the system to work around the rule instead of changing the rule.
Lever
Reorganize

When the finding is unclear ownership: no one decides, or everyone does.

Views that show it: By decision owner, org units and services
Who pulls it: Vice president or cabinet
Watch out for: Moving boxes on the org chart without moving decision rights.
Lever
Incentivize

When the finding is low adoption: the tools exist but work goes around them.

Views that show it: Workflows with workarounds, outcomes and value
Who pulls it: Unit leaders, HR
Watch out for: Mandating use without fixing why people avoid the tool.
Lever
Fix data or system

When the finding is a weak link: a fragile data flow, a disputed source of record or an unrecoverable system.

Views that show it: By data, by sensitivity, by criticality
Who pulls it: System owner, data owner
Watch out for: Patching one interface while the source-of-record question stays open.
Choosing

Four questions before you pull one

  1. 1Is the cause a system, a rule, an owner or a behavior? Each points to a different lever. Most failed projects pulled the system lever for a rule or ownership problem.
  2. 2Who can pull it? Check decision rights. If the lever sits with someone else, such as a system office, the first move is to get them on board.
  3. 3Does context allow it? Funding model and operating model decide which levers are realistic.
  4. 4Do levers need to be combined? Consolidation usually needs a policy change and an incentive too. Plan them together.
Close the loop

Back to step 3: record the change

After a lever is pulled, update the catalog: retire or add systems, move ownership and decision owners, update policy and driver refs, and change driver status. Review the affected views after three to six months to check the finding actually moved.

↺Each change is recorded in the catalog, and the cycle repeats.
Related
Putting it to work →Chancellor’s view →Drivers & mandates →Concept map →