Don't Automate a Broken Process First

Published 2026-04-01 by Faraz Rahimi

Scripts amplify whatever you give them. A broken receiving process at 10x speed is just a louder mess.

Don't Automate a Broken Process First

Tags: Operations, Automation, Process, Python, unlisted

If two people already disagree on when a receipt is "done," a script will pick a side and make it official. That is how you get faster conflict.

I watch the process until I can draw it without question marks. Then I automate the boring middle, not the political edges.

Shrink before you speed up

Remove extra fields, extra status codes, extra approvals that exist because a spreadsheet once needed them. Then put Python on what remains.

Leave a human at the seams

Vendor says the file is correct and the floor says it is not — that is not a parse error. That is a conversation. The script should stop and queue, not "be helpful."

Original post: https://farazrahimi.com/posts/dont-automate-a-broken-process-first