Process review

Bring one process.
See where it stands still.

We map one process as it really runs: every step, who does it, where work waits, and which steps agents can prepare while your people decide.

Pick a process. Watch it come apart.

This is what the review gives you, on a fictional trading group. On your process the steps, roles and waits are your own.

Documents, chats and spreadsheets
  1. System
  2. Agent prepares
  3. A person decides
  4. Work waits
    Example on Zarvane Trading Group, a fictional company.
    Your turn

    Now sketch your own process

    Five questions, answered with buttons. As you answer, the sketch shows where your process waits, what an agent could prepare, and what we would ask first. Print it, or send it with the request.

    1Which process?
    2How do cases arrive?Choose all that apply
    3How many people approve it?
    4Where does it wait longest?Choose all that apply
    5Who chases it today?
    Sketch of your processSupplier payment
    1. Case arrives and is openedFrom email: an agent reads it and opens the caseAgent prepares
    2. Documents collected and matchedAgent prepares
    3. Checked against your rulesAgent prepares
    4. Approval 1 of 2A person decides
    5. Approval 2 of 2A person decidesWaits for a signature
    6. Done and recordedSystem

    On this sketch: 3 of 6 steps an agent can prepare, 1 place where work waits, 2 decisions stay with people.

    What stands out

    • It waits for a signature. The approver gets the case already checked, with every source named, and decides with one button.

    We would start the first conversation with

    • Which of the 2 approvals does a written rule require?
    • Where is a supplier payment case right now, and how would you find out?
    • When a supplier payment is late, who notices first, and how?

    Built from your answers by simple rules, not a promise. Nothing is sent until you send the request.

    What you get from the review

    • MapThe process as it really runsEvery step, who does it and what it waits for. Drawn from your documents and conversations, not from the job descriptions.
    • WaitsWhere work stands stillThe places where a case waits for a signature, a reply or a spreadsheet, and why it waits there.
    • SplitWhat agents take, what people keepFor each step: done by the system, prepared by an agent, or decided by a person. With the rule behind each choice.
    • StartA desk to start withWhich role gets a desk first, which cases go to its queue, and what the first pilot would include.

    How the review goes

    Your data stays yours

    We need the shape of the work, not your figures. Hide names and amounts, or show examples on your screen. How we handle data

    1. You choose the processOne that hurts: payments that wait, contracts that circle, purchases nobody can trace.
    2. A conversation with the people who run itThe process owner and the people who do the work. We ask how it goes on an ordinary day and on a bad one.
    3. A few real examplesDocuments, messages, a spreadsheet. Names and amounts can be hidden before you send them.
    4. We draw the mapSteps in lanes by role, the waits, and the split between system, agents and people.
    5. We walk you through itYou correct what we got wrong. The map is yours to keep, whether or not you go on to a pilot.

    Which process waits the longest?

    Name it in the request. We reply within one working day and agree who joins the first conversation.

    Questions people ask

    Which process should we bring?

    One where cases wait and someone has to chase them: supplier payments, contract approval, purchasing, collections, hiring, or the owner’s instructions. If you are not sure, tell us where it hurts and we will help choose.

    Do we need to install anything?

    No. The review is conversations and a few examples of documents. Nothing touches your systems.

    What if our documents are confidential?

    Hide names, amounts and bank details before sending. The map needs the shape of the work, not the figures. We can also look at examples on your screen without receiving them.

    What happens after the review?

    You keep the map. If it shows a clear first desk, we propose a pilot on that process with your people and your cases. If not, the map still shows where the work stands still.

    Is this the same as a consultant’s process audit?

    The map is drawn on the same model the platform runs on. Every step, role and rule on it can become a desk, a queue and an agent without being described again.

    Talk to us

    Step 1 of 3
    What would you like to do?

    Rather talk first? Book a 30-minute call