Strikes

Some mistakes are lessons. Others are patterns. When the same error happens three times, it is no longer a learning moment—it is a signal that something fundamental is not working, and the team needs protection from it.

At FuzzyFlags, a strike is not a mark of shame. It is a boundary. We do not track minor errors or punish honest mistakes. A strike only applies when a person repeats the same substantive mistake three times after it has been clearly identified, discussed, and understood. Three is the threshold because once is circumstance, twice is a warning, and three times is a pattern that needs intervention.

What counts as a strike

A strike applies to significant, repeated failures that affect the team or the work. This includes:

Your lead asked you to report progress at the end of the day and you didn’t.
You said you were going to hand in something by 2:00 PM and we don’t hear from you until 6:00 PM.
You were told not to change architecture without lead approval, and you did it anyway.
You made a false promise—committing to something you could not deliver.
You skipped giving hours estimations before starting a big sprint or ticket.
You implemented something no one asked for, consuming time and resources the team needed elsewhere.

In every case, the mistake must be the same one, clearly identified, and repeated three times after the person has had a fair chance to correct it.

A strike does not apply to:

Honest mistakes that are caught and fixed without repetition.
Errors made while learning something new.
One-off failures caused by ambiguity, external blockers, or unclear expectations.
Situations where the root cause is a systemic problem, not an individual pattern.

The manager must confirm that the mistake was clearly communicated, understood, and that the person had a fair chance to correct it before the third occurrence. A strike without this context is just bureaucracy.

The cooldown period

After three strikes are issued, a cooldown period follows. This is a deliberate pause to stop the pattern, protect the team, and create space for real change.

See the Cooldown period for how cooldown works, how long it lasts, and what ends it.

What managers must do

Before a strike happens, managers must:

Name the mistake clearly the first time it happens.
Confirm the person understands it and knows what to do differently.
Check for systemic causes before blaming the individual.
Document the pattern so the third time is not a surprise.

After a strike happens, managers must:

Act immediately. A strike without action is worse than no strike at all.
Be direct with the person about what changed and why.
Design the cooldown with a clear path back, not an open-ended timeout.
Follow through on the checkpoints. The cooldown is only meaningful if the return is conditional and real.

What this is not

The strike system is not:

A scorecard for minor imperfections.
A tool for managers to avoid difficult conversations.
A substitute for coaching, training, or removing systemic obstacles.
A way to push people out slowly. If someone is not working out, address it directly.

Strikes exist because repeated patterns erode trust, burn time, and damage team morale faster than almost anything else. A team that tolerates the same preventable failure three times is not a team that values excellence. It is a team that has learned to absorb the cost of someone else’s pattern.

The goal is not to collect strikes. The goal is to make them unnecessary. When a manager does this well, they rarely issue one. When they do, it is because the team needed protection, and the person needed a clear signal that the pattern had to end.