Business capabilities and Enabling capabilities were introduced as two different roles a capability can play. Here’s what that looks like once the method is actually running across an organisation’s master data.
The Business Capabilities
Each master-data domain is its own business capability — something the organisation must be able to do, on its own terms, scored, steered and kept the same way as every other domain: Customer, Material, Vendor, Finance, HR/Workforce, Asset, Supply Chain, Project, Quality & Compliance, Governance & Enterprise Structure, and AI/Analytics/KPI. Each has its own Readiness Score, built to its own domain — see SEE IT for how that’s designed.
The Enabling Capability Behind All of Them
AI housekeeping and certified competence are not built per domain. They are the enabling capability every one of those business capabilities depends on — built once, and never rebuilt from scratch the next time a new domain is brought in. This is the practical reason the model scales: eleven business capabilities do not require eleven separate engines underneath them, only eleven Readiness Scores plugged into the same one.
Why the Distinction Matters
Without naming this split, “AI housekeeping” and “certified competence” can look like project deliverables that need to be redone for every new domain. They aren’t. They’re infrastructure — the enabling capability — built once so that scaling to an eleventh domain is materially easier than building the first one was.
Related: SEE IT · STEER IT · KEEP IT · How the Concepts Fit Together · Home
