A steward with no time and no authority is a name in a spreadsheet, not a control.

You can name forty stewards in a kickoff. It feels like progress. It is a list. A steward needs protected time, real authority to decide, and recognition in how they are evaluated. Take away any one of the three and you have built a costume, not a control.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e12-stewards-without-authority

A data catalog is not a governance program. It is a filing cabinet for a program you never built.

A tool scales a working operating model. It cannot create one. Buy the catalog first, hoping it does the hard work for you, and you get an empty machine harvesting technical metadata into a stale, misleading glossary. Build the program. Then file it.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e11-tool-led-governance

IT cannot tell you what an active customer is. So IT cannot own your governance.

Ownership drifts to IT because the catalogs and the tooling live there. But whether someone counts as an active customer is a business judgment, not a technical one. The business owns the what. IT owns the how. Invert that and the catalog is complete and quietly ignored.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e10-it-owned-governance

Governing four domains at once is how you govern none of them.

Named stewards everywhere, untrained, with no time. Processes defined in parallel with no proven template. A year later, there is no single place you can point to and say governance works here. Prove the operating model in one high-value domain. Then scale the proof.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e9-the-big-bang-rollout

If people describe governance as something done to them, they are already building the shadow systems that will gut it.

Built as a tax, governance gives the data user nothing they can feel, just forms and approvals, so they route around it. Every shadow spreadsheet and unofficial extract is a vote against your process. Make the right thing the easy thing, or get evaded.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e8-governance-as-a-tax

A capability that is built and never used is not worth zero. It is worth less than zero.

Datasets cataloged, users provisioned, models deployed. Every number goes up and to the right, and none of them tells you whether any of it is used. Then a skeptical new leader asks the adoption question, and the whole green dashboard inverts in an afternoon.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e7-vanity-metrics

You cannot build an AI future on foundations you were too proud to audit.

Every ambitious roadmap rests on an assumption no one has checked: that the foundations are good enough. They rarely are. "We will clean the data as part of the project" is where the program goes to die, seventy percent in, with leadership watching the AI initiative stall on data it cannot trust.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e6-ignoring-data-debt

Most data strategies do not fail in design. They die in the first ownership fight nobody was empowered to settle.

You can write a brilliant strategy and still stall in month three, when two units both claim the customer domain and no one is allowed to decide. The missing layer is the operating model. Skipping it does not avoid the fight. It defers the fight to the worst possible moment, the middle of execution.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e5-no-operating-model

If no executive will put their name on a number that your data team produces, the program is already dying.

Data value is hard to attribute, so programs retreat to platitudes about being an asset. Budget committees do not fund platitudes. They fund numbers with a name attached. Tie every serious thing you build to a business owner who will defend it when you are not in the room.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e4-no-line-of-sight-to-value

If your data strategy can be summarized as the name of a platform, you bought infrastructure and called it a strategy.

Platform decisions feel like progress because they are concrete, and a vendor hands you a glossy reference architecture. But if your biggest competitor adopted the same platform tomorrow, what advantage would you have left. Outcome first, then the capability it requires, then the technology. Never the reverse.

Long-form whitepaper is at https://themoderncdo.gumroad.com/l/s2e3-technology-first-strategy