Step-by-Step Implementation Guide

Implementation Overview

Building a job and skill architecture is a structured project with clear phases. The goal: go from raw HR data to a live, integrated, version-controlled architecture in 4–8 weeks. This guide covers the full path from initial assessment to operational governance.

Phase 1: Assessment and Scoping (Week 1)

• Data audit — Export current job data from HRIS. Assess quality: how many unique titles exist? How consistent are descriptions? What grading/leveling exists?
• Scope decision — Start with one business unit, function, or country. Enterprise-wide rollouts in one pass rarely succeed. Pick the area with the highest pain (pay transparency pressure, high hiring volume, or organizational redesign in progress).
• Stakeholder alignment — Brief the executive sponsor, HR leadership, and functional heads. Define success criteria: what does "done" look like?
• Tool setup — Configure Cobrainer instance, set up HRIS integration, prepare data import templates.

Phase 2: Architecture Generation (Weeks 2–3)

• Data ingestion — Upload job catalog, org structure, existing level/grade data. Cobrainer analyzes patterns, identifies duplicates, flags inconsistencies.
• Family and cluster generation — AI groups roles into families and clusters based on skill and task similarity. HR reviews and adjusts.
• Level definition — For each family, define the level structure. Use the organization-size matrix from the Quick Start guide.
• Role profile generation — For each role × level, generate complete profiles: description, tasks, skills, proficiency levels, qualifications, equal pay criteria.

Phase 3: Review and Calibration (Weeks 3–4)

• Expert review — Functional experts review role profiles for their area. Do the tasks match reality? Are the skills right? Are proficiency levels calibrated correctly?
• Cross-functional calibration — Compare levels across families. Does a Level 4 in Engineering represent the same scope and impact as a Level 4 in Finance?
• Pay alignment — Map the architecture to existing compensation structures. Identify where current pay does not align with the new grading.
• Compliance check — Verify equal pay criteria are embedded, gender-neutrality is maintained, and the evaluation methodology is documented.

Phase 4: Integration and Go-Live (Weeks 4–6)

• HRIS integration — Push the architecture into SAP SuccessFactors, Workday, or ServiceNow. Map roles, levels, and skills to the target system's data model.
• Employee mapping — Assign every employee to a role, level, and family in the new architecture. Handle exceptions (roles that do not fit, employees in transition).
• Communication — Brief managers and employees. Explain: what changed, why, what it means for them, where to find their role description and skill profile.
• Version control activation — Enable change tracking. From go-live, every modification to the architecture is version-controlled with full diff history.

Phase 5: Governance and Continuous Improvement (Ongoing)

• Architecture owner — Assign a named person accountable for maintaining the architecture.
• Change process — Define how new roles are created, existing roles modified, and levels adjusted. All changes go through version control.
• Review cadence — Quarterly: review new/changed roles. Annually: full architecture review.
• Integration maintenance — Monitor HRIS sync, resolve mapping issues, update when the target system changes.

Change Management Essentials

• Start with why — Connect the architecture to outcomes employees care about: clear career paths, fair pay, transparent expectations.
• Involve early — Functional experts who participate in the review phase become advocates in the rollout.
• Communicate continuously — Not one launch email. Weekly updates during rollout, monthly updates during stabilization.
• Measure and share — Track adoption metrics (% employees mapped, % managers using templates, # change requests processed) and share progress.