Patching instead of redesigning

After implementing a new process, technology, system or practice, it transpires that there are slight imperfections, small limitations, there is inadequate performance or it just does not work as smoothly as expected.

The usual reaction is to fix it but not by changing what has been implemented but by patching it, adding extra steps, involving other people, and so forth. Initially, the patching seems innocent, simple and quick only to grow to a complex, expensive, dysfunctional burden of workload which becomes unmanageable, spreads and affects organisational performance.

Any examples?
How many spreadsheets does your company use because the IT system does not have the features that the user needs? How many extra steps in the process do you have to take to place and ship a simple order?

If you notice many patches used to fix a dysfunction consider a redesigning approach. Don’t be parsimonious or impatient and do it right the first time. Get the best help you can afford because continuous fixing increases complexity of a system and results in more costs.