Mushroom management is what we practice when the information required to do a job is also the information we have decided not to share. The term is self-describing, which is rare in this field: keep them in the dark, feed them manure, watch them grow. We do not use the term internally. Internally, we call it “managing communication” or “protecting the team from noise,” which are cleaner and mean the same thing.
The mechanics are light on process. A strategy gets decided three levels up. It arrives at execution level as a directive with a deadline and no context. Someone asks why the approach changed. The answer is that leadership has thought carefully about this, which is true, and that the rationale will be shared when appropriate, which means never, or after the decision is irreversible, which is the same thing. The project proceeds. Two quarters later, the results are surprising to everyone except the three people who had the full picture in February.
What makes this durable as a management style is that it requires almost no maintenance. Transparency generates questions. Questions generate meetings. Meetings generate documentation, dissent, and the occasional person who identifies a flaw in the plan before the plan has been executed. Mushroom management eliminates this entire category of risk. The work gets done. The context arrives, if at all, in the retrospective, which is held after the lessons are no longer applicable.
