Data products before AI programmes
Strategy decks jump to “use AI on our data.” The estate answers with duplicate definitions of customer, delayed lakes, and pipelines nobody trusts for decisions that matter. Teams then spend the programme debating models while the inputs remain politically and technically unresolved.
If I had to sequence investment for most insurers and banks I have seen, I would put durable data products ahead of a wide AI portfolio. That is not anti-AI. It is pro-outcome.
Productize the inputs
Treat critical datasets as products: owner, contract, freshness, quality checks, and consumers. AI use cases then compose products instead of scraping tribal knowledge from warehouses.
Without that, every model team rebuilds joins and silently diverges from finance and risk numbers. You end up with a fourth definition of “active policy” and a steering committee arguing about whose dashboard is true.
A data product contract should state grain, keys, allowed latency, quality indicators, and what changes require consumer notification. It does not need to be a novel. It needs to be enforceable.
Ownership beats heroics
Data without an owner becomes everyone’s problem and nobody’s priority. Name a product owner who can say no to breaking changes and yes to investment in quality. Pair them with engineering capacity that is not stolen every quarter by the loudest project.
Architecture’s role is to place those products on the enterprise map: which capabilities they serve, which systems produce them, which AI features may consume them, and where personal data constraints apply.
Quality is a feature
Missing values, late batches, and silently redefined fields destroy model trust faster than a mediocre algorithm. Invest in detection and consumer-visible status. An AI feature that cannot see “data stale” will invent confidence anyway.
Build feedback paths from model errors to data defects. Many “model failures” are upstream semantics. Fixing them once helps every consumer, not only the AI team that found the pain.
Sequence honestly
Sometimes the first year of an “AI programme” should be data platform and governance work with a thin AI wedge that proves value on a well-owned product. That is not failure. That is foundations.
Be honest with sponsors: without trusted inputs, you are funding demos. With trusted inputs, even simple models and rules can outperform a sophisticated stack built on sand.
A practical starting set
Pick a small number of products tied to money and customers—policy, claim, party, payment—and make them boringly reliable. Then let AI initiatives reuse them. Boring reliability is how ambitious AI programmes stop being science projects and start being change the business can absorb.
How this plays out in delivery
In practice, the difference between a slide and an operable change is whether teams can point to owners, controls, and evidence under pressure. That pressure arrives as an incident, an audit question, a vendor outage, or a steering committee that wants to scale a demo. If those answers are improvisations, the feature was never production-ready—regardless of how polished the interface looked in a pilot.
Delivery leaders should therefore reserve explicit capacity for the boring work: contracts, runbooks, evaluation packs, fallback paths, and decision records. Boring work is what makes ambitious AI and platform change survivable. Skipping it to protect a velocity chart is how organizations repurchase the same programme every three years under a new name.
Questions worth asking in design review
Who owns the outcome after launch? What fails first when the dependency is slow or wrong? Which data classes are in motion, and under which policy? What would make us pause or roll back within an hour? What evidence will we examine weekly to know quality is holding?
If a proposal cannot answer those questions without hand-waving, keep the scope in a controlled experiment. Experiments are useful. Unowned production traffic is not an experiment—it is a risk acceptance you forgot to record.
Working habits that keep quality compounding
Write short decision records when you cross a boundary. Keep a living list of invariants for each critical capability. Review with a checklist that targets blast radius rather than style. Instrument silent failure modes, not only HTTP errors. Revisit model, prompt, and vendor changes with the same seriousness as database migrations.
None of these habits require a new framework brand. They require leadership attention and a refusal to confuse demos with operable systems. Teams that practice them can adopt assistants, agents, and new platforms without losing the enterprise plot.
A note on language and accountability
Replace slogans with operational nouns: capability, owner, control, fallback, evidence, exit. Language shapes governance. Teams that speak only in broad transformation slogans struggle to assign accountability. Teams that speak in capabilities can fund, staff, measure, and stop work when the evidence says stop.
Hold that vocabulary in architecture forums and programme boards. Over time it becomes the shared spine that lets software development absorb AI tools without fragmenting into disconnected experiments.
Closing
The through-line is simple: treat AI-related change as architecture and operations work, not as magic. Make ownership explicit, put uncertainty where blast radius is acceptable, measure what can silently fail, and refuse to scale what you cannot run. That discipline is how software organizations get durable value from new techniques instead of a temporary theatre of progress.
How this plays out in delivery
In practice, the difference between a slide and an operable change is whether teams can point to owners, controls, and evidence under pressure. That pressure arrives as an incident, an audit question, a vendor outage, or a steering committee that wants to scale a demo. If those answers are improvisations, the feature was never production-ready—regardless of how polished the interface looked in a pilot.
Delivery leaders should therefore reserve explicit capacity for the boring work: contracts, runbooks, evaluation packs, fallback paths, and decision records. Boring work is what makes ambitious AI and platform change survivable. Skipping it to protect a velocity chart is how organizations repurchase the same programme every three years under a new name.
Questions worth asking in design review
Who owns the outcome after launch? What fails first when the dependency is slow or wrong? Which data classes are in motion, and under which policy? What would make us pause or roll back within an hour? What evidence will we examine weekly to know quality is holding?
If a proposal cannot answer those questions without hand-waving, keep the scope in a controlled experiment. Experiments are useful. Unowned production traffic is not an experiment—it is a risk acceptance you forgot to record.
Working habits that keep quality compounding
Write short decision records when you cross a boundary. Keep a living list of invariants for each critical capability. Review with a checklist that targets blast radius rather than style. Instrument silent failure modes, not only HTTP errors. Revisit model, prompt, and vendor changes with the same seriousness as database migrations.
None of these habits require a new framework brand. They require leadership attention and a refusal to confuse demos with operable systems. Teams that practice them can adopt assistants, agents, and new platforms without losing the enterprise plot.
A note on language and accountability
Replace slogans with operational nouns: capability, owner, control, fallback, evidence, exit. Language shapes governance. Teams that speak only in broad transformation slogans struggle to assign accountability. Teams that speak in capabilities can fund, staff, measure, and stop work when the evidence says stop.
Hold that vocabulary in architecture forums and programme boards. Over time it becomes the shared spine that lets software development absorb AI tools without fragmenting into disconnected experiments.
Closing
The through-line is simple: treat AI-related change as architecture and operations work, not as magic. Make ownership explicit, put uncertainty where blast radius is acceptable, measure what can silently fail, and refuse to scale what you cannot run. That discipline is how software organizations get durable value from new techniques instead of a temporary theatre of progress.
Minimum viable data product
Start with one consumer-critical slice: for example, “policy snapshot by policy id, daily, with freshness SLO and quality checks on status and premium.” Give it an owner, a support channel, and a versioning policy. Then connect one AI use case to it end to end. Prove the loop before you announce a lake-wide AI revolution.
Resist boiling the ocean catalogues. A perfect ontology with no reliable pipelines still cannot feed production AI. Reliability first, richness next.
Semantics wars and how to end them
Expect conflict over definitions. Architecture’s job is to host the decision, record it, and enforce it at interfaces—not to pretend consensus exists when it does not. Temporary dual publishing can be acceptable if consumers know which product is canonical for which purpose and when the duplicate dies.
Put definitions where developers and models can find them: schema registries, glossary pages, and retrieval corpora for staff assistants. A glossary in a slide pack is a glossary that will be ignored.
Funding model
Data products need sustained funding, not only project bursts. If every programme pays only for its own extract, you will rebuild the same joins forever. Platform funding plus consumer chargeback can work; pure project-only funding rarely does.
Show sponsors the reused value: each new AI use case that did not need a new extract is evidence. Without that narrative, data foundations lose to flashy demos every budget cycle.
Putting it into the operating rhythm
None of this sticks if it appears only in a one-off workshop. Put the checkpoints into existing forums: design authority, risk intake, sprint reviews, and operations reviews. Assign named owners. Review the same metrics until the behaviour becomes muscle memory. Tools change. Operating rhythm is how architecture survives tool change.
When you expand scope—new channel, new market, new model provider—re-run the same questions rather than assuming last quarter’s controls still fit. Scope expansion is where quiet regressions hide. A short re-certification beats a long incident report.
What good looks like after six months
You can name owners for each AI-touched capability. You can show evaluation trends and cost trends. You can pause a feature without heroics. Engineers can explain the boundaries without opening a chat history. Sponsors hear outcome language and evidence, not only model brand names. That is the standard. Aim for it deliberately.
Field notes from programmes that stuck
The programmes that keep their gains share a few unglamorous traits. They name a single accountable owner for each capability touched by AI or platform change. They keep a thin evidence pack current: what the feature does, which data it uses, how quality is measured, and how to pause it. They review cost and quality on a fixed weekly or biweekly cadence instead of waiting for a quarterly surprise.
They also refuse to expand scope while basic controls are missing. That refusal feels slow in the week it happens and fast in the year it saves. Sponsors accept it more readily when you offer a dated path: we can widen to segment B when override rates stay under threshold and fallback drills pass. Conditional speed is still speed—just adult speed.
Common failure modes to watch for
Eternal pilots that serve real customers without on-call. Prompt edits in production with no version history. Retrieval corpora that mix clearance levels. Success metrics that count messages sent instead of outcomes achieved. Architecture reviews that only admire diagrams after contracts are signed. Cleanup work that is always scheduled after this critical launch.
Each failure mode is preventable with a small control. The danger is not that teams cannot invent controls. The danger is that delivery pressure makes skipping them look rational until the incident report is written.
A ninety-day improvement plan
Days 1 to 30: inventory AI-touched journeys, owners, and gaps in logging, evaluation, and fallback. Publish the list without blame. Days 31 to 60: close the top three blast-radius gaps; stand up a short design-authority slot for new use cases; put cost alerts in place. Days 61 to 90: run one controlled promotion from pilot to production using a written exit report; kill or contain at least one unmanaged experiment.
At day ninety, present evidence trends rather than tool logos. Leaders can fund what they can see. Visibility is a prerequisite for sustained investment in quality.
How this article should change Monday morning
Pick one capability you touch. Write the owner, the invariant that must not break, the fallback if the AI dependency fails, and the metric you will check next week. Share it with the people who can correct you. Then make one concrete backlog item that turns a gap into a control.
Long articles do not improve estates. Changed operating habits do. Use this piece as a mirror, not as literature. If nothing in your plan of record moves after reading it, the reading did not count.