Skip to content

Playbook — Find your redundant & unowned apps

Outcome: a concrete worklist of the waste and the orphans — applications that duplicate each other, and assets nobody owns.

The situation

There's a cost-cutting push, a rationalization mandate, or you simply suspect you're paying for three tools that do the same job. You need to point at specific, defensible candidates — not a vague "we should consolidate." And you need a name next to every asset, because you can't govern what nobody owns.

You'll walk away with

  • A list of redundancy candidates — capabilities delivered by more than one application (your consolidation shortlist).
  • A list of unowned assets — applications and technologies with no accountable owner.
  • As a bonus, the EOL-risk and unmapped-application signals sit on the same page.

Before you start

Your applications imported (see See your application portfolio), and ideally applications mapped to the capabilities they deliver — redundancy is detected as multiple applications delivering the same capability, so that mapping is what makes it work.

Steps

  1. Open Estate Health. Home & Intelligence (/intelligence) → the Estate Health card, or go straight to /estate-health. The page is organized as four signal sections: no-owner assets, EOL-risk technologies, unmapped applications, and redundancy candidates. → Detail: Estate health
  2. Work the redundancy list. Each redundancy candidate is a capability with more than one application delivering it — your consolidation conversation, with the evidence attached. (The dedicated Redundancy view at /redundancy drills further.)
  3. Close out the unowned assets. The no-owner section has an inline "Assign owner…" field per row — assign, and the row drops off the list and the counts update. This is the fastest possible ownership cleanup. → Detail: Assigning owners
  4. Watch the trend. Estate Health captures snapshots over time, so you can show "N fewer issues since <date>" — proof the cleanup is working, not just a static complaint.

Where people get stuck

Redundancy detection depends on capability mapping. If your applications aren't yet linked to the capabilities they deliver, the redundancy section will look empty — not because you have no duplicates, but because the tool can't see them yet. Do the capability mapping first (AI-assisted in Discover), then the duplicates surface on their own.

Make it stick

The trend line is the hook. Capture a snapshot, do a round of owner assignment and consolidation, and the "issues since last month" delta becomes a recurring number you report — turning a one-time cleanup into an ongoing health metric.