﻿Source: https://workorder.leskovsek.si/

AI ADOPTION, ONE WORKFLOW AT A TIME

# Make room for better work.

Working Order helps SME owners and leadership teams use AI to improve real work, from one person's tasks to a shared operation.

A report that takes too long. A handoff that loses context. A decision that keeps waiting for the same person.

[See what changes](https://workorder.leskovsek.si/#in-practice)

A framework by [Luka Leskovšek](https://workorder.leskovsek.si/#about) AI adoption advisor

THE WORKING ORDER FRAMEWORK

## Three Levels

Start with what the work needs. Different workflows can be at different levels in the same company. **Level three is not the destination for every workflow.**

### [Personal capability](https://workorder.leskovsek.si/#personal-capability)

01 Single-player

![One person with an AI power-up on the existing red-cord workflow.](https://workorder.leskovsek.si/assets/personal-cutout.png)

Help one person do their work better.

+ AI literacy + judgement

### [Shared workflows](https://workorder.leskovsek.si/#shared-workflows)

02 Multiplayer

![People connected through a shared record and AI assistance by red cord.](https://workorder.leskovsek.si/assets/shared-cutout.png)

Change how people work together.

+ Shared context + clear handoffs

### [Business redesign](https://workorder.leskovsek.si/#business-redesign)

03 Redesign the operation

![Shared data and AI execution connect to a decision point, a human owner and a feedback loop.](https://workorder.leskovsek.si/assets/operation-cutout-refined.png)

Rethink how a business area operates.

+ Bounded autonomy + feedback

**Progress follows the workflow.** A level may take a few weeks or several months. Some workflows stay at level one or two because that is where the useful improvement is.

TECHNOLOGY AGNOSTIC

Use the framework with **ChatGPT / Codex, Claude, Copilot**, or the tools that fit your company. The starting point is the work, the people and the outcome you need.

SEE THE CHANGE

## Same enquiry. Different ways of working.

ILLUSTRATIVE CUSTOMER REQUEST

> “40 seats. Start Monday. Can you give us 15% off?”

For this example, the standard discount limit is 10%. The request needs a commercial decision.

01

Single-player

### Personal capability

#### Drafts with the salesperson.

Sales uses AI to structure the 40-seat request and draft the proposal, then checks the output.

Sales + AI

Separate reviews

02

Multiplayer

### Shared workflows

#### Drafts from a shared brief.

AI uses the same source information and open questions that sales, operations and finance can see.

Shared brief + AI

Team review

03

Redesign the operation

### Business redesign

#### Prepares within agreed rules.

AI checks approved data, prepares routine work and flags the 15% discount above the limit.

AI + rules

Within rules routine path

15% discount finance

**Finance owns the discount decision at every level.** Monday is promised only after availability is confirmed. What changes is the preparation, the handoffs and the route through the work.

FOLLOW THE WHOLE WORKFLOW

### 01 Personal capability — full walkthrough

The salesperson works better. The handoffs stay the same.

Change: one person's tasks

1. **Read the enquiry**
   
   A salesperson gathers the email, notes and customer history.
   
   **Responsibility:** Sales

2. **Prepare with AI**
   
   AI helps structure the request and draft a proposal. The salesperson checks it.
   
   **Responsibility:** Sales + AI support

3. **Chase the answers**
   
   Operations checks delivery. Finance checks pricing. Answers return through separate messages.
   
   **Responsibility:** Operations + finance

4. **Assemble and send**
   
   The salesperson brings the answers together and sends the agreed proposal.
   
   **Responsibility:** Sales

#### What we learn

Which preparation tasks benefit from AI, what information is missing, and where time is lost waiting for other people.

#### What we check

Preparation time and factual accuracy, including the time spent checking and correcting AI output.

### 02 Shared workflows — full walkthrough

People work from the same record. The next step is clear.

Change: the shared workflow

1. **Create a shared brief**
   
   Sales records the request, source information and missing details in one agreed place.
   
   **Responsibility:** Sales → shared record

2. **Prepare from agreed inputs**
   
   AI drafts from the shared brief. Open questions go to the person who can answer them.
   
   **Responsibility:** Sales + AI support

3. **Route the review**
   
   Operations and finance review named sections. Their decisions stay attached to the proposal.
   
   **Responsibility:** Named reviewers

4. **Approve and send**
   
   The accountable owner approves the final proposal. Everyone can see its status and next step.
   
   **Responsibility:** Proposal owner

One shared record: source information, open questions, review decisions and status.

#### What we learn

Whether the handoffs work in practice, which decisions still cause waiting, and where people need better information.

#### What we check

Time from enquiry to approved proposal, repeated questions, corrections and the effort required from each team.

### 03 Business redesign — full walkthrough

The operation is designed around decisions, exceptions and outcomes.

Change: the enquiry-to-proposal operation

1. **Qualify at intake**
   
   The workflow checks the required information and routes standard and unusual requests differently.
   
   **Responsibility:** Operation owner defines intake rules

2. **Prepare within boundaries**
   
   Routine preparation runs using approved data and offer rules. Missing or conflicting inputs are flagged.
   
   **Responsibility:** Operation owner sets the boundaries for AI

3. **Decide where it matters**
   
   People handle exceptions and commercial decisions. Approval requirements are explicit.
   
   **Responsibility:** Accountable decision owner

4. **Review the operation**
   
   The approved proposal goes out. Quality, exceptions, cost and outcomes feed the next improvement.
   
   **Responsibility:** Operation owner

Review exceptions, quality and cost. Improve the next run.

#### What we learn

Which steps can be removed, where autonomy is justified, and how the operating rules need to change.

#### What we check

End-to-end turnaround, proposal quality, exception rates and total cost per proposal, alongside business outcomes.

FOR SME OWNERS & LEADERSHIP TEAMS

## Before changing a process, understand how it actually happens.

Help people use AI well. Improve the work they share. Then rethink how a part of your company operates.

Where does the information come from? What changes along the way? Who gets involved? What does the next person need?

INSIDE THE FRAMEWORK

## What changes. What you leave with.

Each level builds on what you learn by doing the work. Choose the scope that fits the workflow and expand when there is a clear reason.

01

Single-player

### Personal capability

Understand your work. Use AI with judgement.

![One person with an AI power-up on the existing red-cord workflow.](https://workorder.leskovsek.si/assets/personal-cutout.png)

You + AI. Same process, better work.

**Who decides** The person doing the work checks the output and owns the result.

We start with people's actual tasks. They learn to use AI, check its output, and recognise where it helps. The existing process stays largely intact, with useful improvements along the way.

As they work, we trace the information: where it comes from, what gets cleaned, transformed or enriched, where it goes next, and who relies on it.

#### What you leave with

Practical AI habits, a map of the current workflow, and specific opportunities to improve it.

#### Consider a wider scope when

People can explain the workflow and judge the result, and the next improvement needs someone else's involvement.

02

Multiplayer

### Shared workflows

Redesign the handoffs. Make the work flow.

![People connected through a shared record and AI assistance by red cord.](https://workorder.leskovsek.si/assets/shared-cutout.png)

People + a shared record. Clear handoffs.

**Who decides** Named reviewers and the workflow owner check, approve and handle exceptions.

We bring together the people who create, review and receive the work. We agree where it lives, how information moves, who acts next, and where a human checks or decides.

Parts of the old process remain. Others are rebuilt. Then we run it with real work, find the waiting, ambiguity and rework, and improve it together.

#### What you leave with

A working process people share: clear inputs, agreed handoffs, named owners, review points and a way to handle exceptions.

#### Consider a wider scope when

The workflow works across people, its results are measurable, and wider changes to roles or decisions have a clear case.

03

Redesign the operation

### Business redesign

Rethink how the operation works.

![Shared data and AI execution connect to a decision point, a human owner and a feedback loop.](https://workorder.leskovsek.si/assets/operation-cutout-refined.png)

Shared data → AI execution → decision. Human owner above. Evaluate + improve below.

**Who decides** Decision rights define where AI can act, where approval is required and who owns the operation.

We take a defined area of the business and work back from the outcome it needs to deliver. That can change the steps, the roles, the decisions, and the way information enters the operation.

We define what can run autonomously, what needs approval, how quality is evaluated, and who responds when something goes wrong. We review the cost and value as the operation runs.

#### What you leave with

A redesigned operation for a defined area, with decision rights, quality checks, cost visibility and an accountable owner.

#### Expand only when

Quality holds in real use, the value justifies the full running cost, and the team can operate and improve it.

AT EVERY LEVEL

## More automation has to earn its place.

01

**People own the result.** We name who checks, who decides and who handles the exceptions.

02

**Quality gets tested on real work.** We compare outputs with agreed examples and criteria, including difficult cases.

03

**Information has a source and a destination.** We establish what data can be used, who can access it and where it belongs.

04

**The full cost counts.** We include setup, tools, checking, rework and ongoing support. Time released and cash saved are tracked separately.

HOW WE WORK TOGETHER

## Bring one workflow. We'll work from there.

Choose work that matters, happens often enough to learn from, and has someone willing to own the improvement.

01 / OBSERVE

### Walk through real work.

We follow a recent example with the people doing and receiving it. We map the information, decisions and delays, and establish today's baseline.

02 / CHANGE

### Run a better version.

We choose the right level, agree one useful outcome, and put a first version into practice. Real use shows us what needs to change.

03 / REVIEW

### Make the next decision.

We review quality, time, cost and adoption. Then we keep it, improve it, expand it or stop. The decision comes with evidence.

THE FIRST PIECE OF WORK

A map of the current workflow, an agreed baseline, one change tested in practice, and evidence for what to do next.

**I bring** facilitation, practical AI guidance, process design and support through implementation.

**You bring** a sponsor, a workflow owner, the people involved and access to the relevant work.

LET'S FIND YOUR STARTING POINT

## What work keeps getting in the way?

A report that takes too long. A handoff that loses context. A decision that keeps waiting for the same person.

Tell me how it works today, who is involved, and what you would like to improve. That's enough to start a conversation.

[Tell me about your workflow](mailto:Luka@leskovsek.si?subject=Working%20Order%20%E2%80%94%20a%20workflow%20to%20discuss&body=Hi%20Luka%2C%0A%0AThe%20workflow%20I%20would%20like%20to%20discuss%20is%3A%0A%0AThe%20people%20involved%20are%3A%0A%0AWhat%20I%20would%20like%20to%20improve%3A%0A)

Luka Leskovšek [Luka@leskovsek.si](mailto:Luka@leskovsek.si)

THE PERSON BEHIND WORKING ORDER

## Luka Leskovšek.

AI adoption advisor

I work with founders and leadership teams on AI transformation.

I also lead engineering at Zebra BI.

What I care about is giving people the tools and knowledge to change how they work in ways that used to be out of reach. For many companies, changes like these were too expensive to attempt and too prone to failure.

AI is opening up possibilities we haven't had before. I want people to understand what's possible, build the confidence to try it, and make changes they can own and keep improving.

[Get in touch](mailto:Luka@leskovsek.si)

## All comparison questions

### AI work

#### 01 — Personal capability

**Drafts with the salesperson.** Sales uses AI to structure the 40-seat request and draft the proposal, then checks the output.

#### 02 — Shared workflows

**Drafts from a shared brief.** AI uses the same source information and open questions that sales, operations and finance can see.

#### 03 — Business redesign

**Prepares within agreed rules.** AI checks approved data, prepares routine work and flags the 15% discount above the limit.

### Team handoffs

#### 01 — Personal capability

**Sales chases separate answers.** Operations checks Monday availability. Finance reviews the discount. Sales assembles the replies.

#### 02 — Shared workflows

**Reviewers use the same record.** Operations and finance review in parallel. Their decisions, the status and the next owner stay visible.

#### 03 — Business redesign

**The exception changes the route.** Finance receives the discount exception. Unclear availability goes to operations. Routine checks follow the agreed path.

### Human decisions

#### 01 — Personal capability

**Existing approvals still apply.** Operations confirms availability. Finance decides the discount. Sales checks the proposal and sends it.

#### 02 — Shared workflows

**Each decision has a named owner.** Operations and finance record their decisions. Sales approves the final proposal in the shared record.

#### 03 — Business redesign

**People decide on exceptions.** Finance decides the discount. Sales approves this exception before sending. AI cannot approve its own exception.
