In the modern workplace, meetings are treated like weather: unavoidable, sometimes irritating, and rarely examined closely enough to understand why they work—or why they fail. Yet the basic mechanics of how groups talk, decide, and move forward were not invented in the age of Slack, Zoom, or project-management dashboards. They were shaped long before those tools existed, by people who had to solve a different problem: how to coordinate complex activity reliably when communication was slow, information was incomplete, and mistakes were expensive.
A Financial Times piece recently highlighted a striking fact: a meeting process devised by a US officer and engineer in the 19th century still underpins the way many organizations run discussions today. The point is not that modern companies copy old paperwork or follow 1800s etiquette. It’s that the logic of structured meetings—agenda discipline, clear roles, decision-making steps, and documentation—has proven durable. In other words, the “infrastructure” of coordination has roots that reach back to an era when the stakes of miscommunication were immediate and physical.
To understand why this matters, it helps to look at what meetings are actually for. Most meetings are not primarily about exchanging information. They are about converting scattered inputs into coordinated action. That conversion requires a sequence: framing the problem, ensuring everyone is working from the same facts, debating options without losing the thread, deciding what will happen next, and recording commitments so the organization can execute afterward. When that sequence is missing, meetings become performances—talk that feels productive but produces little that can be acted on.
The 19th-century method addressed exactly that conversion problem. It emerged from a world where engineering and military operations demanded repeatability. If you can’t rely on improvisation, you build procedures. And if you build procedures, you need a way to ensure they’re followed consistently across teams and locations. Meetings became one of the most important control points in that system.
What the officer-and-engineer contribution did, in practical terms, was to treat meetings as a process rather than a conversation. That sounds obvious now, but it was a shift in mindset. A conversation can drift. A process has checkpoints. A conversation can end with vague agreement. A process ends with documented decisions and responsibilities. The durability of the approach suggests that organizations keep rediscovering the same truth: groups don’t naturally coordinate well under uncertainty; they coordinate better when the interaction itself is designed.
The most visible legacy of that early thinking is agenda structure. Modern agendas often look like a list of topics, but the deeper function is to impose order on attention. An agenda is not just a schedule; it’s a promise about what the group will do with time. It signals which items require discussion, which require information sharing, and which require decisions. Without that distinction, meetings become a catch-all where everything is treated as equally urgent and equally debatable. The result is predictable: the loudest voices dominate, the most complex issues get rushed, and the group leaves with no clear sense of what changed.
The 19th-century framework emphasized that meetings should move from purpose to outcomes. That means the agenda isn’t merely descriptive (“we will talk about X”). It’s prescriptive (“we will decide whether to do X,” or “we will align on the facts needed to decide X later”). This is one reason the method still resonates in modern business: it aligns with how organizations actually operate. Decisions require criteria. Alignment requires shared assumptions. Execution requires commitments. A meeting that doesn’t specify which of these it is doing becomes a blur.
Another enduring element is the insistence on roles and responsibilities. In many workplaces, meetings are treated as democratic by default: anyone can speak, everyone can weigh in, and the group collectively “figures it out.” That approach can work when the topic is simple and the group is small. But when complexity rises, democracy without structure becomes chaos. The officer-and-engineer logic recognized that coordination needs ownership. Someone must frame the issue, someone must facilitate the flow, someone must capture decisions, and someone must ensure follow-through.
This is where the method’s influence becomes less obvious but more powerful. Even when organizations don’t consciously reference 19th-century procedures, they often replicate their role logic through modern equivalents: meeting chairs, facilitators, note-takers, action-item owners, and decision logs. These roles are not bureaucratic decoration. They are mechanisms for reducing ambiguity. Ambiguity is the enemy of execution. If nobody is responsible for capturing what was decided, then decisions exist only in memory—and memory is unreliable.
Documentation is the third pillar of the enduring process. In the 19th century, written records were not optional conveniences; they were essential tools for continuity. When information travels slowly, you can’t assume that what was said in one place will be remembered accurately elsewhere. Written minutes, reports, and formal notes served as the bridge between discussion and action.
Modern organizations have digital tools, but the underlying problem remains. People forget. People interpret. People assume. Without a record, meetings become self-contained events rather than inputs to future work. The 19th-century approach treated documentation as part of the meeting’s job, not an afterthought. That’s why the best versions of the method still feel strict: decisions should be recorded, action items should be assigned, and the meeting should end with clarity about what happens next.
There’s also a subtle but important psychological effect. When a meeting is run as a process with explicit steps, participants behave differently. They prepare more deliberately because they know the meeting will test their ideas against criteria. They speak with more intention because they know the discussion is meant to produce something specific. They listen differently because they can anticipate where the conversation is headed. In contrast, when meetings are open-ended, participants often treat them as opportunities to vent, network, or signal status. That may feel socially productive, but it rarely produces operational outcomes.
This is where the unique take on the story becomes interesting: the meeting process didn’t just survive because it was “good.” It survived because it fits the way organizations manage risk. Risk in coordination is not only about technical errors; it’s about process failures. A team can have brilliant ideas and still fail if it can’t convert those ideas into aligned action. The 19th-century method functioned as a risk-control system for group decision-making.
Consider the environment that produced it. Military and engineering contexts required coordination across units, timelines, and constraints. The cost of misunderstanding could be severe. Procedures were a way to reduce variance in outcomes. A meeting process that standardizes how information is presented and how decisions are made reduces the chance that the group will “agree” while actually disagreeing. It also reduces the chance that the group will postpone decisions indefinitely because nobody is accountable for closing the loop.
That accountability is another reason the method remains relevant. Many modern meetings suffer from a particular failure mode: they generate momentum but not closure. People leave energized, but nothing changes. The meeting becomes a ritual of progress without the burden of completion. The 19th-century approach pushed toward closure by design. It treated the meeting as a mechanism for reaching determinate outcomes—decisions, assignments, and next steps—rather than as a forum for indefinite exploration.
If you’ve ever attended a meeting where the final ten minutes are spent asking, “So what are we doing?” you’ve seen the opposite of that logic. The group has discussed, debated, and shared perspectives, but it never performed the final step: translating discussion into commitments. The 19th-century method’s emphasis on moving from talk to outcomes is essentially a cure for that pattern.
So why does this matter now, in an era of remote work and AI-assisted productivity? Because the meeting problem has not disappeared—it has intensified. Remote work increases the friction of coordination. People can’t read body language as easily. Interruptions are harder to manage. Time zones complicate scheduling. Chat tools create parallel conversations that fragment context. Meanwhile, AI tools can summarize transcripts, but summaries can also mask the absence of real decisions. A transcript can be accurate and still fail to produce clarity about what the organization will do next.
In that environment, the old process logic becomes even more valuable. It reminds organizations that the goal is not to talk efficiently; it’s to decide and execute reliably. AI can help capture information, but it can’t replace the meeting’s structural purpose. If the meeting lacks an agenda that distinguishes discussion from decision, if roles are unclear, if documentation doesn’t translate into action, then the meeting will still fail—even if it produces a polished recap.
There’s also a deeper cultural angle. Many organizations have developed meeting habits that reflect status dynamics rather than operational needs. People speak to demonstrate expertise. Others speak to protect themselves from blame. Some participants use meetings to delay decisions until more information arrives. These behaviors are not always malicious; they are often rational responses to incentives. But they can undermine the meeting’s function.
A process-based meeting method counters those dynamics by making the meeting’s outputs explicit and measurable. When the meeting is designed to end with decisions and assignments, it becomes harder to hide behind ambiguity. When documentation is required, it becomes harder to rewrite history later. When roles are defined, it becomes harder for the loudest voice to steer the outcome without accountability.
This is why the 19th-century method can be seen as more than a historical curiosity. It’s a blueprint for organizational governance at the micro level. Every meeting is a mini institution. It has rules, norms, and outputs. The officer-and-engineer contribution helped formalize those rules in a way that could be repeated. That repeatability is what makes it scalable—from a unit in the field to a department in a corporation.
To make the connection to modern practice concrete, it helps to translate the core principles into everyday meeting design:
First, define the meeting’s purpose in decision terms. Instead of “Discuss Q3 marketing strategy,” aim for “Decide the top two channels for Q3 and assign owners for the experiments.” This forces the group to confront what “done” looks like.
Second, separate information sharing