Service Catalog Rescue: Help Teams Know What Exists, Who Owns It, and What Breaks It

As systems grow, teams lose track of what exists and who is responsible. Participants build a practical service catalog from messy clues: repos, deployments, dashboards, alert routes, docs, vendor accounts, and tribal knowledge.

The goal is not a vanity spreadsheet. It is an operating map that helps during incidents, onboarding, audits, and planning. Teams decide the minimum useful fields, freshness rules, and ownership habits needed to keep the catalog alive.