What a team that writes its own job descriptions gets right about work
Field notes on the people, places, and systems that keep things moving.
Why this is happening
Pay is only one part of a good job. Control over pace, clarity about expectations, and a way to raise a problem matter just as much.
A good way to understand a team that writes its own job descriptions is to ask what it replaced. The comparison reveals the real constraint, not just the advertised improvement.
“Skill is a relationship before it is a certificate.”
The details that matter
The quiet parts of a workplace, the greeting, the handover, the shared kettle, are often the parts that keep it running.
The strongest version of a team that writes its own job descriptions leaves room for the person who arrives late, the one who is unsure, and the one who has done it before.
What to keep in mind
Apprenticeships work when the person teaching has time to teach. That time has to be scheduled, not assumed.
There is a difference between improving a system and replacing its memory. The second is much easier to do by accident.
The lesson of a team that writes its own job descriptions is not that everything can be fixed. It is that small, repeated attention is usually where useful change begins.