---
id: KB-CR-015
url: https://app.codecontract.io/help/use-cases-by-role/teaching-this-to-someone-in-twenty-minutes
idioma: en
categoria: casos-por-rol
subcategoria: operaciones
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-PS-005, KB-CR-011]
citadoPor: [KB-CR-017]
---

# Teaching this to someone in twenty minutes

_What to cover, what to skip, and in what order, so they start using it today._

**Responde a:** training a colleague on the platform · how to explain the system to someone new · short training session · getting the team to learn it

Long training does not work: it is forgotten before it is needed. What works is twenty minutes on that person's real work, and having them leave having actually done one thing.

## The twenty-minute script

1. **Five minutes: where their own material is** — Their inbox, their files, their outstanding items. Nothing about the general structure.
2. **Five minutes: searching for something they need often** — Let them search, in their own words. It is what sticks most.
3. **Five minutes: doing one thing end to end** — Uploading one of their documents, sending a request, answering something.
4. **And five minutes: what to do when something is off** — Who to ask and where to look. It prevents silent abandonment.

> [!IMPORTANT]
> The fourth block is most often skipped and determines whether the person comes back. Someone who gets stuck and does not know who to ask stops using the tool without telling anyone, and that surfaces weeks later.

## What NOT to cover on day one

| Not this | Why |
| --- | --- |
| The full folder and project structure | They will not use it today and it eats the session |
| Configuration options | They are not theirs |
| Everything the platform can do | It makes it feel complicated |
| The rare cases | They will come up, and then get solved |

> [!WARNING]
> And do not do it on someone else's screen. Have them sit at their own session with their real files: half of what is learned is where their own things are, and that does not transfer by watching.

## The following week

**En corto**

- A ten-minute refresher after four or five days.
- Based on their questions, not your script.
- And looking at what they actually did, which is usually less than they say.

That short refresher pays off more than doubling the initial session: it lands exactly when the person has hit their own questions.

> [!NOTE]
> If someone needs to learn much more than this to do their job, the process is probably built more elaborately than necessary. Training complexity is a good indicator of process complexity.

**What about people who resist?**

Start with what annoys them, not with what interests you.

**Is a manual needed?**

One page with four things and who to ask. A long manual goes unread.

**And for someone who only signs?**

Two minutes: it arrives, they open it, they sign. Nothing else needed.

## Ejemplos

**A company runs a two-hour session for ten people and nobody uses it afterwards.**

- Switches to twenty minutes each on their real work
- Adds a ten-minute refresher after five days

→ Eight of the ten are using it within a month, with no further training.

**The whole system is explained in twenty minutes.**

- Shows one complete process end to end

→ Something usable is learned.

**It is taught with made-up data.**

- Uses a real case from their work

→ They recognise what they see.

**It is explained and nobody touches anything.**

- Lets the person do it

→ Learning happens by doing.

**It is taught and a week later they are not using it.**

- Assigns them their own case that day

→ Usage starts with the training.

**The same explanation is repeated for every person.**

- Documents the process

→ The second person learns on their own.