4 ms·
I've seen a number of mutiny attempts - some were famously successful, some worked out exactly as you would guess a "mutiny" would when their leader discovered.
by ghshephard 14y ago
I've seen a number of mutiny attempts - some were famously successful, some worked out exactly as you would guess a "mutiny" would when their leader discovered.
In one mutiny, during a pretty significant re-org/layoffs, part of our organization had been sold to another (perceived to be inferior) company - the majority of the organization (that hadn't been laid off) - was just happy to still have a job, but a select group of technical employees decided (under the direction of a strong ring leader) - that they would not go to the other company. The ringleader was able to get five or six key technical employees to mutiny with him, and that would have been sufficient to jeopardize ongoing operations. His demands were met, and they were able to stay with initial company. No retribution ever occurred, and they had several successful years as employees.
Another attempt at clear-cut mutiny that I've seen, was a technical leader who was not fond of his manager, reach out to a competing organization (In a clear cut Red/Blue scenario) in the company, and volunteered to "take all his employees over" to that organization. The manager, for whatever reason, forwarded the email to the technical leader's manager, and that technical leader was then terminated the next morning for "insubordination." - Over the next two to three months every single member of that team resigned their jobs in protest, causing disruption for the next several quarters at the company. Mutiny both failed, and caused great disruption to the company.
The OP article is pretty good - it captures pretty much all of the elements that make for mutiny, and the circumstances in which it can be successful, and how it takes place.
- speeder 14y agoI saw a preemptive counter-mutiny once that ended badly... One person was leader of a newly formed team, and a kind of star programmer (that actually delivered). That person started to bypass the most direct boss, and talk directly to the CEO, frequently. So we have a CEO that like the "victim", and a person between CEO and "victim" that want to get rid of the "victim" because he is a potential threat. Then "victim" has some health issues, and start to code much slower... the "boss" attempts to fire him, but CEO rescue him. Then "boss" awaits for CEO go some months later to a meeting, asks "victim" to show his finished project (the deadline was still next week, but "boss" claimed he could review now), declares it as failed, and fire him in a very public way, forcing him to exit the building with all of his stuff immediately and leave all his credentials and keys behind. Also "boss" stealthly sets up some e-mail filter, so "victim" cannot mail the CEO. Other employees realized what happened, and most of them quit (Even several ones that had nothing to do with the "victim") "boss" gambled, he was the favourite of CEO, and he knew that a public firing could not be undone by the CEO, because the CEO would not do anything that looked like a public punishment... Indeed, CEO did nothing, except watch his ship almost sink (it did not sunk, they could hire another team after about a year and a half...)