The Screen Trap: Why Digitizing a Broken Process Only Breaks It Faster//////////The pitfalls of paving the cow path: why unplanned and half-hearted digitization doesn’t work & what are the solutions

 @Prof Archie D'Souza

A few decades ago, while working as a branch manager for a freight forwarding company, we rolled out a brand-new accounting software system. It was state-of-the-art—on paper, at least. But it raised an immediate, glaring problem: where were the computers to feed the data and print the invoices? And who, exactly, was going to train a workforce entirely unaccustomed to digital entry? I was told about rollout. The ambition was there, but the reality quickly hit: we had advanced software with nowhere and no one to run it; no computers in the branch to process the data, and no trained staff to bridge the gap. It was an early, hard lesson in a timeless truth.

“Accounts,” I was told, “have to be computerized.”

“Of course!” I said, “But for that, we need computers and trained staff.”

So, for the next few months, manual accounting continued at the branch level. A copy of the ledger entries was sent to the head office, and entries were made there. Each branch was provided with a printout of the account statements.  

Very often, we think we’re moving forward but what we’re experiencing is an illusion of progress. This is a common scenario where a company decides to "go digital." They take a messy, paper-heavy, disjointed process and simply turn it into an app, a software portal, or a digital form. Of course, I’m referring to an era that was long before portals and apps.

The Reality Check: This is exactly what I told my boss, "You cannot streamline a broken, disconnected process merely by putting it on a screen; the entire operational framework requires a paradigm shift."

Then it dawned on the board that introducing computerization in accounting was a process that needed a great deal of work. Then in the late 80s came Tally and it was introduced across branches but only after the right systems were in place and the accounting team trained to use Tally. Further, with the version of Tally we got, we could bill in multiple currencies. Any accounting statement that we needed, as well as accounts receivable statements, were system-generated.

Fast forward to the internet era.

We’ve all been there. A company recognizes that its operations are sluggish, siloed, and drowning in paperwork. Leadership gathers in a conference room, diagnoses the bottleneck, and announces the grand solution: "We are going digital."

Months and thousands of dollars later, a sleek new software portal goes live. Employees are given login credentials, training sessions are held, and management breathes a sigh of relief. The era of efficiency has arrived.

Except... it hasn't.

Instead of saving time, employees find themselves clicking through five different windows, jumping across clunky approval loops, and dealing with digital bottlenecks that feel suspiciously like the old paper ones. The tools have changed, but the frustration remains identical.

Why? Because you cannot streamline a broken, disconnected process merely by putting it on a screen; the entire operational framework requires a paradigm shift.

The Pitfall: Paving the Cow Paths

What does this mean? Let me first explain the concept. How often do resort to automating old, inefficient habits just because "that's how we've always done it." This is exactly what the concept of “paving the cow paths” refers to. We have the tendency to simply customise existing systems, preserving them rather than reengineering them. This process is often seen in IT and business processes. It leads to a system that lacks the necessary improvements or enhancements even though it may be more efficient in execution. The metaphor of a cow path illustrates the inefficiency and ineffectiveness of a route that has been worn by habit, which can become a permanent fixture in infrastructure. Automating such processes without a thorough understanding of their necessity or potential for improvement can result in a system that is more efficient at doing something it may no longer need to do. This is a critical lesson for organisations to consider while deciding how to leverage technology to improve processes.

We need to look at an old metaphor from urban planning and IT. This is exactly what we continue to do; pave the cow paths.

The Result: Instead of saving time, technology often just amplifies frustration. Now, to repeat what I’ve already said, people are clicking through five different screens to achieve the same bottlenecked result they used to achieve with a sticky note.

To understand why digital transformation fails so often, it helps to look at this old metaphor.

The Illusion of Progress

The danger of the "screen trap", as we’ve seen, is that screens create an illusion of progress.

When you digitize a process, it looks innovative. Dashboards light up, reports can be generated with a click, and executives can track metrics in real-time. But if the underlying operational framework is fractured, putting an interface over it is merely putting a fresh coat of paint on a crumbling foundation.

• The Communication Gap: If Sales and Operations don't actually talk to each other offline, giving them a shared project management tool won't force them to communicate; it will just give them a digital space to misunderstand each other faster.
• The Complexity Creep: Software makes it very easy to add steps. Because "it’s just a button," teams tend to add extra review layers, optional fields, and redundancy that would never survive in a physical workflow.

Technology is an amplifier. If you feed a broken process into a digital platform, the platform doesn't fix the process—it amplifies the chaos.

 Designing for the Paradigm Shift

True modernization doesn't start with code, software selection, or UI design. It starts with a paradigm shift in how you view the work itself.

Before introducing a single new tool, teams need to embrace a first-principles approach to their operations. Technology should only ever enter the picture after the process has been radically simplified and redesigned. This should be the approach:

• Process First, Tech Second: Technology should only amplify a well-designed strategy, not fix a broken one.

• Obliterate Before You Automate: Look at a workflow and ask: Why do we even do this step? If the original reason no longer exists, cut the step entirely rather than digitizing it.
• Focus on Outcomes, Not History: Stop asking, "How do we move this task from step A to step B the way we used to?" Instead, ask, "If we were building this company from scratch today, how would we achieve this outcome?"
• Break Down the Silos: Re-engineer the framework so that cross-functional teams intersect naturally, rather than tossing work over digital walls from one app to another.

• First-Principles Thinking: Break down what it takes to look at an operational framework with fresh eyes:
• Where is the friction?
• What are we actually trying to achieve (the outcome), versus the steps we take to get there?
• How do different departments actually communicate and intersect?

Look Beyond the Glass

Screens are windows. If the room behind the window is a chaotic, disorganized mess, cleaning the glass isn't going to change the view.

Call to Action: Ask yourself ~ Where in your organization are you trying to solve a structural problem with a software solution?

If your organization is looking to modernize, stop treating technology as the magic eraser for bad workflows. Step back, look at the underlying framework, and be willing to change the rules of the game before you put them on display.