Scope Creep Issue #4: You Bought Software to Simplify Work. So Why Does It Feel Like More Work?

This piece first appeared in Scope Creep, our LinkedIn newsletter about why work breaks down and what fixes it. Every edition runs here on the blog eventually, but LinkedIn subscribers get it the day it publishes. Subscribe to Scope Creep on LinkedIn and skip the wait.

with lessons from healthcare

You can always tell when a tool has crossed the line from solution to problem. It’s not the price increase. It’s not the outage. It’s the moment someone asks “what’s the status of the Henderson project?” and instead of answering, you open a platform, click into a portfolio view, apply two filters, remember that someone renamed the custom field last quarter, re-apply the filters, find the project, click into it, scan three tabs, and then say “let me get back to you.” That question took four seconds to ask and four minutes to answer. The gap between those two numbers is what your software is actually costing you.

Every mid-market team tells the same story if you give them enough time. It starts with something simple. Trello. Basecamp. A Google Sheet that one person built and the whole department now revolves around like it’s a sacred text (it is). For a while, it works. Fifteen projects, everyone in the same hallway, the spreadsheet holds.

Then the team grows. The project count hits 50. You need dependencies, resource views, a way to report across a portfolio. The spreadsheet has been held together with conditional formatting and prayers for six months. So you go shopping for a grown-up tool.

And here is where the story typically splits into on of two equally bad endings:

Ending one: you buy something simple again, because the last simple thing worked. Except now you have 200 projects across four departments and the tool tops out at task lists and Kanban boards. You’ve outgrown it before the first invoice arrives.

Ending two: you overcorrect. You buy the platform with 400 features, configurable everything, and a sales demo that made it look like the answer to every question you’ve ever had. Three months in, you’ve hired a consultant to configure it. Six months in, one person on your team understands how it works and everyone else routes their questions through that person like they’re a help desk. The tool didn’t simplify work. It became work. It has its own meetings now.

Most teams think this is a training problem. It isn’t. Pendo’s Feature Adoption Report found that 80% of features in the average software product are rarely or never used. Only 12% of features drive 80% of daily usage. Vertice’s SaaS wastage research confirms it from the buyer’s side: 21% of applications in the average tech stack are complete shelfware, and another 45% are underutilized. That’s not your team failing to adopt the tool. That’s the tool shipping 400 features so it wins the comparison chart, knowing your team will use 40. Globally, Pendo estimates that pattern represents $29.5 billion in R&D spent globally on building features that never get adopted.

Your team is paying the downstream cost of that math every time they open a tool that was built to impress a buyer, not support a user.

Now put this in a hospital, where the person who needs the tool most has the least amount of time to fight with it.

Healthcare organizations need the depth. A hospital running projects across clinical operations, IT, marketing, facilities, and compliance needs dependency management, portfolio reporting, audit trails, approval workflows. A Kanban board isn’t going to cut it when you’re coordinating a system migration that touches nursing schedules, patient intake, and three regulatory requirements simultaneously. The work is legitimately complex.

But roughly half of healthcare technology implementations fail to meet their goals, and mid-sized hospitals get hit the hardest. They have the operational complexity that demands a serious system and the staffing reality that makes a high-maintenance system impossible. Healthcare IT News reports that clinician engagement during implementation is the strongest predictor of whether a tool sticks. But nobody is going to ask a nurse manager who’s already running at 110% to spend three weeks learning how to configure a workflow builder.

So IT sets up the system. It launches. The people who built it understand it. The people who use it don’t. Within a quarter, half the hospital is back in email and the other half is logging into the platform just often enough to keep it from looking abandoned. Everyone pretends this is adoption. It isn’t. It’s compliance with the appearance of adoption, which is the most expensive kind of theater an organization can produce.

The question was never “simple vs. powerful.” That framing is a trap the software industry built to justify selling you complexity. The question is whether the tool creates work or absorbs it.

A tool that creates work needs an admin, a consultant, a configuration phase, ongoing maintenance, and a training program that you’ll run once and never repeat. A tool that absorbs work gives you the depth your projects demand without making the software itself a project. The difference isn’t the feature count. It’s whether a new person on the team can open the tool on day one and understand where things stand without scheduling a walkthrough.

If the tool needs its own project manager, it has already failed at the one thing you bought it to do.

The next time someone pitches you a tool with 400 features, ask one question: how many of those features will my team actually use on a Tuesday morning? If the answer requires a consultant to explain, you already have your answer.

If you’re evaluating project management tools for a healthcare team and tired of choosing between too simple and too complex, this breakdown of HIPAA-compliant PM software is worth a read before your next vendor conversation.