Choose one repeated job with a clear owner, a clear source, and a result the team can check.
Start with work the team already knows
The first AI system should not depend on a new habit that nobody asked for. It should help with a job the team already repeats and already knows how to judge.
Good starting points include preparing a first reply, building a standard document, or finding an approved answer across existing files.
Use a simple test
A useful first job has four parts.
- It happens often enough to matter.
- The source information can be named.
- A person can check the result.
- One person owns the workflow.
Agree the check before the build
Run a few examples by hand and note the time, corrections, and missing information. Use the same examples to check the system. Count review time too. A faster draft is not a saving if someone must spend longer fixing it.
Leave a smaller system behind
The best first build is often smaller than the first idea. It should be easy to explain, easy to stop, and easy for the team to run after handover.
