ODC
What is Orthogonal Defect Classification (ODC)?
ODC uses data we already have to reveal insight we often don’t see — insight about how software is built, where it slows down, and how it can improve.
It’s a framework that turns the defect stream of any software process into measurable patterns. These patterns diagnose process behavior, helping teams make better engineering, management, and financial decisions.
Although ODC originated with defects, it applies equally to changes — design updates, customer issues, or production incidents. Each of these is a signal rich with information. ODC captures those signals, quantifies them, and provides an “MRI of software development,” showing what’s really happening inside.
ODC gives you the MRI of software development — a way to see inside and understand how your process truly behaves.*
Why ODC Matters
ODC helps teams make better decisions:
- Engineering – improve quality and speed
- Management – focus on what truly drives results
- Business – reduce cost and cycle time while increasing reliability
ODC analytics can be applied across the lifecycle — from requirements to testing — giving teams objective, data-driven insight into how their work produces value.
How ODC is Applied
Introducing ODC successfully requires experience and sensitivity to culture and context.
Sometimes the goal is urgent diagnosis — results in days or weeks. In other cases, ODC is adopted enterprise-wide to create a common language of measurement and improvement. Each situation demands a tailored approach aligned with the organization’s readiness and business priorities.
Our team brings decades of experience implementing ODC across diverse industries and project types. We work with you to define the right scope, method, and adoption path.
Who Uses ODC
ODC has been applied by organizations large and small — including IBM, Motorola, Cisco, Lucent, Telcordia, Caterpillar, Cognizant, — across domains such as embedded systems, enterprise software, and business applications.
Training and Support
Applying ODC effectively takes more than theory.
Different roles — developers, analysts, project managers, and executives — use ODC data differently. Our training programs address these varied perspectives, combining classroom learning, guided practice, and project engagement to make ODC real inside your organization.
History
ODC was invented by Ram Chillarege at IBM Research, where he founded the Center for Software Engineering and led the implementation of ODC across the company.
He received IBM’s Outstanding Technical Achievement Award and later the IEEE Technical Achievement Award for the invention of ODC. Since 2001, Ram has continued advancing ODC through his consulting practice, publications, and teaching.
Learn More
This site contains both foundational and advanced materials on ODC:
- ODC Chapter 9 — SRE Handbook (McGraw-Hill) – comprehensive overview
- ODC: A 10× for Root Cause Analysis – short, practical article
- Orthogonal Defect Classification: A Concept for In-Process Measurements – the original paper
- 5 Differences Between Classical and ODC Root Cause Analysis – short video overview
- Case Study: Test and Development Process Retrospective Using ODC Triggers – applied example