Consistency Doesn't Come From Rules

Every organization wants consistency. Very few achieve it.

I've led five retail organizations, and one lesson has stayed with me: consistency doesn't come from rules. It comes from standards.

The distinction matters because standards aren't just about defining what people should do. They're about making expectations clear, explaining why they matter, and giving managers the tools to help people meet them.

That's where the real work begins.

Where I learned it

We were growing quickly. Thirty corporate kiosks stood up in six months, from concept to completion.

Then TELUS acquired Clearnet. During the integration, I met my counterpart on the TELUS side. He had recently rolled out a store management program, and he described its impact in a sentence that stayed with me:

It brought consistency to leadership, and the results were incredible.

Until then, I'd been treating consistency primarily as an operations problem. He helped me see it differently.

It was a management problem.

Soon after, we introduced Store Management Camp — a four-month development and coaching program for store managers.

Within six months, sales had increased by 30%. Employee engagement reached 89–91% and remained there for years.

But the numbers aren't the part I find most interesting. It's how we got there.

From rules to reasons

Take name tags.

One of our standards was no business-related opening and introducing yourself.

Before talking about products, plans, or promotions, we wanted our people to start by making a personal connection.

The name tag supported that standard.

Knowing someone's name puts you at ease. Forgetting someone's name, or not knowing it in the first place, can add tension to an interaction.

The name tag removed that risk. It made the first interaction more comfortable and supported a bigger expectation: make the customer comfortable before you start talking business.

That's what makes a standard different from a rule. We didn't just define what to do. We explained why it mattered.

My job wasn't simply to tell people what the standard was. It was to make sure they understood it, could demonstrate it, and had managers who reinforced it consistently.

When people understand why a standard matters, it becomes easier to own it, reinforce it, and deliver it consistently.

Define the how

"Deliver great service" sounds good. But what does it actually mean?

It's an outcome, not an instruction. It tells a manager what to expect but doesn't give them much to work with.

So we defined the how.

• Acknowledge the customer within  seconds.

• Use a non-business related opening and introduce yourself

• Ask open-ended questions.

• Present a full solution.

These weren't just instructions for employees. They gave managers something specific to observe, coach, and reinforce.

And that changed the conversation.

Instead of telling someone to deliver better service, a manager could ask: Did you greet the customer? What questions did you ask? Did you explore the full solution?

We had moved from an abstract expectation to observable behaviour.

That also made it easier for new employees to develop capability. They didn't have to rely entirely on watching the person next to them and hoping they picked up the right habits.

We had defined what good looked like.

This is where I believe many consistency initiatives fall short. They define the desired outcome, publish it, and expect managers to translate it into daily behaviour on their own.

Then they're surprised when forty managers produce forty different results.

Why wouldn't they?

Each manager was left to define the how for themselves.

"Show me"

One of the most useful phrases we had was two words: "Show me."

Instead of asking, "Do you understand?" we asked, "Show me how you'd do it."

There's a meaningful difference.

"Do you understand?" often produces the answer we want to hear. "Show me" gives us the opportunity to see whether someone can actually apply what they've learned.

It surfaces the gap while there's still time to address it. And it changes the responsibility of the manager.

If someone can't demonstrate the behaviour, the first question shouldn't always be, "Why weren't you listening?" It should be, "Did I teach this clearly enough? Did I give you the opportunity to practise? Have I provided the coaching you need?"

That's not about lowering standards. It's about taking responsibility for helping people reach them.

What it added up to

Six months in, we had better numbers.

But what we were really building was something more important: a shorter distance between the performance of our best managers and the performance of the median manager. That, to me, is the opportunity.

The goal isn't to have a few exceptional managers carrying the performance of an organization. It's to understand what those managers do differently, define the behaviours that matter, and build a management system that helps more people consistently deliver them.

This is where leadership and management come together.

Management defines the expectations, standards, and operating disciplines.

Leadership creates the trust, clarity, and connection that make people want to meet them.

You need both.

Rules can tell people what they're required to do. They can't, on their own, create ownership, capability, or pride in the work.

When you define the how and connect it to the why, standards stop feeling like rules. They become part of how people work, lead, and deliver results together.

And that's where consistency begins.