A Three-Layer Analysis (TLA) of Livy, History of Rome, Book 7
1. Question
In Livy’s History of Rome from its Foundation, Book VII, the Roman army led by the consul Aulus Cornelius entered a dangerous position in mountainous Samnite territory.
The Roman army was large, but it could no longer use its strength effectively.
It had entered a deep valley, while the Samnites controlled the surrounding high ground. As a result, the Romans faced serious limits:
- they could not advance safely;
- they could not retreat safely;
- they could not form a wide battle line;
- cavalry could not maneuver effectively;
- reserves were difficult to deploy;
- the baggage train reduced mobility.
At this moment, the military tribune Publius Decius identified an unoccupied hill overlooking the enemy position and occupied it with a small detachment.
The detachment did not defeat the main Samnite army.
Yet it played a decisive role in saving the Roman main force.
Why could such a small force have such a large effect?
This study examines the question through Three Layer Analysis, or TLA, and OS Organizational Design Theory, or OSODT.
2. Abstract
The main conclusion of this study is that Decius’s small detachment saved the Roman army not by defeating the Samnites through superior numbers, but by occupying a critical control point, dividing enemy attention, changing enemy deployment, and creating time for the Roman main force to escape.
Cornelius’s army did not suffer from a shortage of soldiers.
Its real problem was:
the inability to convert its existing military resources into executable action.
The Roman army had lost operational options.
It could not easily:
- move forward;
- withdraw;
- deploy;
- use cavalry;
- employ reserves.
Decius identified an unoccupied hill that:
- overlooked the enemy camp;
- could be reached by light troops;
- could threaten the enemy’s side or rear;
- could not easily be ignored by the Samnites.
Once Decius occupied the hill, the Samnites faced two problems:
Attack the Roman main force in the valley
or:
Respond to Decius’s force on the hill.
This divided their attention.
The main Roman army gained time to escape.
From an OSODT perspective, Decius’s detachment was not simply a small combat unit.
It was:
a high leverage local application activated at the critical failure point of the entire military system.
The central principle is:
A small application can create system level effects when it is connected to a high value control point and given a limited mission that directly removes the cause of system failure.
3. Research Method
This study uses Three Layer Analysis, or TLA.
Layer1: Fact
Layer1 extracts the main events from Livy’s Book VII:
- the crisis of Cornelius’s army in the mountains;
- Decius’s discovery of an unoccupied hill;
- occupation of the hill by light troops;
- division of Samnite attention;
- escape of the Roman main force;
- isolation of Decius’s detachment;
- reconnaissance of enemy positions;
- night breakout;
- reuse of the information after the detachment returned.
Layer2: Order
Layer2 converts these events into structure.
The analysis focuses on:
- Role;
- Logic;
- Interface;
- Failure and Risk;
- Purpose and Value;
- Judgment Criterion.
Special attention is given to:
- control points;
- limited local objectives;
- mobility;
- division of enemy attention;
- creation of time;
- distribution of risk;
- intermediate command;
- recovery of information;
- preservation of the main force.
Layer3: Insight
Layer3 connects the structure to OSODT.
The main analytical question is:
Why can a small execution unit create an effect far greater than its size when it is placed at the correct system level control point?
4. Layer1: Fact
4.1 The Roman Main Force Was Not Short of Soldiers
Cornelius’s army still had many soldiers.
However, its position in the valley prevented those soldiers from being used effectively.
The army could not easily:
- widen its battle line;
- use cavalry;
- move reserves forward;
- retreat with the baggage;
- maneuver as a large formation.
The problem was therefore not:
lack of military resources.
It was:
loss of the path through which those resources could be used.
Decius’s role was not to add more combat power.
It was to make the main force capable of moving again.
4.2 Decius Looked at the Structure of the Battlefield
A conventional battlefield response might focus on:
- enemy numbers;
- enemy formation;
- a point for frontal attack.
Decius instead noticed:
an unoccupied hill overlooking the enemy position.
The hill had several important features:
- it gave a view of the enemy;
- it gave a view of the Roman main force;
- it could threaten the enemy from another direction;
- light troops could reach it quickly;
- the Samnites had not yet occupied it.
Decius therefore identified an unused environmental resource.
4.3 The Hill Was a Control Point over Enemy Decision Making
The value of the hill was not only physical elevation.
If the Romans held it, the Samnites had to consider several risks:
- Roman observation of their camp;
- possible flank attack;
- possible connection with the main Roman force;
- possible threat to movement routes;
- possible use as a point for reinforcement.
Therefore, the Samnites could not simply ignore Decius’s force.
A small force could create a large response because of where it was located.
4.4 Small Size Increased Mobility
The hill was difficult for a large force with baggage to reach.
But a light detachment could climb it.
This made small size an advantage.
The detachment was:
- light;
- fast;
- less visible;
- suited to narrow terrain;
- focused on one mission.
Therefore:
small scale did not mean low capability. It produced a different type of capability.
4.5 The Mission Was Narrowly Defined
Decius’s detachment did not have to:
- destroy the Samnite army;
- control the entire valley;
- recover the baggage;
- hold the area for a long period.
Its mission was limited to:
- occupy the hill;
- draw enemy attention;
- create time for the main force to escape.
Because the mission was limited, a small force could perform it.
4.6 The Detachment Divided Samnite Attention
Before Decius occupied the hill, the Samnites could concentrate on the Roman main force in the valley.
After the hill was occupied, the Samnites faced a new choice.
Option A
Attack the Roman main force.
But then leave Decius’s force on the high ground.
Option B
Attack Decius’s detachment.
But then reduce pressure on the Roman main force.
This decision problem divided Samnite concentration.
4.7 The Detachment Created Time
The most important resource produced by Decius’s force was not land or manpower.
It was time.
The Roman main force needed time to:
- reorganize;
- move toward the escape route;
- preserve formation;
- leave the valley.
The Samnite response to Decius delayed pressure on the main Roman force.
Therefore:
the detachment bought time for the larger system.
4.8 The Main Force and the Detachment Performed Different Missions in Parallel
After Decius moved to the hill, the Roman army was no longer performing only one action.
Main Force
- escape from the valley;
- preserve the army;
- reorganize the formation.
Decius’s Detachment
- hold the hill;
- attract enemy attention;
- delay enemy pressure.
This parallel execution increased the number of actions available to the Roman army.
4.9 The Detachment Accepted Concentrated Risk
Occupying the hill separated Decius’s force from the main army.
The detachment could itself be surrounded and destroyed.
The structure was:
Keep Everyone Together
→ Risk Losing the Entire Army
versus:
Separate a Small Force
→ Concentrate Risk Locally
→ Increase the Survival Chance of the Main Force
This was not only an act of courage.
It was a form of risk allocation.
4.10 The Detachment Was Not Designed as a Disposable Unit
After the main force escaped, Decius did not simply accept the destruction of his own force.
He personally reconnoitered:
- enemy positions;
- the state of the encirclement;
- security weaknesses;
- possible escape routes.
He then organized a night breakout before the Samnite encirclement was complete.
The operation therefore included:
deployment
and:
recovery.
4.11 Decius Updated His Decisions after the Situation Changed
The situation after the main army escaped was different from the situation when Decius first occupied the hill.
Decius did not continue following the original action mechanically.
He reassessed:
- enemy deployment;
- night security;
- open routes;
- timing.
The method changed while the higher purpose remained the same.
4.12 The Night Breakout Avoided the Enemy’s Strongest Conditions
Decius did not attempt to break out through a full daylight frontal battle.
He chose the night, when:
- enemy visibility was lower;
- gaps in the encirclement could be used;
- a small quiet force had an advantage;
- direct confrontation could be reduced.
Night movement also created risks for the Romans.
Therefore Decius used controlled and secret communication to keep the detachment synchronized.
4.13 The Return of the Detachment Helped Restore Morale
The return of Decius’s force had value beyond simple manpower.
It showed the larger Roman army that:
- field judgment had worked;
- the isolated detachment had not been abandoned;
- the Samnite system had weaknesses;
- survival and counterattack remained possible.
The return therefore helped restore confidence and morale.
4.14 The Information Gathered by the Detachment Was Reused
Decius’s detachment also returned with information about:
- terrain;
- enemy positions;
- routes;
- security conditions.
The Roman army later used improved knowledge of the mountain environment to approach and attack the Samnites.
The local rescue operation therefore produced value beyond immediate survival.
5. Layer2: Order
5.1 The Main Crisis Was Loss of an Execution Path
The Roman army still had resources.
But the path between:
Resource
and:
Effective Action
had failed.
Therefore:
A large organization can stop functioning even while it still possesses resources if it loses the path through which those resources can be applied to the objective.
5.2 In Crisis, Identify the Failure Point Rather than Attack the Whole Problem
Decius did not try to solve:
the entire Samnite problem.
He identified:
why the Roman army could not move.
The failure point was created by:
- enemy concentration;
- high ground control;
- loss of Roman movement.
The unoccupied hill offered a way to break that structure.
5.3 Small Resources Can Produce Large Effects at a Control Point
The hill was a critical node.
Control of that node affected:
- enemy perception;
- enemy deployment;
- enemy timing.
Therefore:
The effect of a resource depends not only on its size, but also on the leverage of the point where it is applied.
5.4 Small Units Need Local Objectives
A small detachment should not receive the entire system level objective.
Instead, the larger problem should be decomposed.
The mission should be:
correct the specific point that prevents the entire system from functioning.
This was the structure of Decius’s mission.
5.5 Dividing Enemy Concentration Can Restore Freedom of Action
It may not be necessary to destroy an opponent.
It may be enough to create a new problem that cannot be ignored.
Therefore:
Creating multiple simultaneous demands can divide an opponent’s attention, judgment, and resources.
5.6 Time Can Be Created as an Operational Resource
Decius did not directly increase the main army’s soldiers or supplies.
He increased the time available for escape.
Therefore:
In crisis, buying time can be a decisive form of resource creation.
5.7 Parallel Execution Increases the Organization’s Action Space
The main force and the detachment performed different local missions.
This changed the system from:
one organization performing one action
to:
one organization performing several coordinated actions.
Therefore:
Role differentiation can expand the total action space of the system.
5.8 Risk Does Not Always Need to Be Distributed Equally
When the entire system faces destruction, evenly preserving risk across all units may be impossible.
A more rational design can be:
concentrate a high risk mission in a limited package
in order to:
reduce the total system risk.
However, this must not become routine sacrifice.
5.9 High Risk Applications Need Recovery Design
Decius’s operation included a plan for the survival of the detachment.
Therefore:
A healthy high risk application should define not only deployment conditions, but also termination, withdrawal, and recovery conditions.
5.10 Local Autonomy Means Changing Means while Preserving Purpose
Decius changed his method as the situation changed.
He did not change the higher purpose.
Therefore:
Healthy field autonomy means preserving the approved purpose while updating the means according to local conditions.
5.11 Local Information Should Return to the Higher OS
The information collected during the detachment mission was returned to the main force and later reused.
Therefore:
A local success becomes organizational capability only when its information and learning are reconnected to the higher OS.
5.12 Intermediate Command Can Correct Higher Level Error
The consul held supreme command.
But the initial movement into the dangerous terrain created the crisis.
Decius, at an intermediate command level:
- recognized the failure;
- proposed a correction;
- formed a local application;
- personally executed it.
Therefore:
The value of intermediate command is not only transmitting instructions. It also includes correcting higher level failure in order to preserve the higher purpose.
6. Layer3: Insight
6.1 A Small Application Can Create System Level Effects at the Right Control Point
The first major insight is:
A small application can generate effects much larger than its resource size when it is connected to a critical control point of the whole system.
Decius’s leverage came from position, not numbers.
6.2 Crisis Resolution Does Not Mean Solving the Entire Problem
A small unit could not defeat the entire Samnite army.
It did not need to.
It only needed to remove the condition that prevented the Roman main force from acting.
Therefore:
In crisis, the problem should be decomposed until a local correction can restore system movement.
6.3 Small Scale Can Produce a Different Type of H
Large scale creates:
- mass;
- endurance;
- reserve capacity.
Small scale can create:
- speed;
- stealth;
- terrain access;
- narrow mission focus.
Therefore:
Scale is both a capability and a constraint.
6.4 Influence Depends on the Response Forced on the Opponent
Decius’s force was small, but the Samnites could not ignore it.
Therefore:
Influence can be measured not only by the size of the acting unit, but by how much the opponent must change its own behavior in response.
6.5 Changing the Enemy’s Decision Structure Is an Operational Effect
The detachment changed the question facing the Samnites.
Instead of asking only:
How do we destroy the Roman main force?
they also had to ask:
What do we do about the Roman force on the hill?
Therefore:
Changing an opponent’s decision structure can itself function as an attack.
6.6 Time Has High Leverage in Crisis
A small delay may separate:
destruction
from:
escape.
Therefore:
Time can become more valuable than additional manpower when the main system needs only a short window to reposition.
6.7 Parallel Execution Expands System Options
When every actor performs the same action, the organization may remain trapped.
Different local missions create more possible system states.
Therefore:
In complex crises, coordinated parallel execution can be stronger than uniform action.
6.8 Concentrated Local Risk Can Reduce Total System Risk
A high risk local mission can be justified when:
- the whole system faces greater loss;
- the mission is clearly limited;
- the expected system benefit is high;
- recovery is designed.
Thus:
Local risk concentration can be a tool for total risk reduction.
6.9 Heroic Action Must Be Converted into Reproducible Structure
The courage of Decius mattered.
But courage alone does not explain the result.
The operation succeeded because:
- the control point had high value;
- light troops were selected;
- the mission was limited;
- the enemy could not ignore the threat;
- the main force used the opportunity;
- withdrawal was designed;
- information was returned.
Therefore:
Heroic success becomes organizational capability only when its structural conditions are identified and made reproducible.
6.10 Intermediate Roles Can Function as Field Architects
Decius did more than execute a received order.
He:
- detected the system failure;
- found an unused environmental resource;
- designed a local intervention;
- allocated risk;
- collected information;
- restored system continuity.
In this sense:
An intermediate role can become a field architect that redesigns local structure in order to protect the higher OS.
6.11 Leverage Model for a Small Detachment
The operational effect of Decius’s detachment can be expressed conceptually as follows:
Operational Effect of a Small Detachment
= Value of the Control Point
× Mobility
× Degree of Enemy Attention Diversion
× Alignment with the Main Force
× Time Created
A small unit can have system level impact when:
- the control point is important;
- the unit can reach it quickly;
- the opponent cannot ignore it;
- the main force uses the opportunity;
- enough time is created.
6.12 Final Insight
The final insight of this study is:
Decius’s small detachment played a decisive role in saving the Roman army because it was placed at a high leverage control point that directly corrected the cause of the army’s paralysis.
Cornelius’s army suffered not from:
lack of soldiers
but from:
lack of operational options.
Decius’s detachment created the following sequence:
Occupy Unused High Ground
→ Create a New Threat
→ Divide Enemy Attention
→ Change Enemy Deployment
→ Reduce Pressure on the Main Force
→ Create Time
→ Restore the Main Force’s Escape Option
Therefore, the decisive value of the detachment was not that:
a few soldiers killed many enemies.
It was that:
a few soldiers changed the structure of the battlefield and restored the action space of the entire Roman army.
7. Implications for Modern Organizations
7.1 Do Not Try to Solve a Large Crisis All at Once
A company may face problems such as:
- declining sales;
- organizational exhaustion;
- customer loss;
- project failure.
The entire problem may look too large.
But one bottleneck may be preventing the system from moving.
The first task is therefore:
identify the critical failure point.
7.2 Place Small Teams at High Leverage Points
Instead of moving the entire organization, a small team may be more effective when assigned to:
- a critical customer;
- a bottleneck process;
- a key technical dependency;
- an information interface.
7.3 Give Small Teams Limited Missions
A small team should not be told:
fix the whole company.
It should receive a clear local objective such as:
- restore this customer interface;
- remove this bottleneck;
- stabilize this process;
- recover this information flow.
7.4 Buying Time Can Be a Valuable Crisis Strategy
A temporary measure can still have high value if it creates time for the main system to reorganize.
Examples include:
- extending cash runway;
- temporarily stabilizing a failing service;
- reducing customer loss;
- delaying a noncritical launch.
7.5 Middle Managers Should Be Able to Correct Local Failure
If a top level plan no longer fits reality, middle management should not be limited to repeating instructions.
It should be able to:
- detect problems;
- propose alternatives;
- activate limited corrective action;
- escalate when necessary.
7.6 High Risk Projects Need Exit Conditions
For:
- pilot projects;
- emergency teams;
- new market experiments;
organizations should define:
- success conditions;
- stop conditions;
- withdrawal conditions;
- recovery of people and resources.
7.7 Return Local Learning to the Main Organization
A successful small team should return:
- procedures;
- judgment criteria;
- customer information;
- risk information;
- lessons learned.
Otherwise, local success remains isolated.
8. Conclusion
The action of Publius Decius is easy to read as a story of heroic self sacrifice.
But from an organizational design perspective, courage alone does not explain why the operation succeeded.
Cornelius’s army was large.
But after entering the valley and losing control of the high ground, it could no longer convert its military resources into effective action.
The Roman problem was not:
insufficient force.
It was:
the loss of the execution path through which force could be used.
Adding more soldiers to the same valley would not solve the underlying problem.
The structure of the battlefield had to change.
Decius identified an unoccupied hill.
He then placed:
- a small;
- light;
- fast;
- mission focused
detachment on that control point.
This created a chain:
Enemy Perception Changes
→ Enemy Deployment Changes
→ Pressure on the Main Force Falls
→ Time Is Created
→ The Main Force Escapes
→ Roman Operational Options Return
From an OSODT perspective, this leads to an important general principle:
Even a small application can produce an effect far greater than its resource size when it is correctly connected to a control point of the whole system.
A second principle is equally important:
In crisis, a small team should not be asked to solve the entire system problem. The larger problem should be decomposed, and the small team should correct the specific failure point that prevents the system from functioning.
Decius’s detachment was also not treated as a purely disposable unit.
After the main force escaped, Decius:
- updated his recognition of the battlefield;
- reconnoitered escape routes;
- organized secure communication;
- conducted a night breakout;
- returned information to the main army.
Therefore:
A healthy high risk local application should be designed from deployment through withdrawal, recovery, and knowledge return.
The case also shows the value of intermediate command.
The highest commander’s earlier decision had placed the Roman army in danger.
Yet an intermediate role:
- recognized the failure;
- identified an unused resource;
- designed a corrective operation;
- restored operational freedom.
For this reason, Publius Decius should not be understood only as a brave officer.
From an OSODT perspective, he functioned as a field architect who detected the failure point of the Roman military OS, activated a high leverage local application, and restored the continuity and action space of the entire army.
9. Sources
- Livy, History of Rome from its Foundation, Book VII. Japanese edition, Kyoto University Press, 2008.
- OS Organizational Design Theory, R1.36.05.00.
- TLA Layer1, Livy Book VII.
- TLA Layer2, Livy Book VII.
- TLA Layer3 29, Livy Book VII.
- TLA Layer2, OS Organizational Design Theory R1.36.05.00.