Master data management promises a single version of the truth. But a golden record built from wrong source data is just a single version of a wrong truth, and now it is official.

In this contrarian standalone, Richard argues that survivorship rules pick a value, they do not verify one, so a golden record can launder bad data into a clean, trusted, authoritative error. The fix is not in the master data hub. It is upstream, at the source. And he does the math on what it costs to fix the source against what it costs to keep perpetuating the problem.

What you'll learn:

- Why a golden record promotes bad data instead of fixing it

- How survivorship picks a value without ever verifying it

- Why the real fix is upstream: quality at capture, provenance, and source accountability

- The 1-10-100 rule: about a dollar to prevent, ten to correct, a hundred to let it fail

- Where AI actually fits: it can flag the error, it cannot make bad data true

Read the whitepaper: https://themoderncdo.gumroad.com/l/a-single-version-of-the-wrong-truth

Every MDM program assumes everyone already agrees what a customer is. That assumption is where it dies.

Is one customer a person, a household, a legal entity, an account. The definition lives entirely in the edge cases the kickoff skips, and the buried disagreement erupts deep in the build, when the matching rules force a decision. Decide what one customer is before you try to master it.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e20-no-definition-of-master

MDM does not fix bad data. It gives bad data a gold star and removes the warning label.

MDM matches and merges. Neither operation creates correct data. Feed it bad inputs and it selects one of them, stamps it golden, and broadcasts it everywhere with more authority than it ever had. Quality comes before matching, or the master just promotes your mess.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e19-ignoring-upstream-quality

Writing code was the scarce skill in software for fifty years, and vibe coding just made it nearly free. Andrej Karpathy named it in early 2025; by November it was Collins Dictionary's word of the year. Google and Microsoft now say a quarter to a third of their new code is AI-generated. So here's the uncomfortable question for every engineering leader: your developers can produce more code than ever, but how well do they actually understand the vertical they're writing it for?

In this standalone episode, Richard Muirhead argues that the bottleneck in software was never the typing, it was understanding the problem, and AI automated the translation while leaving the understanding exactly where it was. The result is teams shipping flawless, fluent code that solves the wrong problem. He covers why domain judgment is now the scarce skill, where the real return is, and the traps that turn fast code into confident mistakes.

In this episode:

- Why "vibe coding" bakes the trap into its own definition

- The wrong-problem failure mode: code that compiles, demos, ships, and is still wrong

- Why two-thirds of developers say their top AI frustration is "almost right, but not quite"

- The fix: value domain judgment, embed engineers in the business, point AI at understanding

- The ROI, the speed illusion, and three traps including why you can't vibe-code a domain

Read the full whitepaper: https://themoderncdo.gumroad.com/l/the-code-that-solved-the-wrong-problem

Work with Richard: https://perigee.pro

The Modern CDO is written and hosted by Richard Muirhead, fractional Chief Data Officer and founder of Perigee.

The most consequential decision in your MDM program is being made by whoever is configuring the tool.

Which source wins when two systems disagree decides whose version of reality is authoritative. Too often an implementer picks a sensible default under deadline pressure. That is a business judgment, attribute by attribute, and it belongs to the domain owner, validated against real records before go-live.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e18-survivorship-without-ownership

Without governance underneath it, your MDM hub is an expensive argument that runs on a server.

You reached the agreement, configured the hub, and the golden records were trusted at launch. Six months later they have drifted back into disorder, because mastering data is not a thing you finish. The survivorship rules are business judgments that need an owner forever, not just at setup.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e17-mdm-with-no-governance-underneath

Mastering customer, product, vendor, and asset at the same time is how you master none of them.

Each master data domain is its own deep, contentious negotiation, and contentious negotiations do not parallelize. Start them all at once and eighteen months later you have four half-mastered domains, which is to say four nobody trusts. Master one completely first.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e16-mastering-every-domain-at-once

Master data management is a business agreement enforced by software. Skip the agreement and the software just automates the fight.

The hard part of MDM was never the hub. It was getting the business to agree on what a customer is and which source wins. Automate before you agree and you do not get a single version of the truth. You get an automated version of your disagreement, running at machine speed.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e15-mdm-as-a-technology-project

Governance built only to pass an audit dies the moment the auditor leaves the building.

A program born from an audit gets optimized to survive audits. It passes, the regulator moves on, and it loses its only reason to exist. Use compliance as the trigger. Then build for the value, because the same inventory and lineage the regulator wants are what the business runs on.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e14-compliance-only-governance

If your data quality work has an end date, you are paying to clean data that will be dirty again by next year.

The cleanup crosses its finish line, everyone celebrates, and a year later the data is back where it started, because the sources that made the errors never changed. Quality is not a state you reach. It is an operation you run, with monitoring and a loop back to the source.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e13-data-quality-as-a-one-time-project