Role definition / job architecture input
Job Profiling (Job Analysis)
Job profiling systematically documents what a role actually requires — its purpose, accountabilities, activities, capabilities and conditions — producing the single source of truth that hiring, levelling, pay and development all depend on.
Get the profile wrong and every system built on it inherits the error.
- Problem
- Role definition / job architecture input
- Altitude
- Role to enterprise
- Effort to run
- Moderate
- Evidence base
- Strong
Theory & origin
Job analysis is the oldest discipline in HR, formalised in the scientific-management era and later codified in instruments like McCormick’s Position Analysis Questionnaire (1972) and the US O*NET database. It documents the role as designed — purpose, accountabilities, activities, required capabilities and conditions of work — producing the profile every downstream people process inherits: recruitment, job evaluation, levelling, pay, development and workforce planning. Because so much is built on it, a profile that records the incumbent’s habits rather than the role the strategy needs propagates that error through the whole system.
Explore the model
How a consultant runs it
- 01 Interview incumbents and managers and observe the work to separate the role as designed from the role as it has drifted.
- 02 Write accountabilities as the outcomes the role owns, not a task list — this is what makes the profile durable.
- 03 Map required capabilities to the competency framework so profiles, hiring and development share one language.
- 04 Validate the draft with the manager and a job-family lead to catch inflation and overlap with neighbouring roles.
- 05 Version and govern profiles centrally; they feed job evaluation, workforce planning and recruitment, so drift is expensive.
When to use
- 01 Standing up hiring, levelling or pay for a new or redesigned role
- 02 Before job evaluation or building job architecture — profiles are the input those depend on
- 03 Resolving role overlap, scope creep or accountability disputes between adjacent roles
When not to use
- 01 As a static document filed and forgotten — a profile drifts as the role changes
- 02 For fast-changing or project roles better described by a live skills profile than fixed accountabilities
- 03 When the real need is org design, not documenting the current role
Worked example
A scale-up hiring its first operations lead keeps rejecting candidates without knowing why. A profiling exercise separates the accountabilities (own fulfilment SLA, own systems reliability) from the founder’s wish-list of activities, maps the capabilities each actually needs, and reveals the role was two jobs. Split into an ops manager profile and a systems analyst profile, both fill in six weeks and the scope disputes end.
Common pitfalls
- 01 Listing tasks instead of accountabilities, producing a profile that dates within months
- 02 Profiling the incumbent's habits rather than the role the strategy needs
- 03 Letting every profile inflate scope in the hope of a higher grade
- 04 Building profiles in isolation so neighbouring roles overlap and leave gaps
Sample deliverables
What you actually hand over. Select an artifact to preview a sample.
Role profile
Sample- Purposeowns payroll accuracy for 2,000 staff
- Accountabilities6 outcomes
- Capabilitiesmapped to competency framework
- Metricsaccuracy %, on-time run rate