How a Battle That Shouldn’t Have Started Almost Ended the War in an Afternoon
The first two articles in this series examined two men: Henry Heth, whose assumption-driven advance triggered the engagement at Gettysburg, and Richard Ewell, whose paralysis at Cemetery Hill let the Union army survive it. Each article looked at one leader, one decision, one moment in the cycle of the Adversity Nexus and asked what Epistemic Rigidity was keeping him there.
What I want to do in this article is zoom out.
Because here is the thing I keep coming back to as I work through this material. July 1, 1863, was not really a story about two leadership failures. It was a story about a system that failed. And it failed not because two men made bad decisions on the same day, but because an entire command structure was running the same cognitive framework simultaneously, and that framework had drifted so far from accurate reality assessment that it could not respond to what was actually in front of it.
The Reasoned Leadership framework has a name for this condition. It is called Mass Epistemic Rigidity, and Gettysburg, once you know what to look for, is one of the most complete historical examples of it I have found anywhere.
What Mass Epistemic Rigidity Actually Is
The Reasoned Leadership framework is precise about how Mass Epistemic Rigidity differs from individual Epistemic Rigidity. It is more than a collective version of individual rigidity. It is a systemic condition where hierarchy, tradition, and institutional inertia reinforce intellectual stagnation. Organizations afflicted by it display several defining characteristics: institutional anchoring to outdated operational models even when evidence suggests a need for adaptation; reinforced hierarchical thinking that entrenches rigid decision-making and makes it difficult for dissenting voices to challenge the prevailing norm; suppression of innovation where new approaches are dismissed as impractical or incompatible with existing structures; and cyclical justification of strategic failures where the organization rationalizes poor decisions through selective reasoning rather than correcting them.
Read that list and then look at the Army of Northern Virginia on July 1, 1863.
This was an army that had defeated larger, better-supplied Union forces repeatedly across two years of war. It had done so through aggressive offensive action, through the audacity of its commanders, through an institutional culture that rewarded boldness and trusted its leadership chain to act decisively without waiting for perfect information. Those qualities had produced Fredericksburg, Chancellorsville, and Second Bull Run. They were genuinely exceptional qualities that had built the army’s remarkable record.
But those same qualities, by the summer of 1863, had become the army’s primary cognitive anchor. The success had been so consistent, and the command culture Lee had built around his own authority and judgment had become so deeply ingrained, that the army had lost the structural capacity to accurately assess situations that did not conform to its existing mental model. The institutional anchoring was not to bad principles. It was to principles that had worked brilliantly and had therefore stopped being questioned. And an unquestioned principle, no matter how sound it once was, is exactly how Mass Epistemic Rigidity takes root.
Lee: The Source Code of the System
To understand how Mass Epistemic Rigidity operated in the Army of Northern Virginia on July 1, you have to start with Lee, because he was not just the commanding general. He was the cognitive architecture from which every subordinate’s decision-making descended.
By the summer of 1863, Lee had achieved something that very few military commanders manage: he had become, in the minds of his subordinates, functionally infallible. His record justified enormous respect, and nobody disputes that. But the Einstein Effect, the cognitive bias that describes the undue credibility granted to authoritative or respected sources, had transformed legitimate respect into something far more dangerous inside the Confederate command structure. It had become institutional deference.
The Einstein Effect operates in both directions inside hierarchical organizations. At the top, it produces a leader who over-trusts their own judgment because everyone around them consistently validates it. Dissenting voices become rare, not because the leader actively suppresses them, but because the culture gradually learns that the revered leader’s assessments carry a weight that dissent cannot easily overcome. Below the top, it produces subordinates who unconsciously filter their own assessment of reality through the lens of what the respected leader would think or want, rather than what the situation actually demands.
This is the precise condition that existed in Lee’s army by July 1863. His campaign into Pennsylvania was built on assumptions that were, at minimum, worth examining rigorously: that the army could sustain an extended offensive operation in enemy territory without reliable cavalry intelligence, that another major Confederate victory on Northern soil would break Union political will, and that the army’s fighting qualities would compensate for whatever operational uncertainties arose. Within the command culture Lee had built, largely through the weight of his record and the deference it produced, there was no structural mechanism for those assumptions to be seriously challenged.
A.P. Hill approved Heth’s advance on the morning of July 1 without meaningful pushback, despite the explicit instruction not to bring on a general engagement. The Einstein Effect had done its work at the corps level: Hill’s own confident assessment of the situation was shaped by the army’s inherited belief in its own superiority, a belief installed and validated by Lee across two years of success. Heth made his assumption-driven march without serious reconnaissance for the same reason. The Mass Epistemic Rigidity was not a top-down conspiracy. It was a culture, and cultures shape decisions invisibly.
When Lee himself arrived on the field at Seminary Ridge during the late morning and watched a battle he had not planned unfold in front of him, his own Epistemic Rigidity was already shaping what he saw. His Motivated Reasoning weighted the evidence of Confederate success heavily. His Confirmation Bias filtered out the signals that the Union forces retreating south of town were not broken but reorganizing. His Anchoring Bias, built on two years of his army performing brilliantly in exactly these kinds of fluid engagements, told him the momentum was meaningful and should be pressed. He committed to the engagement. The battle that nobody had planned became the battle that everyone was now fighting.
Three Decision Points, One System Failure
When I look at July 1 through the Mass Epistemic Rigidity lens, what I see is not three separate leadership failures happening to coincide on the same day. I see one systemic failure expressing itself through three distinct decision points.
Heth’s advance was the system initiating contact without adequate intelligence, a direct consequence of an army culture so anchored in its own effectiveness that it had stopped treating information gaps as serious operational variables. Heth did not fail independently. He failed as a product of a command environment in which the absence of cavalry intelligence, which should have signaled genuine uncertainty requiring caution, was treated as a minor logistical inconvenience rather than a warning that the entire operational picture was unreliable.
Lee’s commitment at Seminary Ridge was the system encountering an accidental engagement and choosing to embrace it rather than question it. By the time Lee arrived on the field, the Mass Epistemic Rigidity of the army’s command culture had already shaped the situation into one that looked, through the lens of that culture, like an opportunity rather than a risk. His Motivated Reasoning constructed a compelling internal narrative: the army had caught the Union force in a vulnerable moment, the momentum was with the Confederates, this was the decisive engagement he had come north to find. What that narrative filtered out was the question he most needed to ask: is this actually the ground we want to fight on, and do we know enough about what is in front of us to commit to this?
Ewell’s hesitation at Cemetery Hill was the system encountering a moment that required independent initiative outside the familiar cognitive framework, and freezing. As I examined in Article 2, Ewell’s primary failure was the Einstellung Effect locking him into cautious deliberation when the situation demanded improvised aggression. But the deeper point, in the context of the full system, is that Ewell’s hesitation was itself a product of the army’s Mass Epistemic Rigidity. Lee’s vague “if practicable” order reflected a command culture that had not built the structural capacity for subordinates to exercise bold independent initiative when the commanding general’s guidance was ambiguous. And Ewell, in his first major independent corps action, reached for the familiar solution of careful deliberation precisely because the culture he had operated within had never required him to develop the cognitive independence that the moment demanded.
These were not three men failing separately. They were three expressions of the same organizational condition.
The Union Side: What the Opposite Looks Like
The contrast on the Union side of July 1 is worth examining carefully, not as a simple good-versus-bad comparison, but as an illustration of what the Adversity Nexus predicts about cognitive clarity at different stages of the cycle.
The Army of the Potomac in the summer of 1863 was not an army operating from abundance. It had been repeatedly defeated, had changed commanding generals multiple times in less than a year, and was now operating under Meade, who had held the job for three days and had not yet established anything close to the institutional authority Lee carried. By almost any measure, the Union army was in Stage 1 of the Adversity Nexus: adversity real and immediate, desire for a solution urgent, and no accumulated success generating the complacency that abundance produces.
The Adversity Nexus predicts something specific about Stage 1 and Stage 2: this is where authentic leaders emerge from genuine necessity, where the urgency of the situation cuts through the cognitive noise that accumulates during periods of comfort, and where the Epistemic Rigidity wheel spins more slowly because familiar solutions are not available. That prediction maps almost exactly onto what happened on the Union side of July 1.
Buford read the terrain accurately on the evening of June 30 because he had no abundance of success to generate assumptions about what he would find. He assessed the ground as it actually was and deployed accordingly. Reynolds committed his corps without waiting for complete orders because the existential nature of the situation demanded it. Hancock arrived on Cemetery Hill with almost nothing and manufactured a defense through sheer force of projected confidence, improvising in real time because improvisation was the only tool available. Meade, three days into command he had not sought, was making decisions from necessity rather than inherited expectation.
None of these men were free from bias. Nobody ever is. But the cognitive conditions created by genuine Stage 1 adversity are structurally different from the cognitive conditions created by Stage 5 abundance. When survival is immediate and real, the brain’s threat-detection systems override the pattern-matching shortcuts that Epistemic Rigidity relies on. The Union commanders on Cemetery Hill were not smarter than the Confederate commanders on Seminary Ridge. They were operating from a different stage of the cycle, and that stage was, paradoxically, the more cognitively honest one.
The System’s Final Accounting
By nightfall on July 1, 1863, the Army of Northern Virginia had won a significant tactical victory and walked itself into a strategic trap that would take two more days to fully close.
The Confederate army had driven two Union corps through Gettysburg and off the fields north and west of town. Thousands of prisoners had been taken. By any conventional measure of a day’s fighting, the Confederates had won. But Cemetery Hill, Cemetery Ridge, and Culp’s Hill, the high ground that would define everything that followed, sat in Union hands and was hardening by the hour. The window for taking it by pursuit had opened and closed in ninety minutes without a Confederate division moving toward it.
This is the long-term consequence the framework predicts for organizations afflicted by Mass Epistemic Rigidity: rather than acknowledging mistakes and adapting, they rationalize failures through selective reasoning, reinforcing flawed strategies instead of correcting them. That is precisely what happened as the Confederate army assessed July 1 from the lens of its own command culture. The day looked like success. The narrative of the army’s superiority remained intact. The assumptions that had driven the day’s decisions were not interrogated. They were confirmed.
Lee went to bed on July 1 planning to attack again on July 2. The assumptions that had driven every Confederate decision of the first day, about the army’s invincibility, about the Union army’s fragility, about the irrelevance of intelligence gaps, were all still in place, still unquestioned, still doing the cognitive work that Mass Epistemic Rigidity does so effectively.
The trap was set. The army just could not see it yet.
Next in the series: Article 4, “Longstreet Was Right: Lee’s Refusal and the Flanking Argument,” moves to Day 2 and examines the most consequential strategic disagreement of the entire battle, what the frameworks reveal about why the man with the better argument lost it, and what happens when Mass Epistemic Rigidity meets the one subordinate willing to push back.
This article is part 3 of the 6-part series Three Days at Gettysburg: A Reasoned Leadership Analysis
0 responses to “Three Days at Gettysburg: A Reasoned Leadership Analysis Part 3”