How to assign work to the right person

Assigning work sounds like the simplest thing in the world. In practice it's where most small teams lose jobs — because "assigning" often means mentioning something to someone, and mentioning isn't assigning.

Why assignment fails

Three common versions, all recognisable:

The group ask. "Can someone sort the Hartley quote?" Everyone hears it. Nobody owns it. It doesn't happen.

The corridor handover. You tell someone as they're walking to a meeting. They meant to write it down. They didn't.

The assumed handover. You forward an email with no message. They think it's for information. You think it's a job. Neither of you finds out for a week.

In each case the work was communicated but never owned. That's the gap.

Picking the right person

For most small teams, the honest answer is that "the right person" is decided by three things, in this order:

1. Who can actually do it? Skills and access. If they can't finish it without three other people, they're the wrong owner — or the job needs splitting.
2. Who already holds the context? Whoever spoke to that customer, quoted that job, or fixed it last time. Context is expensive to transfer; use what already exists.
3. Who has the capacity? The most capable person is usually the most loaded. Assigning everything to your best person is a bottleneck in disguise.

If two people fit equally, pick one anyway. A merely-adequate owner beats a perfect ambiguity.

What a proper handover contains

A task that lands with someone should carry enough that they can start without coming back to you. That's four things:

• What's actually needed — the outcome, not just a subject line. "Quote Ridgeway for the oak kitchen" beats "Ridgeway".
• By when — a real date.
• The context — the email, the note, the call summary, the customer's history. Attached, not "it's in my inbox somewhere".
• What done looks like — sent? signed? paid? Ambiguity here is where jobs stall at 90%.

If it takes you longer to write that than to do the job yourself, do the job yourself. Otherwise, write it properly — you pay the cost once, versus three interruptions later.

Make it visible, not verbal

The single highest-value change: assign work in the shared list, not in conversation.

Conversation is fine for context, but the assignment itself needs to exist somewhere both of you can see tomorrow. This isn't about distrust. It's that human memory is a terrible database and everyone's is equally bad.

The practical rule: if it isn't on the list with their name on it, it hasn't been assigned.

Let people hand it back

Ownership only works if it can be declined. If the person you assigned to can't take it — wrong skills, no capacity, not actually their job — they need an easy, blame-free way to reassign or flag it.

Teams where handing work back is awkward don't get fewer misassignments. They get silently accepted tasks that quietly don't happen.

Following up without micromanaging

The difference between managing and micromanaging is mostly about what you check.

• Micromanaging: asking how it's going, repeatedly, at random.
• Managing: having dates and statuses that make progress visible, and only intervening when something is overdue or blocked.

If your list shows what's due and what's stuck, you don't need to ask — which means the times you do ask carry actual signal.

The one rule worth adopting

Nothing goes on the list without a name and a date.

It sounds bureaucratic. In practice it takes about five seconds per task and it eliminates the single largest category of lost work: the job that everyone saw and nobody owned.