Most organisations are very good at building data products.
They are far less good at stopping them.

In this episode, Roland Brown tackles one of the most uncomfortable yet essential capabilities of mature data organisations: sunsetting data products properly. Building directly on the failure modes discussed in Episode 68, he explains why keeping bad or outdated data products alive quietly damages trust far more than removing them.

Roland shows that most data products don’t linger because they are still valuable they linger because organisations avoid difficult conversations. “Someone might still be using it.” “We might need it later.” “It took effort to build.” These well-intentioned hesitations result in products that are neither alive nor dead, creating ambiguity, confusion, and false confidence.

The episode reframes sunsetting not as deletion or failure, but as a deliberate lifecycle stage one that was already implied in the anatomy of a good data product introduced in Episode 62. Products are born, they mature, they evolve and eventually, they should retire.

Roland outlines the clearest signals that a data product should be considered for retirement:

• The decision it supported no longer exists
• Trust has eroded to the point of constant validation
• No one is willing to own the outcome
• A clearer, better product has replaced it

None of these are failures. They are signals of change.

The episode then walks through what responsible sunsetting actually looks like in practice:

• Making the decision explicit instead of letting decay continue
• Identifying who is still impacted and how
• Providing a clear replacement or exit path
• Running a managed transition period
• Retiring interfaces cleanly and visibly

Roland explains why silent decay is far more dangerous than visible retirement. Products that quietly rot teach consumers that data products can’t be trusted not just the bad ones, but all of them.

A practical revenue example illustrates how sunsetting, when done transparently, actually increases confidence rather than disrupting it. Consumers know where to go, what to use, and what no longer applies.

The episode closes with a powerful maturity signal:
healthy data ecosystems are not defined by how many products they have but by how confidently they can let go of the ones that no longer serve decisions.

Sunsetting is not an admission of failure.
It is an act of respect for consumers, for clarity, and for trust.

Discover insights on:

• Why bad data products linger longer than they should
• The hidden cost of keeping outdated products alive
• How to recognise when a product should be retired
• Why sunsetting is a lifecycle capability, not cleanup
• What responsible, low-risk retirement actually looks like
• How killing bad products strengthens the entire ecosystem

“A product you’re afraid to kill
is a product that’s already dangerous.”

🎧 Listen to The Data Journey wherever you get your podcasts, or visit thedatajourney.com