In my last article I proposed a definition: a Knowledge Spine is the operationalization of an enterprise ontology — the ontology instantiated on a semantic platform and connected, at query time, to your lakehouses, domain knowledge graphs, and unstructured sources.
The most common response was some version of the same question: “Fine. How do we actually build one?”
The traditional answer is a multi-year semantic program. I think that answer is obsolete. Done right, with today’s tooling, you can go from nothing to a working backbone in six months — a blitz build. Here’s how, and why it’s now possible.
Why Speed Is Suddenly on the Table
Three things changed the math:
LLMs collapsed the modeling bottleneck. Drafting an ontology used to mean months of workshops. Today an LLM drafts candidate classes, relationships, and definitions from your existing glossaries, schemas, and documents in days — and your SMEs shift from authors to reviewers. Review is 10x faster than authorship.
Virtualization killed the ETL tax. The spine connects to lakehouse tables through virtual mappings. No migration project, no new copies of data, no six-month integration workstream. Mapping is configuration, not construction.
Extraction became a commodity. Pulling entities and relationships out of contracts and reports used to require a bespoke NLP team. Now it’s an LLM pipeline you stand up in a sprint — emitting output in terms of the ontology.
The constraint was never the technology’s speed. It was the waterfall habit of modeling everything before shipping anything. Drop that habit, and the blitz is open.
The Prime Directive Still Holds
Speed doesn’t change the unit of delivery: never “the ontology,” always an answered question — something the business needs to know that the current stack can’t tell them. A blitz is not modeling faster. It’s shipping answers faster.
Days 0–30: First Vertebra Live
Week 1 — pick the question, draft the model. One cross-silo question with a named sponsor who cares about the answer, not the technology. LLM-draft the ontology from existing schemas and glossaries; SMEs review and cut it to the 15–30 classes the question needs. SHACL constraints from day one.
Week 2 — instantiate and connect. The model goes onto the semantic platform. Map one or two lakehouse sources virtually. A federated query runs end to end — ugly is fine.
Weeks 3–4 — ship the answer. A dashboard, an API, or an agent that a named business user touches. The deliverable of the first month is a believer.
Days 31–60: Harden While Hot
Momentum is the blitz’s fuel; trust is its armor. In parallel, not in sequence:
- Governance as code: ontology into version control, review and release process, SHACL validation on every change.
- First extraction pipeline: contracts or reports relevant to the question, emitting entities conforming to the ontology.
- Instrumentation: query logs and feedback capture — the roadmap is driven by what users actually ask.
Days 61–90: Second Vertebra — the Federation Test
The second use case forces the question the first could dodge: how do domains connect without merging?
Pick an adjacent question that shares concepts with the first. Refactor the shared concepts into a small upper ontology; leave everything domain-specific in modules owned by domain teams. Resist the merge — the spine aligns identifiers and upper-level concepts; it doesn’t absorb.
If nothing moved into a shared upper ontology by day 90, you built an application, not a spine.
Months 4–6: Backbone by Default
Now compound. Add a vertebra every 30–45 days — each one a named question, a named user, a shipped answer. Meanwhile:
- Ground AI by policy. Every copilot and RAG pipeline resolves entities through the spine, so “where did this answer come from?” always has a lineage-backed answer.
- Publish the endpoints. SQL for BI, GraphQL/SPARQL for apps, grounding APIs for agents — connecting to the spine becomes the path of least resistance.
- Put the ontology on a release cadence. Versioned, reviewed, boring. Like all good infrastructure.
By month six the roadmap inverts: domain teams queue up to attach their vertebrae, because attaching is faster than building alone.
The Blitz Team
Small and senior: an ontologist/knowledge engineer, a semantic platform engineer, a data engineer for mappings and pipelines, and a product-minded lead who owns the question backlog. Plus part-time domain stewards who own their module’s definitions — meaning is authored where the knowledge lives. Four to five people. Not twenty.
“We’re a 50,000-Person Enterprise — Four People Won’t Cut It”
Correct — and that’s not how it scales. The spine scales the way platform engineering does: the hub stays small because it only owns the platform, the upper ontology, and the standards. Scale happens in the limbs.
Each domain stands up its own vertebra squad — its steward plus two or three engineers — building its module in parallel, against spine standards. Ten domains means ten parallel squads, while the central team grows to perhaps six or eight and shifts from building vertebrae to certifying them: reviewing modules, guarding the upper ontology, keeping the paved road paved.
At true global scale — multiple divisions, multiple regions — divisions run their own spines federated to a thin global upper ontology. Same pattern, one level up.
The rule at every size: the four-to-five person team builds the first vertebrae. Growth is many small teams attaching in parallel — never one big central team modeling on everyone’s behalf.
What Kills a Blitz
The cathedral reflex. Sneaking “while we’re at it” modeling into sprint one. Antidote: no class enters the ontology without a question that needs it.
Skipping the armor. Speed without governance produces a demo, not a backbone — fast to build, faster to rot. The day-31 hardening is not optional.
The tool-first trap. Buying the platform before the question exists. In a blitz the platform is instantiated in week two of a use case — never before one.
The Bottom Line
Two-year semantic programs die of sponsor fatigue before they ship. The blitz inverts the risk: a believer in 30 days, federation proven in 90, a backbone that earns its keep by month six — with governance hardened along the way, not bolted on after.
Vertebra by vertebra, at sprint speed.