Job characteristics model — Organizational Development

Richard Hackman and Greg Oldham's job characteristics model (1975) specifies what makes work motivating, and it is one of the best-supported models in organizational psychology. Its practical strength: it targets the design of the work itself, which is more durable than motivating the person.

Evidence: Strong. Meta-analytically supported across decades and many samples: the five characteristics relate reliably to satisfaction, motivation, and performance, and the mediating psychological states have held up reasonably well. Two caveats are real. Most measurement is self-report, so perception and objective job design are entangled. And growth need strength as a moderator has produced inconsistent results, so do not assume enrichment helps everyone equally — ask.

Use when: engagement is poor and the causes are not pay, safety, or management behavior; when designing roles or team boundaries; when automation is changing what a job contains.

Do not use when: the constraint is workload volume rather than work design.

The five core characteristics

Skill variety — the degree to which the job requires different activities and talents.
Task identity — the degree to which the job requires completing a whole, identifiable piece of work with a visible outcome.
Task significance — the degree to which the job substantially affects other people's lives or work.
Autonomy — the degree of freedom in scheduling and determining procedures.
Feedback from the job itself — the degree to which doing the work provides direct information about performance. Note: from the work, not from a manager. This is the most commonly missed characteristic.

The three critical psychological states

Variety, identity, and significance → experienced meaningfulness of work.
Autonomy → experienced responsibility for outcomes.
Feedback → knowledge of actual results.

All three states must be present for high internal motivation. This is why autonomy alone does not fix a job that is meaningless, and why meaningful work without feedback leaves people unable to improve.

Motivating potential score

MPS = ((Skill variety + Task identity + Task significance) / 3)
      × Autonomy
      × Feedback

The multiplication is the point: autonomy or feedback near zero collapses the score regardless of the other three. A meaningful job with no autonomy and no feedback is not motivating, however important it is.

Moderator: growth need strength

The effects are stronger for people with high growth need strength — those who want development and challenge. Enriching the job of someone who does not want enrichment can increase stress rather than motivation. Ask.

Implementing principles

Hackman and Oldham's five implementing concepts:

Combine tasks — reverse fragmentation; restore whole pieces of work.
Form natural work units — give a person or team ownership of a coherent domain, client group, or product.
Establish client relationships — connect the worker directly to the person they serve. Powerful for both significance and feedback.
Vertical loading — give planning and control responsibilities that were previously the manager's.
Open feedback channels — make results visible directly from the work.

Examples by audience

Health care: task identity is damaged when care is fragmented across handoffs — no one clinician sees the patient's whole journey or outcome. Named-nurse and continuity-of-care models are direct applications, as is simply telling a team what happened to the patients they treated. Feedback from the work is frequently absent in acute settings, and its absence is demoralizing in a way staff struggle to articulate.
Software: "you build it, you run it" raises task identity, autonomy, and feedback simultaneously. Conversely, a team that only writes code to someone else's specification, hands it to QA, and never sees production has low identity, low autonomy, and no feedback from the work — MPS near zero, whatever the salary. Fast pipelines and observability are feedback mechanisms, not just engineering conveniences. See team-topologies.
Executive: when automating or outsourcing, examine what the remaining job contains. Removing the interesting fragments and leaving exception handling destroys skill variety and task identity, and the resulting attrition is usually attributed to something else.

Limitations

Mostly self-report measures, so perception and job design are entangled.
Weaker for jobs with genuinely little discretion.
Says nothing about workload, pay, or interpersonal conditions.
Growth need strength as a moderator has inconsistent support.