Training-serving skew
the failure mode where a feature's value at training time differs from its value at prediction time in production, because the two paths compute it differently or draw from unsynchronized data, silently degrading a model's real-world accuracy below what its offline evaluation predicted.
Defined in 2 GAGE programs, which carry 3 distinct definitions of it. The wording above is taught in Certified AI Data Governance Professional (CADGP).
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
the failure mode where a feature's value at training time differs from its value at prediction time in production, because the two paths compute it differently or draw from unsynchronized data, silently degrading a model's real-world accuracy below what its offline evaluation predicted.
When a feature is computed differently in training than in production (different time windows, sources, or definitions), so the live model is effectively fed different data than it learned from. A leading, hard-to-diagnose cause of production degradation.
A silent failure in which a model performs well in testing but poorly in production because a feature was computed differently during training than at live inference. A feature store prevents it by serving the same feature definition to both.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- The feature store: one governed source for every model, or chaos per project · Feeding the Machines, Certified AI Data Governance Professional (CADGP)
- Enterprise Integration Strategy · Technology, Platforms and Vendors, Certified AI Transformation Professional (CATP)
- Analytics, Telemetry and Observability · Technology, Platforms and Vendors, Certified AI Transformation Professional (CATP)
Where it shows up at work
A definition is where Training-serving skew starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.
Decides where AI should be used, where it should not, and which use cases create measurable value, tied to the organization's priorities.
One lesson on this page teach it as a primary outcome.
Roles that hire for it
Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.
- Chief AI Officerneeds it at depth
- Chief Information Officer, technology leadership editionneeds it at depth
- Chief Technology Officer, AI engineering editionneeds working knowledge
How job descriptions say it
Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.
One interview question about it
Fifty AI ideas are on the table. How do you pick the three worth doing, and how do you say no to the rest?
Asked of candidates for ai strategy and opportunity triage. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.
If you come from another field
Some backgrounds already carry this competency, and the readiness check gives credit for it.
- A business, MBA or technology management degree carries it as a claim to back up: Strategy and opportunity triage are the core of the degree.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.