Sixty minutes, four signals: giving the board a quarterly view of the technology horizon
Photo: Hashoo Foundation USA, CC BY-SA 2.0, via Wikimedia Commons
Most UK organisations still commit their technology direction to a document written once, approved alongside the annual budget, and then left largely undisturbed until the following cycle. The document is seldom the difficulty. The difficulty is the distance between the assumptions it records and the world the organisation actually operates in twelve months later.
By the time a board reads that a platform is approaching the end of vendor support, or that a regulator has shifted its expectations of operational resilience, the useful window for a calm and well-funded response has usually closed. What follows is a compressed procurement, an emergency remediation budget and a post-implementation review asking why nobody saw it coming. In most cases somebody did see it. There was simply no recurring moment at which it could be said out loud.
Why annual planning drifts
A twelve-month strategy cycle assumes a stable environment. Few mid-market organisations have one. Supplier licensing models change, assurance regimes tighten, key staff leave, and the platforms underpinning finance, payroll and case management are revised on the vendor's timetable rather than the client's. None of these events is dramatic in isolation. Together they erode the foundations of a plan nobody has revisited.
The remedy is not more foresight. It is rhythm: a short, repeatable session in which directors look outward rather than inward, and leave with a small number of specific commitments.
Four signals worth an hour a quarter
Regulatory and assurance movement
Not a legal update. The question is narrower: which obligations are changing in a way that touches systems, records or evidence? Data protection expectations, sector guidance on outsourcing and third-party risk, procurement rules, and the assurance questionnaires that customers and insurers now issue all deserve a line. If nothing has moved, say so and move on.
Supplier and vendor roadmap change
Ask what has changed in the last quarter among the five suppliers the organisation could not operate without. Licensing, end-of-support dates, product retirements and changes to support tiers all matter. Recent history offers a warning: organisations that treated a major licensing restructure as a commercial annoyance rather than a planning event spent the following two years renegotiating from a weaker position.
Cyber-resilience expectations
The direction of travel is consistent: more evidence, faster recovery, clearer ownership. Boards should track not only incidents but the expectations placed on them — by insurers, customers, regulators and their own auditors. A short quarterly note on what evidence the organisation could produce today, and what it could not, is worth more than a maturity score.
Skills and capability signals
Single-person dependencies, roles open for two consecutive quarters, contractors whose knowledge is not being transferred. These are horizon issues as much as people issues, and they surface more reliably in a standing conversation than in an annual workforce plan.
The sixty-minute agenda
| Minutes | Item |
|---|---|
| 0–5 | Confirm last quarter's three commitments and their status |
| 5–35 | Four signals: five minutes of evidence and three minutes of discussion each |
| 35–50 | Implications: what would have to change, and by when |
| 50–60 | Agree three decisions and name owners |
The discipline lies in the proportions. Most of the hour is spent looking outward, not reviewing delivery. Delivery reporting already exists; this session exists for what delivery reporting cannot capture.
From observation to three decisions
Foresight exercises fail when they end in a list. A list has no owner and no consequence. The session should close with exactly three decisions, each falling into one of three categories.
Accept and record. The signal is real, but the exposure is tolerable, the timing distant, or the cost of acting now exceeds the cost of waiting. Recording the reasoning is the point; it makes a later reappraisal honest rather than retrospective.
Test within thirty days. The signal may matter, but nobody in the room knows enough. A named director, a defined question and a date is sufficient. The output is a one-page finding, not a project.
Escalate into the next funding gate. The exposure is material and the organisation has a choice to make about money, sequencing or risk appetite. This becomes a board decision with options attached, not a recommendation buried in an appendix.
Three decisions per quarter is twelve per year. That is a modest governance load and a substantial improvement on a single annual review that nobody remembers agreeing to.
What to leave out
Exclude vendor demonstrations, programme status, and anything that could be described as a technology tour. Exclude scenario planning that runs to dozens of permutations. Exclude, above all, the temptation to treat the session as a rehearsal for a digitisation narrative the organisation has no intention of funding.
The test of a horizon scan is not whether it produced an impressive artefact. It is whether, nine months later, the organisation can point to a decision taken earlier and more cheaply than it otherwise would have been.
A template that survives contact with the board pack
One page, four rows for the signals, three lines for the decisions, and a standing note of what was considered and dismissed. Circulate it before the meeting, keep the format identical every quarter, and archive the series. After two years that archive becomes the organisation's own evidence base — and the most useful input to the annual strategy refresh, which can then begin with observed change rather than a blank page.
