← The Decision Window

Module 5 · 20 min

Making it survive

Why good systems die, and the routines that keep them alive.

Watch & reflect · optional

Developing and Sustaining Shared Leadership in Higher Education

UWE Bristol Business School · UWEBBSChannel · External learning resource

Video thumbnail: Developing and Sustaining Shared Leadership in Higher Education
YouTube · loads only when playedWatch on YouTube

A higher education example of shared leadership and sustaining institutional practice. Its scope is leadership, not data system maintenance. Use the checklist below to review budgets, access, documentation and succession as well.

If the current champion left, which responsibilities could colleagues carry forward without outside help?

The three deaths

Three dependencies are worth checking before handover. They are risks to investigate, not predictions of when a system will fail.

One person holds it together. Check whether colleagues have the documentation, access and experience to continue when that person moves.

Project funding pays the operating costs. Identify who will fund hosting, licences, maintenance and staff after the project closes.

Outputs have no review routine. Agree which decisions the information serves, who reviews it and how actions are recorded.

Capability is not training

Training develops individual knowledge. Institutional capability also needs arrangements that survive a change of staff:

  1. A named owner with responsibility and authority.
  2. A recurring review linked to a decision that matters.
  3. A documented routine describing what is produced, by whom and when.
  4. Someone able to take over, with the necessary access and practice.

Missing arrangements are questions for a continuity plan, not a formula for predicting a failure date.

The handover test

The conventional measure of a successful engagement is that the deliverables were delivered. That measures the consultant, not the institution.

The better test, applied six months after the consultant leaves:

  • Has the output been used in a decision? Name the decision.
  • Has anyone inside the institution changed the system, added an indicator, altered a report, fixed something?
  • Could the institution rebuild it if the files were lost?
  • Has anyone new been taught to run it, by someone internal?

Use these questions to discuss continuity. The number of yes answers is not a validated measure of sustainability.

Write this test into the contract at the start. A partner confident in their work will agree to it. One who resists has told you something.

Governance that serves judgement

Most data governance frameworks are written to satisfy an audit. They specify who may access what, how long records are kept, and which standards apply. All necessary, none of it sufficient, and a framework that stops there produces a system that is compliant and unused.

Governance that serves judgement adds three things the compliance version omits:

  • Named decision rights. Not "the committee reviews", which person, for which decision, on what evidence.
  • A standing question. Every recurring forum has one question it exists to answer. If a forum cannot state its question, it is a status update, and status updates are where evidence goes to be acknowledged.
  • A rule for stopping. What triggers retiring an indicator, a report or the whole system. Without it, everything accumulates and attention is finite.

The tool

Score your most important data system out of ten. Each item is one point.

That last option is real and almost never taken. Retiring a system that is not working frees budget, attention and credibility. Institutions keep dead systems running because stopping looks like admitting a mistake, which is itself a rung 1 problem, about what the institution believes failure means.

The tool · The living system checklist

0/10Running on momentumDecide deliberately whether to invest in making it survive or to retire it honestly and stop paying for it.

Saved on this device as you type. It comes back in your systems brief at the end.

Onetsa · The Decision Window · Module 5

The living system checklist

onetsa.co · info@onetsa.co

What to take away

  • Systems die from a departing champion, an ending funding cycle, or an empty calendar.
  • Capability needs clear ownership, a recurring routine, documentation and someone able to take over.
  • Measure handover by use, not by deliverables, and write the test into the contract.
  • Governance should name decision rights and include a rule for stopping.

Check your understanding

Nothing here is recorded and there is no score. The questions are for you.

1.A data system has a skilled, committed manager who personally ensures it runs. She is the reason it works. What is the most accurate assessment?
2.Which of these best indicates a living system rather than a dead one?
3.A project funded data system is handed over at project close. Which omission most reliably kills it?
4.Six months after an engagement ends, you want to test whether the handover held. Which question is most revealing?

The Decision Dispatch

Practical thinking on evidence and public decisions.

Short essays on data systems, MEL, DPI and AI in public institutions. Register your interest in the planned monthly dispatch.