Technology roadmaps naturally collect new requests. They are less likely to identify work that can stop, records that can be consolidated, or services that need an ownership review. A stop-doing list can make the next planning cycle more focused without assuming that every older service is unnecessary.
Start with a question, not a deletion
Identify duplicated reports, unclear recurring tasks, and services whose purpose needs confirmation. Ask the business and technical owners to explain their dependencies before proposing a change.
Record the reason for reviewing each item and the evidence still needed. A service with few visible users may support an infrequent but important process.
Plan the approved outcome
If an item is retained, make its purpose and owner clearer. If it is changed or retired, use the appropriate review process for access, information, contracts, and operational impact.
Carry the outcome into the roadmap so future planners understand what was decided. Removing an unexplained line from a spreadsheet can cause the same request to return later under another name. A short decision record keeps the planning effort from going in circles.
Practical takeaway
Balance the investment roadmap with a reviewed list of work to clarify, consolidate, or retire through the approved process.