Because that's how every single part of New Eden that was lost in 2011 was lost....All of it was due to internal rot. - Ripard Teg: "Didn't Want that Space Anyway"
'Rot' is the most common diagnosis given to explain the collapse of an Eve alliance or coalition. It is also the most useless. It is a term so generic that it can have entirely different meanings to the speaker and listener depending upon what's in their minds at the time. Further, in one sense or another it is so broadly applicable to almost any failscade that has ever occurred in New Eden that in most cases it is not a very meaningful indicator of root cause.
But it has the advantage of being safe.
Anyone from the bitterest vet to the most callow pubbie can look at the wreckage of a nullsec alliance, nod their head knowingly, say "Well, this was obviously a bad case of rot." and be reasonably confident their thesis will not be disproved. You see, if one defines rot very loosely as, for example, a loss of organizational integrity, the word describes the very phenomenon for which it was intended to provide a causal explanation. It becomes tautology; The loss of organizational integrity invariably accompanies organizational collapse because organizational collapse is, in effect, the loss of organizational integrity.
When Atlas Alliance failscaded in the Summer of 2010, the cause was largely attributed to internal rot. Which is to say that Atlas Alliance failscaded and nobody could be bothered to take a close look at the root causes. Looking at their collapse in hindsight, it's evident that a number of factors were in play. Atlas was structured with responsibility for major decision, particularly military decisions, in the hands of one person and the rest of the leadership tasked with caretaker/maintenance roles. This created a single point of failure in their leadership structure. Secondly, the advent of the Dominion sovereignty mechanics along with the supercarrier buff had profoundly altered the strategic and tactical nature of nullsec sov warfare. The Atlas military leadership was slow to recognize adapt to this new military reality. Finally, in the absence of attention from the leadership, key industrial interests
within the alliance had become distanced from the core interests of Atlas.
Soon after the collapse of Atlas, Against All Authorities came under attack by White Noise, Pandemic Legion, The Initiative[DOT] and IT Alliance. Once again, the defenders appeared to be quickly overwhelmed by the invaders and, with -A- retreating from their space and a failscade appearing imminent, it looked very much like a repeat of the Atlas collapse. With -A-'s demise assumed, the blogosphere and podcast universe wrote and broadcast the alliance's obituaries with 'rot' as the cause of death.
Of course we all know in hindsight that -A-'s leadership had decided to to retreat the bulk of their PvP strength into NPC nullsec and nearby Stain Empire space rather than allow those forces to be ground down in an unlikely defense of Catch, Teneferis, et al. -A- gambled that their organization was hardy enough to hold the troops together in exile until the enemy had dispersed and could be attacked and destroyed piecemeal. It was a daring move that flew in the face of nullsec strategic orthodoxy of the time, and its success can be attributed in no small part to the strength of the same -A- organization the blogosphere had declared shot through with rot.
Now, in taking back their lost territory, -A- faced primarily The Initiative[DOT] and their two vassal alliances, Dead Terrorists(DT) and CO2, along with an attempted "all in" intervention by IT Alliance. The fates of those four alliances are instructive when discussing rot as the exclusive cause of territorial changeover and alliance failscade.
After the invasion, DT and CO2 were settled into former -A- space between Initiative's new home in Catch and the Southern Russian alliances in order to serve as a buffer between the Initiative and the potential hostiles on the southern flank. DT and CO2 alliances were relatively new to nullsec, CO2 having prior experience in Providence and DT fresh out of lowsec. The Initiative appears to assumed that -A- was done for, Stain Empire and Red Overlord were only a marginal threat, and that CO2 and DT were capable of dealing with any trouble coming from that direction.
When the -A- counteroffensive, supported by Stain and Red Overlord, did occur, it became quickly evident that the Initiative had completely misjudged the strategic situation. As I described in Noblesse Oblige
, Initiative compounded that error by a complete mishandling of events at almost every level. DT, new to nullsec warfare and fighting against the seasoned Southern Russians, were quickly overwhelmed and failscaded. CO2 held on longer but was forced to evacuate Impass soon after when their defense of that region collapsed. While CO2 managed to avoid a complete failscade, they were no longer effective as a combat unit by the time the order to bug out was given, and their organization was crippled by internal turmoil in the immediate aftermath of their loss.
Rot as its conventionally understood assumes decay of a mature organization over time owing to a neglect of organizational qualities that made it successful in the first place, or by an accrual of factors that serve to break down or undermine the qualities needed to maintain a robust organization. Both CO2 and DT were relatively young alliances, and neither had been sitting complacently in their new territories for very long before -A- and Stain struck back. They lost territory to the counterattack and their organizations lost functional integrity, but neither suffered from 'rot' as it's conventionally understood.
The Initiative, while it made strategic and managerial blunders, did not do so because of deterioration in their organization due to rot. Relative to their opponents they were a young alliance and had, only months before, been a key player in the successful invasion of -A- space. The leadership of a young and healthy organization made mistakes and bad decisions. However, that doesn't mean the organization has succumbed to rot, but speaks pre-existing organizational weaknesses having to do with factors such as inexperience and nothing to do with the decay of a formerly robust organization over time.
Which brings us to IT Alliance.
As most of you know, IT Alliance was cobbled together from the wreckage of Band of Brothers (BoB) after the latter was disbanded from within by a turncoat director. Though regarded as effectively the same organization as BoB, IT Alliance's structure and personnel included fundamental changes from that of its predecessor. Over time internal reaction and response to those changes downgraded the overall effectiveness and coherence of the alliance. By the time of their "all in" intervention in support of The Initiative, nominal loyalty to SirMolle was the only thing holding IT Alliance together; although his effective control of that organization had diminished over time. A number of factions with incompatible agendas had developed within the alliance; their leadership largely at odds with each other and more interested in their rivals' failure than in IT Alliance's success.
Meant to force the alliance to pull together, IT Alliance's "all-in" intervention in December of 2010 on behalf of The Initiative served to exacerbate schisms within the organization and revealed the dysfunction beneath IT Alliance's facade of strength and unity. Within a week, Test Alliance's invasion of Fountain supported by Goonswarm forced IT Alliance to abandon
The Initiative to its fate. IT Alliance's loss at PQNY-Y
in the Fountain campaign showed how undermined SirMolle's alliance had become. The subsequent debacle at Z3OS-A was, for all intents and purposes, IT Alliance's death stroke. Though the enemy had not taken Delve and the alliance formerly known as BoB lingered on paper for a time, IT Alliance had come to its end.
In the case of IT Alliance one can reasonably call out rot as the reason the alliance lost its nullsec territory and dissolved. However, rot is still a symptom. If one wanted to understand or communicate meaningful information as to why IT Alliance folded, 'rot' as a stand-alone diagnosis doesn't deliver much in the way of useful information.
When confronted with events for which we don't know the precise cause, humans tend to assign causes in very broad and sometimes misleading terms. Bygone diagnoses like "brain fever", "vapors" and "humour" may have been more or less meaningless, but they made the people of that time feel a little less helpless in the face of illness or death. However, at the end of the day they meant little more than "I don't know" when it came to determining a cause.
"Rot" has become a convenient shorthand used when we wish to forgo deeper analysis, or lack the inputs or insight needed to do deeper analysis. It has become a one-size-fits-all diagnosis that is, more often than not, ignorance or indolence masquerading as insight. Next time someone tries to palm it off as obvious unvarnished truth, politely ask them to define their terms and defend their argument.