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.
It produces the single source of truth that hiring, leveling, 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, formalized 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, its purpose, accountabilities, activities, required capabilities and working conditions, producing the profile that every downstream people process depends on: recruitment, job evaluation, leveling, pay, development, and workforce planning. Because so much is built on it, a profile that records an incumbent's habits instead of the role the strategy actually needs will spread that error through the whole system.
Key components
The parts at a glance. Click any term for the full definition, a field example, and the common failure, in the model below.
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 actually drifted.
- 02 Write accountabilities as the outcomes the role owns, not a task list. This is what makes a profile durable.
- 03 Map required capabilities to the competency framework, so profiles, hiring and development all share one language.
- 04 Validate the draft with the manager and a job-family lead, to catch inflation and overlap with neighboring 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, leveling 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 that are better described by a live skills profile than by 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 and cannot say why.
A profiling exercise separates the real accountabilities (own the fulfilment SLA, own systems reliability) from the founder's wish list of activities, maps the capabilities each part actually needs, and reveals that the role was really two jobs.
Split into an ops manager profile and a systems analyst profile, both fill within six weeks, and the scope disputes end.
Common pitfalls
- 01 Listing tasks instead of accountabilities, which produces a profile that goes stale within months
- 02 Profiling the incumbent's habits instead of the role the strategy actually needs
- 03 Letting every profile inflate its scope in the hope of a higher grade
- 04 Building profiles in isolation, so neighboring roles end up overlapping or leaving gaps
Sample deliverable
One real engagement, start to finish. Watch the numbers travel from raw input, onto the chart, into the finished artifact.
Input
- Fulfilment operations38%
- Systems debugging27%
- Reporting19%
- Vendor management16%
Process
Observed hours are coded to accountabilities, and the split exposes the real design
Time study: Operations Lead
- Findingtwo jobs hidden in one role
- SplitOps Manager plus Systems Analyst
- Both filledwithin six weeks