What is iatrogenic management?

Iatrogenic management is harm to a team caused by the very things meant to help it—extra meetings, tools, oversight, and process. The word borrows from medicine, where "iatrogenic" describes illness brought on by the treatment itself. The defining trait is that each fix looks reasonable in isolation, but the accumulated "treatment plan" lowers trust, focus, and output instead of raising them.

Is iatrogenic management the same as micromanagement?

Micromanagement is one symptom of it, not the whole condition. Iatrogenic management is broader: it covers any well-intentioned intervention whose side effects outweigh its benefits, including tool sprawl, defensive approval gates, always-on availability rules, and ritual meetings. Micromanagement is the version aimed at people; the iatrogenic kind is baked into your systems.

How do I know if a process is iatrogenic?

Run a simple test: remove it for a few weeks and watch what actually breaks. If nothing does—or if people are quietly relieved—the process was a side effect, not a support. Genuinely load-bearing systems make themselves missed fast. A 71% productivity jump from cutting meetings is the kind of evidence that a "fix" was really a cost.

Isn't some structure and oversight necessary?

Absolutely—management is a treatment, and treatments work at the right dose. The goal isn't zero meetings or zero process; it's matching the intervention to the real problem and stopping there. Iatrogenic management isn't caused by having structure. It's caused by adding structure reflexively and never removing any.

Where does the word "iatrogenic" come from?

It comes from the Greek *iatros* ("healer") and *genesis* ("origin")—literally "brought forth by a healer." In medicine it describes any disease or complication caused by a medical activity, from a diagnostic test to a prescription. Applied to work, it names the same paradox: harm that arrives wearing the costume of help.

Iatrogenic Management: 7 Fixes That Hurt Your Team

Medicine has a word for the kind of harm doctors hate to talk about: harm caused by the treatment itself. It's called iatrogenesis, from the Greek for "brought forth by a healer." A test that triggers a needless surgery. A drug whose side effect needs a second drug. The cure, doing the damage.

It is not a rounding error, either. One widely cited 2016 analysis estimated that medical error causes more than 250,000 deaths a year in the United States—enough to rank it the third leading cause of death. The figure is hotly debated; researchers at McGill argue it "strains credulity." But even the critics don't put the number at zero. The uncomfortable lesson survives the argument: sometimes the people trying to help are the ones causing harm.

Your management can work the same way. Iatrogenic management is what happens when the fixes you prescribe to help your team—another meeting, another tool, another check-in—become the thing that's slowing it down. The conventional wisdom says good managers add structure, especially as you scale. That's true, right up until it isn't. Like any treatment, management has a dose, and past that dose the side effects outweigh the benefit.

Here are seven iatrogenic management habits that look like care and act like harm—plus how to deprescribe.

1. The Recurring Meeting You Added to "Stay Aligned"

A team feels out of sync, so you prescribe the obvious remedy: a standing meeting. It helps at first. Then it calcifies into a weekly ritual nobody can cancel, and the cure becomes the disease.

The dose response here is brutal. When researchers studied companies that cut meetings, the results read like a clinical trial: cutting meetings by about 40% raised productivity by 71%. Removing the treatment made the patient healthier. That is the signature of iatrogenic harm—the intervention you were sure was helping was a net drag.

The deprescription isn't "no meetings." It's matching the dose to the disease. Kill the recurring slot and replace it with a real working session only when there's actual work to do together. Most status updates are a document, not a meeting. If you're not sure which of your meetings are load-bearing, the fastest diagnostic is to cancel one for a month and watch what breaks. Usually, nothing does—except the meeting toil you'd stopped noticing.

2. Tool Sprawl: A New Tool for Every Worry

Every anxiety has a SaaS subscription waiting for it. Visibility problem? Buy a dashboard. Handoffs slipping? Buy a tracker. Each tool is a reasonable prescription on its own. The harm is in the stack.

The average company now runs 106 apps, and the side effects compound. Workers toggle between apps about 1,200 times a day, burning nearly four hours a week—roughly 9% of their time—just reorienting after each switch. Your team isn't fighting the work. It's fighting the medicine cabinet you keep refilling.

Medicine has a name for this too: polypharmacy, the slow accumulation of prescriptions that interact badly. Roughly 45% of older adults are on five or more medications, and more drugs mean more adverse events, not fewer. The deprescription is the same one a careful doctor uses—review the whole list, not one drug at a time, and pull anything that isn't clearly earning its place. Tool sprawl is iatrogenic management you can see on an invoice.

3. Micromanagement: The Check-In That Proves People Are Working

You can't see your remote team, so you prescribe reassurance: a quick check-in, a status ping, a "just circling back." It scratches your itch. It also tells your team you don't trust them—and that side effect is expensive.

Microsoft put a number on the itch. It calls the condition productivity paranoia: 85% of leaders say the shift to hybrid work makes it hard to be confident their people are productive, and only 12% have full confidence—while 87% of employees report they're getting their work done. The gap isn't a productivity problem. It's an anxiety problem, and micromanagement is the treatment that makes it worse.

This is iatrogenic in the purest sense: the act of measuring changes the patient. People who feel watched perform for the watcher—they look busy instead of being productive. The deprescription is to treat your own anxiety somewhere other than your team's calendar. Replace surveillance with a default of written, visible progress people update on their own time, and let the work be the status.

4. Process Bloat: The Approval Gate You Built After One Bad Week

Something broke. A bad deploy, a wrong number in a deck, a client surprise. So you install a gate: from now on, everything routes through a review. You've treated one rare event by sedating the entire team forever.

Doctors call the reflex version of this defensive medicine—ordering the extra test not because the patient needs it, but because you're afraid of the one case in a thousand. The test has its own risks, and now everyone bears them. In a company, the cost shows up as process bloat: approvals, sign-offs, and "just loop me in" rules that outlive the incident that spawned them.

The deprescription is to size the cure to the actual risk. Ask the honest question: how often does the bad thing happen, and how bad is it when it does? If it's rare and recoverable, a checklist beats a gatekeeper. Reserve heavyweight approval for the truly irreversible calls, and let everything else stay fast. A permanent tax to prevent a temporary problem is over-management with compound interest.

5. The "Always Available" Rule That Never Sleeps

Responsiveness feels like a virtue, so you reward it—fast replies, green dots, instant pings. What you've actually prescribed is a steady drip of interruption, and focus is the organ that fails first.

The mechanism is well documented. Every "quick question" is a context switch, and the switching itself is the damage—the four hours a week your team loses to tool overload and fragmented attention come straight out of the deep work that actually moves the business. Demanding constant availability is like waking a recovering patient every hour to ask if they're resting. The check-in defeats the cure.

Deprescribe by making focus the default and interruption the exception. Protect blocks of uninterrupted time, set explicit response-time expectations (most messages do not need an answer in five minutes), and move the real conversations into one scheduled session instead of fifty pings. Availability is a dose, not a personality trait—and the right dose is lower than your instinct says.

6. The Prescribing Cascade: The Fix for the Last Fix's Side Effect

This is the one that makes iatrogenic harm metastasize. A tool creates confusion, so you add a meeting to clarify the tool. The meeting creates pre-work, so you add a doc to prep for the meeting. The doc needs a template, so you add a process to maintain the template. Nobody chose this system. It accreted, one reasonable fix at a time.

Medicine calls it the prescribing cascade—a drug causes a symptom, the symptom gets diagnosed as a new problem, and a second drug gets prescribed for it. Each step is defensible. The whole is a patient on eleven medications, none of which can safely be stopped because they're now propping each other up.

The deprescription is to treat the cascade, not the latest symptom. When something isn't working, your first move should be to ask what to *remove*, not what to add. Before any new ritual or tool earns a place, one should have to leave. Most "alignment" overhead is just the residue of older fixes nobody retired—the coordination crisis is rarely a missing tool and almost always too many.

7. The Wellness Patch for the Burnout You Caused

Here's the cruelest stage. The first six habits have left your team drained, distracted, and defensive—so you prescribe a cure for that, too. A wellness app. A mandatory fun day. Another engagement survey to find out why morale is low.

It's symptomatic treatment: you're medicating the side effects of the over-management instead of stopping the over-management. The survey itself becomes one more thing on an overloaded plate, and the burnout it's meant to measure gets a little worse. This is the moment a good clinician stops adding and starts subtracting.

The deprescription is to read the symptom as feedback about the system, not the people. Low energy and quiet quitting are usually rational responses to too many meetings, too many tools, and too little trust. You don't need a new perk. You need to remove the things that made the perk necessary.

The Cure: How to Deprescribe Your Iatrogenic Management

The pattern under all seven habits is the same. Each fix is individually defensible. Together, they're a treatment plan that's harming the patient. The instinct of a stretched manager is always to add—and iatrogenic management is what that instinct produces at scale.

The opposite skill is rarer and more valuable: subtraction. The best operators run their teams the way a careful geriatrician manages a long medication list—suspicious of every prescription, always asking what can come off. It's the same counter-intuitive muscle behind knowing when *not* to act: the move that feels responsible can be the one that costs you.

This is also where consolidation does real work. A lot of management overhead exists only to stitch together tools that don't talk to each other—the meeting to discuss the doc to explain the dashboard. Collapse video, a shared canvas, AI, and the resulting action items into one workspace, and several "prescriptions" disappear at once: the status meeting becomes a working session, and two or three apps leave the stack. That's the bet behind Coommit—fewer interventions, same care. Run the audit this week. For every meeting, tool, and check-in, ask the doctor's question: is this still earning its side effects? Whatever can't answer, deprescribe.