Run IT by the Numbers: Data-Driven IT Governance
IT departments generate enormous amounts of data — tickets, deployments, incidents, project milestones, cloud bills, license counts. Yet many important IT decisions are still made on intuition, anecdotes, and whoever argues most persuasively in the steering committee.
The consequences are predictable: investments that can't be justified to the board, projects that keep going long after they should have been stopped, teams that are overloaded while others are underused, and an IT function that struggles to show the business what it actually delivers.
This article outlines Run IT by the Numbers: an initiative to shift IT decision-making from intuition to evidence, by combining a standardized metrics framework, integrated financial data, and transparent reporting.
Symptoms of Running IT on Gut Feeling
- No standard metrics: every team measures different things, in different ways, so performance can't be compared or benchmarked.
- Siloed data: project, financial, and operational data live in separate tools, so nobody sees the full picture — for example, what a service really costs relative to the value it delivers.
- Subjective priorities: investments are chosen on opinion rather than evidence, and are hard to defend to executives.
- Inefficient resource allocation: without visibility into performance, people and budget can't be moved from struggling initiatives to promising ones.
- Little transparency: stakeholders can't see progress, so accountability is weak and trust in IT suffers.
In the organization behind this business case, only around 30% of IT decisions were based on data, the project success rate was 70%, and stakeholder satisfaction with IT stood at 60%.
The Approach
1. A Standard Metrics Framework
Define a balanced set of KPIs across the main domains of IT, for example:
| Domain | Example Metrics |
|---|---|
| Project and product delivery | On-time and on-budget delivery, project success rate, benefits realized |
| Software delivery | Deployment frequency, lead time for changes, change failure rate, time to restore service |
| Operations and service | Availability, incident volume and resolution time, SLA performance |
| Financial | Cost per service, run vs. change spend, cloud cost efficiency, budget variance |
| Risk and compliance | Security incidents, audit findings, compliance status |
| Customer and people | Stakeholder satisfaction, employee engagement, skills coverage |
The goal isn't to measure everything, but to measure the few things that drive decisions — consistently, everywhere.
2. Integrate Financial Data
Connect cost data from finance, procurement, and cloud billing to IT services, applications, and projects. When IT knows what each service costs and what value it delivers, conversations with the business move from "IT is expensive" to "here's what we spend, what it delivers, and the options for spending it differently."
3. One Source of Truth
A central platform automatically collects data from project management tools, service management, financial systems, and operational monitoring — eliminating manual spreadsheet consolidation and providing a single, trusted version of the numbers.
4. Dashboards for Every Audience
Executives see strategic alignment, value, and risk. IT leaders see portfolio health and resource use. Teams see their own operational performance. Everyone sees the same underlying data.
5. Decisions Backed by Evidence
Metrics are built into governance processes: investment proposals include expected outcomes, portfolio reviews compare actual against planned results, and underperforming initiatives are adjusted or stopped based on evidence.
6. Continuous Improvement
Performance data reveals bottlenecks and opportunities. Regular reviews turn those insights into concrete improvement actions — and the metrics themselves are refined as the organization learns what matters.
Platform Options
| Option | Description | Indicative Investment | Trade-offs |
|---|---|---|---|
| 1. Status quo | Continue intuition-based decision-making. | None upfront | Persistent inefficiency, risk, and weak alignment |
| 2. Off-the-shelf IT governance tool | Deploy a commercial tool for metrics and reporting. | ~$250K upfront + ~$120K/year | Fast (3-6 months) with pre-built integrations, but limited customization and growing license costs |
| 3. Custom data-driven governance platform (recommended) | A tailored platform with a standard metrics framework, financial integration, dashboards, and automated data collection. | ~$500K upfront + ~$80K/year | Takes 12-18 months, but fits the organization's own processes and has lower running costs |
Implementation Roadmap
| Milestone | Target |
|---|---|
| Project kickoff | January 2026 |
| Requirements gathering and metric definition | February 2026 |
| Platform design | April 2026 |
| Development, phases 1 and 2 | July-October 2026 |
| Testing and quality assurance | December 2026 |
| User training | January 2027 |
| Platform deployment | February 2027 |
| Post-deployment review | March 2027 |
The team includes a project manager, business analysts to define the metrics, developers, a data governance lead, a change manager, and trainers.
Managing the Risks
| Risk | Probability | Impact | Mitigation |
|---|---|---|---|
| Integration challenges | High | High | Early assessment of source systems and a detailed integration plan |
| Resistance to change | High | Medium | Change management and clear communication of benefits |
| Data quality issues | Medium | High | Data governance policies and automated validation |
| Project delays | Medium | High | Clear milestones and regular progress reviews |
| Budget overruns | Medium | High | Contingency reserves and close expense monitoring |
| Low adoption | Medium | Medium | Training, support, and acting on user feedback |
There's also a cultural risk worth naming: metrics can be gamed or used to blame people. A data-driven culture works when numbers are used to learn and improve, not to punish — and when leaders model that behavior themselves.
Measuring Success
| Metric | Baseline | Target |
|---|---|---|
| Share of IT decisions backed by data | 30% | 80% |
| IT project success rate | 70% | 85% |
| Stakeholder satisfaction with IT | 60% | 90% |
| Time to produce a performance report | 4 hours | 2 hours |
| Compliance and operational incidents | 10 a year | 7 a year |
| Annual savings from operational efficiency | $0 | $1.2M |
Conclusion
Running IT by the numbers isn't about replacing judgment with spreadsheets. It's about giving judgment better material to work with — so decisions about priorities, investments, and resources are grounded in evidence that everyone can see and trust.
When IT can show clearly what it spends, what it delivers, and how it's improving, it earns a different kind of conversation with the business: less about defending budgets, more about deciding together where technology can create the most value.