Reduce techno-complexity by limiting new tool adoption

Before adopting any new technology at work, evaluate whether it actually reduces or just redistributes cognitive load.

Why it works

Techno-complexity arises from the accumulation of tools requiring ongoing maintenance, learning, and context-switching — each new platform adds overhead beyond its stated benefit. The mechanism is cognitive load: every tool in active use occupies a working-memory slot for potential notifications, updates, and logins. The threshold where tools produce net cost rather than net benefit is reached earlier than most people expect.

How to do it

1. Before adopting a new tool (app, platform, service), ask: "Does this replace something I’m already using, or add to the stack?"
2. If it adds to the stack: trial it for 30 days and evaluate whether it actually reduces friction or just moves it.
3. Set a rule: before adding a new tool, you must remove one.
4. Quarterly, audit your full tool stack and remove everything that is not actively generating net value.

Evidence

Cognitive load theory predicts diminishing returns as total working-memory demands increase. Rosen’s technostress research identifies techno-complexity as a distinct stressor component, associated with anxiety and reduced performance in high-tool-load workers. (mechanistic)

Rosen’s empirical work on technostress is primarily survey-based and observational; the specific "add one remove one" protocol is a practical application of the mechanism rather than a directly tested intervention.

Sources

• Rosen, Carrier & Cheever (2013), iDisorder — technostress research framework

Common mistake

Evaluating a tool by its best-case feature set rather than its actual integration cost — the decision point should be total overhead, not headline functionality.