University leadership team facing a decision, with data and a clear path forward on the meeting table

By Steve Whitehead

I’ve sat in that cabinet meeting more times than I can count: the enrollment trends are on the screen, course-fill rates in the appendix, student feedback summarized, budget projections reconciled, the report carefully prepared. Everyone in the room understands the issue. And then the next step just hangs in the air — what decision are we making, who owns it, and by when?

That’s where good ideas get stuck in higher education. The insight has arrived. What the institution hasn’t done yet is give it a decision to move.

I’ve come to draw the distinction this way: data as decoration gets reviewed while the decisions stay the same. Data as leverage is gathered for a named decision, with an owner and a date attached.

A dashboard that has never changed a decision is a museum.

The gap between a data-driven identity and movement

In PwC’s Global Data and Analytics Survey 2016 (Big Decisions 2.0), about 2,100 executives described their organizations this way: 39% highly data-driven, 53% somewhat data-driven, and 8% rarely data-driven. The results establish how many leaders identify their organizations as using data. The harder question is whether that data changes what the organization does.

Higher education has its own evidence of the challenge. A 2024 scoping review of 77 empirical studies, summarized in The Insight Gap, found organizational factors influenced evidence use in 73% of cases. The evidence reaches the institution through people, decision rights, timing, and operating routines. Those conditions shape whether it travels any further.

You see it in everyday work. A report gets delivered, but no decision date ever lands on the calendar. A dashboard gets reviewed, but no priority or resource moves. A pilot keeps running, but nobody has agreed on what would make it expand, adapt, or end.

The report date is not the decision date. In my experience, the shift that matters is designing the data around the decision — because the other direction, the decision around an endlessly expanding supply of data, is the default we all drift into.

A university dashboard displayed like an exhibit while a meeting table waits for a decision

The Spark needs somewhere to land

The Spark is the institution’s capacity to see possibilities: new evidence, fresh ideas, emerging needs, and opportunities to serve students better.

The Anvil is the operating reality those possibilities meet: budgets, authority, calendars, policies, workload, and the people responsible for delivery.

The Forge connects them. It gives an idea a defined decision, a clear owner, and a first move.

The question a leader answers with data is the question the data was gathered for. When that question is unclear, even excellent analysis can fill the room without focusing the choice.

Donella Meadows captured what well-placed information can do: “There are places within a complex system ... where a small shift in one thing can produce big changes in everything.” In her essay on leverage points, she names information flows as one of those places. In a university, that usually means getting the right evidence in front of the person who can actually make the call — in time for the call to matter. I’ve watched that one change turn a stuck committee into a moving one.

A documented example: course capacity at UMBC

A 2017 case study of the University of Maryland, Baltimore County, describes how course-capacity decisions could move from paper reports and historical patterns toward current course-utilization information. With utilization data, academic advising could identify courses with room for more students, request additional seats, or guide students toward suitable alternatives. Academic chairs and deans could use the same evidence to allocate or reallocate limited resources. Read the UMBC case study.

What I find worth studying in that case is how practical the shift was: the course data finally had a decision to serve. It could inform a request, a student’s next step, or the allocation of a scarce resource. The report became part of the machinery of movement.

A five-minute test for any report or dashboard

Take one pending decision, not the entire institutional data environment, and look at the report, dashboard, or committee process connected to it.

Set a five-minute timer. Answer these questions:

  1. What decision is pending? Write it as a choice someone can make.
  2. Which data could change that choice? Separate decision-shaping evidence from useful background.
  3. Who owns the decision? Name one accountable role.
  4. When will the decision be made? Put the date on the calendar.
  5. What changes afterward? Identify the budget, behavior, calendar, priority, or workflow that moves.

If you can’t name the decision, the owner, and the date, the artifact is probably serving as decoration. If you can, the data has a route to action.

The rule I use with leadership teams: the report should answer a defined question before the meeting, so the meeting can do the work only a meeting can do — the judgment, the trade-off, the commitment. The meeting is where leaders decide what the evidence means for the institution. It shouldn’t be where the institution first discovers why it collected the evidence.

An academic leader and department chair using course-use information to make a scheduling decision

DIAGNOSE the decision the data must serve

Start with one idea already in discussion at your institution: a program redesign, a student-success intervention, a scheduling change, a funding choice.

Say the decision out loud, in plain language. Then be honest about the evidence you need to make it responsibly, the evidence that would help without being decisive, and the uncertainty you can carry into the first move.

If you’re a provost, this makes the decision bottlenecks and competing priorities visible. If you’re a dean, it clarifies how the choice touches faculty capacity, students, and resources. Either way, you give your stakeholders a shared question instead of a crowded agenda.

A sharp diagnosis turns a crowded agenda into a decision the institution can actually make.

STRIKE with evidence tied to action

Keep the strike bounded. In my work with institutions, that’s meant testing a scheduling adjustment in one program cluster, reallocating a defined amount of discretionary funding for one term, changing a single step in a student-support workflow.

Set the terms before work begins:

  • What will change?
  • Who owns the first move?
  • What evidence will be reviewed?
  • When will the team decide to continue, adapt, or stop?

This structure is what makes a pilot useful. Without a decision at its end, activity can slide into Innovation Theater: work that looks active while the choice it was meant to inform sits parked. And every unresolved choice adds Decision Debt — more rework, more repeated meetings, more teams waiting for direction.

The smallest credible move can turn incomplete evidence into learning your institution can actually use.

EMBED what the decision changes

A decision gains force when people meet it in the operating system: in a named owner’s responsibilities, a calendar commitment, a resource allocation, a communication to affected teams, a scheduled review.

Embedding also means knowing when to retire a data artifact. When a recurring report no longer informs a pending decision, serves a distinct audience, or meets an essential compliance, accreditation, or longitudinal need, I sit down with its steward, review what it’s for, preserve the underlying records as required, and then end or redesign the recurring presentation. People deserve evidence that earns their attention.

A leader applying a short timed check to a decision sheet and setting aside an unused report

A real strategy shows up in calendars, budgets, team behavior, and measurable results. Data should be visible in those places because it helped shape a decision, and because leaders can see what happened after the decision was made.

I’ll say this plainly, because it’s the honest limit of my own field: consulting can generate valuable insight. Sustained action takes an operating rhythm that keeps decisions, owners, and follow-through connected. I’ve seen that inside a university just as much as anywhere else. When insight is linked to authority, timing, and a consequence, the institution can learn and move at once.

The Spark opens possibilities. The Anvil gives leaders a place to test them against the work. The Forge turns the chosen direction into action people can see and carry forward. That’s the rhythm I build with institutions, and it’s the one I’d put against any dashboard.

We don’t choose. We forge.