Kılman Training

What Should You Know Before Starting With Automation?

Most automation projects stall not for technical reasons but because the wrong task was picked first. This series takes that on end to end across a full curriculum: what to automate first, where to look when a system goes quietly wrong, and how customer data should be collected from the start.

Who is this series for?

Anyone running their own business with a small team who feels that repeating work is eating their time. No coding background is expected. The lessons do not describe a product; they describe which decision leads to what, so they may help whichever tool you work with.

The series does not walk through the menus of a particular tool, nor writing code, nor pricing. Since the subject is the order of decisions, it can be read without a system already in place; the process you currently run is enough. Nothing beyond paper and pen, or an empty spreadsheet, is needed to start. Each lesson leaves a written output behind, and that output becomes the input of the next lesson.

How does the series run?

1. Which task should you automate first?

Choosing a task with three criteria and not automating a broken process. Output: a task inventory and a baseline.

2. Writing a process down

Boundary, steps, decision points, exceptions and the handover test. Output: a filled process map.

3. Collecting customer data correctly

Which field to collect, where it lives, who reaches it. Output: a field dictionary and a deduplication key.

4. Choosing a tool

Scoring off the shelf, no-code and custom builds against seven criteria. With a downloadable comparison table.

5. Building the first automation

Filling in the setup sheet, building the five parts in order, going live through a narrow gate. With a downloadable setup sheet.

6. Making systems talk

Field mapping, direction, format conversion, the first load and drop behaviour. With a downloadable integration map.

7. When you say the automation is not working

Diagnosing a system that runs wrong without raising an error. A silent fault is more dangerous than a loud one.

8. Exceptions and fault handling

Unexpected input, duplicate records, the alerting path and making silent faults visible through measurement. With a downloadable exception log.

9. Bringing the team into the process

Who uses what, which permission, first week support, the single door and writing down the rules that live in one head. With a downloadable handover checklist.

10. Measuring and growing

Going back to the baseline, defining four measures with their counting rules, writing the time gained and the growing or stopping decision. With a downloadable measurement record.

The series is designed as a full curriculum. The curriculum stands above in order; modules added later take their places in it as well.

How to use the lessons

Each lesson is written as a module: concepts, a step by step method, a template to fill in, a worked example from end to end, a week long exercise, common mistakes, a checklist and a glossary. They are written to be read in order, though each stands on its own. While reading, pick an example from your own business and put the questions in the lesson to that example; that is when the series earns its keep. If something stays unclear, you can write to us.

The exercises feed one another: the process map you write in the first lesson becomes the ground of the diagnosis in the second, and the input of the field dictionary in the third. Keeping the outputs of the three lessons in one file therefore leaves you with a tidy record once the series ends.

Hear About New Modules

New modules get added as the series fills out. If you would like to hear about them, a message on WhatsApp is enough.

💬 Notify Me on WhatsApp

If you want to talk through where to start in your own business, write to us and we can look together.

Get a Quote on WhatsApp

Frequently Asked Questions

Is this training paid?
No, every lesson on the page is open. You are not asked to open an account or fill in a form.
Do I need to know how to code?
You do not. The lessons describe the order of decisions rather than the use of a tool: what to do first, what to measure, where to stop. Those questions can be answered without writing code.
Do you run corporate training?
Yes, sessions can be arranged for a team. The content is written around the systems that team already uses; the lessons here are the open part of those sessions. Write to us for details.
Will new lessons be added?
The series is open ended. New lessons get written as questions accumulate; if a subject comes up often, telling us is enough.
Which languages are the lessons in?
Like all content on the site, nine: Turkish, English, German, Spanish, French, Russian, Korean, Chinese, Japanese. You can switch from the language control at the top right.