Can't, won't, or doesn't believe it pays off

When work isn't happening, a new lead reaches for a treatment: a reminder, a pep talk, a prize. Each one fixes only one kind of cause, so start with a motivation diagnosis: why isn't this happening for this person?

Three questions cover almost every case:

• Can they? Skill, tools, time and a clear picture of what good work looks like.
• Do they want to? Whether the work, as it is set up, feels worth doing and fair.
• Do they believe it pays off? Whether effort leads to a result, the result gets noticed, and what follows matters to them.

At Klasna in April, three coordinators skip three different things. The same prize for all three would miss at least two causes. Treat each person as a separate case, collect evidence from conversation and recent work, and only then choose the fix. A diagnosis is a hypothesis: you test it by changing one thing and watching what happens.

The first cause to rule out is can't: the person lacks a skill, a tool, the time, or a clear picture of what good work looks like. It's the most common cause with new people and new tasks, and the cheapest to fix.

The evidence is usually in the questions people ask. Dmytro, a seasonal coordinator, leaves refund disputes in his queue, and he has asked Olha twice where the refund policy ends. He wants to handle them; he doesn't know where the line is. Nobody walked him through the exceptions.

The fix matches the cause: walk through the exceptions together, give him a short checklist, and review his first few disputes side by side. A pep talk, a prize or a warning would treat a problem he doesn't have.

Watch one trap: explaining a gap by who someone is ("seasonal staff care less") is a prejudice, not a diagnosis. Judge the situation, not the contract or the person's background.

Won't means the person can do the work but the work, as it's set up, clashes with what they value or feels unfair. It's often a respectable reason, and you only find it by asking.

Diagnostic questions are open and tied to real, recent work: "Walk me through the last ticket where you opened a draft. What happened next?", "In which tickets would a draft actually save you time?", "What would a draft need to sound like before you'd send it?" They give you facts and the person's own reasons.

Two kinds of question spoil the diagnosis. Pressure dressed as a question ("You know everyone else uses them, right?") tells the person the answer you want. A label dressed as a question ("Or are you just not a fan of change?") judges before you've listened.

Bohdan knows the AI draft tool and has time for it. In the one-to-one he explains that the drafts sound like a call centre while families write to him by name. Now you know the cause, and it isn't stubbornness.

People keep putting effort into something when they believe it pays off, and that belief has three links. Will my effort work? Does trying lead to a result? Will anyone notice? Does the result reach someone who matters? Is what follows worth it to me? Thanks, a smoother day, a fairer share, a skill, money: whatever this person values.

One broken link is enough to stop the effort, even when the other two are strong. That's why "doesn't believe it pays off" is a separate cause from "can't" and "won't": the person can do the work and doesn't object to it, but experience has taught them that it changes nothing.

Taras can write a three-line hand-up note and isn't against notes. But in the March rush noted hand-ups waited hours, just like the ones without a note. Effort, no visible result. Find the link that broke and repair the chain, not the person.

When the cause is "doesn't believe it pays off", training and reminders miss: the person can do the work and isn't refusing on principle. The fix is to repair the broken link so that effort visibly leads somewhere.

Taras skips the hand-up note because "nobody reads them anyway", and in March that was true: noted hand-ups waited as long as the rest. So change what happens after a note. Answer noted hand-ups first, within two hours. After a week, share how much faster they were solved, so the whole team sees the result. Olha adds the third link: thank him when a note was good, for what it saved, not for writing it.

Avoid two tempting moves. A public reminder in the team chat adds pressure without changing the result. Counting notes for a review rewards writing notes, not writing useful ones: a metric on the effort, while the problem was the missing result.

Intrinsic motivation is effort that comes from the work itself: it's interesting, it's done well, it helps someone. Extrinsic motivation comes from outside the work: a bonus, a ranking, a check, a deadline set by someone else.

Both are real, and they behave differently. Extrinsic rewards work best for simple, countable tasks, and they pull attention towards exactly what they count. On work that needs judgement, a reward or an order can push intrinsic motivation aside: the person starts doing what is checked instead of what is good.

Bohdan ignores the AI drafts because careful, personal replies matter to him. That's intrinsic motivation, and it's an asset. An order to use the drafts would cost you that care. Involve him instead: ask where a draft could save him time without the call-centre tone, and let him rewrite the wording the assistant starts from.

Money is the most tempting fix because it's fast and looks fair. Iryna adds an April bonus: UAH 20 for every ticket a coordinator closes above 60 a week. It may lift the count. It fixes none of the three diagnosed causes.

A bonus doesn't teach Dmytro the refund exceptions (can't). It doesn't make generic drafts feel right to Bohdan (won't). It doesn't make anyone read Taras's notes (the broken link). What a bonus adds is one more reason to do what it counts, and it pulls attention towards that number and away from everything it doesn't count, such as careful replies or hard tickets.

Pay still matters: people need to feel it's fair, and an unfair system turns into "won't" quickly. But treat a bonus as a tool for simple, countable work, not as a cure for motivation. What a one-number bonus does to behavior is the next lesson's subject, and module 4's case looks at the data.

You can usually tell the three causes apart by listening to how people describe the problem. "I'm not sure where the line is" points to can't. "This makes the work worse" points to won't. "Nothing changes anyway" points to a broken link in "does it pay off?".

Fairness hides inside "won't". When someone's effort goes unseen, or the credit goes to someone else, people quietly hold effort back from a game they think is rigged. The next-but-one lesson takes fairness on directly.

In a remote team, diagnose in conversation, not from dashboards or online status: a green dot tells you nothing about why. And know where your job ends. If low drive comes with exhaustion, poor sleep or trouble at home, it isn't a motivation puzzle; suggest professional support and ease the load.

How it fits together: diagnose first, match the fix to the cause, then check whether it worked. Next, Goals people accept shows how to set goals people commit to, and what a one-number target like Iryna's bonus does to behavior.