--- title: "The forms paradox: when workflow automation costs more than the work" date: "2026-04-30" excerpt: "Most mid-market firms have at least one work-request form that takes longer to fill in than the task it's supposed to coordinate. Here's the three-question test for finding yours — and the surprisingly hard reason it's still there." tags: ["Operations", "Mid-market"] author: "Tom Leyden" --- A few weeks ago I was sitting in a discovery session with a mid-market team, walking through the work-request forms their operations staff fill out every day. We got to one — a small administrative task, no more than ten minutes of actual work — and someone said the kind of sentence that should be printed on every operations leader's wall: > *"It's actually more effort to fill out the work request than just do the task yourself."* She wasn't being lazy. She was right. The form had been built for a good reason — once. There were roles to coordinate, an audit trail to maintain, a queue to manage. But the team had changed, the tooling had changed, and the form had quietly become more expensive than the work it existed to organise. This is the **forms paradox**, and almost every mid-market firm I work with has at least one — usually three or four. They sit in Monday.com, ClickUp, Asana, Jira, ServiceNow, or someone's home-grown SharePoint list. They take 4-6 minutes to fill out. The work itself takes 8. ## Why the paradox persists The honest answer is that **nobody's job is to audit automation**. Workflows get added because someone, at some point, was solving a real problem. Then they ossify. The team rotates, the systems get replaced around them, the original problem evolves — but the workflow stays, because: - The person who introduced it has moved on - Removing it feels like a regression ("we used to track this") - Auditing automation isn't on anyone's KPIs - The cost of keeping it is invisible — it's distributed across everyone who fills it in - The benefit, even if vanished, is still vaguely defensible in a meeting The result: every quarter, your operations team's actual job gets a few percent slower, in ways nobody can quite articulate. ## The three-question test When I walk into a workflow review, I look for three signals. Any one of them is a flag; any two is a kill candidate. **1. Who is faster — the requester or the doer?** If the person filling out the form could do the task themselves in less time than it takes to specify it, the form is debt. There are exceptions: regulated work that needs a separation of duties; complex coordination across many teams; tasks that genuinely require a specialist. But "I could do this faster than I'm describing it" is the strongest signal of misallocated effort I know. **2. Does anyone read this status field after it's set?** Open up the workflow. Look at the fields. For each one, ask: *who reads this?* If the honest answer is "nobody since the audit two years ago," the field is theatre. Theatre fields multiply over time — every change to the process adds a few, every removal of a process leaves them behind. They are the operational equivalent of dead code. **3. If you turned this workflow off tomorrow, who'd notice?** Run the thought experiment. If the form vanished overnight, what would break? What would slow down? Who would call you? If the honest answer is "nobody for at least a fortnight," the workflow is no longer earning its keep. The hard version of this question: *what would the team do instead?* If the answer is "just send an email" — that was the original system, and it was probably fine. ## The fix isn't deletion — it's honesty Most operations leaders I've worked with already suspect which forms are the dead weight. What they don't have is the political cover to remove them, because no one can quite remember why they were added. The simplest fix I've seen work: a quarterly **workflow audit** — half a day, every three months, where each form gets a one-line answer to the three questions above. Items that fail two or more get a 30-day amnesty: turned off, replaced with the simplest alternative (usually email or a 30-second Slack thread), and reviewed at the next audit. If nobody complained, it stays off forever. You'll be amazed how much faster your operations team gets in six months. ## The bigger pattern The forms paradox is a special case of a broader truth: **automation isn't free**. Every workflow you add is either earning its keep or accumulating as overhead. Mid-market firms accumulate this overhead faster than enterprise (less central governance) and faster than small business (more tooling), which puts them in a uniquely painful sweet spot — too much automation to manage informally, not enough governance to manage formally. The way out isn't to add more tooling. It's to look honestly at what you've already got, and ask whether the work request is faster than the work. If you're not sure where to start, pick the workflow your team complains about most. The complaints are usually right. --- *Want a fresh pair of eyes on your operations stack? I run a one-day workflow audit for mid-market firms — no slide deck, no framework theatre, just an honest read of what's earning its keep and what's draining your team. [Get in touch](/contact-us/).*