Most support teams have a certification programme. Very few tie it directly to salary bands. This is the framework we built at Tyco/JCI EMEA — specific score thresholds, defined job codes, and a 10% base salary increase that made advancement worth pursuing.
By 2014, the Tyco/JCI EMEA technical support operation had a tiered structure on paper and a certification programme in development. What it didn’t have was a compelling reason for agents to pursue advancement. If passing a test and reaching a higher tier didn’t change your title, your pay, or your day-to-day responsibilities in a visible way, the framework was aspirational rather than motivating.
The restructuring project — applied across the EMEA Video, Access, North and South Intrusion verticals — was designed to close that gap. The goal was a system where advancement was clearly defined, objectively assessed, and financially rewarded. Not a framework where promotion felt like a management favour. One where an agent could see exactly what was required, demonstrate it, and receive a defined outcome.
The framework defined four progression levels, each with specific knowledge requirements, defined responsibilities, and advancement criteria. Critically, each level had a corresponding Tyco job code and salary band — so advancement wasn’t subject to budget availability or manager discretion. It was a defined outcome of meeting the criteria.
One of the most impactful design decisions was requiring three assessment formats rather than one. A written test measures recall. An oral assessment — conducted by L2 team leads — measures reasoning and the ability to explain a diagnosis under pressure. A practical assessment, using real lab equipment, measures whether an agent can actually configure and troubleshoot the system, not just describe how they would.
The combination was more resource-intensive than a simple written test and significantly harder to game. An agent who had memorised written answers but lacked genuine product depth would struggle in the oral and practical components. Assessments were administered by senior regional technical team members, which had the secondary benefit of making those senior engineers part of the career development process.
Tying a 10% salary increase to a certification outcome means committing to that increase before the assessment cycle runs. We worked through this with the EMEA HR team to ensure advancement from L1 Junior to L1 Senior was reflected in a formal job code change — not just a title change.
A title change with no compensation or job code movement is visible to employees as cosmetic. A formal grade change — with a different job code in the HR system, a different salary band, and a documented basis for it — is a real career progression. The framework only worked as a retention and motivation tool because the advancement was materially real, not just symbolically acknowledged.