Which Process Is Eating Your Office's Week?

Usually it is one chain: the same order, typed again at every step, by one person. Each step takes a few minutes. Together they take most of a week, and nobody sees it, because no single step looks like the problem.

This is the third pattern in Friction, Found, our series on the friction we see most often inside growing companies.

What is the chain?

The chain is a run of manual steps that carries one piece of work from start to finish, where each step retypes what the step before it already knew.

Picture an order arriving by email. Someone types it into a spreadsheet. Then into an invoice template. Then into the accounting system. Then into the report the owner reads in the morning. Five entries for one order, and the details are the same every time: the customer, the quantity, the price, the date.

Each step was added for a good reason. The spreadsheet came first, because it was free. The invoice template came when the spreadsheet could not print one. The accounting system came at tax time. Nobody designed the chain. It grew one link at a time.

How can you tell if one is eating your week?

Four signs tend to show up together:

• The same details get typed more than once, into different places.
• One person carries most of the chain, and work waits when they are busy.
• Invoices go out in batches, on the day that person catches up.
• Small mismatches turn up between systems, and fixing them is its own job.

The second sign is the one to watch. When a chain runs through one person, it is also a single point of failure. We wrote about that from the people side in what happens when one person is out for two weeks.

What does the chain cost?

Time first. A few minutes per link, times five links, times every order in a week, is how a back office loses most of its week without anyone deciding to spend it that way.

Errors second. Every retype is a chance to get a number wrong. The mistakes are small, and they surface late: on an invoice a customer questions, or in a total that does not match at month end.

Speed third. Work moves at the pace of the person carrying it. If invoicing waits until Thursday, so does cash.

Why does the chain survive when leadership wants something else?

Because the priority changed and the systems underneath it did not.

Picture an owner whose stated goal is staff who are fully present with customers. Then look at the day those same staff actually have: status checks across vendor portals, manual entries for the one partner that never got connected, a report someone builds by hand every morning. None of it was a decision against the priority. It is what the tools ask for, and the tools win, because the tools are where the work lives.

That gap is worth naming out loud. When a priority and the daily work point in opposite directions, the work wins every time.

What is the first move?

Follow one order from start to finish, and count every time someone types it.

1. Pick a typical order, job or load, not an unusual one.
2. Write down every place its details get entered, in order, and who enters them.
3. Next to each step, note what gets typed that already exists somewhere else.

That list is your chain. The longest stretch of retyping is usually obvious once it is on paper. It is also where the first fix goes: make the first entry the only one, and let the steps after it read what is already there.

Does fixing it mean replacing everything?

No. Most chains break at one or two links, not five. The order details that land in the spreadsheet can usually reach the invoice without being typed again. The invoice can usually reach the accounting system the same way. Each link you remove gives time back and closes a gap where errors start.

Start with the link that is typed most often and checked least. Leave the rest alone until the first one is working. We covered why one shared record matters before any tool goes in, in what a single source of truth actually requires.

What does it look like when the chain breaks?

Here is one we can describe. A small trucking carrier ran its back office on one computer, with invoices and documents built from templates and retyped for every load. One person carried roughly 10 hours a week of that entry, and if the computer was ever lost, the records went with it.

We built one-click data entry, invoices that generate themselves from the same data, and a portal where drivers track their own loads. The admin time came down from about 10 hours a week to 2 or 3. The person who carried the chain got most of that time back for work that needs judgment.

Where should you start if you see this in your own company?

Run the one-order trace. It takes an afternoon, and it turns a vague sense that the office is buried into a short list of links.

If you want a second set of eyes on that list, bring it to a Friction Audit. Give us 45 minutes and we will walk the chain with you, find the link to break first, and show what the tools you already pay for could carry. The Leverage Map that comes out of it is yours to keep.