We struggle to get our staff to follow our documented processes consistently without constant nagging. How can we use identity-driven language in our standard operating procedures to shift their behavior from mere task compliance to personal ownership?

Question

Tyler Smith · Accepted Answer

When staff ignore documented processes, it is usually because standard operating procedures are written as dry, mechanical checklists. This makes compliance feel like a chore. To change this behavior, we must apply Jonah Berger's concept of identity-driven language to how we document and discuss our core processes.

Instead of writing a manual that tells people what they have to do, we write it to reflect who they are when they are executing at their best. We change verbs into nouns. For example, instead of writing instructions for how to handle customer complaints, we frame the process around being a professional problem solver. We shift the language from "you must follow these steps to resolve an issue" to "as a client experience defender, this is how we protect our relationships."

This subtle linguistic shift turns a simple task into an opportunity for your employees to claim a positive, professional identity. When people view themselves through the lens of a valued role rather than just a checklist follower, their natural pride drives compliance. This reduces the need for micro-management, increases execution consistency, and builds a culture where following the process is a natural expression of who your people are.