Skip to content
Log in
← Glossary

intrinsic motivation

Doing the work because it is interesting, meaningful or a source of growth in itself. It is supported by autonomy, a sense of competence and connection with others, and can be weakened by controlling rewards.

Intrinsic motivation is the drive that comes from the work itself: it is interesting, it feels meaningful, or it makes you better at something you care about. Nobody has to pay or push for it. A coordinator who rewrites a reply until it sounds right for that family, or who keeps digging into a strange video fault after the ticket could have been closed, is acting on it.

Research on work motivation keeps returning to three conditions that feed it: autonomy (some say in how and when the work is done), competence (the feeling of getting better and doing the job well) and relatedness (working with people who matter to you, for people the work helps). Remove them and interest fades; support them and people put in effort that no rule could demand.

For a lead, the practical lesson is about what not to break. Controlling rewards and orders for work people already care about can weaken intrinsic motivation, because the work starts to feel like something done for the reward or the boss. Close supervision, rigid scripts and tools forced on people without a say have the same effect. Intrinsic motivation doesn't replace fair pay or clear goals, but it is what makes good work happen when nobody is checking.

Example

Klasna's Support team gets an AI draft assistant for routine replies. Bohdan, ten years in support, ignores it. Over six months he solved 160 video-failure tickets, handed up only 2 (a solo rate of 160 / 162 = 98.77%) and saw 3 reopened (3 / 160 = 1.88%). Careful, personal replies are what he values in the job.

An order ("use the drafts in every ticket") would treat this as stubbornness. A one-to-one shows a different cause: the drafts "sound like a call centre", and Bohdan rewrites every one, so starting from scratch is faster. The lead keeps the craft and adds autonomy instead:

Move
Condition it supports
Bohdan picks where drafts help (scheduling, package questions)
autonomy
He rewrites the wording the assistant starts from
competence
His version becomes the team's template
relatedness

The same pattern shows up later in the year: from January to July Bohdan closes the fewest tickets (1,537) and spends the most hours mentoring colleagues (36 of the team's 84, or 42.86%). No bonus asked for that.

Common mistakes

  • Reading low effort as low motivation. Check first whether the person can do it and whether effort visibly pays off; "won't" is only one of three causes.
  • Paying for what people already enjoy. A controlling reward can turn a craft into a chore and lower effort once the reward stops.
  • Forcing tools and scripts without a say. Ask where a tool helps and let people shape it; autonomy is the cheapest support you have.
  • Assuming one source fits everyone. Some people care about the craft, others about learning or helping families; ask instead of guessing.
  • Treating it as a substitute for fair pay. Intrinsic motivation doesn't survive pay or workload people see as unfair.

Learn it in the course