Replacing software creates work of its own. Records must move, staff must learn the new system, and someone must maintain its connections. A technology assessment should establish whether that effort addresses the problem you actually have. Sometimes a configuration change is enough. In other cases, a product limitation is already costing the team more than a transition would.
Identify the Task the Tool Must Support
For a worked example, follow a U.S. engineering firm’s project from sales approval to time entry and billing. Record where staff enter the same information twice. At each transfer, check whether the problem comes from an inconsistent project code, an unused integration, or a product that cannot support the required relationship. Those findings lead to different spending decisions.
If the firm has enabled an AI assistant inside an existing subscription, include its access and role in the assessment. Gartner’s October 2026 outlook identifies AI agent identity as an emerging concern. Ask which records the assistant can read or change and who maintains those permissions. The assessment should cover how the application is being used today, including features added since the original purchase.
Compare Keep, Improve, Replace, and Retire
Compare the options against the same operating problem. In the engineering firm example, different project codes cause reentry between time capture and billing. The next move depends on whether the gap sits in the approved process, the configuration, or the product’s capabilities.
| Option | Evidence That Supports It | Question to Resolve |
|---|---|---|
| Keep | The tool supports the task and the reported problem comes from inconsistent use. | Which instruction or ownership gap needs attention? |
| Improve | An approved configuration or connection could resolve the gap. | Can a limited test demonstrate the required result? |
| Replace | A required capability is unavailable or continuing constraints outweigh a supported alternative. | What migration, training, and continuity work does the change require? |
| Retire | The purpose is no longer needed or another approved system already provides it. | Who confirms data retention, remaining dependencies, and the exit plan? |
Test the Consequences of Each Choice
Include data cleanup, staff training, and integration maintenance in the cost comparison. Staying with a tool may require a control or workaround; replacing it may create migration and continuity risks. Ask the security and privacy owners to assess relevant data handling. Keep unsupported assumptions visible, especially where a vendor has not confirmed an integration or export feature. A feature shown in a sales presentation is not proof it fits your setup.
Make the Next Decision Explicit
End with a ranked set of actions: retain, repair, investigate or replace. State the evidence and conditions behind each recommendation. Where a small configuration test could answer the question, propose that before a full selection project. Identify who approves the next step and which records should be preserved. The assessment succeeds when management can choose an informed path, including the reasonable decision to keep an existing tool.
GAO’s 2025 legacy-system review considered attributes including vendor support, security risk and operating costs. The agency used those factors to identify priorities for modernization. A business can apply the same broad discipline at a smaller scale without adopting federal scoring rules.