Capability, component, element, unit, delivery — one architecture, not four separate ideas.
SEE IT, STEER IT and KEEP IT can look like three unrelated tools until you see what they’re built from. This page is the map: how a capability, its components, the three elements, and a finished capability unit all connect — and why none of it was invented from scratch.
What a Capability Actually Is
At the individual level, a skill combined with knowledge and behaviour becomes a competence. At the organisational level: Capability = Competence + Resources + Process. Tested competence, backed by real resources and a working process — that combination is a capability. Skilled people are necessary, but not sufficient: left unmanaged, competence is assumed, not proven. Certified competence — tested against a score, not carried by three people — is the method’s answer.
Business Capabilities vs. Enabling Capabilities
Not every capability plays the same role. Business capabilities define outcomes the organisation must deliver — Sales, Production, Customer Service — each one an outcome the market experiences directly. Enabling capabilities — shared services like IT, Finance, HR — don’t face the market themselves; they support, accelerate or strengthen the business capabilities that do.
The Three Components of Any Business Capability
Every business capability, whoever owns it, is the combination of three components: Platforms & Tools, Business Processes, and People & Competencies. These aren’t three separate checklists — they’re the three places a capability actually lives, and each one needs its own question answered: what technology is needed, what process is needed to adopt and maintain it, and what skills are needed to fully benefit from it.
From Component to Element
This is the connection that makes the method work: each of the three components has a matching element that keeps it honest, and the three elements are what this whole site calls SEE IT, STEER IT and KEEP IT.
| Component | Element | What it produces |
|---|---|---|
| Business Processes | SEE IT | Readiness Score — a 0–100 score read off the record itself |
| Platforms & Tools | STEER IT | AI housekeeping — routines that run to schedule, with a person deciding the hard cases |
| People & Competencies | KEEP IT | Certified competence — knowledge tested against the score, held by the unit |
See It, Steer It and Keep It in depth on their own pages: SEE IT, STEER IT, KEEP IT.
From Element to Capability Unit
Snap all three elements together for one specific domain and you no longer have a service — you have a Capability Unit: something that can see its own condition, steer how it’s produced, and keep what’s learned. Two of the three elements — AI housekeeping and certified competence — are built once and reused unchanged across every domain. Only the Readiness Score is domain-specific: the swappable slot. That’s what makes the model scale — designing a new capability unit means designing one new score, not one new product.
How It’s Actually Delivered
The same three-step sequence proves a capability unit before it’s ever scaled: Assess & baseline (a real, scored baseline — no decision is asked for yet), Pilot (one housekeeping routine run on real data, competence paths identified), then Recommend & scale (one recommendation, carried by the organisation’s own numbers). Full detail on each package’s delivery: Business Case, Digital Transformation, Change Management Consulting.
Why It Works: Coordination Theory, Not a New Idea
The method doesn’t invent new coordination mechanisms — it industrialises three that organisational theory already named. Henry Mintzberg described five ways any organisation coordinates work, from the most informal (mutual adjustment, direct supervision — asking a colleague, escalating to a person) to the most standardised. Without a method, coordination defaults to the two simplest, person-dependent mechanisms — the pattern behind firefighting and knowledge held by very few people. Given the means, three more become available, running continuously and at machine speed:
- Standardisation of outputs → SEE IT (the Readiness Score)
- Standardisation of work processes → STEER IT (AI housekeeping)
- Standardisation of skills → KEEP IT (certified competence)
The Whole Architecture, in One Line
A capability is competence plus resources plus process. Its three components — processes, tools, people — are kept honest by three elements: SEE IT, STEER IT, KEEP IT. Solved for one domain, the three elements become a capability unit. Delivered the same way every time: assess, pilot, scale. None of it depends on any one person remembering how it’s supposed to work.
Where to Go Next
See the actual toolkit behind each piece: Inside the Method. Go deep on one element: SEE IT, STEER IT, KEEP IT. See it applied to a real domain: A Master Data Capability, Seen and Steered.
Related: Inside the Method · SEE IT · STEER IT · KEEP IT · Home
