Technology Waste Audit

Decide: cancel, merge, or ask why

Purpose: Give each finding the decision it actually needs — shelfware gets cancelled, redundancy gets merged once migration cost is understood, and shadow IT gets a question before either.
Inputs: The license ledger and capability map from the first two systems
Method: Shelfware: cancel or downgrade, split into verified-recoverable-now versus locked-until-renewal
Redundancy: confirm the overlap, check contract lock-in, price the migration, then merge toward the tool with the stronger reason to exist
Shadow IT: ask why it exists before deciding what to do — sanction it or replace it if the need is real, shut it down only once those don’t apply
Report savings in separate labeled buckets rather than one combined figure
Output: A decision for every finding, and savings sorted into verified, renewal-period, potential-exposure, and productivity-cost buckets.
Data: Documents and SOPs Spreadsheets and interviews

The reasoning behind this one capability, with a worked example.