CM-301g · Module 2

Role Redefinition

4 min read

When an AI initiative changes a role substantially, 'the role will evolve' is not a statement. It is an anxiety-generating non-answer. Employees whose roles are changing need to know what the new role looks like before they encounter it, not after.

Let me be clear about what 'the role will evolve' communicates to a high-C, high-S employee whose professional identity is built on process expertise and deep knowledge: it communicates that leadership does not know, has not decided, or is not willing to tell them. Any of these conclusions produces resistance. The honest one might produce grief but it also produces trust. Trust can coexist with transition. Uncertainty about what leadership is actually planning cannot.

Role redefinition should be a deliverable, not a promise. Before the AI initiative launches for any role group, produce a written role definition that describes the post-AI version of that role: what tasks remain, what tasks change, what new capabilities are required, what the success criteria look like, and what the career path looks like in the new structure. This document is not a guarantee — circumstances change. But it demonstrates that leadership has thought through the role change with enough specificity to put it in writing. That specificity is the difference between a transition people can prepare for and a transition that feels like it is being done to them.

Do This

  • Produce a written role definition document before the AI launches for each affected role: 'Here is what the data analyst role looks like after the AI is deployed'
  • Include skill requirements in the new role definition — what does the role need that the current incumbent may not yet have, and what is the development path
  • Review the new role definition with affected employees before launch — this creates engagement and catches errors in your assumptions about what the role actually involves
  • Update the role definition as the AI implementation matures — the first definition is an estimate, not a contract

Avoid This

  • Tell employees 'the role will evolve' without specifying what evolution means — this is vagueness dressed as reassurance
  • Redefine roles after the AI launches, when employees have already formed conclusions about what their role will become based on what they observe
  • Produce a role definition document without reviewing it with employees — leadership assumptions about what the role involves are frequently wrong in informative ways