---
id: KB-PS-014
url: https://app.codecontract.io/help/getting-started/which-process-to-start-with
idioma: en
categoria: primeros-pasos
subcategoria: empezar
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-PS-004, KB-CF-013]
citadoPor: [KB-PS-018, KB-PS-020]
---

# Which process to start with?

_The highest-yield one is not the biggest: it is the one that makes you chase someone outside._

**Responde a:** where do i start rolling this out · which process to digitise first · choosing the first use case · start with the easiest or the most useful

The choice of first process decides whether the project moves by itself or has to be pushed every week. And almost everyone chooses badly for the same reason: they start with something internal, which is easy to change, when the return lies in what goes outward.

## The three usual candidates

| Candidate | Return | Difficulty | Verdict |
| --- | --- | --- | --- |
| Supplier or contractor documentation | High | Medium | The best first, nearly always |
| Staff signatures | High | Low | A good first if there is turnover |
| The historical archive | Low at first | High | Never first |

> [!IMPORTANT]
> The first wins because it combines three things: someone outside is involved, documents expire, and it repeats. Those three together are exactly where a tool like this returns time from week one.

## How to scope it to fit a month

1. **One supplier type, not all of them** — The hauliers, or one site's subcontractors. Ten or fifteen, not two hundred.
2. **The document list you already request** — Do not take the chance to redesign what is asked for: that is another project.
3. **With the people who already do it** — The whole company does not need to join to test one process.
4. **And a date to decide** — Thirty days. Without a date the trial stretches until nobody remembers what was being tested.

> [!WARNING]
> The second sinks the most projects. Setting up the process brings the temptation to review which documents are requested, who approves and against what criteria — and suddenly the project depends on three decisions that are not yours.

## Signs you chose well

**En corto**

- Within two weeks someone outside has supplied without being called.
- Someone on the team asks whether another case can be added.
- And "how's X going?" is answered by looking, not asking.

If none of the three has happened after a month, you probably chose a process that was too internal or too infrequent. That is not failure: it is information for choosing the next one.

> [!NOTE]
> What does not help is starting two processes at once "to go faster". If something fails you will not know which caused it, and the conversation with the team becomes vague.

**What if our most painful case is internal?**

Do it anyway, knowing the return will be smaller and slower.

**How many people should take part?**

Those already doing that work. Adding spectators does not help.

**Can we switch process midway?**

Yes, and sometimes it is right. Note why — that is the instructive part.

## Ejemplos

**A company wants to start by uploading its whole historical archive.**

- Starts with documentation from fifteen hauliers
- Sets a decision date at thirty days

→ Within two weeks the hauliers supply unprompted and the archive is postponed to month two.

**The chosen process depends only on people inside.**

- Picks one that means waiting on somebody outside

→ The saving shows from week one, because that is where the lost time is.

**You start with something that happens twice a year.**

- Picks what repeats every week

→ The template pays for itself in the first month.

**The chosen process is run by one person and nobody else sees it.**

- Picks one two or three people touch

→ Somebody beyond whoever set it up notices the result.

**You pick the most important process, which is also the most delicate.**

- Starts with one where a mediocre result breaks nothing

→ You learn without risking the critical process.

**Nobody knows which process consumes most time today.**

- Asks where the week goes before choosing

→ The choice rests on real time rather than an impression.