Skip to content
Interface language: English
Imperium / Signal

The workaround has worked for a year: when an auxiliary spreadsheet becomes a second system

Assess an auxiliary spreadsheet that has become part of the work. Reconstruct the missing decision, conflicting statuses and conditions for keeping or closing the workaround.

Article language: English

A seated woman beside a glass sphere with dark reflections.
In this article

“The system says it has been received, but check the spreadsheet too.” A new employee hears this on their first day. A month later they say the same thing to the next person. An auxiliary file has entered ordinary work, although the company's diagram still shows only one tool. The word “auxiliary” no longer defines its role.

Imagine a workshop that restores picture frames. A year ago, the team set up a spreadsheet to record customers' approval of the scope of work. The main system showed that a frame had arrived, but did not distinguish physical receipt from readiness to begin the assignment. Staff now export a list of cases and manually enter approval. This hypothetical example lets us assess the workaround's future: what is missing from the main route and what sustains the additional record.

The spreadsheet is not a problem merely because it is a spreadsheet. It may have made work possible when the system could not describe it correctly. But establish whether it remains a controlled supplement or has become a second place where decisions about delivering the service are made. If nobody knows what can start without it, the company should include it in its actual way of working.

Reconstruct a case that can be handled only through the workaround

Start with one assignment. Frame R-26 is at the workshop, but the customer has not yet approved the agreed scope. The main system says “received”. The spreadsheet records that approval is pending against the same identifier. The person planning the work looks in both places because neither alone describes the whole situation.

Ask the person who created the workaround what they would do without the file. If they would have to search correspondence and establish approval for every frame, the spreadsheet holds information needed for a decision. If it merely makes an already visible list easier to order, its role is different. These functions can be identified without debating which tool the company likes more.

Steven Alter's Theory of Workarounds, published in 2014, describes the emergence and execution of workarounds as a phenomenon requiring an explanation of conditions and motivations. The original abstract also points to using the theory to classify workarounds and examine how adaptations lead to broader planned system change.

At the workshop, the cause is the missing distinction between two states. If the company concludes that people merely need to read “received” more carefully, it will not supply the missing meaning. Conversely, copying the entire spreadsheet into a new application may preserve the old way of working around the problem. First name the decision the main flow does not support.

Also check when the workaround stopped being exceptional. Does it concern one unusual frame, one customer or every new assignment? A year of daily use may mean the company needs a permanent process element. The file's age alone does not prove it. What matters is the range of cases for which the extra step is actually still necessary.

Do not begin by looking for someone to blame for creating the spreadsheet. In our example, someone noticed a gap and made it possible to separate ready cases from those waiting. Understand that idea, then assess its current effects. Banning the file without providing the needed information may simply move the record into private notes outside the team's view.

Establish where the status really changes

The R-26 customer approves the scope in a message. An employee records the approval in the spreadsheet. Someone else uses it to prepare the assignment for work. The main system still says “received”. At that moment the spreadsheet is part of delivering the service, although formally it was only meant to help review the list.

Reconstruct the route with the people who actually handle it. Who reads the message? How do they connect it to the frame? What does the note mean, and can someone reach the source of the approval? You do not immediately need a new tool. You need to distinguish information received, its interpretation and the decision to begin a specific scope.

If two people change the same status in different places, establish which information is decisive and for what purpose. A newer file save date does not mean every item in it is newer. Someone may have corrected a telephone number while leaving an old approval entry. The origin of the specific information matters for the next action.

A similar issue arises in a forecast sent to a supplier (in Polish) when a plan is mixed up with an order. Here too, physical receipt of the frame and approval of work may happen in a different order. One label should not pretend to represent both events, even if they occur almost together in most cases.

Also choose a case where the decision changes. The customer first approved the scope and then asked to discuss it again. Will the planner see the current information? If the spreadsheet keeps only a green cell, the team needs to know what changes it and when. Appending another note at the end of the row may not reach the recipient.

Trace R-26 through one morning. At 8:15 an export was made, at 8:40 approval was recorded, and at 9:10 the customer asked to revisit part of the scope. The planner sees the green cell from 8:40 because the new message went to another employee. The required correction is to get the update to the place where the decision is made. More frequent exports of the basic “received” status will not resolve the discrepancy.

Also establish whether approval covers the whole assignment. If the customer approved one element while another remains under discussion, a single green cell obscures the scope. The team should state what was agreed, on what basis and which action is still waiting. It need not build an elaborate dashboard. It must allow the provider to distinguish an approved part from an unresolved one.

Aeneia conceptual photography

The return of an old export is another useful case. Someone opens yesterday's list and saves it again under today's date. R-26 may regain an outdated state even though nobody intended to reverse a decision. The case identifier, basis for the update and method for checking discrepancies matter more than the tab colour.

Microsoft's documentation on refreshing external connections in Excel distinguishes data saved in a workbook from data fetched from a source. Refreshing the connection retrieves changes from that source. When assessing a file, establish whether it uses a connection, manual import or directly entered data.

At the workshop, manually entered approval is separate information from the exported status. Even if the company later automates retrieval of the list, it must still decide where approval is stored and updated. A system connection will not create the missing meaning. It can only refresh some data faster.

A working workaround can reveal the need for a better rule

In research published on 12 February 2026, Outmazgin, Soffer and Hadar analyse how knowledge of recurring workarounds can support process improvements. The original article describes development of an approach in several organisations and a separate demonstration. The authors also identify limitations of qualitative research and a small number of organisations. Here a workaround supplies information about a mismatch, not a ready answer for every company.

In our story, the company could change the main status rule, deliberately keep a separate approval register, or create another connection between information and the case. The choice depends on what it can implement and maintain. Moving the note into the system will help if the planner can recognise the current state and its basis.

Keeping the spreadsheet can also be a conscious decision. It then needs an owner, update rules and a way to resolve discrepancies. Someone covering for its creator must be able to handle an ordinary case. It is not enough that everyone can open the file. Access to a row and understanding a note are different capabilities.

Before changing the rule, check whether the gap comes from different departmental purposes. Reception wants to confirm that the item arrived; the planner must establish whether work may begin. Both pieces of information are needed. Giving one status two meanings creates a conflict that additional training in clicking may not remove.

If improvement requires waiting for a change to the main tool, name the conditions for continued use of the workaround. Who maintains the record, which cases does it cover, and when will the team reassess it? The review date should relate to a possible decision. Confirming every year that the spreadsheet still exists mainly establishes its next birthday.

Company knowledge architecture (in Polish) concerns organising sources and making information findable. Here the action taken on that information must also be established. A well-described file can still lead to starting an assignment incorrectly if the rule for updating approval is unclear.

Recognising that difference can be a starting point for Aeneia Audit. A company can bring one assignment, the view in the main system and the way it uses the auxiliary spreadsheet. This makes it possible to trace the actual information flow and assess where AI support makes sense after meanings and roles have been clarified.

The change must survive an ordinary working day

Prepare a small trial using cases selected for the agreed scope. For R-26, approval arrives after the physical receipt of the frame. In another case, the scope returns for discussion. The person handling both should be able to state what may start and why. The trial outcome should confirm a decision in the work, not merely the appearance of a new field.

If you supplement the main system, check the route to planning. A new state may appear in assignment details but not in the list the team uses. It may also disappear in a data export (in Polish). The reason for creating the spreadsheet then still exists for people working from the attachment, even if the administrator's screen now looks correct.

If you retain a separate register, test how a substitute handles it. A new person must find the approval, connect it to the case and report an ambiguity. They should not have to guess that green always means full approval. If there is a discrepancy, they need the right person to resolve it and a way to pause that particular step.

A team error report (in Polish) should preserve the case identifier, visible states and expected outcome. “The spreadsheet is broken again” does not explain whether a row disappeared, approval was confused or an old file was opened. This distinction lets the team fix the right place instead of rebuilding the whole tool every time.

Do not close the old route as soon as a new one is created. Cases already using the auxiliary record need to be accounted for. For each, establish where the current information will reside and who will check it. Retiring an automation (in Polish) is a broader change, but also requires distinguishing the stopping of new inputs from completing work already started.

When using an AI assistant, show it only sources intended for the task and check its output against identified cases. If it is to prepare a list of ready cases, it must not treat physical receipt alone as approval to work. The model should not invent the missing rule between two columns. The company establishes it first.

At the next review, return to the reason the spreadsheet was created. Can R-26 now be handled correctly without the old note? If so, its remaining role can be accounted for. If not, the team should be able to identify the missing step. If closing the note still requires a call to the spreadsheet's creator to establish approval, the work needs further improvement. The team should be able to make the right decision during that person's absence too.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear