The Fatigue of 'Better': When New Tools Just Add New Work
Bryan Runion ·
We're sold a constant stream of new tools promising to make our work easier. But what's the hidden cost of always adapting, and what happens when the burden of learning outweighs the benefit?
Another one of those emails landed in my inbox last week. The subject line was upbeat, full of words like exciting, streamlined, and new. A platform was being rolled out, mandatory for everyone, and it promised to fold three of our existing tools into one elegant solution. It promised to make things simpler.
My stomach dropped. Not with excitement, but with a quiet, weary resignation. I didn't see a simpler future. I saw the invisible tasks already spooling out in front of me: the webinar I'd watch on 1.5x speed, the hours I'd lose migrating old histories, the week of troubleshooting someone's login. I saw another tax on my attention, another dialect to learn before I could get back to the actual work.
We talk a lot about innovation. We rarely talk about our human capacity to absorb it. We get sold on the next big thing before we're ever allowed to grow fluent in the last one, and the result is a low-grade, collective fatigue. A feeling of being perpetually in training, forever a novice, never quite caught up.
The myth of seamless integration
Every new tool arrives as a key that unlocks a more efficient world. The marketing shows clean dashboards and happy, collaborating teams. What it never shows is the messy, human reality of what integration actually means. It isn't a clean technical handoff. It's a disruption of habit, memory, and hard-won workflow.
It ignores the real cost of learning a new language. Every platform, no matter how intuitive it claims to be, has its own internal logic and its own map of how work should flow. Learning it isn't about finding the buttons, it's about building a whole new mental model, and that energy has to be pulled from somewhere else.
It creates a mountain of shadow work. The unbilled, untracked hours spent moving data, rebuilding templates, and re-explaining the system to confused collaborators are the shadow work of innovation. That labor almost never shows up when a company calculates the return on a new tool, yet it lands directly on the people already at capacity.
It quietly anoints unwilling experts. On every team, one or two people become the unofficial support desk for the new system. It isn't in their job description and rarely gets recognized, but it becomes a steady source of interruption and one more layer of responsibility draining the focus they need for their own work.
Productivity isn't a platform
After enough of these cycles, you start to wonder whether we're chasing the wrong thing. We get so focused on finding the perfect platform that we forget to protect the one condition focused work actually depends on: our attention. Maybe true productivity isn't about adding another tool. Maybe it's about defending the ground we already stand on.
There's real power in stability and mastery. A good enough tool that everyone knows deeply carries a quiet efficiency all its own. When you don't have to think about the tool, you can give all of your thinking to the work, and chasing perfection often robs a team of that hard-won fluency.
We should measure the cost of adoption, not just the promised benefit. Before switching, it helps to ask sharper questions. How many collective hours will training take, what does the dip in productivity during the transition cost, and what institutional knowledge, currently held inside the old system, is at risk of being lost?
We can learn to tell innovation from novelty. Some tools genuinely offer a better way to work, and many just repackage the same functions behind a slicker screen. Developing the wisdom to know the difference is a kind of courage, the courage to say, thank you, but no. The cost of this switch is higher than the problem it solves.
When a tool actually earns its place
None of this is an argument against tools. It's an argument for asking a better question of them. The problem was never software. The problem is that most platforms are built for everyone, which means they're built for no one in particular, and the work of bending them to fit a real production falls on the person holding it all together.
In our world, that person is often the stage manager. When the tools don't understand theatrical workflow, the stage manager becomes the living integration layer, the human memory holding a dozen documents together between rehearsals, departments, and versions. That's the shadow work made visible, and it's exactly the weight this whole reflection has been circling.
The tools worth staying with are the ones built from inside that problem rather than sold from above it. It's part of why I'm building BackstageOS, so the show carries its own memory instead of the SM carrying it in their head. I don't offer it as the next shiny thing, because that would betray the whole point of this piece. I offer it as an example of the test worth applying to anything new: does it ask you to become fluent in one more dialect, or does it finally let you set a few of them down.
A few things worth remembering
The effort of learning a new tool is real, tangible work. It's a direct withdrawal from the finite account of attention and energy we hold for our primary responsibilities.
Our capacity to adapt is not infinite. Treating people as if they can endlessly absorb new systems without consequence is a direct path to burnout.
Stability has its own uncelebrated value. Fluency with a steady set of tools tends to build more sustainable productivity than the promised gains of the next platform.
True integration is a human process, not a technical one. It changes habits, workflows, and muscle memory, and that always comes with friction and a cost worth naming out loud.
Before your team adopts the next platform, try running it through one honest question first: what will this cost the people already at capacity, and who's going to quietly absorb it. If you want more tools and stories that honor the work behind the work, that's what we make here at Half-Hour.