Mushroom management

Mushroom management, also known as Pseudo-Analysis or Blind Development, is a mocking term used to describe the running of a company where the communication channels between the managers and the employees do not work properly.[1] The term may well have originated from the proverbial way mushrooms are grown: "Keep them in the dark and feed them with sh*t".

Description

Mushroom management is a style of management in which the personnel are not familiar with the ideas or the general state of the company, and are given work without knowing the purpose of this work. Open-book management is the opposite of mushroom management. Mushroom management means that workers' curiosity and self-expression are not supported. The employees often have no idea what the company's overall situation is, because the leaders tend to make all the decisions on their own, without asking anyone else to give their opinion.[2] This problem can occur when the manager does not understand the employees' work (in a programming company, for example) and therefore cannot communicate effectively with the employees.[3]

Mushroom management can also be found in environments that are unrelated to business. It can sometimes be found within schools, when students working in a group decide not to share information with the other students in the group. This means that they will appear more intelligent and hardworking during assessments.[4]

Reasons

The main reasons for the development of mushroom management within a company can be found at the managerial level. Mushroom management often develops when managers see themselves as the sole decision-makers within the company, rather than the people who lead all the employees towards a shared success. This can often take place unintentionally: managers fear that their employees will discover important new ideas instead of them, which drives the managers to make bad decisions and prevent employees from taking an active role in their work. As a result, the employees end up doing this work in a mechanical, repeated fashion, without contributing in a more productive or active way.[5]

Benefits

The key feature of mushroom management is that the employees have limited responsibility over the company. The importance of the decisions they have to make is minimal, which can often reduce workplace-related stress.[6]

Consequences

The consequences of mushroom management can be extremely detrimental for everyone involved in the company. If the flow of information within a company is insufficient, the people involved often have a limited understanding of how to react in situations that require quick assessment and prompt decision making.[7] For example, a company that makes and sells shoes might research their customers' preferences and discover that these preferences have changed. However, if this piece of information is not passed on to the sales manager of an individual shop, then the shop will still display the “old” shoes and will not attract the customers' attention effectively. At the end of this process, the blame is sometimes even attributed to the shop assistants, because they are the employees in a direct contact with the customers.[8]

Examples

Richard Fuld, Lehman Brothers CEO

Bankruptcy of Lehman Brothers

When the bank Lehman Brothers went bankrupt in 2008, considerable information about the bank's management was revealed, including the way Richard S. Fuld, Jr., the former CEO, organised the bank. The bank had started to concentrate more and more on excessively risky mortgages; however, neither the employees nor the public were aware of the bank's financial situation.[9] Fuld, together with other managers, had kept a significant amount of essential information secret, as well as lying to the investors and to all other involved parties. Everybody else had thought that Lehman Brothers were involved with a variety of investments, including both safe and risky investments; in reality, though, they had been working with a much more risky portfolio than was appropriate.[10] After the bank became bankrupt, Fuld refused to take the blame for any of these events, even though he was responsible for the concealment of the information.[11]

Titanic sinking

Sinking of the Titanic

Mushroom management can also occur during the handling of one-off, individual situations. When the ship Titanic hit an iceberg, only a few members of the crew were aware that the ship was going to sink. Most of the crewmen were not informed about the seriousness of the situation by the captain, which resulted in chaos and disorganisation. The captain attempted to act on his own, without incorporating the officers into his decisions.[12]

Countermeasures

Sharing information with co-workers and employees is often unavoidable; however, one of the most important tasks for a manager is to differentiate between information that can be shared with others and information that cannot be shared. A company should not share all its information with its employees, because that could be even more damaging. Managers should learn how to distribute information and how to communicate with the people they are responsible for.[13] The best way to avoid mushroom management is transparency.[14]

Good mushroom management

Sometimes, mushroom management can be very helpful if it is handled carefully. This method involves the company's employees being divided into various groups, each of which has all the information which it specifically needs. Meanwhile, the manager is in charge of giving each group the required information. This kind of management is extremely difficult, though, and requires considerable skill.[15]

See also

References

  1. ↑ "Mushroom management". Oxford Reference. Retrieved 20 October 2014.
  2. ↑ Mar, Anna. "Mushroom Management". Simplicable- business guide. Simplicable. Retrieved 22 October 2014.
  3. ↑ Neill, Colin; Laplante, Philip (2006). Antipatterns: Identification, Refactoring, and Management. Boca Raton, Florida: CRS Press. pp. 120–1. Retrieved 22 October 2014.
  4. ↑ "Mushroom Management". ProjectWIki. Retrieved 21 October 2014.
  5. ↑ "Mushroom Management". Changing Minds. Changing Minds. Retrieved 22 October 2014.
  6. ↑ Neill, Colin; Laplante, Phillip (2006). Antipatterns: Identification,Refactoring and Management. Boca Raton, Florida: CRS Press. p. 121. Retrieved 22 October 2014.
  7. ↑ Smith, Gregory. "Mushroom Management- Don't keep your workforce in the dark". ManagerWise. ManagerWise. Retrieved 22 October 2014.
  8. ↑ Neill, Colin; Laplante, Phillip (2006). Antipatterns: Identification,Refactoring and Management. Boca Raton, Florida: CRS Press. p. 121. Retrieved 22 October 2014.
  9. ↑ Harress, Christopher; Caulderwood, Kathleen. "The Death Of Lehman Brothers: What Went Wrong, Who Paid The Price And Who Remained Unscathed Through The Eyes Of Former Vice-President". International Business Times. Retrieved 29 October 2014.
  10. ↑ Montgomery, Ashileigh. "The Dearth of Ethics and the Death of Lehman Brothers". Sevenpillars Institute. Retrieved 29 October 2014.
  11. ↑ Harress, Christopher; Caulderwood, Kathleen. "The Death Of Lehman Brothers: What Went Wrong, Who Paid The Price And Who Remained Unscathed Through The Eyes Of Former Vice-President". International Business Times. Retrieved 29 October 2014.
  12. ↑ Smart, John M. "Saving the Titanic- Crowdsourcing to Find Hard Solutions, and Unlearning to Implement Them". Ever Smart World. John M. Smart. Retrieved 23 October 2014.
  13. ↑ Mar, Anna. "Mushroom Management". Simplicable- Business Guide. Simplicable. Retrieved 22 October 2014.
  14. ↑ Monty, Scott. "Why transparency and authenticity wins in business and in marketing". The Guardian. Retrieved 29 October 2014.
  15. ↑ Munro, Simon. "I suck at mushroom management". EMC Consulting. EMC. Retrieved 22 October 2014.
This article is issued from Wikipedia - version of the Monday, March 21, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.