The Military as an Organizational Design Problem

Begin with the course synthesis's central claim: militaries are not exotic, non-human organizations. They are human organizations designed for an unusually severe operating environment, and their operating principles make sense only against that environment. The synthesis compresses the mandate into a single sentence worth keeping on the table all semester:

JP 1 (2013, incorporating Change 1, 2017) supplies the doctrinal grounding. Its theory chapter defines war bluntly — "War is socially sanctioned violence to achieve a political purpose" — and reaches for Clausewitz to characterize the environment: war combines "friction, chance, and uncertainty," which "often combine to cause 'the fog of war,'" placing "a burden on the commander to remain responsive, versatile, and adaptive in real time." The strategic security environment, it says, "is characterized by uncertainty, complexity, rapid change, and persistent conflict," in which "uncertainty, ambiguity, and surprise will dominate the course of regional and global events" (JP 1, ch. I). Note the epistemic stance: uncertainty is not an exception to be engineered away but the permanent operating condition the organization is designed for. Doctrine treats friction the way Simon (1947) treats bounded rationality — as the premise, not the problem.

The course synthesis decomposes this into five environmental conditions. State them precisely, because each one deletes an assumption that classical organization theory relies on:

Now run the classical predictions against these conditions. Each of the four theory anchors makes a claim that survives only partially:

What kind of artifact is doctrine? JP 1's own answer is functional. The purpose of joint doctrine is "to enhance the operational effectiveness of joint forces by providing fundamental principles that guide the employment of US military forces toward a common objective." Its content is distilled experience: "Using historical analysis of the employment of the military instrument of national power in operations and contemporary lessons, these fundamental principles represent what is taught, believed, and advocated as what works best to achieve national objectives" (JP 1, ch. I). And its mechanism is standardization with a stated payoff: doctrine "standardizes terminology, training, relationships, responsibilities, and processes among all US forces to free joint force commanders and their staffs to focus their efforts on solving strategic, operational, and tactical problems" (ch. I, emphasis added). That last clause is Galbraith's information-processing argument in doctrinal prose: standardization is not conformity for its own sake; it is a device for conserving scarce attention and channel capacity so they can be spent on the genuinely uncertain parts of the task.

The authority question is where the design gets subtle. Doctrine must bind — otherwise it cannot standardize — but it must not bind absolutely, or it becomes the predictable script the adversary exploits and the substitute for judgment the environment punishes. JP 1 threads this needle with a precisely worded escape clause:

Notice the structure of the clause: the deviation right is assigned to a specific role (the commander), conditioned on circumstances, and paired with responsibility — deviate, and you own the outcome. This is not weak standardization; it is standardization with a priced exit. Compare Hansen, Nohria & Tierney (1999): doctrine is a codification strategy that explicitly refuses to let the repository replace the person. The judgment stays load-bearing.

JP 1 also positions doctrine inside a three-way taxonomy that the 2013 revision formally established ("a taxonomy relating to policy, strategy, doctrine, and concepts" — Summary of Changes). The distinctions matter because each artifact type has a different relationship to time and to authority — and the system even reserves a pre-doctrinal instrument for the seam between strategy and doctrine: the non-authoritative Joint Doctrine Note 2-19, Strategy (2019), which grounds the strategic level without yet binding the force.

Finally, precedence: "joint doctrine takes precedence over individual Service's doctrine, which must be consistent with joint doctrine" (ch. VI). The knowledge system is itself hierarchical — a capstone, keystone publications beneath it, Service doctrine beneath those — which is why the seminar can treat the doctrine hierarchy as an organizational memory architecture in Walsh & Ungson's (1991) sense. Session 02 takes that up directly; Session 03 examines the factory that produces and revises it.

That hierarchy is not just asserted by the capstone; the layer beneath it declares the relationship in its own voice. Joint Publication 3-0, Joint Operations (2017, incorporating Change 1, 2018) is the keystone operations publication — the pub that tells joint force commanders how to actually run an operation — and it opens by naming its place in the stack:

Read the two documents together and the cascade from charter to execution is legible. JP 1 establishes the organizational logic — jointness, the levels of warfare, the joint functions, unity of command; JP 3-0 carries that same logic into how the force operates, describing the "fundamental keystone constructs—such as unified action and joint functions—that apply regardless of the nature or circumstances of a specific joint operation" (ch. I). Unified action — "the synchronization, coordination, and integration of the activities of governmental and nongovernmental entities to achieve unity of effort" (ch. I) — is the operational form of the same integration problem Section 04 traces in the command structure: where JP 1 downgrades the goal to unity of effort whenever unity of command is impossible, JP 3-0 makes unity of effort across non-military partners the operating discipline of every campaign. And where the classical predictions bent, JP 3-0 records the bend in doctrine's own accounting: it recognizes not JP 1's nine principles of war but twelve "principles of joint operations," having added restraint, perseverance, and legitimacy: "Experience gained in a variety of IW situations has reinforced the value of three additional principles—restraint, perseverance, and legitimacy" (ch. I). The keystone pub is JP 1's design logic under the load of contemporary operations — the principle set grows exactly where the adversarial, legitimacy-constrained environment of Section 02 pressed on it.

The Services are deeply differentiated organizations: distinct operating domains, distinct cultures, distinct statutory duties under Title 10 to organize, train, and equip forces. JP 1 does not fight this differentiation; it builds on it. "All Service components contribute their distinct capabilities to the joint force; however, their interdependence is critical to overall joint effectiveness. Joint interdependence is the purposeful reliance by one Service on another Service's capabilities to maximize complementary and reinforcing effects of both" (ch. I). Jointness "implies cross-Service combination wherein the capability of the joint force is understood to be synergistic, with the sum greater than its parts." This is Lawrence & Lorsch's (1967) finding made statutory: the best performers are simultaneously highly differentiated and highly integrated — and the integration does not happen by goodwill. It is compelled by law (Goldwater-Nichols, 1986), enforced by a doctrine hierarchy, and exercised through a standing command structure.

The structure begins with a deliberate split. "The President and SecDef exercise authority, direction, and control of the Armed Forces through two distinct branches of the chain of C2" (ch. II): an operational branch running President → Secretary of Defense → combatant commanders, for missions and forces assigned to their commands; and an administrative branch running President → Secretary of Defense → Military Department Secretaries → Service forces, for everything else — raising, training, equipping, administering. Every soldier, ship, and squadron sits in both branches at once. The design separates the authority to employ the force from the authority to prepare it, so that warfighting command is unified across Services while institutional stewardship stays with the Services that possess the domain expertise.

Two features of this diagram repay close reading. First, the Chairman of the Joint Chiefs — the highest-ranking officer in the Armed Forces — sits on a dotted line: "the CJCS, however, may not exercise military command over the CCDRs, JCS, or any of the Armed Forces" (ch. III). The nation's senior military professional is by law an advisor and a communications conduit, not a commander. Professional advice is structurally separated from command authority — a deliberate institutional check worth holding against Aghion & Tirole's (1997) formal-versus-real authority distinction: the CJCS holds enormous real authority (agenda, advice, doctrine) and essentially no formal command. Second, unity of command is defined with unusual precision: "all forces operate under a single commander with the requisite authority to direct all forces employed in pursuit of a common purpose," and "two commanders may not exercise the same command relationship over the same force at any one time" (ch. V). Where unity of command is politically impossible — interagency, multinational — doctrine downgrades the goal honestly to unity of effort: "coordination through cooperation and common interests" (ch. V).

Within the operational branch, authority is not a scalar but a typed vocabulary. JP 1 devotes an entire chapter to four command relationships plus supporting authorities, each with a defined scope, a delegation rule, and an exclusion list:

Read as organizational theory, this table is a decision-rights instrument of remarkable resolution. Where a firm might distinguish "solid line" from "dotted line," JP 1 distinguishes at least seven typed relationships, each answering in advance the questions the course synthesis says must never need renegotiation under fire: who commands, what forces, what mission, what may be decided, when authority transfers, who succeeds. And succession is itself pre-scripted: in a commander's absence, "interim command will pass to the deputy commander," and failing that "to the next senior officer present for duty who is eligible to exercise command, regardless of Service affiliation" (ch. IV). Condition 3 — the organization degrades — is answered not by resilience rhetoric but by a default rule that operates automatically when the chain breaks.

That excerpt is the series' thesis in four doctrinal sentences: centralize purpose and priorities; decentralize methods; and note the stated reason — span-of-attention limits, not management fashion. It is bounded rationality as an organizing principle. JP 1's mission-command passage completes it: mission command "empowers individuals to exercise judgment in how they carry out their assigned tasks," relying on "commander's intent" — "a clear and concise expression of the purpose of the operation and the military end state" that lets subordinates act "without further orders, even when operations do not unfold as planned" (ch. V). Command relationships fix who may decide; intent fixes what deciding well means. Session 05 gives this its full treatment as an incomplete-contracting problem.

The three levels of warfare "link tactical actions to achievement of national objectives. There are no finite limits or boundaries between these levels, but they help commanders design and synchronize operations, allocate resources, and assign tasks to the appropriate command" (JP 1, ch. I). Note what doctrine claims for the construct: not that reality is layered, but that the layering is useful — an admission that this is an imposed decomposition, in Simon's (1962) sense, chosen because near-decomposable problems are the only kind bounded agents can manage.

Then doctrine undermines its own tidy picture, deliberately. "With today's constant 24-hour media coverage and easy access to the Internet … a tactical-level plan and resulting action can have severe operational or strategic implications. … an action by one Soldier, Marine, Sailor, or Airman on the battlefield at the tactical level could potentially cause significant disruption to operational and strategic-level planning. … In this sense, during execution all three levels overlap" (ch. I). The decomposition is load-bearing for planning and accountability, and simultaneously known to leak under the information environment's compression. An organization that partitions its problem and documents where the partition fails is doing contingency theory to itself.

The second partition is by intensity. The range of military operations (ROMO) arranges uses of the military instrument "across a continuum of conflict ranging from peace to war" in three broad categories: military engagement, security cooperation, and deterrence (the ongoing shaping activities — deterrence being "a state of mind brought about by the existence of a credible threat of unacceptable counteraction"); crisis response and limited contingency operations; and major operations and campaigns, which "feature a balance among offensive, defensive, and stability operations through six phases: shape, deter, seize initiative, dominate, stabilize, and enable civil authority" (ch. I). The same organization must run church-quiet engagement activities and large-scale combat with the same people and structures — a range-of-demand problem no single Burns-and-Stalker pole could serve.

The third partition is grammatical, and it is the one most transferable to any organization. JP 1 distinguishes three terms most institutions blur. A task is "a clearly defined action or activity assigned to an individual or organization … imposed by an appropriate authority." A function is "the broad, general, and enduring role for which an organization is designed, equipped, and trained" — what the organization is for. A mission "entails the task, together with the purpose" (ch. I). The mission's mandatory five-part form — who, what, when, where, and above all why — hard-wires purpose into every assignment. This is the grammatical precondition for decentralized execution: a subordinate who has only a task must ask for new orders when circumstances change; a subordinate who holds task-plus-purpose can re-derive correct action locally. The five-part mission statement is intent made compulsory at every echelon.

JP 1 calls the joint force "a values based organization" whose leaders' "character, professionalism, and values … have proven to be vital for operational success" (ch. I) — and then, unusually for a command document, devotes an appendix to what that means. "A professional is a person of both character and competence" (App. B). The values are enumerated — "Duty, honor, courage, integrity, and selfless service are the calling cards of the profession of arms" — and defined operationally, not ornamentally: integrity is "the cornerstone for building trust"; moral courage is "the ability to act rightly in the face of popular opposition, or discouragement"; and teamwork "requires delegation of authority commensurate with responsibility," because delegation "unleashes the best efforts and greatest initiative among all members of military teams" (App. B). Read functionally, the values appendix is the trust-production system that makes the decentralized execution of Section 04 safe: mission command runs on "a high degree of mutual trust," and trust "results from honest efforts to learn about and understand the capabilities that each member brings … demonstrated competence, and planning and training together" (ch. V). Normative control is not the soft alternative to structure here; it is the enabling condition for the structure's most important feature.

Condition 5 gets the same double treatment — structural and normative. Structurally, civilian control is wired into every chain in Section 04: both branches begin with the President; orders reach combatant commanders through the Secretary of Defense; the senior officer commands nothing. Legally, "the Armed Forces of the United States will adhere to the law of war … during all military operations," a body of law "binding on the US and its individual citizens" (ch. I) — obedience is owed to lawful authority, not to superiors as persons. The course synthesis draws the professional consequence: candid advice before the decision, objection when orders are unlawful, disciplined execution once a lawful decision is made, accountability for both giving and carrying out orders. And it names the failure modes on both sides — insubordination, where personal agreement becomes a precondition for action, and unthinking obedience, where members surrender legal and moral agency. "A capable military requires obedience without servility."

The synthesis's deepest structural claim is that mission primacy imposes a lexical ordering on the organization's considerations — and that the ordering is what distinguishes military from commercial reasoning:

1. 01 First consideration
   Lawful political purpose. The mission is not self-justifying; it inherits legitimacy from civilian direction and law. Remove this rung and mission primacy degenerates into "results justify anything" — the failure mode the synthesis flags explicitly.
2. 02 Second consideration
   Mission accomplishment. The question is not "is the expected return worth the cost?" but "what must be accomplished, what risks are necessary, and what resources must be committed?" Units and departments exist to contribute to the common objective, not to maximize local performance indicators.
3. 03 Third consideration
   Preservation of the force. Not disposability: competent leadership conserves lives and resources "because they are morally important and operationally necessary." But preservation ranks below mission — the inversion of an ordinary employer's duty structure, and the reason conditions 4 and 5 demand so much legitimacy.
4. 04 Fourth consideration
   Efficiency and administrative convenience. Last, explicitly. Readiness logic preserves surge capacity, redundancy, and reserves that peacetime efficiency logic would cut — the civilian-efficiency versus military-readiness table in the synthesis is the clearest single statement of the difference.

NDP 1 (2020) shows the same substrate in a Service voice. Its command philosophy chapter grounds mission command not in regulation but in geography and heritage: "In the not-too-distant past, Navy and Coast Guard sea captains and Marine commanders had to operate for months at a time with minimal communication back to higher headquarters. This cultivated a rich heritage of mission command that is a particular necessity in naval warfare" (NDP 1, ch. I). The epigraph it chooses is the most compact statement of the doctrine–training–initiative triangle in the corpus:

Finally, the synthesis insists the whole design is a system of tensions to be continually balanced, not rules to be applied. The seminar returns to these six paradoxes all term; state them now as the course's standing agenda:

1. Degree or kind? Firms also face intelligent, adaptive opponents — competitors reverse-engineer strategies and poach talent. Is the military's "intelligent adversary" condition a difference in kind from market competition, or only in stakes? Identify precisely which classical assumption fails under an adversary that targets the organization's structure (its leaders, channels, and procedures) rather than merely its market position — and whether any firm faces that.
2. Integration by statute. Lawrence & Lorsch found that high performers pair differentiation with costly integration achieved through internal mechanisms. The U.S. answer — Goldwater-Nichols — imposed integration by law over Service resistance. Is the joint construct evidence that sufficiently deep differentiation makes voluntary integration impossible? What is the civilian analogue of "jointness is not automatic and it is perishable"?
3. The escape clause. Doctrine binds "except when, in the judgment of the commander, exceptional circumstances dictate otherwise." Does that clause make doctrine stronger organizational memory (because it stays honest about its own limits) or weaker (because every deviation is self-authorizing after the fact)? Compare Hansen, Nohria & Tierney's warning against straddling codification and personalization: is doctrine a straddle that works, and if so, why?
4. The matrix that dares not speak its name. Every service member sits in two chains of command — operational and administrative. Militaries supposedly cannot tolerate matrix ambiguity, yet this is a matrix, resolved by typing the authorities (COCOM/OPCON vs. ADCON) so finely that the chains rarely claim the same decision. Could a firm adopt "typed authority" instead of dotted-line ambiguity? What breaks first?
5. Advice without command. The Chairman — the highest-ranking officer — commands no forces by law. Aghion & Tirole would say he holds real authority without formal authority. What does this separation buy the principal (the President), what does it cost, and why do firms almost never split their senior expert's advice from line authority this cleanly?
6. Levels under compression. JP 1 concedes that one tactical actor "could potentially cause significant disruption to operational and strategic-level planning." If the information environment collapses the levels during execution, is the three-level construct still carving the organization at its joints — or is it retained because accountability requires a decomposition even when causality ignores it?
7. Values as design or as myth. JP 1 calls the joint force "a values based organization" and devotes an appendix to duty, honor, courage, integrity, and selfless service. Meyer & Rowan (1977) would ask whether this is load-bearing normative control (the trust substrate that makes decentralized execution safe) or institutional myth decoupled from practice. What evidence, internal to the documents we read, could distinguish the two?
8. The transfer test. Take an organization you know — hospital, startup, platform firm, open-source project. Which of the five environmental conditions does it actually face, at what intensity? Using the synthesis's Part V, name one military practice it should borrow and one it should refuse — and state the environmental condition whose absence justifies the refusal.