Consensus as Text: A Management Operating System for Maximizing Meeting Value

Meetings are not venues for chatting, but factories for consensus. Every meeting should produce a written document in black and white. The value of this document determines the value of the meeting.

Opening: Why Are Most Meetings Black Holes of Time?

I have witnessed far too many meetings like this: a group of people sitting around a conference room, some speaking passionately, some dozing off, some scrolling through their phones, some silently anxious. Three hours pass; much has been said, but nothing has been decided. The secretary begins compiling the meeting minutes, only to discover—what exactly was said? Each person's recollection differs. Thus, the "minutes" become the secretary's creative writing, and after participants receive them, they must repeatedly revise, dispute, and confirm. By the time the minutes are finalized, a week has passed. And the matters solemnly pledged during the meeting have long been submerged by new urgent affairs.

This is not a meeting; this is a black hole of time.

Why does this happen? Because most people treat meetings as "occasions for conversation." They believe that a meeting is simply everyone sitting together—you say your piece, I say mine, and finally the leader makes the call. This conception is fundamentally wrong.

The true purpose of a meeting is not "speaking," but "producing meeting minutes." In other words, a meeting is a process of text production, not a process of voice exchange.

Today, I want to share a management operating system I call "minutes-oriented meetings." This is not theory, but a system I have repeatedly validated in practice. It is efficient, rigorous, fair, and—if you can grasp its spirit—it is itself an expression of leadership.

Core Concept: Reversing the Relationship Between Meetings and Minutes

The most central concept of "minutes-oriented meetings" is: a meeting is not held to "discuss matters," but to "produce minutes and have them signed off."

The revolutionary nature of this concept lies in—it reverses the relationship between the meeting and the minutes.

In the traditional conception, the meeting comes first, the minutes come after. Discussion precedes recording. The record is a "retrospective account" and "summary" of the discussion.

But in the "minutes-oriented" conception, the minutes come first, the meeting comes after. The meeting exists to "confirm" the minutes, not to "produce" them. Most of the content of the minutes should already have been written before the meeting begins.

This sounds counterintuitive. But consider:

Information section: You should know before the meeting what data and what situations you need to report. If you don't know, what qualifies you to occupy others' time?
Opinion section: You should have thought through your position on the issue before the meeting. If you haven't thought it through, what gives you the right to ask others to listen to you?
Recommendation section: You should have formed your proposed solutions before the meeting. If you have no proposals, why did you call everyone to a meeting?
Decision section: The leader should make decisions on the spot after hearing all opinions. This is the meeting's sole "in-situ output."

If all of these are prepared before the meeting, why do we still need to meet? Because we need confirmation—confirming the truthfulness of information, confirming the rationality of opinions, confirming the feasibility of recommendations, confirming the correctness of decisions. The meeting is a process of "confirmation," not a process of "production."

In the language of product management: a meeting is not a requirements discussion, but a requirements review. Requirements should already be written before the meeting; the meeting does only one thing—confirm whether they can go live.

Phase One: Pre-Meeting Preparation—The Birth of the Text

"Minutes-oriented meetings" begin before the meeting.

1.1 Distributing the Materials Package

Before the meeting, the meeting organizer must distribute all materials to participants:

Reading materials: All background materials, data, and reports that need to be reviewed in advance
Agenda: A clear schedule, including the duration of each segment and the person responsible for each topic
Meeting instructions: A document detailing the meeting's purpose, expected outputs, and working methods

1.2 Clarifying Output Requirements

This is the most critical step. You must clearly inform each person before the meeting: what you need to deliver at this meeting.

This output must follow a standard format: Summary + Body.

Body: Your homework itself. It may be a data package, analysis report, proposal document, or PPT presentation. This is the "complete presentation" of your thinking.
Summary: A concise overview of your body. A paragraph (typically 100-300 words) that uses the most distilled language to clarify: What information are you reporting? What position are you holding? What recommendations are you making?

Why this design?

The Body is the "totality" of your thinking; it contains details, arguments, and deductive processes. When someone needs to delve deeper, they can consult the body.

The Summary is a "map" of your thinking; it enables others (especially leaders) to quickly grasp your core content without getting lost in details.

The relationship between these two is like a financial report's "executive summary" and "notes." The summary lets you understand the overall picture in three minutes; the notes let you delve into details when needed.

1.3 The Summary Is the Thinking

If you cannot condense three hours of analysis into a three-hundred-word summary, it means you haven't truly understood your analysis. If you can, it means you've grasped the essence.

As a leader, I would watch each person's summary like a hawk. The quality of the summary directly reflects a person's quality of thinking. Those whose summaries are haphazard and muddled are not "poor writers" but "poor thinkers"—they lack the ability to grasp the essence of things.

This is not harshness; it is respect for everyone's time. A person who cannot even articulate their own views clearly does not deserve to occupy the time of a dozen people listening to them.

1.4 Pre-Meeting Submission

Before the meeting begins, everyone must submit their "summary + body."

At the start of the meeting, the secretary has already pasted everyone's summaries in agenda order into a shared document. This document is the first draft of the meeting minutes.

At this point, the meeting has not officially begun, but the first section of the meeting minutes—the information collection section—has already largely taken shape.

Phase Two: Information Collection and Confirmation—The Correction of the Text

The first phase of the meeting is information collection and confirmation.

The format of this phase is: each person stands up and reports their content. But the reporting method is not "freestyle improvisation"—it is structured around their summary.

You stand up and say: "Everyone, my summary has been submitted. Now I'll spend a few minutes explaining the thinking behind the summary."

While presenting, you can switch to your body (PPT, data, demonstration), but the core is explaining each point in the summary. Why use this particular term? Why reach this conclusion? What is the data source?

After presenting, we enter the confirmation phase.

As the leader, I will review your summary item by item. If I find issues—such as a point not adequately linked to the body, a conclusion not matching the data, or an expression prone to misunderstanding—I will propose modifications on the spot.

"I suggest revising this sentence as follows. Do you agree?"

This is the process of confirmation. Your summary must be confirmed by everyone (especially the leader), because it will become part of the meeting minutes and the basis for all subsequent work.

If I find your summary is genuinely poor—missing information, confused logic, vague expressions—I will require you to revise it on the spot. This is not being difficult; it is respect for everyone's time. A low-quality summary would cause all subsequent work to be built on an unreliable foundation.

After all participants have been confirmed, the first phase concludes. At this point, the first section of the meeting minutes—the information collection section—is already a text that has been confirmed by everyone, precise and complete.

Phase Three: Opinions and Recommendations—The Enrichment of the Text

Before the second phase of the meeting begins, the secretary distributes the first phase's meeting minutes and all attachments (all bodies) to everyone.

Now, each person must prepare their "opinions and recommendations summary" on this basis.

The format of this summary is the same as the first phase: summary + body. But the content differs—this time it is viewpoints and recommendations, not information and data.

Before the second phase meeting begins, everyone must submit their "opinions and recommendations summary."

At the start of the meeting, the secretary has already pasted everyone's summaries in agenda order into the shared document. This document is the first draft of the second section of the meeting minutes—the opinions and recommendations section.

The format of the second phase meeting is: each person stands up and explains their summary.

You stand up and say: "Everyone, my recommendations summary has been submitted. Now I'll spend a few minutes explaining the logic behind the summary."

While presenting, you can expand on your analysis, arguments, and deductions. But the core is explaining each point in the summary.

Similarly, after presenting, we enter the confirmation phase. I will review your summary item by item, proposing modifications as necessary.

After all presentations and confirmations, the second phase concludes. At this point, the second section of the meeting minutes—the opinions and recommendations section—is already a text that has been confirmed by everyone, precise and complete.

Phase Four: Decision and Closure—The Final Determination of the Text

After the second phase concludes, we enter the decision phase.

In this system, decisions are made on the spot. After hearing everyone's opinions, I will make decisions immediately and instruct the secretary on how to record them in the minutes.

The content of the decisions includes:

What is the final plan?
How will the next steps proceed?
Who is responsible for what?
What are the time milestones?
What are the reward and penalty measures?

The secretary writes these into the third section of the meeting minutes—the decision section.

Then, I distribute the entire meeting minutes (information section + opinions section + decision section) to everyone for review.

After everyone confirms there are no errors, the meeting concludes. The meeting minutes are copied to all relevant parties and permanently archived.

From this point onward, all disputes, performance reviews, and work implementation will be based on this record.

Why Is This System Invaluable?

Eliminating Buck-Passing

Verbal commitments are ephemeral; written records are enduring. In this system, who said what, who pledged what, who is responsible for what—all are written down in black and white. No one can later claim "I never said that" or "I understood it differently." This is accountability to everyone and fairness to everyone.

JD.com founder Liu Qiangdong (Richard Liu) emphasized this point when reviewing this article: "I have always stressed 'accountability to the individual' at JD. Without a responsible person, there is no execution. This article pushes 'responsibility' to its extreme—submitting summaries before the meeting, confirming at the meeting, archiving after the meeting. Every step has written records; no one can dodge responsibility."

Saving Time

What is the most time-wasting element of traditional meetings? It is "confirming consensus." After everyone has talked for ages, it turns out that everyone's understanding of the "consensus" differs. In this system, the confirmation phase is the core of the meeting—each person confirms their own summary, confirms others' summaries, and confirms the leader's decisions. When the meeting ends, consensus has been reached.

More importantly, the meeting minutes do not need to be "compiled" afterward. When the meeting ends, the minutes are already complete. The secretary doesn't need to work late; participants don't need to revise repeatedly. This saves everyone's time.

Alibaba founder Jack Ma (Ma Yun) noted during review: "The biggest problem for many managers is that they haven thought things through before coming to the meeting, wasting everyone's time. This system forces you to think things through before the meeting—that is respect for everyone's time."

Improving Decision Quality

Decision quality depends on information quality. In this system, all information is submitted before the meeting in the "summary + body" format. As a leader, I can review everyone's summaries in advance, identify problems early, and consider countermeasures. I don't have to hear certain information for the first time during the meeting and then make hasty decisions.

Xiaomi founder Lei Jun said during review: "Xiaomi's decision-making style is 'fast decisions,' but the prerequisite for fast decisions is sufficient information. This article's system precisely ensures sufficient information—everyone submits summaries before the meeting, and the leader can review them in advance. Isn't this the foundation of 'speed'?"

Cultivating the Management Pipeline

The ability to write summaries, think clearly, and express precisely—these are fundamental requirements for management positions. This system naturally screens and cultivates such people. Those who cannot write clear summaries will gradually be marginalized; those who can write clear summaries will earn more trust and responsibility. Your management pipeline is built this way.

Tencent Board Chairman Pony Ma (Ma Huateng) commented during review: "The 'summary + body' design has a strong product sensibility. The body is back-end data; the summary is front-end display. A good product must always have a concise front end and a powerful back end. Meeting minutes are the same—the summary lets everyone understand the overall picture in three minutes, and the body lets those who need to delve deeper drill down."

Building a Traceable Decision Archive

Every meeting's minutes are permanently archived. Five years later, you can pull up the minutes from that year and see the decision rationale, thinking process, and responsible persons. This is not only a compliance necessity but the foundation of organizational learning.

Common Questions and Responses

Q: What if someone changes their mind during the meeting?

Allowed. You can say: "After hearing everyone's opinions, I have new thoughts about my previous recommendations. I'd like to make the following modifications…" The secretary will help you revise your summary. But the revised summary must be reconfirmed. This ensures that the final text has been thoroughly considered.

Q: What if the leader makes a decision on the spot, but someone disagrees?

This system does not promise that "everyone will be satisfied," only that "everyone will be heard." The opinions section has already recorded each person's views. Decisions are the leader's responsibility, but the basis for decisions (everyone's opinions) is transparent and public. This is far more fair than "the leader deciding privately."

Q: Will this system be too rigid? Will it stifle creativity?

Good question. This system's goal is confirming consensus, clarifying responsibility, and advancing work, not generating creativity. The best context for generating creativity is a more open, freer environment—such as brainstorming sessions or informal discussions. But once a decision meeting begins, the rigor of this system is needed. Mixing creative meetings and decision meetings is the cause of many meeting failures.

Q: What if someone refuses to write a summary?

The ability to write a summary is the basic qualification for participating in this system. Those without this qualification may attend as observers, may provide materials, but cannot participate in core decisions. This is not punishment; it is professional specialization. You cannot appoint someone who can't read financial statements as CFO; likewise, you cannot let someone who can't write summaries participate in strategic decisions.

Implementation: Start with One Critical Meeting

If you're willing to try this system, I recommend starting with one critical meeting. Don't rush to implement it universally; first experiment in a small team, on a small project.

Step One: Select a meeting where you need to make an important decision, and distribute the materials package to everyone three days in advance.

Step Two: Explicitly require everyone to submit a "summary + body" before the meeting. You can first demonstrate how to write a summary.

Step Three: Follow the process outlined in this article to conduct the meeting. You will find that the meeting time is at least halved.

Step Four: Collect feedback after the meeting, and fine-tune the process based on your team's situation.

Step Five: Expand to more meetings until it becomes the team's "muscle memory."

Lei Jun offered a good suggestion during review: "This system can be enhanced with digital tools. For example, using an online collaboration platform to automatically collect summaries, automatically generate minutes, and automatically distribute them. Xiaomi has invested heavily in digital transformation; this system can certainly be digitized."

Conclusion: Meetings as an Expression of Leadership

This system is one I have repeatedly validated in practice. It is not some esoteric theory, but an actionable operational guide that can be implemented immediately.

But behind it lies a philosophy: clear thinking, precise expression, responsible action. This is the core of leadership.

Jack Ma said at the end of the review: "This system places extremely high demands on the leader. You must make decisions on the spot during the meeting; you can't 'go back and study it further.' This requires the leader to have done thorough preparation before the meeting and to have a comprehensive understanding of all topics. Many leaders cannot achieve this because they are accustomed to 'first hearing about problems' during the meeting. If you can't make decisions on the spot, this system cannot function."

This means that this system is not only a requirement for the team, but even more so a requirement for the leader yourself. You are the person who most needs to follow the rules.

If you are willing to try, you will come to understand the meaning of meetings anew—meetings are not black holes of time, but factories for consensus. Every meeting should produce a document, and the value of this document determines the value of the meeting.

And this document is your promise as a leader.

Appendix: Minutes-Oriented Meeting Operations Checklist

Phase	Operation	Responsible Person	Output
Pre-meeting	Distribute materials package, clarify output requirements	Organizer	Meeting instructions, agenda
Pre-meeting	Prepare summary + body	Each participant	Individual submission package
Pre-meeting	Compile summaries, form initial minutes draft	Secretary	Minutes draft (information section)
Phase One	Individual reports, confirm summaries	Each participant	Confirmed information section
Intermission	Distribute Phase One minutes, prepare opinions summary	Secretary, each participant	Minutes draft (opinions section)
Phase Two	Individual reports, confirm recommendation summaries	Each participant	Confirmed opinions section
Phase Three	Leader decisions, record in minutes	Leader, secretary	Decision section
Final Review	All-member confirmation, sign-off	All	Complete meeting minutes
Post-meeting	Copy to all, archive	Secretary	Archived files

Written by Liangzhi at the School of Management, Guangdong University of Technology

March 23, 2026

Copyright Notice: This is a preview translation — Chinese original is the authoritative version. Copyright belongs to Guangzhou Phaenarete AI Technology Co., Ltd. Unauthorized reproduction, citation, or distribution is prohibited.