Our team treats technology adoption as an extra chore rather than a core part of their daily routine. How do we use identity-based language during our session days to get our people to identify as AI-powered operators instead of just tech users?

Question

Tyler Smith · Accepted Answer

To drive deep operational change, you must shift your team's vocabulary from actions to identities. When you ask people to use AI tools, they view it as an extra administrative task on top of their already overflowing workload. It becomes a chore that they easily deprioritize when daily fires break out.

During our session days, we actively rewrite this narrative. Instead of setting Rocks that focus on the verb of using technology, we define seats on the Accountability Chart that reflect the noun of who they are. We transition our language from asking people to build automated workflows to expecting them to be automated systems builders.

We stop saying we need to test AI tools and start saying we are an AI-first organization. This shift in language, moving from can't to don't and from doing to being, creates a psychological shift. When a team member views themselves as an AI-powered operator, leveraging automation is no longer an optional task. It is a core part of their professional identity.

We weave this identity-based language directly into our GWC evaluations. We assess whether our leaders truly get, want, and have the capacity to operate in a modern, automated seat. By making technology adoption a matter of identity rather than a task list, we eliminate the passive resistance that often stalls digital transformation. Your team stops viewing automation as a threat or an extra chore and starts embracing it as their primary way of operating.