The win is real. Now don't lose it.
You tried something and it worked. Maybe you cut a fulfillment error rate in half, or got invoices out on time three weeks running. Good. But a win that lives only in your head — or in one person's habits — isn't a system. It's a lucky streak waiting to end the day that person goes on vacation.
The next move isn't to celebrate and chase the next fire. It's to decide how you'll lock the win in so it survives a new hire, a busy Tuesday, or a second location. That means picking the right tool for the job: an SOP, a template, or an automation.
These three aren't interchangeable. Use the wrong one and you either waste effort or fail to hold the gain. Here's how to tell them apart and choose correctly.
Three vehicles, three different jobs
SOPs (standard operating procedures) are for processes that involve judgment, sequence, or people coordination. They're a written set of steps — what to do, in what order, and what "done right" looks like. Use an SOP when a human still has to make calls along the way: a client onboarding call, a quality check, a closing checklist.
Templates are for recurring outputs — documents, emails, reports, quotes — where the content changes but the structure doesn't. A template locks in the format and key fields so nobody starts from a blank page and nobody forgets a section. Proposals, weekly reports, and onboarding emails are classic candidates.
Automations are for repetitive, rules-based tasks with no judgment required. If the input reliably determines the output — send this reminder, move this data, flag this threshold — software should own it end to end. This is where a Zapier flow, a script, or a built-in workflow tool earns its keep.
The mistake most teams make is reaching for the fanciest tool first: automating something still too variable to mechanize, or writing a ten-page SOP for a task a one-page template would solve. Match the vehicle to the nature of the task, not to what feels impressive.
A quick test to pick the right one
Ask three questions about the win you want to lock in:
- Does it require judgment or vary by situation? If yes, write an SOP. Don't try to automate discretion — you'll either strip out the nuance that made it work, or build something brittle that breaks on the first edge case.
- Is the output a repeated document or message with a consistent structure? If yes, build a template. It's the fastest way to standardize without touching any software you don't already use.
- Is it fully rules-based, high-volume, and free of exceptions? If yes, automate it. This is exactly the territory covered in Is Your Process Ready to Automate? A Readiness Check — worth a pass before you commit engineering time or a subscription to it.
Often a single win needs a combination. A better client follow-up process might be an SOP for how the conversation should go, a template for the follow-up email, and an automation that schedules the send. Don't force one vehicle to do all three jobs.
Write it down before you scale it
Whichever vehicle you choose, the standardizing step has one non-negotiable rule: write it down while it's fresh. Wait a month and the details blur — the next person who tries to replicate the win gets a worse version of it. This is the same discipline the 90-day plan calls for in its final phase: turning "we figured out a fix" into a one-page SOP or template that a future hire could follow without you in the room.
Keep it short. A checklist beats a manual. If your SOP runs past one page, you're probably documenting exceptions instead of the core process — split those into a separate note and keep the main path clean.
For automations, the "documentation" is the automation itself plus a short note on what it does and what to check if it breaks. Nobody needs a manual for a trigger-and-action flow, but somebody other than you should be able to glance at it and understand the logic.
Roll it out wider, not all at once
Once the win is locked into a repeatable form, expand it deliberately. If it worked in one location, one team, or with one type of client, pilot the rollout with a second group before pushing it everywhere. This catches the assumptions that were specific to the original context — a template that assumed a field your other team doesn't collect, an automation that assumed a data format your second system doesn't use.
This staged approach is exactly the kind of standardization work covered in Turning One Win Into a Standard: The Lock-In Step Most Teams Skip. The step between "it worked once" and "it works everywhere" is where most teams get impatient and skip the verification. Don't be one of them. A win that only holds up in its original context isn't standardized yet — it's just been lucky twice.
If you're layering this on top of automations already running, check your capacity before adding more. Rolling out three new automated pieces in the same week you're also implementing a new tool is how good ideas turn into support tickets. How Many Automations Can You Run at Once? A Sequencing Guide walks through how to stage this without overwhelming your team or your systems.
Close the loop
Locking in a win isn't the finish line — it's raw material for the next planning cycle. Once the SOP, template, or automation is running cleanly across the wider team, go back to your list of opportunities and ask what's next. What did this rollout teach you about your process maturity? Did the automation reveal a data problem you didn't know you had? Did the SOP surface a step nobody could actually explain consistently?
Feed those observations into your next round of triage — the same automate/improve/ignore sort described in The One-Week Triage: Automate, Improve, or Ignore Your Fixes. Standardizing one win well usually exposes the next one. That's the point of running this as a cycle instead of a one-off project: each fix you lock in makes the next fix easier to spot, easier to build, and easier to trust.
A win you can't repeat is a story. A win you've turned into an SOP, a template, or an automation is an asset. Take the extra hour to build it right, and it'll keep paying you back long after you've forgotten the fire drill that started it.