Why Your Team Stops Following Process: The Friday Rule That Took Down 94 Websites
Teams stop following a process when it works so well that nobody remembers why it exists. Success makes structure invisible, invisible structure becomes negotiable, and negotiable structure breaks under load. The fix isn't more rules. It's knowing who owns each rule, explaining why it exists, and checking the quiet systems before they fail.
It was Friday the 13th, and it was unseasonably cold. I had taken a personal day to go to the Biltmore Estate with my family, and we were all bundled up on the playground, trying to stay warm while my daughter ran around having the time of her life.
Around two in the afternoon, my phone started lighting up. First a Slack notification, then another, then a call from our agency partner, and then the CEO of the client company, all saying the same thing: their websites were down.
Not one site, but the site for every one of their 94 locations around the world.
How one skipped rule took down every site
We had launched the new platform on a Tuesday, which is exactly when you're supposed to launch. Everything was stable, the client was happy, and we told them not to touch anything until Wednesday so everything had time to propagate.
They didn't touch it, we didn't touch it, and for three days it ran without a single issue.
Then on Friday afternoon a small request came in, the kind of quick update that takes a few minutes. My lead developer didn't see any reason to let me know he was about to push a change to production on a Friday, so he went ahead and did it.
We had one rule in our company that nobody ever needed reminding of: nothing goes to production on a Friday. Ever.
He pushed it anyway, and every one of their 94 location sites went down at once.
Five sessions. Real fixes. A clear next move.
One on one, within ten days. $500.
Start the Sprint$500. Full refund if the first session isn't for you.
Why a ten-minute fix took more than two hours
It wasn't the kind of break you can undo with a click. It was a conflict in the hosting configuration, and the one person who could untangle it was the developer who had built the infrastructure in the first place.
Our team was smaller than it had been at that point, so he was only working with us on contract, which meant we no longer owned his time. He needed notice before we made any change that might require him, and nobody had told him a production push was happening.
When the sites went down, he was on a call with his actual employer, and he couldn't just walk away from it.
The structure we had built for exactly this situation was simple. Every production push got advance notice to the whole team, the infrastructure developer had to confirm he was available before any hosting change, and nothing went live on a Friday.
If anyone had followed it, he would have said something like, "Sure, I'll be free in two hours, let's do it then," and if anything had gone wrong, it would have taken ten minutes to fix before anyone noticed.
Instead, all 94 sites had been down for half an hour before the calls even started, and I was standing on a playground with no laptop while executives spiraled in a group thread about rolling back a brand-new platform that had been live and stable across every location for three days.
When the right person finally became available, the fix took ten minutes.
The total downtime was two hours and ten minutes. The cost was three months of lost trust with that client.
Why do teams stop following processes that work?
What I had to sit with afterward was that the rule didn't fail because it was a bad rule. It failed because it had worked so well for so long that everyone forgot why it existed.
Launches were smooth and nothing broke, so the team stopped connecting all that stability to the structure that was creating it. Over time the rule started to feel like a formality, and a formality is the easiest thing in the world to skip "just this once."
I've watched this same pattern play out in nearly every business I've worked with. Success makes structure invisible, invisible structure becomes negotiable, and negotiable structure breaks the moment it's under load.
"Just this once" is never a random slip. It's what happens when nobody can see what the rule is holding up anymore.
Solo. Not Alone.
Software, creative support, and education to help service-based business owners turn interest into trust and bookings.
See Club SoloWhat skipped processes look like in a service business
You probably don't push code on Fridays, but you almost certainly have your own version of this.
It's the intake form you skip for the referral who "already knows what they want," the deposit you don't collect because the client is a friend, the handoff checklist your team quietly stopped using because nothing has gone wrong in months, or the scope you never wrote down because the client seemed easy to work with.
Every one of those is a Friday push. It's fine right up until the day it isn't, and it never breaks on a calm Tuesday when you're at your desk. It breaks when you're on the playground.
How to hold your team accountable to process
The answer isn't more rules. It's keeping the ones you already have in plain sight, and there are four ways to do that.
Know who owns what. When you don't understand who owns what, there's nobody to be accountable for anything. So when something goes wrong, everyone points fingers at everyone else, because no one took ownership of the actions that were taken.
That Friday, nobody owned the decision to push, and nobody owned telling the one person who could fix it. Every rule needs a name next to it.
Say why the rule exists, not just what it is. "No Friday deploys" is a rule that people will eventually work around. "No Friday deploys, because if it breaks, the people who can fix it are gone for the weekend" is a reason, and people are far less likely to skip a reason.
Treat the first exception as a warning sign. The first time someone asks for "just this once" is the moment to stop and ask what changed, not the moment to show how flexible you are.
Check your quiet systems on purpose. The processes that haven't broken in a while are the ones most likely to be skipped, so look at them before they remind you they exist.
The structure that keeps your business stable is load-bearing, and the day it starts to feel optional is the day you need to pay the most attention to it.
Should You Hire an Agency or Do It Yourself First? Why the $10,000 Agency Can't Fix Your Message
5 min readFrequently asked questions
Why do employees stop following procedures?
Usually because the procedure has worked for so long that nobody connects it to the results anymore. When nothing goes wrong, a rule starts to feel like a formality, and formalities get skipped "just this once."
How do you hold employees accountable without micromanaging?
Put a name next to every rule and every decision, and explain why the rule exists. People skip rules they don't understand far more often than rules they know are protecting something.
What is a change freeze, and does a small business need one?
A change freeze is a window when nobody makes changes to live systems, like no updates on Fridays or before a holiday. Any business that relies on a website, booking system or software for revenue benefits from one.
Who should own a process in a small business?
One person, by name. When a process belongs to "the team," nobody is accountable when it breaks, and everyone points at everyone else.
If something in your business keeps breaking and you're not sure why, that's exactly what we look at in the Next Level Sprint: five sessions, one on one, within ten days.
Start the Sprint$500. Full refund if the first session isn't for you.
Dave Zaron has spent 16 years building the systems behind high-stakes launches, including the infrastructure for #TeamSeas, the $30M campaign led by MrBeast and Mark Rober. He helps service business owners who've hit a plateau see exactly what's keeping them stuck.
Keep reading
Should You Hire an Agency or Do It Yourself First? Why the $10,000 Agency Can't Fix Your Message
Thinking about hiring an agency or outreach service to get more clients? Why you need to do the work yourself first, and what you need to know before anyone else can help you.
Not a Tech Person? Why Business Owners Still Have to Own Their Systems
\"I'm not technical\" is one of the most expensive things a business owner can say. Why you don't need to be your own CTO, but you can't lead what you refuse to understand.
Delegation vs Abdication: How Handing Off Work Can Cost You a Client
What's the difference between delegation and abdication? A real story of a six-week promise on a 24-week project, and how business owners can hand off work without losing control.