Introducing pay bands without setting the building on fire

Every company reaches a size where ad hoc pay stops working. Introducing bands is the fix, and it is also the project most likely to blow up in your face, because it takes something that was ambiguous and makes it explicit for everyone at the same moment.

Do the analysis before you promise anything

Build the bands, map every current employee onto them, and look at the total cost of correction before a single word goes out. If you announce a levelling exercise and then discover you cannot afford the fixes, you have created a grievance queue instead of a pay structure.

Fix the below-band cases first, quietly and quickly

People paid below the band for their level get corrected before the framework is announced, not after. There is no version of this where telling someone they have been underpaid for two years and will be corrected next quarter goes well.

Say what happens to people above the band

Some people will be above their band, usually good performers hired at a competitive moment. Freezing them without explanation is how you lose them. Be direct: their pay is protected, future increases will be smaller until the band catches up, and here is what a move to the next level requires.

Managers should never be hearing about the framework at the same time as their teams. Brief them a week ahead, with the specific numbers for their own people and answers to the three questions they will be asked.

Publish the criteria, not necessarily the numbers

Full pay transparency is a separate decision with its own tradeoffs. What is not optional is publishing what each level requires. If someone cannot read what would move them up, the framework reads as a ceiling rather than a ladder.

A workable sequence

• Weeks one to three: benchmark, draft levels, map everyone, cost the corrections.
• Week four: leadership sign-off on the total, including the fixes.
• Weeks five and six: correct below-band pay individually.
• Week seven: brief managers with their own team's data.
• Week eight: publish the framework and the level criteria to everyone.