Spotting media breaks in your company: how to take stock

A media break occurs when information changes its medium and is re-entered by a person in the process. The technician writes the parts used on a note, and in the office they are typed into order entry. An order arrives by email, someone reads it on screen and enters the line items into the inventory system. Timesheets exist on paper, while the costing lives in a spreadsheet. In all three cases the same detail exists twice shortly afterwards, with no connection between the two versions. That is what distinguishes a media break from a plain change of system: when two programs exchange data through an interface, the medium changes as well, but nobody copies anything by hand.

The first cost is the obvious one: working time. It arises not only from the typing itself but mostly from everything around it. The document has to be found, an illegible entry triggers a call back, the customer number is looked up in the second system, and while you are at it you check the price to be safe. Pure data entry is rarely the problem. The effort sits in the detours that form around the entry, and those detours are invisible in every system, because they lie between the systems.

The second cost is the more unpleasant one: divergence. As soon as the same detail is maintained in two places, the records drift apart. A change in quantity is corrected in the order but not in the spreadsheet. A new delivery address lands in the customer file but not on the delivery note that has already been printed. Later it can no longer be established which version is correct, because nowhere was it recorded when and by whom it was last changed. A data entry problem thus turns into an information problem: the company cannot answer a simple customer question with confidence, even though all the data is in the building.

Taking stock rarely fails on method and often on organisation. If the survey is meant to run alongside daily business, it gets abandoned as soon as the first bottleneck appears. Plan fixed, short time slots rather than one large block. An hour per station is enough in most cases if you know beforehand what you are asking about. The survey should take place where the work happens, not in a meeting room, because the decisive details become visible at the workplace: the pile next to the keyboard, the second list in the folder, the note under the desk pad.

Clarify in advance who takes part and in which role. What you need are the people who carry out the workflow every day, not those who can describe it. Managers should know about and back the survey, but should not attend if their presence means workarounds go unmentioned. Where a works council exists, the survey belongs on its table early, especially if times are being recorded. That is not a formality; it prevents the survey from later being perceived as performance monitoring. Assessing the legal position in a specific case belongs in expert hands.

The most productive findings come not from system reports but from conversations. The reason is that the interesting points sit where people bypass the official route because it does not work. These workarounds are not indiscipline but repairs: someone noticed that a detail was missing and built themselves a stopgap. Those stopgaps show exactly where the actual workflow has gaps. They appear in no written procedure and vanish from the conversation the moment it feels as though they might be punished.

So ask about activities, not assessments. Instead of asking where things go wrong, ask: what did you copy out by hand this morning? Which list do you keep on the side because the system will not give it to you? Which detail do you regularly have to look up somewhere else? What do you print out, and why? What do you do when a customer calls and wants to know the status of their order? The last question is particularly productive, because it walks the entire document path from the customer's point of view and uncovers exactly the points where the trail goes cold.

Record the answers verbatim rather than in polished form. The wording someone uses to describe their stopgap often contains the decisive constraint: that the list is only maintained on Thursdays, that a colleague knows the prices by heart, that the printout is necessary because there is no mobile signal on site. Such conditions later decide whether a change holds in daily operation or gets bypassed again after two weeks.

After the survey you have a list of findings, often more than expected. Fixing all of them is neither necessary nor affordable. Ranking reduces the list to what is worth doing. Three figures are enough for this. Volume says how often the break occurs per week. Time says how many minutes a case ties up, including searching and queries. Error consequence says what happens when the transfer goes wrong: is it noticed immediately, or does the wrong value carry through to the invoice.

Volume times time gives the tied-up effort and is the figure easiest to communicate. Error consequence is harder to quantify and often the more important one. A break that costs only a few minutes but regularly leads to an incorrect invoice is more serious than one that ties up a lot of time and corrects itself immediately. So rank error consequence separately and in simple grades: immediately visible, visible later in-house, visible only at the customer.

Not every break found is a call to act. There are cases in which manual transfer remains the appropriate answer, and it is part of an honest survey to write that down as such. The most important case is rarity: a case occurring a handful of times a year does not justify a technical connection that has to be maintained permanently. The second case is dependence on judgement. Where every case has to be examined, weighed and decided, automation does not replace the examination but hides it.

The third case concerns the other side. If a customer or supplier only supplies data in a form that cannot be interpreted reliably, manual capture is often cheaper than any recognition setup that needs readjusting with every change of format. Here too the decision should be recorded in the list with its reasoning. A documented deliberate decision is something different from an overlooked finding, and it spares the company from having the same discussion again in two years.