The core idea
The model links five job characteristics—skill variety, task identity, task significance, autonomy and feedback—to psychological states and work outcomes. Variety, identity and significance contribute to experienced meaningfulness; autonomy to responsibility; feedback to knowledge of results. Individual and contextual differences affect responses. The sketch is a compressed conceptual map, not a validated assessment instrument or a reproduction of the original scoring model.
Source and attribution [1]Using it in practice
Observe the job from end to end. Can someone see a complete piece of work, understand who benefits, make relevant decisions and learn whether the result was useful? Redesign the workflow with the people doing it. Add resources and decision rights alongside responsibility. Evaluate the effect on handoffs and workload so a richer role does not create confusion elsewhere.
An example, not a reported case
Worked example · illustrative
A payroll assistant processes isolated corrections with little feedback. The team gives them ownership of a defined monthly exception process, contact with internal customers and a review of recurring errors. They gain clearer task identity and feedback while escalation boundaries remain explicit. Success means fewer repeat errors and a manageable role, not simply more tasks assigned to the same person.
What to watch for
Enrichment is not universally welcome or sufficient. Working conditions, relationships and personal preferences also matter, and autonomy must fit genuine safety constraints.
Map the job people actually do
Observe the work and discuss which tasks provide variety, ownership, significance, discretion and feedback. Do not rely solely on the job description. A role described as autonomous may involve constant approvals, while a routine task may have a clear and valued connection to customer safety. Ask employees where the work feels fragmented or where they cannot see the result of their contribution. Use the model to identify redesign possibilities, not to assign a person's worth.
Reconnect a fragmented task
For illustration, an administrator who enters data but never sees its use might join a short review of how that data supports service decisions. A wider redesign could give them ownership of resolving a defined type of query from start to finish. Check workload, authority and training before adding responsibility. Meaningful task ownership requires access to the parts of the process needed to complete it, otherwise the employee merely becomes accountable for dependencies they cannot influence.
Design feedback into the work
Make information about results timely and useful. An error returned months later provides little opportunity to learn; a clear validation message or brief review may help sooner. Distinguish feedback from surveillance: the purpose is to improve the task, not to monitor every movement. Ask whether the employee can interpret and act on the information. A dashboard that displays a score without explanation may add pressure while contributing little to competence.
Check individual and operational fit
People differ in preferences, experience and circumstances, so offer support and avoid assuming that more complexity is always better. Pilot a redesign with volunteers where feasible and examine service quality, workload and employee experience. Consider team dependencies as well as individual jobs. The model's dimensions are useful prompts, but a single combined score should not dictate a redesign. Preserve essential safety controls while finding real opportunities for discretion and learning.
Redesign with the people doing the work
Map the actual task sequence and ask where employees can exercise judgement, see an outcome and obtain useful feedback. Test a small change, such as ownership of a complete customer request. Check workload and support so greater responsibility does not simply mean more work. Use employee experience and service evidence to assess the change rather than assuming enrichment will suit everyone.
Trace the experience created by the task design
Ask whether an employee completes a meaningful whole, sees the effect on others, uses varied skills, exercises discretion and receives information from the work itself. These questions concern the job, not merely the employee’s attitude. A fragmented process can obscure purpose and feedback even when managers give frequent encouragement. Observe the work sequence and ask which changes would improve understanding or ownership without compromising essential standards.
Evaluate an enrichment experiment with safeguards
Let a trained employee manage a customer request through to resolution, with escalation support and access to the necessary information. Compare the experience with the previous fragmented process and check errors, waiting time, workload and learning. Not everyone wants the same form of enrichment, and a broader role may require development or reward review. A stronger sense of responsibility is not beneficial if employees are held accountable for decisions they cannot control. Adjust the design using both operational and employee evidence.
Take it into your next conversation
Three useful questions.
- Can people see the purpose and result?
- Which decisions can move closer to the work?
- What support makes responsibility manageable?
Related terms
Go to the evidence
Sources & attribution
Further reading: Michael Armstrong with Stephen Taylor (2023), Armstrong’s Handbook of Human Resource Management Practice, 16th edition, chapters 19–20. Edition & reading notes ↗
[1] Hackman & Oldham (1976). Motivation through the design of work: test of a theory. ↗
The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.
Application guidance expanded on 26 September 2026. These practical suggestions and invented examples are editorial explanations; further-reading sources are not the original authors of the historical models unless expressly identified. Original overview review dates are retained.
Published 2026-09-20 · Reviewed 2026-09-25. Editorial approach