When a fix causes another problem, start by making the failure reproducible. A useful repair plan connects the reported issue to a cause, a tested change and a controlled release.

Before you add more features, check how your software handles business rules, data, failures, testing and release. These questions apply to web apps, mobile apps and internal tools.

Before a software handover, verify the code, accounts, operating costs and release process you will depend on. Turn missing access and unanswered technical questions into a written handover plan.

When one file handles the interface, business rules and data access, a small request can involve several kinds of work. Review its responsibilities and dependencies before deciding what to change.

Compare the work needed to improve your current product with the full cost and risk of replacing it. Start with the business requirement and the evidence in the existing system.