IT Management Activities Glossary and Definitions
IT Performance and Measurement Glossary
Return to the main IT Leadership Knowledge Base page
Table of Contents
- IT Metrics and KPIs
- IT Value Management / Business Value Realization
- Quality Management (ISO, Six Sigma applied to IT)
IT Metrics and KPIs
IT Metrics and Key Performance Indicators (KPIs) encompass the measurement frameworks organizations use to assess the performance, efficiency, and business value of their technology function. Effective metrics programs move beyond purely technical measurements toward business-relevant indicators that demonstrate IT’s contribution to organizational success and support data-driven decision-making about technology investment and improvement priorities.
IT metrics typically span multiple categories reflecting different stakeholder perspectives and management purposes. Operational metrics track day-to-day technology performance, including system availability and uptime, incident volume and resolution times, and service desk performance indicators like first-call resolution rates. Financial metrics assess technology cost efficiency and value, including total cost of ownership trends, IT spending as a percentage of revenue, and return on investment for major technology initiatives. Strategic metrics connect technology performance to broader business outcomes, such as the percentage of IT spending allocated to innovation versus maintenance, or technology’s contribution to specific business objectives like customer satisfaction or revenue growth.
A common challenge in IT metrics programs is avoiding “vanity metrics” that are easy to measure and generally trend positively but don’t actually provide meaningful insight into genuine performance or value delivery. Effective metrics programs instead focus on outcome-oriented measures that genuinely reflect whether IT is delivering intended business value, even when these measures prove more challenging to define and track than simpler operational metrics.
Balanced scorecard approaches have become popular frameworks for organizing IT metrics, ensuring measurement programs address multiple relevant perspectives, including financial performance, customer or user satisfaction, internal process efficiency, and organizational learning and growth, rather than over-emphasizing any single dimension at the expense of others.
Modern DevOps and platform engineering practices have popularized specific metric frameworks like DORA metrics (deployment frequency, lead time for changes, mean time to recovery, and change failure rate), which provide well-validated indicators of software delivery performance that correlate with broader organizational performance outcomes.
Effective IT metrics programs require careful consideration of metric definition consistency (ensuring metrics are calculated consistently over time and across different teams to enable meaningful comparison), appropriate metric governance (avoiding metric proliferation that creates confusion and reporting burden), and clear connection between measured metrics and actual decision-making, ensuring metrics programs drive genuine action and improvement rather than becoming purely retrospective reporting exercises disconnected from operational and strategic decisions.
IT Value Management / Business Value Realization
IT Value Management, also called Business Value Realization, is the discipline of ensuring technology investments actually deliver their intended business value, extending accountability beyond simply completing projects on time and budget toward confirming that promised business outcomes are genuinely achieved and sustained. This discipline addresses a persistent challenge in technology management: organizations frequently invest significant resources in technology initiatives based on compelling business cases, but often fail to systematically verify whether those promised benefits actually materialize.
The value management discipline typically begins during initial business case development, establishing clear, measurable benefit statements that will be used to assess success, rather than vague aspirational statements that can’t be objectively evaluated after implementation. This includes establishing baseline measurements before implementation begins, providing a clear comparison point for assessing whether the initiative actually achieved its intended improvement.
Benefits realization tracking continues throughout and after project implementation, moving beyond traditional project management’s focus on delivery milestones toward ongoing measurement of whether promised business outcomes are actually being achieved. This often requires extending measurement well beyond traditional project closure, as many benefits, such as productivity improvements or cost reductions, may take considerable time to fully materialize after technical implementation is complete.
A particularly important discipline within value management is distinguishing between output measures (confirming that technical deliverables were completed, such as a new system being deployed) and outcome measures (confirming that the deployment actually achieved its intended business impact, such as improved customer satisfaction or reduced operational costs). Many technology initiatives successfully deliver outputs while failing to achieve genuine business outcomes, making this distinction critical for honest value assessment.
Value management also requires appropriate governance structures, typically involving business sponsors who retain accountability for benefits realization even after IT has completed technical delivery, since realizing many technology benefits requires business process changes and adoption that fall outside IT’s direct control. Regular value realization reviews, often conducted six to twelve months after implementation, provide structured opportunities to assess actual outcomes against original projections and identify any additional actions needed to fully realize intended value. Organizations with mature value management practices demonstrate more disciplined investment decision-making, as the expectation of genuine post-implementation accountability discourages unrealistic business cases and encourages more honest, achievable benefit projections during initial investment approval.
Quality Management (ISO, Six Sigma applied to IT)
Quality Management in IT applies structured quality methodologies, originally developed for manufacturing and broader business process improvement, to technology service delivery and software development, aiming to systematically improve consistency, reduce defects, and enhance customer satisfaction with IT products and services.
ISO 9001, the internationally recognized quality management standard, provides a framework applicable to IT organizations, emphasizing systematic process documentation, continuous improvement cycles, customer focus, and evidence-based decision-making. IT organizations pursuing ISO 9001 certification typically must demonstrate documented processes for key IT activities, systematic tracking of quality metrics and customer satisfaction, and formal continuous improvement mechanisms that use quality data to drive ongoing process refinement.
Six Sigma methodology, originally developed at Motorola and popularized through adoption at General Electric, provides a data-driven approach to reducing defects and process variation, traditionally applied to manufacturing but increasingly adapted to IT service delivery and software development contexts. The methodology’s DMAIC framework (Define, Measure, Analyze, Improve, Control) provides a structured approach to quality improvement projects, beginning with clearly defining the problem and success criteria, measuring current process performance, analyzing root causes of quality issues, implementing improvements, and establishing controls to sustain achieved improvements over time.
Applied to IT contexts, quality management principles often focus on reducing defects in software development (such as production bugs or security vulnerabilities), improving consistency in IT service delivery (such as reducing variation in service desk response quality or incident resolution approaches), and systematically eliminating waste in IT processes, drawing on Lean principles that complement Six Sigma’s statistical rigor with a focus on eliminating non-value-adding activities.
Quality management in software development has increasingly integrated with broader quality assurance and testing practices, including automated testing frameworks, code review processes, and continuous integration practices that build quality verification directly into the development pipeline rather than treating quality assessment as a separate, later-stage activity.
Effective IT quality management requires balancing the rigor and discipline these methodologies provide against the risk of excessive bureaucracy that can slow delivery without proportionate quality benefit, particularly in fast-moving technology environments where methodologies originally designed for stable manufacturing processes must be thoughtfully adapted rather than applied rigidly. Organizations that successfully adapt quality management principles to IT contexts demonstrate more consistent service delivery, reduced defect rates, and stronger systematic capability to identify and address root causes of recurring quality issues, rather than repeatedly addressing the same underlying problems through ad hoc, reactive fixes.