The obsession with Victorian-era bureaucracy is killing corporate productivity.
Lately, management gurus have fallen in love with a romanticized past. They point to Robert’s Rules of Order, drafted in 1876, or mid-19th-century parliamentary procedures as the ultimate cure for our broken calendar culture. The argument sounds elegant: if we just return to rigid agendas, formal motions, and strict timekeeping, our modern Zoom fatigue will vanish.
It is a comforting lie. And it is completely wrong.
I have watched Fortune 500 executives spend millions of dollars retraining their staff to follow structured parliamentary protocols. The result? Total paralysis. By trying to turn a software engineering team or a marketing department into a 19th-century legislative assembly, companies do not make collaboration efficient. They just codify bureaucracy.
The 19th-century approach to meetings was designed for an era of physical paper, slow mail, and hierarchical command-and-control structures. Applying it to a digital economy is like installing a steam engine in a Tesla. It is time to abandon the old playbook entirely.
The Flaw of the Structured Agenda
The first thing traditionalists tell you is that every session requires a strict, pre-distributed agenda. They claim that an agenda ensures everyone stays on track.
In reality, a rigid agenda is a defense mechanism for the unprepared.
When you lock a discussion into an unyielding, chronological sequence days in advance, you eliminate the ability to pivot based on real-time data or immediate insights. If a critical flaw in your product strategy emerges five minutes into a session, a traditionalist will say, "Let’s park that discussion for the next scheduled review."
That is operational cowardice.
The most effective organizations do not use agendas to restrict conversation; they use a single, sharp problem statement. If you cannot state the purpose of a gathering in one provocative sentence, do not schedule it. Instead of "Q3 Marketing Review," the focus should be: "Why did our customer acquisition cost spike by 40% last week?"
If the discussion strays from solving that specific problem, you do not need a parliamentarian to call a point of order. You just need a leader who is not afraid to tell people to sit down.
Robert’s Rules are a Tool for Conformity
Let’s look closely at Robert's Rules of Order. Henry Martyn Robert created this system to prevent chaos in chaotic assemblies. It relies on motions, seconds, amendments, and voting.
Here is what people miss: parliamentary procedure is intentionally designed to slow things down. It protects the status quo by forcing every idea through a grueling gauntlet of procedural hurdles.
In a fast-moving business environment, speed is a competitive advantage. If your team has to debate whether a motion to alter a software feature is in order, your competitor has already shipped the update.
Furthermore, voting creates winners and losers within a team. It fosters a political environment where employees spend their time lobbying colleagues in the hallway before the session even starts.
Intel long ago popularized the concept of "Disagree and Commit," pioneered by Andrew Grove. You do not need a formal vote to move forward. You need a culture where dissenting opinions are voiced aggressively, a decision is made by the designated owner, and everyone aligns behind that decision—regardless of whether they voted for it. 19th-century rules do the opposite; they encourage passive-aggressive compliance.
The Myth of the "Collaborative" Meeting
The standard consensus states that meetings are where collaboration happens. The 19th-century model treats assembly as the primary vehicle for collective thought.
This is an expensive misunderstanding of human cognition.
Brainstorming in a group is a terrible way to generate high-quality ideas. Decades of psychological research show that group brainstorming leads to evaluation apprehension, where people hold back their best thoughts for fear of judgment, and social loafing, where individuals let a few dominant voices do the heavy lifting.
Imagine a scenario where eight executives sit in a room for two hours to brainstorm a new brand slogan. You are throwing roughly $2,000 worth of hourly compensation into a garbage can.
True collaboration is asynchronous. It happens in shared documents, code repositories, and deep, solitary focus.
- Step 1: Write a comprehensive, multi-page proposal detailing the problem, the evidence, and the proposed solution.
- Step 2: Distribute the document 48 hours before anyone speaks.
- Step 3: Require participants to leave inline comments and criticisms silently.
By the time you actually gather, the baseline information is already digested. You do not waste 30 minutes listening to someone read slides. You spend 15 minutes resolving the three most contentious points of disagreement highlighted in the text.
If there are no disagreements in the document, cancel the gathering. The decision is already made.
Why Shorter Is Not Always Better
The modern counter-argument to the long, drawn-out Victorian meeting is the 15-minute standup or the arbitrary 30-minute calendar block. Silicon Valley popularized this, and corporate America copied it without thinking.
This is just the other side of the same broken coin.
Short, rushed timeslots favor the loudest, most charismatic people in the room. They penalize deep thinkers, introverts, and those who require time to analyze complex data before responding. When you force every discussion into a 20-minute window, you only have time for superficial consensus. You end up scheduling another session next week to solve what you botched this week.
Amazon’s famous narrative-driven approach proves that longer, structured silence is infinitely more valuable than rapid-fire talking. Starting a session with 20 minutes of absolute silence to read a memo ensures everyone possesses the exact same context before a single word is spoken. It feels awkward. It feels slow. But it compresses the actual decision-making loop from weeks into minutes.
The Brutal Truth About Attendance
The 19th-century model views meetings as representative bodies. Everyone who might be affected by a decision feels entitled to a seat at the table.
This democratic instinct is poison for corporate execution.
Every single person added to a room increases the complexity of communication exponentially. The formula for communication channels is:
$$C = \frac{n(n - 1)}{2}$$
Where $n$ is the number of people. A gathering of 4 people has 6 communication channels. A gathering of 12 people has 66 channels. 12 people cannot have a nuanced, rapid debate; they can only perform for one another.
+-------------------+-----------------------+-------------------------+
| Number of People | Communication Channels| Primary Output |
+-------------------+-----------------------+-------------------------+
| 3-5 | 3 - 10 | High-velocity decisions |
| 6-9 | 15 - 36 | Informational alignment |
| 10+ | 45+ | Pure theater |
+-------------------+-----------------------+-------------------------+
If your name is not on the document as an author, an approver, or a critical subject matter expert whose specific domain is under review, you should not be there. Being excluded from a session is not an insult; it is a gift of time.
If you want to build trust, do not invite fifty people to watch a decision get made. Make the decision with three people, document the rationale clearly, and publish it to the entire company immediately. Transparency is achieved through open documentation, not through crowded rooms.
Kill the Minutes, Publish the Commitments
The 19th-century guide dictates that someone must take meticulous minutes, recording who said what, who seconded which motion, and what time the session adjourned.
Nobody reads meeting minutes. They are a compliance mechanism used to cover people's tracks after the fact.
Stop writing summaries of conversations. Nobody cares about the narrative arc of how you reached a conclusion. They only care about what happens next.
Replace minutes with an immutable commitment log. At the absolute end of the discussion, the leader must dictate three things into a shared tracker:
- What is the specific action item?
- Who is the single individual accountable for it? (No, "The Dev Team" is not an answer. It must be a human name.)
- What is the exact deadline?
If you leave a room without these three variables clearly defined for every single initiative, the past hour was a complete failure, regardless of how polite, structured, or "parliamentary" the behavior was.
Stop looking to the 19th century to solve 21st-century organizational rot. The solution to bad meetings isn't more rules; it is fewer meetings, smaller groups, and ruthless asynchronous preparation. Open your calendar right now. Delete half of what is on there. Demand a written memo for the rest. If the organizer complains, tell them you are too busy actually working to watch them read a script.
