The Second-Time Rule: Turn Fixes Into Systems

Last week I caught myself about to make a one-time fix.

I was working on Multi, the tool that turns content into YouTube videos. An agent added a high-priority item to the product backlog. The backlog sorts by arrival time, so the high-priority item landed at the bottom.

My instinct was to drag it to the top. Five seconds, problem solved. But tomorrow another agent adds another item and it sinks to the bottom again.

I fixed the source instead and added a prioritization protocol to the top of the backlog file: priority tiers, ordering rules. Now any agent that touches the backlog reads the protocol and places the item where it belongs.

I did the work once. It pays off each time.

Each problem gives you two options. You can patch the instance or write the protocol that handles each future version.

A patch solves it once. Next time the same problem shows up, you patch again.

A protocol solves the source. Next time the same problem shows up, the protocol handles it automatically.

Rule of thumb: the second time you do something, turn it into a protocol. The first time is discovery. The second time is when you build a rule.

🔮

What’s one repeat problem you could solve at the source?