Consistency Compounds
You watch your team pull off a heroic week.
Late nights. Fast fixes. Loud praise. A good result.
Then Monday hits.
Someone skips a step, because “we know how this goes”. A small error slips in. Nobody spots it, because everyone feels tired and pleased.
Two weeks later, you deal with the mess. You do not have an effort problem. You have a standards problem.
Intensity feels like leadership because it looks like movement.
Standards feel boring because they look like repeat work.
Yet standards carry organisations through pressure, audits, incidents, and change. Standards also protect good people from bad days.
So here is the real question. Do you reward the surge, or do you build the system?
Intensity creates stories, standards create outcomes
Intensity often shows up as:
- the big push before a deadline
- the rescue job when something break•
- the all hands scramble when a client shouts
- the leader who stays latest, speaks loudest, replies fastest That behaviour can save the day.
It can also hide weak routines. Standards show up as:
- the same checks, every time
- the same language, every shift
- the same handover discipline, even when you feel rushed
- the same expectation of quality, even when nobody watches
You cannot scale intensity. You can scale standards. Ask yourself. When your best people go on leave, does delivery wobble?
When you onboard someone new, do they learn “how we do it”, or do they learn “how Dave does it”?
When pressure rises, do you keep the basics, or do you drop them first?
High risk sectors already solved this, you can steal it
Surgery teams use checklists, not because they forget how to operate, but because they refuse to rely on memory under pressure.
A global study published in 2009 linked a 19 item surgical safety checklist with lower complications and deaths across diverse hospitals.**
WHO (World Health Organisation) later reported that trials showed serious complications reduced by about a third when teams used the checklist.
Aviation does the same thing.
Pilots do not treat checklists as optional admin. The UK Civil Aviation Authority publishes guidance to promote best practice in how operators design and use electronic checklists, because good checklist use supports safety benefits. ***
Those teams still need skill. They still need judgement. Yet they anchor performance in a shared standard. You can do that in any organisation.
Standards do not mean rigidity, they mean clarity
Some leaders hear “standards” and picture a binder nobody opens. That is not the job. A standard is the current best way you know to do the work, written and trained so a team can repeat it.
Standards give you a baseline. Baselines let you spot drift early. Drift is where risk grows. Toyota built a world famous production philosophy around eliminating waste and improving efficiency, with employees pursuing daily incremental improvement.
This only works when teams can see the process clearly and improve it deliberately. Standards give you something to improve. Without them, you only have opinion.
How to build standards that people actually use
You do not need a transformation programme. You need a few decisions, taken seriously.
Start here.
1) Pick the moments that matter most
Choose three to five points where errors cost the most. Not every task. The critical ones.
Examples:
- shift handover
- permit to work steps
- client onboarding
- quality sign off
- incident reporting triggers
If you cannot name your critical moments, you cannot protect them.
2) Define what “good” looks like in plain language
Write it so a new starter can follow it. Keep it short. Use the language your team already uses.
Include:
- the sequence
- the minimum checks
- what “stop” looks like
- who owns the decision when something feels off
Then train it. Don’t just publish it.
3) Build a rhythm, not a poster
Standards live in routines.
Use simple rhythms:
- a two minute start of shift check
- a five minute handover script
- a weekly quality review that looks at one real job
- a monthly drill that rehearses a rare but serious event
Rhythm beats reminders.
4) Coach in the moment, not in the review
If someone misses a step, deal with it kindly and fast. Treat it as signal, not failure.
Ask:
- What made it hard to follow the standard today?
- What did you not have that you needed?
- What do we need to change so this becomes easy?
You do not enforce standards with fear. You enforce them with design.
5) Measure adherence, not just outcomes
Most dashboards tell you what happened after the fact. (TEGinsight is the dashboard that gives you live data on team morale and so much more)
Add measures that tell you if behaviour stayed on track:
- percentage of handovers completed properly
- number of jobs stopped for a safety check
- rework caused by missed steps
- time to spot and correct drift If you only measure outcomes, you only manage regret.
Your standards reveal your leadership
Standards are not a process issue. They are a leadership choice. You show your team what matters by what you tolerate.
If you tolerate “we’re busy” as the reason to skip the basics, you teach your team to gamble. If you protect the basics when pressure rises, you teach your team to stay reliable.
So here is the uncomfortable question. Do you want to feel like the hero, or do you want your team to win without needing one?
If you want to build standards that hold under pressure, and a culture that stays calm when work gets hard, get in touch. We will help you design repeatable leadership behaviours, not motivational spikes.
Forward this to a colleague who cares about quality, not noise.
Expand your community. The TEG Newsletter introduces you to…