The Executive Technology Scorecard

Governed by a Wall of Greens

Here is how most executive teams govern their largest controllable expense. Once a month, a slide appears: a grid of projects, each with a colored dot. The dots are mostly green. Occasionally one turns amber, gets discussed for four minutes, and turns green again by the next meeting. Everyone nods. Millions of dollars of technology spend have just been "governed."

The wall of greens survives because both sides prefer it. IT leaders learn that ambers invite interrogation, so status becomes negotiation. Executives lack the instruments to ask better questions, so they settle for the ones the slide can answer. The result is an information vacuum at exactly the altitude where technology decisions allocate capital — and vacuums get filled by anecdote, vendor pitch, and whichever leader argues best.

The alternative isn't more reporting. It's fewer, better numbers — a scorecard that treats technology the way the executive team already treats every other function it governs.

Why the Usual Metrics Fail Upward

The metrics IT naturally produces — uptime, ticket counts, velocity, server utilization — are operational instruments, and they fail at the executive altitude for a simple reason: no business decision changes when they move. If uptime drops from 99.95% to 99.9%, what does the CFO do differently? Nothing. The number is real, but it isn't decidable.

A scorecard metric earns its place only if it passes two tests. First, a non-technical executive can understand it without translation. Second, a specific decision changes when it crosses a threshold — funding moves, a priority shifts, a risk gets accepted or retired. Everything else, however lovingly measured, belongs on an operational dashboard two levels down.

The Five Numbers

• 1. Run cost by business capability. Not the IT budget by cost center — the cost of operating each business capability: what order-to-cash costs to run, what customer service technology costs per interaction. This is the number that turns "IT is expensive" into "supporting this product line costs 3× the revenue it protects," which is a sentence a board can act on. It's also the hardest number to produce, which is exactly why producing it is a competitive advantage.
• 2. Delivery lead time. The elapsed time from "we decided to do this" to "customers are using it," measured for real initiatives, not sprints. This is the speed of the business's nervous system. When it trends up, every strategy gets slower regardless of how good the strategy is. It's also the single best proxy for accumulated technical debt — indebted estates can't ship fast no matter how hard the teams work.
• 3. Risk posture, stated as exposure. Not a compliance percentage — a short register of the top exposures in business terms: "our billing platform leaves vendor support in 14 months," "recovery of the ERP has never been tested," "one engineer holds production access to payments." Each with an owner and a decision: fix, accept, or transfer. Executives are professional risk-pricers; give them risks they can price.
• 4. Debt trend. Whether the estate is getting easier or harder to change — direction matters more than the absolute score. A simple quarterly re-score (delivery drag, key-person risk, deployment confidence, changeability) plotted over time answers the only question leadership needs: are we paying down or borrowing more?
• 5. Initiative return, measured after the money. Every funded initiative stated its expected benefit to get funded. This line reports actuals against those promises — six and twelve months after go-live, when everyone would prefer to forget them. Nothing changes an organization's estimating honesty faster than knowing the estimate will be revisited in public.

Building It Without a Six-Month Program

The scorecard fails when it launches as a measurement program with a steering committee. It succeeds when it starts rough and monthly: version one is five slides with the best numbers available today, caveats stated out loud. Run cost by capability might start as an allocation estimate; the risk register might start with three items. That's fine — the discipline of publishing monthly is what forces the numbers to get better, because every gap becomes visible to people with the authority to close it.

Two rules keep it honest. The scorecard belongs to the executive team, not to IT — it's the instrument panel they fly with, so they define the thresholds that trigger decisions. And every number keeps its trend: a single month's figure informs, but the twelve-month line is what actually governs.

What Good Looks Like

You know the scorecard is working when the monthly conversation changes shape. Nobody discusses dot colors. The CFO asks why order-to-cash run cost rose 8% and gets an answer with a decision attached. A modernization initiative gets funded not because engineering lobbied hardest but because the debt trend and lead-time lines made the case arithmetically. And when the board asks "are we getting value from technology?", the answer is a page of trends, not a feeling.

The prerequisite for most of these numbers is knowing which systems support which capabilities and how they connect. If you can't produce that map today, start there — business capability modeling is the one-page discipline that makes every number on this scorecard possible.

John

Founder, Splendor Technologies

20+ years in AI, enterprise architecture, and application development. Helping organizations modernize technology and drive measurable business outcomes.