Building a process improvement mindset for SOPs and teams

Executive overview

When a new team member inherits an unclear SOP, they face a choice that reveals their relationship with process. Most people either blindly follow flawed instructions or quietly patch them to look capable — neither improves the system.

The third path treats process as a living, collective resource that each person is responsible for making slightly better.

Small, documented improvements compound into SOPs that get clearer with every handoff.

The two wrong mindsets

• "Process is gospel": follow steps exactly, assume confusion is your fault, make undocumented guesses
• Each undocumented guess stacks on prior ones until the process is unrecognisable
• "People are everything": blame the last person, fix it in your head, keep the SOP vague to stay indispensable
• Both approaches protect the individual at the expense of the system

The process improvement mindset

• View every unclear step as an opportunity to leave the process better than you found it
• If a colleague is reachable, ask them to clarify ambiguous terms before proceeding
• If not, document your assumptions directly in the SOP with a note explaining the reasoning
• Documented assumptions mean mistakes are traceable and no individual is blamed
• The next person inherits clarifications, not the same confusion

Why this compounds over time

• Each handoff adds a layer of specificity: "send test email" becomes "send test email to this address"
• Mistakes become learning events for the whole team, not performance failures for one person
• Incentives align: improving the SOP benefits everyone, hoarding knowledge benefits no one
• Most meaningful process gains come from small, incremental tweaks — not formal redesign projects