Job Crafting
Job Crafting
What is job crafting?
- A bottom-up approach where employees redesign their own work
- Three types of job crafting: task, relational, and cognitive
- An intervention that boosts engagement and helps prevent quiet quitting
What job crafting really changes is not the wording of the job description but who gets to touch the boundaries of the work. In most organizations, the org chart set the scope of work and individuals simply accepted it. Once job crafting takes hold, the questions in one-on-ones change. "This work doesn't suit me, so please move me to another team" becomes "Within this job, what should I do more of and what less?", and leaders can adjust work allocation instead of losing the person.
More useful in practice than the three types of task, relationship, and cognitive crafting is the split between expansion and avoidance. Expansion adds tasks worth learning from and collaborative relationships. Avoidance trims demands that feel burdensome. Avoidance is also needed just before burnout, but if the whole team leans only toward avoidance, the leftover work piles up on a few people. That is why, in practice, it works well to set the share of working time people can adjust at their own discretion at about 10–20% and to renegotiate it with the leader each quarter. It is easy to confuse with empowerment or job rotation, but those are top-down, with the organization handing down authority and positions, whereas job crafting is bottom-up, with individuals raising their hands first.
The most common mistake is using it as an order to "go make your own work." If leaders don't spell out how far people can adjust and which performance metrics must hold, team members either play it safe and change nothing, or drop their core work and chase only the visible side projects. Tying it directly to performance reviews makes it riskier still. Crafting plans turn into self-promotion documents, and the people who quietly prop up others' work lose out. Another trap: if it's used to push unpopular tasks onto someone with "you craft it and take it," the program won't last six months. Unless you track at the team level where the dropped tasks went, job crafting becomes just a polished name for offloading work.
Sangmi LeeSpecialist instructor in customer service, leadership, and communication
John KimInstructor John Kim, author of B2B Marketing Design and CEO of Nanum ConsultingThe concept was formulated in a 2001 paper by Amy Wrzesniewski and Jane Dutton, and spread alongside research in positive psychology and job design.
Let’s look at a hypothetical case: the customer support team at Company A, a B2B software company with 320 employees. In one year, 4 of the team’s 12 members left, pushing voluntary turnover up to 33%, and exit interviews kept returning to the line “I feel like a ticket-processing machine.” Instead of requesting more headcount, the team lead decided to first try a 3-month job crafting experiment.
- In week one, Team Lead Park broke each team member's weekly work into four buckets (ticket handling, manual writing, customer onboarding, internal QA) and timed them. Two people were spending 34 hours a week on ticket handling alone.
- When a team member said in the week-2 one-on-one, "There's nothing I can cut back," the team lead set a boundary: "You can change up to 20% of your working hours however you like, but let's hold the customer satisfaction score at 4.2."
- Manager Kim, a third-year employee who enjoyed writing documentation, cut 6 hours a week of direct support and used that time to turn the top 20 recurring inquiries into self-service documents customers could look up themselves.
- A senior team member who enjoyed talking with customers volunteered to take on new-customer onboarding calls, and the team lead agreed on the condition that they take one extra night-duty rotation per month.
- Three months later, repeat inquiries fell from 41% to 27% of all tickets. Daily handling per person dropped from 38 to 31, yet satisfaction rose to 4.4, the team engagement survey score climbed from 58 to 71, and no one else left the team.