Reconciliation weeks that do not exhaust app owners

Enterprise catalogs go stale when reconciliation feels like a surprise audit. We start with a visible calendar anchor: a five-day window, two office hours, and a single shared metric everyone agrees to move slightly upward. The goal is motion without shame.

On day one, publish a one-page scope that names systems in play and explicitly lists what is out of scope for that cycle. Owners respond faster when they know which fields are frozen and which ones are fair game. Pair that page with a short Loom-style walkthrough if your culture tolerates async video; otherwise use a annotated screenshot set.

Mid-week, run a facilitated session that ends with three named follow-ups, each assigned to a person rather than a mailing list. Close the week with a lightweight readout aimed at leadership: three bullets on progress, one bullet on deferred items, and a reminder of the next reconciliation window. The rhythm trains teams to expect maintenance instead of heroics.

This approach will not fix systemic data quality debt in a single pass. It does create receipts: calendar entries, invites, and a short narrative you can reuse when external reviewers ask how ownership is practiced.