A job description is written once, usually before the person who’ll do the job even exists. Then that person shows up, and the actual work starts drifting away from the paper it was defined on – a little more mentoring here, a little less spreadsheet work there, a Slack channel they started that somehow became load-bearing for the whole team. Most managers either don’t notice this or treat it as scope creep to be corrected.
There’s a name for it, and it’s not a problem to fix. It’s called job crafting, and organizations that understand it tend to get more engaged, more resilient employees out of the same roles.
What job crafting actually means
Job crafting was named by researchers Amy Wrzesniewski and Jane Dutton in a 2001 paper in the Academy of Management Review. Their definition: employees making physical and cognitive changes to the task or relational boundaries of their work. In plainer terms – people adjusting what they do, who they do it with, and how they think about why it matters, all without waiting for a formal role change.
This is different from job design, where a company builds a role from the top down. Job crafting happens from the bottom up. The org chart says one thing; the lived experience of the job is shaped, in small and constant ways, by the person doing it.
The three forms of job crafting
Wrzesniewski and Dutton broke it into three categories, and it’s worth knowing all three because most conversations about “employee autonomy” only ever touch the first one.
Task crafting is changing the number, scope, or type of tasks someone does. A finance analyst who starts building dashboards nobody asked for, because they’re good at it and it saves the team time, is task crafting.
Relational crafting is changing who you interact with at work, or how. An engineer who starts sitting in on customer calls, even though it’s not in their job description, is relationally crafting – they’re widening who they connect with because it makes the work feel less abstract.
Cognitive crafting doesn’t change any actions at all. It changes how someone frames the meaning of what they’re already doing. A well-known example from Wrzesniewski’s research involved hospital cleaning staff: some saw the job strictly as cleaning rooms, while others saw themselves as part of the patient’s healing environment, actively noticing what patients needed and adjusting their pace and presence around that. Same job, same pay, same tasks – completely different relationship to the work.
Why this matters right now
The timing isn’t incidental. According to Gallup’s most recent State of the Global Workplace report, global employee engagement fell to 20% in 2025 – its lowest point since 2020. That’s a lot of people showing up and doing the minimum required, not because the work is beneath them, but because nobody’s ever asked what would make it feel like theirs.
Job crafting doesn’t fix compensation problems or bad management. It’s not a substitute for either. But it does address something engagement surveys often miss: people don’t disengage only because a job is objectively bad. They disengage because a job feels imposed on them rather than shaped by them. Job crafting gives people some authorship over their own day.
This connects to a distinction worth sitting with – the difference between workplace culture and employee engagement. Culture is the environment a company builds. Engagement is how connected an individual feels within it. Job crafting operates in that gap: it’s one of the few engagement levers an employee can pull on their own, without waiting for HR to redesign the whole system.
What it looks like in practice
It rarely looks dramatic. A support rep who starts writing internal FAQ docs because she’s tired of answering the same question five times a day is task crafting her role into something closer to knowledge management. A junior HR generalist who starts scheduling informal one-on-ones with new hires, beyond what onboarding requires, is relationally crafting toward something closer to an employee experience role – sometimes long before the title catches up.
Neither of these people asked permission first. They noticed a gap, had enough latitude to fill it, and the organization was smart enough not to stop them.
That last part is the one companies get wrong most often. Employees crafting their roles need room to experiment, which means managers need to resist the instinct to redirect every deviation back to the original job description. Some structured space helps here – simple engagement practices like regular one-on-ones or peer recognition create the kind of visibility where crafting behavior gets noticed and encouraged instead of quietly shut down.
How managers can support it without losing the plot
Job crafting works best with a light hand, not an initiative. A few things actually help:
- Ask what people would change if they could: Most employees have already thought about this. They just haven’t been asked, or they assume the answer is no.
- Notice drift before correcting it: If someone’s actual work has quietly shifted from their job description, that’s information, not a compliance issue. Find out why before pulling it back in line.
- Protect some unstructured time: Crafting needs slack in the schedule. A calendar booked wall to wall leaves no room for anyone to build something that wasn’t assigned.
- Separate crafting from performance reviews, at least at first: If every deviation from the job description has to be justified in a review cycle, people will stop experimenting. Let it happen informally before it becomes a KPI.
Harvard Business Review’s research on this, published by Dutton and Wrzesniewski in “What Job Crafting Looks Like”, makes a similar point: the goal isn’t to hand employees a blank slate, but to give them enough room within existing structures to make the role fit who they are.
Where job crafting tends to go wrong
It’s not automatically good. A few failure modes are worth watching for:
Crafting can drift into scope creep that burns someone out, especially if a manager quietly lets an employee absorb extra work without adjusting title, pay, or recognition. It can also create quiet inequity – the confident, well-networked employee crafts their way into more interesting work, while a quieter colleague doing equally good work never gets the same latitude.
And sometimes crafting is a symptom, not a solution. An employee constantly reshaping their role because the base job is a mismatch for their skills isn’t a job-crafting success story. That’s a hiring or role-design problem wearing a job-crafting costume.
The bottom line
Nobody experiences a job exactly as it’s written down. The real question is whether an organization notices that gap and works with it, or spends energy forcing people back inside lines that were drawn before anyone knew what the work would actually require. Job crafting isn’t a program you launch. It’s a permission you give – and, more often than people expect, employees were already halfway there.
