Career Plateau

Both are survivable if named. Neither survives being managed by vagueness, and vagueness is the usual approach: the employee is told they are valued and to be patient, twice, and then resigns with an offer that has a title on it.

The specific Indian aggravation is title inflation elsewhere. When the market awards a manager title at a point in a career where your structure does not, your grade is competing against a word, and the employee's family and peers use the word rather than the grade.

• Time in grade, by grade and by function. A group whose median time in grade is drifting upwards is plateauing, and it will show attrition six to twelve months later.
• Promotion rate by function. Where one function promotes at three times the rate of another, the second is not underperforming; it is shaped differently, and its people can see that.
• Internal move rate. Low lateral movement means the only route upward is out, and it usually reflects managers blocking transfers rather than employees not wanting them.
• Span and layer analysis. A layer with few positions and long tenure is a queue, and the length of the queue is knowable.
• Exit reasons clustered at a particular grade. The grade where people leave is the grade where the structure narrows.
• Pay compression against market at the top of a band. An employee at the maximum of their range with no promotion available has neither a raise nor a route, which is the sharpest form of plateau.

The genuine options are limited, and they work better when the situation has been stated plainly.

• Scope. More responsibility in the same role, with a visible remit change, is the most available response and needs the pay structure to allow movement within a band.
• Specialist tracks. A senior individual contributor route with real seniority and real pay is the standard answer for technical populations, and it fails wherever it is created as a consolation with no authority attached.
• Lateral moves. A sideways move that adds a new function is a genuine career step. It requires managers to release people, which requires the organisation to stop treating a transfer as a loss.
• Project leadership. Time-bound leadership of something cross-functional gives the experience the next role needs and tests readiness at the same time.
• External visibility. Representing the organisation, mentoring, or teaching provides recognition that is not a promotion, and it is undervalued.
• Honest timing. Where a role genuinely will open in eighteen months, saying so, with what has to be true for the person to be considered, is better than either silence or an implied promise.

What does not work is the title change without a change in work or pay. It buys about one appraisal cycle, and it devalues the title for everyone who holds it legitimately.

• Have it before the employee raises it. Once they have asked, any answer sounds like a reaction.
• Say which kind of plateau it is. Employees generally take a structural answer better than a vague one, and much better than discovering later that they were never a candidate.
• Be specific about capability where that is the issue: what is missing, what would demonstrate it, and by when it would be reassessed. Vague development advice is heard as a refusal.
• Do not promise what the structure cannot deliver. A promise recorded in an appraisal document and unfulfilled becomes a grievance and, sometimes, evidence.
• Accept that some people will leave, and that a well-handled departure produces a rehire candidate and a referral source rather than a bad review.
• Where the plateau is organisation-wide in a function, treat it as a design problem for that function rather than as a series of individual conversations.