What is this meeting about?
Career Architecture is becoming increasingly important for organizations preparing for the EU Pay Transparency Directive.
Whether you are maintaining an existing framework, revamping it, or implementing Career Architecture for the first time, the underlying structure needs to support consistent and explainable decisions on jobs, levels, careers and pay.
In this session, Monique Driessen and Charlotte Wheeler from WTW will take us through the fundamentals of Career Architecture and discuss what organizations should have in place to create a robust foundation for EU Pay Transparency.
Presentation:
Stream:
Key take-aways:
Career architecture is evolving beyond traditional job evaluation and grading into business infrastructure connecting jobs, levels, skills, careers, reward, and workforce planning. The discussion highlighted that organizations gain more value when job architecture, levelling, and skills architecture operate as an integrated framework rather than as separate HR structures.
The conversation also exposed several practical tensions: simplicity versus precision, global architecture versus collective labour arrangements, and ambitious skills strategies versus the challenge of measuring skills objectively. The strongest interest in continued exploration centered on skills architecture and rewarding for skills, with links to AI, reskilling, workforce planning, and career mobility.
- Start with the business problem, not the architecture. Define the outcomes career architecture is intended to influence, such as career visibility, internal mobility, employee retention, pay fairness, skills visibility, workforce planning, recruitment effectiveness, or cost optimization. Establishing baseline measures before implementation also creates a more credible basis for evaluating whether the architecture is delivering value.
- Connect jobs, levels, and skills. Job architecture, levelling, and skills architecture create greater value when designed as an integrated framework. In particular, organizations should clarify what skills mean, which capabilities matter, how they connect to work and career opportunities, and how proficiency will be assessed before making major investments in detailed skills taxonomies.
- Design for employees and managers, not only HR specialists. Technical quality alone is insufficient. Employees need to understand where their roles sit, what differentiates levels, and which opportunities and capabilities support progression. Managers need to be able to explain these distinctions. Employee experience should therefore be a design criterion for career architecture, rather than merely a communication activity following implementation.
- Build for change rather than trying to predict every future job. AI and other changes can alter the capabilities required within existing roles as well as create new work. Architecture therefore needs enough flexibility to incorporate evolving skills, roles, and career pathways without requiring continual redesign. This also strengthens the connection between career architecture, reskilling, and strategic workforce planning.
- Treat implementation as an ongoing capability. Leadership sponsorship, governance, HR technology, manager understanding, employee visibility, measurement, and maintenance all matter. The meeting’s financial-services example demonstrated the value of measuring outcomes, gathering employee feedback after implementation, and revising parts of the architecture that do not work sufficiently well in practice.
Caveat: These Key Takeaways are derived from the designated meeting content and should be reviewed before publication. AI generated by Copilot from designated meeting content only | Rumbold