Chapter 2: Setting IT Goals, Baselines, KPIs, and Success Metrics
A credible information technology achievement requires more than an impressive description of the work completed. Organizations must be able to demonstrate what conditions existed before an initiative, what they intended to improve, and what measurable results followed. Clear IT department goals, reliable baselines, and meaningful IT key performance indicators transform a general claim of success into an evidence-supported achievement story.
Measurement should begin before implementation—not after a project has been completed. When organizations decide later which numbers will make an initiative appear successful, they risk selecting incomplete or misleading information. Establishing objectives and measurements at the beginning creates a fairer and more useful basis for measuring IT success.
Align IT Strategy with Organizational Goals
Technology initiatives should support an identifiable organizational need. An IT department might aim to increase system reliability, but the larger objective may be to prevent disruptions to customer service. A data initiative may seek to consolidate information, while its organizational purpose is to improve decision-making. A cloud migration may modernize infrastructure, but its broader goals could include scalability, resilience, faster deployment, or cost control.
Before selecting information technology metrics, connect the proposed initiative to objectives involving growth, operational efficiency, customer experience, employee productivity, public service, accessibility, risk reduction, sustainability, or innovation. This connection helps explain why the project mattered.
Artificial intelligence and digital transformation projects especially require defined organizational objectives. “Implementing AI” is not a meaningful goal by itself. A stronger goal might be to reduce the time required to review documents, improve the accuracy of demand forecasts, accelerate internal knowledge retrieval, or enable faster customer support while maintaining human oversight.
Establish Credible Baseline Conditions
A baseline records conditions before a technology initiative begins. Without it, an organization may be able to report its new performance but cannot demonstrate the extent of the improvement.
Depending on the initiative, baseline information might include:
- Current system uptime and outage frequency
- Average response time or latency
- Processing capacity and resource utilization
- Help desk volume and resolution time
- Software deployment frequency
- Project delivery time and cost
- Employee time spent on manual processes
- User adoption and satisfaction
- Security incidents or unresolved vulnerabilities
- Energy consumption and infrastructure expenses
Baseline periods should be long enough to represent normal performance. Comparing a new system’s best month with an unusually poor week under the previous system would create a distorted impression. Organizations should document the measurement period, source, methodology, assumptions, and known limitations.
Select Meaningful IT KPIs
The strongest IT KPIs connect technical performance with stakeholder or organizational value. System uptime, for example, is important because outages can interrupt operations, delay services, reduce revenue, or affect public trust. Latency matters when slow performance interferes with employee productivity or customer experience. Capacity matters when an organization needs to serve more users, locations, transactions, or devices.
Common IT performance metrics include availability, reliability, incident frequency, mean time to resolution, processing speed, error rate, deployment frequency, capacity utilization, service request completion, recovery time, and service-level agreement performance.
Not every organization needs the same measurements. A hospital may prioritize the availability and recovery of critical systems. A university may measure secure access, adoption, and digital accessibility. A government agency may track service availability and citizen processing times. A nonprofit may focus on affordability, efficiency, and the number of people served. A growing business may emphasize scalability, customer experience, deployment speed, and technology ROI.
The best metrics reflect the organization’s size, industry, mission, risks, users, and objectives.
Measure Delivery, Costs, and Return on Investment
Technology projects should also be evaluated according to how effectively they were delivered. Organizations can compare planned and actual completion dates, budgets, milestones, scope, resource requirements, and implementation quality. A project delivered later than expected can still be an achievement when the organization explains the challenges, decisions, revised expectations, and eventual value honestly.
Technology ROI can include direct financial returns, cost savings, and cost avoidance. Direct savings may result from retiring legacy systems, consolidating licenses, reducing infrastructure costs, or automating labor-intensive work. Cost avoidance may include preventing the need for additional capacity, outside services, emergency repairs, or future maintenance.
Digital transformation ROI should not be based on financial estimates alone. Other relevant results may include faster service delivery, improved data quality, stronger compliance, greater resilience, increased accessibility, better employee experiences, and expanded organizational capacity.
All calculations should disclose the time period, assumptions, implementation costs, recurring expenses, and method used. Estimated savings should be identified as estimates rather than presented as audited results.
Separate Outputs from Outcomes
Outputs describe what the organization produced. Outcomes explain what changed.
Examples of outputs include migrating 100 applications, training 2,000 employees, deploying 500 devices, or automating 20 workflows. These figures show scale, but they do not independently prove value.
Outcomes might include reducing application downtime, increasing employee adoption, shortening processing times, improving satisfaction, lowering costs, or enabling more people to access a service. A strong achievement story usually includes both: what was delivered and what resulted from it.
Keep Claims Accurate and Verifiable
Organizations should resist the temptation to use exaggerated percentages, unsupported claims, or selective comparisons. Statements such as “eliminated all risk,” “achieved complete reliability,” or “created millions in value” require exceptional evidence and may reduce credibility.
Measurements should be traceable to approved reports, dashboards, financial analyses, surveys, service records, or other authorized sources. Limitations and incomplete results should be acknowledged where relevant.
Credible baselines and IT metrics help organizations understand performance, improve future decisions, and prepare stronger case studies, leadership reports, and award nominations. Organizations interested in recognizing measurable technology achievements can review current Globee Awards programs, categories, eligibility requirements, nomination rules, achievement periods, and deadlines at GlobeeAwards.com.