Insights · November 11, 2026 · 13 min
How to Find the Processes Making Work Harder Than It Needs to Be
Repeated questions, duplicate entry, handoffs, and workarounds can reveal where everyday work is harder than it needs to be.
Not every operational problem looks like a problem.
Sometimes it looks like an employee maintaining a spreadsheet because the company's software doesn't provide the information they need. Sometimes it's a manager repeatedly asking for updates, a customer having to provide the same information twice, or an employee spending part of every morning sorting out something that should have been handled the day before.
The business keeps operating. Customers are served. Employees find ways to get things done.
But getting the work done and having a process that works well are not necessarily the same thing.
When employees regularly compensate for missing information, confusing steps, unclear responsibilities, or disconnected systems, those extra efforts can gradually become part of normal operations. Eventually, the business may stop noticing how much work is required just to keep everything moving.
This is operational friction: unnecessary difficulty, delays, or extra effort that occurs as work moves through a process.
Finding that friction doesn't require complicated analysis or specialized software. It starts with paying attention to the small, recurring frustrations that people have learned to accept as part of their jobs.
The challenge is knowing what to look for—and understanding what those signals are actually telling you.
Operational Problems Often Become Normal Operations
Think about the everyday work happening inside a business.
Customer requests arrive. Employees exchange information. Tasks move between people. Orders are processed, appointments are scheduled, and invoices are sent.
Over time, employees develop ways to handle situations the original process doesn't accommodate. They create shortcuts, maintain additional records, send reminders, or take on responsibilities that aren't clearly assigned.
Many of these adjustments begin for perfectly reasonable reasons. The problem arises when extra work becomes so routine that nobody questions why it's necessary.
Research into differences between intended business processes and actual workplace behavior identified numerous contributing factors, including unclear responsibilities, unavailable resources, technology limitations, and processes that don't adequately account for the needs of employees. [1]
What matters for a business owner isn't the terminology used to describe these differences. It's recognizing that the way work actually happens may be very different from the way everyone assumes it happens.
Several recurring patterns can help reveal where to look.
Listen for the Questions People Keep Asking
One of the easiest ways to spot possible friction is to pay attention to everyday conversations.
"Did anyone follow up with that customer?"
"Where is the latest version?"
"Who's handling this?"
"Has that invoice been sent?"
An occasional question is normal. But when people repeatedly ask the same kinds of questions, it may indicate that the process isn't giving them the information they need.
Consider a small contracting business where the office manager regularly contacts field employees to find out whether jobs are complete.
The field employees believe they've finished their responsibilities. The office manager needs the information to update customers and prepare invoices. Yet there's no consistent way to communicate when the work is finished.
The visible frustration is constant follow-up. The underlying issue may be that the workflow doesn't clearly establish who updates the job status, when that update occurs, or where the information should be recorded.
This distinction matters.
Reminding employees to communicate better might temporarily reduce the frustration. But if the process doesn't provide a reliable way to share information, the same problem may continue.
When you hear a recurring question, ask what information is missing and why someone must repeatedly request it.
Sometimes the question itself is the clue.
Look for Information Being Entered More Than Once
Duplicate data entry is another useful signal.
A customer completes an online form, but an employee manually transfers the information into scheduling software. Later, someone copies those details into an invoice or tracking spreadsheet.
Each step may take only a few minutes. But repeated across dozens or hundreds of transactions, the additional work can become substantial.
It also creates opportunities for inconsistent or incomplete information.
A 2023 observational study of documentation across paper records and electronic systems found substantial repetition, with copied information appearing in 77% of entries in one of the systems examined. [5]
Although the study involved hospital documentation, it illustrates the difficulties that can arise when information must move between disconnected systems.
For a business owner, the important questions are practical:
Where does the information originate? Where does it need to go? Why does someone have to enter it again?
There may be legitimate reasons to maintain information in multiple places. Different systems serve different purposes, and some records must remain separate.
The goal isn't to eliminate every repeated entry automatically. It's to determine whether employees are performing necessary work or compensating for a process that could function more effectively.
If the same information repeatedly passes through multiple hands or systems, follow its path.
Pay Attention to Where Work Changes Hands
Many operational problems don't happen while someone is performing a task. They happen when responsibility, information, or materials move from one person to another.
These transitions are called handoffs.
Imagine a service business where one employee receives customer requests, another prepares estimates, and a third schedules approved work.
Each employee might perform their responsibilities correctly. Yet customers still experience delays because approvals aren't communicated consistently or important details are missing when the next person receives the work.
The problem isn't necessarily anyone's individual performance.
It may be the connection between their responsibilities.
Research examining operational failures across two hospitals found that poorly connected routines between interdependent departments contributed to recurring problems. Individual departments followed their established procedures, but those procedures didn't always support the departments depending on them. [2]
The underlying lesson applies beyond healthcare: a collection of well-performed tasks doesn't automatically create an effective end-to-end process.
When work moves between people, examine what happens at the transition.
Does the next person receive everything needed to continue? Is responsibility clearly transferred? Does someone know when the previous step is complete?
A missing handoff can create delays, repeated questions, and extra work even when everyone involved is doing their job.
Investigate the Spreadsheet Beside the System
Many businesses invest in software to manage customers, inventory, scheduling, projects, or finances.
Yet employees frequently create spreadsheets, personal notes, or unofficial tracking methods alongside those systems.
It's easy to assume these workarounds are unnecessary or that employees simply aren't using the software correctly.
But the reason for their existence may be more revealing than the workaround itself.
Research examining unofficial systems alongside enterprise software found that these systems can indicate shortcomings in how official technology is implemented or used. [4]
Another study, involving employees adapting to a mandatory enterprise system, found that some unofficial workarounds helped people complete essential work when the technology didn't adequately support their circumstances. [3]
These findings don't mean every workaround is beneficial. Unofficial tracking methods can introduce accuracy, security, and information-management risks.
They do, however, suggest a useful approach: study the workaround before trying to eliminate it.
Consider a marina using specialized software to manage memberships and customer accounts. An employee also maintains a spreadsheet of outstanding member requests.
Why?
Perhaps the software doesn't provide a useful view of pending requests. Maybe the functionality exists, but employees aren't familiar with it. Or perhaps nobody has established a consistent process for assigning and closing requests.
Each explanation points toward a different potential improvement.
Deleting the spreadsheet without understanding its purpose could leave employees without information they rely on. Buying new software without investigating the existing process could create additional expense without solving the problem.
The spreadsheet isn't necessarily the problem.
It may be showing you where to look.
Watch How Work Actually Happens
Ask someone to explain how a process works, and they'll often describe the intended steps.
Watch them perform the process, and you may discover something different.
An employee opens three applications to answer one customer question. Someone walks across the office to get information that should already be available. A manager maintains a personal list because there's no reliable way to see outstanding work.
These actions may never appear in a procedure or workflow diagram.
Research into observing work as done demonstrates how structured observation can reveal interactions between employees, technology, tasks, and working environments that other information-gathering methods may overlook. [6]
A small business doesn't need to conduct a formal observational study to apply this principle.
Sit with an employee while they perform a routine task. Follow a customer request from beginning to end. Ask someone to explain the steps they take when something doesn't happen as expected.
Pay particular attention to moments when employees stop their normal work to find information, correct an error, contact someone, or use an unofficial process.
Then ask why.
The purpose isn't to scrutinize employee performance. It's to understand what the process requires people to do in order to complete their work successfully.
Employees often know where the friction exists because they're the ones dealing with it every day.
Follow One Problem Until You Understand It
Consider a hypothetical example involving a small home-services business.
The owner notices that customers frequently call to ask about the status of their service requests.
The initial assumption is that employees aren't providing timely updates.
But rather than immediately requiring more customer communication, the owner follows one request through the existing process.
A customer submits a request through the website. An office employee reviews it and enters the details into scheduling software. A technician receives the assignment and completes the work.
The technician sends a text message confirming completion. The office employee updates a separate spreadsheet used to track outstanding requests. Finally, someone contacts the customer.
Several opportunities for friction become visible.
Customer information is entered more than once. Job status is communicated through a separate channel. The office relies on a spreadsheet to track information already associated with the service request.
Most importantly, the owner discovers that no single step consistently establishes when a request is complete and ready for customer follow-up.
What initially looked like an employee communication problem may actually be a workflow visibility problem.
That changes the questions worth asking.
Does the scheduling software already support status updates? Who should be responsible for marking work complete? Could the office use a single reliable source of information rather than maintaining parallel records?
The investigation doesn't automatically establish the right solution. Further discussion with employees and examination of the existing tools would still be necessary.
But it moves the business beyond treating repeated customer calls as an isolated frustration.
It identifies a specific part of the workflow worth improving.
That's the value of looking beyond the first visible problem.
Not Every Extra Step Is Unnecessary
Recognizing operational friction requires judgment.
Some processes include approvals, checks, documentation, or additional steps because they protect quality, manage risk, or meet legitimate business requirements.
Employees may also perform certain tasks differently because customer situations require flexibility.
Research into process deviations recognizes that routine and less predictable work can require different levels of variation. [1]
The objective isn't to make every process identical or remove every step that appears inconvenient.
It's to understand which activities contribute meaningful value and which exist primarily to compensate for avoidable problems.
An approval that prevents an expensive mistake may be worthwhile. An approval that simply duplicates another review may deserve reconsideration.
A spreadsheet serving a specific analytical purpose may be useful. One maintained only because employees cannot access current information in the official system could indicate an opportunity for improvement.
Before deciding something should change, understand why it exists and what purpose it serves.
Simplification without understanding can create problems of its own.
Start With One Process, Not the Entire Business
Finding operational friction doesn't require reviewing every process in the organization.
Choose one recurring frustration and follow it.
Start with something specific: scheduling appointments, processing customer requests, preparing estimates, tracking orders, or following up on outstanding invoices.
Avoid broad statements such as "communication is inefficient" or "we need better technology." Those describe general concerns without identifying where the work is breaking down.
Instead, investigate one activity using a few practical questions.
1. Where does the work begin and end?
Identify what triggers the process and what a successful outcome looks like.
2. What actually happens between those points?
Follow the steps employees take, including any spreadsheets, emails, manual entries, or workarounds that aren't part of the official procedure.
3. Where does friction appear?
Look for repeated questions, missing information, duplicate tasks, waiting, unnecessary handoffs, or employees regularly correcting or chasing work.
4. Why does that friction exist?
Talk with the people involved. Determine what purpose each step serves and whether the difficulty is caused by the process, technology, information, responsibilities, or another factor.
5. Is the problem meaningful enough to address?
Consider how frequently it occurs, who it affects, and what consequences it creates. A rare inconvenience may not justify changing an established process. A recurring issue that wastes employee time, delays service, or creates mistakes may deserve attention.
You don't need to identify the solution during this initial investigation.
The immediate objective is to understand the problem well enough to determine whether an improvement is warranted.
That's a more productive starting point than purchasing another application, introducing a new procedure, or asking employees to work harder.
Better Operations Begin With Seeing the Work Differently
Businesses can spend years adapting to operational problems without realizing how much unnecessary effort those adaptations require.
Employees compensate. Managers follow up. Spreadsheets multiply. Customers wait.
Eventually, the extra work becomes familiar.
But familiar doesn't necessarily mean efficient.
The most useful improvement opportunities aren't always the largest or most obvious problems. Sometimes they're the recurring frustrations everyone has learned to work around.
Start paying attention to those moments.
Listen for repeated questions. Follow the handoffs. Notice where information gets entered twice. Ask why employees maintain unofficial systems. Observe what happens when a routine task doesn't go according to plan.
Then choose one recurring problem and understand what's actually causing it before deciding what to change.
You don't have to find everything that's wrong with your business. Start by understanding one process that's making work harder than it needs to be.
That's where better operations begin.
Research Sources
1. König, U. M., Linhart, A., & Röglinger, M. (2019). Why do business processes deviate? Results from a Delphi study. Business Research, 12, 425–453.
2. Tucker, A. L., Heisler, W. S., & Janisse, L. D. (2014). Designed for Workarounds: A Qualitative Study of the Causes of Operational Failures in Hospitals. The Permanente Journal, 18(3), 33–41.
3. Davison, R. M., Wong, L. H. M., Ou, C. X. J., & Alter, S. (2021). The coordination of workarounds: Insights from responses to misfits between local realities and a mandated global enterprise system. Information & Management, 58(8), 103530.
4. Jones, D., Behrens, S., Jamieson, K., & Tansley, E. (2004). The Rise and Fall of a Shadow System: Lessons for Enterprise System Implementation. Australasian Conference on Information Systems Proceedings.
5. Ludley, A., Ting, A., Malik, D., & Sivanadarajah, N. (2023). Observational analysis of documentation burden and data duplication in trauma patient pathways at a major trauma centre. BMJ Open Quality, 12(2).
6. Joseph, A., Neyens, D., Taaffe, K., Bayramzadeh, S., Catchpole, K., et al. (2022). Understanding "Work as Done": Using a Structured Video-Based Observational Method to Understand and Model the Role of the Physical Environment in Complex Clinical Work Systems. HERD, 15(3), 13–27.
← How to Find the Processes Making Work Harder Than It Needs to Be
