Where is your team losing time?
Most organisations outgrow the way they work. We look at how the work really gets done with your team, put a cost on the time it loses and change it with you, a stage at a time.
Why it happens
Nobody designed the process. It built up.
A business that has grown is usually running on a way of working that suited it when it was smaller. The work still gets done, but it takes more people, more checking and more chasing than it should.
Nobody sat down and chose that. A spreadsheet was started to cover a gap, an approval was added after one mistake, a second system arrived and someone became the person who copies between the two. Each step made sense on the day it was added. Together they are now how the work gets done, and nobody owns the whole of it.
That is why the problem is hard to see from the top. Each team knows its own part and the delays it hands to the next. Nobody has the whole route in front of them, so nobody can say what it costs.
Where the time goes
The cost is hidden in ordinary work
When we map a process with the people who do it, the time is rarely lost in one obvious place. It is spread across small things that each look harmless on their own:
- Typing it again. The same details entered into a spreadsheet, then a stock system, then the finance system, with a chance of a mistake every time.
- Waiting. Work that sits in an inbox until someone approves it, answers the phone or comes back from leave.
- One person’s memory. Steps that only one person knows how to do, so the work stops when they are away and nobody can improve what they cannot see.
- Checking and chasing. Time spent confirming that the last step happened, because there is nowhere to see it.
None of this appears as a line in the accounts. It appears as overtime, slow replies to customers, a backlog that grows even after you hire, and capable people spending their day on work a better process would not ask of them.
An example
One order, before and after
Take a customer order. It arrives by email and is typed into the order spreadsheet. Someone phones the warehouse to check the stock, waits for an answer, then types the order into the stock system. A manager approves it by email when they get to it, and it is typed a third time into the finance system before the invoice goes out.
Before 7 steps · typed 3 times · 2 waits
- Order arrives by email
- Typed into the order spreadsheet Typed by hand
- Stock checked by phone Waits
- Typed into the stock system Typed again
- Manager approves by email Waits
- Typed into the finance system Typed again
- Invoice sent
After 4 steps · entered once · 1 decision
- Order arrives on a form
- Stock checked by the system
- Manager approves the exceptions
- Invoice sent
Redrawn with the people who handle it, the same order takes four steps. It arrives on a form, so it is entered once. The system checks the stock, and the manager sees only the orders that need a decision, the unusual ones, instead of every one.
Most of that change is a matter of agreement. Deciding that the manager need not approve every order, or that a form replaces the email, costs nothing to build. The part that does need software, joining the order form to the stock and finance systems, is the work of Systems and automation, and we plan it with you from the same map.
Know a process in your business that runs like the first list? Start a conversation
How we work
From a map of the work to a change that lasts
The first few weeks are spent with your team, where the work happens. We start with one process that is clearly costing time, chosen with you. We sit with the people who do each part of it, follow real pieces of work from start to finish and draw the route as it is, including the workarounds nobody wrote down.
Then we bring the people involved together to check the map and agree where the time goes.
-
Map the work
We sit with the people who do the job and draw what happens now with them, one step at a time, workarounds included.
-
Count the cost
Together we put hours, delays and mistakes against each step, so every change can be ranked by what it saves.
-
Redesign it together
We redraw the process with your team and try the new way on a small part of the work first.
-
Change in stages
Each stage goes live with training and a named owner, and we measure it with you against where you started.
They follow the stages of every project we run with a client: understand, prioritise, prove, then build and embed, applied here to the way the work runs. Since 1995 we have built apps, training and systems with organisations such as Jaguar Land Rover, BP, Cummins and the RAF, and understanding with your team how the work is done comes before any of it.
What you get
Something your team can act on
Everything we make with you is written for the people who will use it, so the work carries on when we are not in the room.
A map of how the work runs
Every step of the process, who does it, which system or spreadsheet it touches and how long it waits before the next one. It is drawn with the people involved and checked by them, so it is a record your team agrees with, and a new starter can read it to see how the work moves.
A ranked list of changes
Each change says what it saves in hours, delays or mistakes, what it needs (a decision, a new form, some training or new software) and who in your team owns it. The changes that cost little and save the most come first, so you can start on them straight away and judge the rest with the figures in front of you.
A way to bring people with you
A change only counts once people work the new way. For each stage we agree with you what changes first, how it is tried on a small part of the work, how each team learns it and how you will know it has taken hold. Where people need more than a briefing, from guided walk-throughs to practice they can repeat, we plan it with you as Training and adoption.
We stay with you until the new way is the normal one, and measure the result together against where you started.
Questions
Good to know
-
How much of our team’s time will it take?
We ask for short sessions with each person involved, at times that suit the work, and a workshop or two to check the map and agree the changes. Nobody is taken off their job for long, and the people who know the work best are the ones we spend most time with.
-
Do we have to buy new software?
No. Many changes need none: a step removed, an approval moved, a form made simpler or one list shared by two teams. Where software would save more than it costs, the list of changes says so and we plan it with you.
-
What happens first?
A conversation about the part of the work that is costing you most. Tell us about it in the form below and we will talk it through with you, then agree together which process to map first and who should be involved.
-
What if our problem is small?
Small is a good place to start. One slow process, mapped and changed with the people who run it, shows your team what is possible, and you can decide from there whether to look further.
-
What if our team is wary of change?
That is common, and it is why we map the work with them rather than about them. The people doing the job usually know best which steps waste their day, and a new way they helped design is one they are far more likely to keep.
Start here
Tell us where the time goes
Tell us which process is costing your team time, even roughly. We will talk it through with you and work out together where to look first.
Rather talk now?
[email protected] +44 (0)1767 317614 Book a meeting (opens in a new tab)
How we help
The other ways we work with you
-
AI Consultancy
An AI Opportunity and Risk Review: find the uses that pay back, join them to your systems and manage the risks.
-
Systems and automation
Software that joins the systems you already run and takes the repeated steps out of the working day.
-
Training and adoption
Training and support built round each role, so a new system or way of working is the one people use.