> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to choose which process to automate first
- URL: https://blog.jestor.com/choose-which-process-to-automate-first/
- Published: 2026-09-16T18:55:35.000Z
- Updated: 2026-09-16T18:55:35.000Z
- Author: Bruno Bannach

Deciding **which process to automate first** determines whether there is a second one. The best first candidate is frequent, painful and well understood, which is a narrower set than the list of processes people complain about.

## Why the first choice is usually wrong

The obvious candidate is whatever caused the most recent problem. That process is often complex, politically contested and poorly understood, which makes it the worst possible starting point.

A difficult first automation produces a visible struggle, and the organization concludes the approach does not work.

What makes a poor first candidate:

- A process nobody has documented
- A process several teams disagree about
- A process that runs a few times a year
- A process about to change for other reasons
- A process whose pain is felt by nobody in particular

## Scoring candidates

| Factor        | Good first candidate          | Save for later            |
| ------------- | ----------------------------- | ------------------------- |
| Frequency     | Daily or weekly               | A few times a year        |
| Pain          | Someone complains regularly   | Theoretically inefficient |
| Clarity       | The rules can be written down | It depends who you ask    |
| Ownership     | One team owns it              | Contested between teams   |
| Stability     | Unlikely to change soon       | Under review already      |
| Measurability | The gain is visible           | Benefit is diffuse        |

## Step by step to choose

1. **List candidate processes** with their frequency.
2. **Ask who complains about each**, since a named person predicts adoption.
3. **Test clarity** by asking two people to describe the rules.
4. **Confirm one team owns it**, avoiding contested territory.
5. **Check it is not about to change** for unrelated reasons.
6. **Pick the one where the gain will be obvious**.
7. **Measure before starting**, so the result can be shown.

## Why a named complainant matters more than the size of the saving

A process with a large theoretical saving and no one who cares will not be adopted. A smaller process with someone who actively wants it fixed gets used from day one, and that person becomes the internal advocate for the next one.

## Why choose Jestor

In **Jestor**, a first process can start from a template installed in minutes or from a spreadsheet already in use, so the time between choosing and having something working is short. Automations are built without code, and **SLA** per stage provides the before and after measurement.

## Frequently Asked Questions

### Should I start with the biggest inefficiency?

Not necessarily. Start where someone actively wants it fixed. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### How do I test whether a process is clear enough?

Ask two people to describe the rules and compare their answers.

### Why avoid contested processes first?

Because the disagreement, not the tool, becomes the obstacle.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.