Walk any floor long enough and you will find workarounds. A spreadsheet one person keeps. A sticky note on a machine. A text message that stands in for a form. They are easy to dismiss as bad habits. I treat them as information.
A workaround exists because the official way did not work. Somebody had a job to finish and found a way. That makes every workaround a small process built by the person who knows the work best, and it points to exactly where the system fell short.
So I ask about them with curiosity, not criticism. What do you do when the form does not fit? Where do you keep the thing you cannot find anywhere else? The answers are often better than what the company designed.
There are two ways to get this wrong. One is to ban the workaround, which removes the fix and leaves the problem. The other is to leave it alone, which keeps critical knowledge in one person's notebook. The better path is to learn what the workaround solves, then build it into the process so it does not depend on one person.
A good process often starts as somebody's workaround that the company finally noticed.
Ask three people this week what they do when the usual way does not work. Write down the answers. You are likely to have the first draft of your next process.
If you would like help turning workarounds into a process, reach out to us. Email us at info@devconsultantsllc.com or call (201) 540-7762.

