The Hungry Hungry Meeting
A meeting is work only if it produces work.
It must produce a decision, an assignment, a changed priority, a settled standard, or a clearer course of action. Otherwise, it has only taken time from work that might have been done elsewhere.
The distinction is important. No organization can operate without meetings. People must confer, decide, correct, coordinate, and take responsibility together. But a meeting does not become useful because it appears on the calendar, because senior people attend, or because the subject is important.
The meeting must be judged by its result.
A one-hour meeting with eight people is not a one-hour expense. It is eight hours of working time, plus the interruption before it and the recovery after it. The cost may be justified. Often it is. But the cost should be visible before the meeting is called.
The manager who calls a meeting assumes responsibility for the time of every person present. That responsibility begins before the invitation is sent. It begins with a simple question: What must this meeting produce?
The Cost Must Be Seen
Time is not one resource among many. It is the one resource that cannot be stored, replaced, or recovered.
Money can sometimes be found. Staff can sometimes be hired. Machinery can sometimes be repaired. Lost time is gone. The hour used poorly cannot be reclaimed by apology, enthusiasm, or a better agenda next week.
This makes the meeting a serious managerial act.
Many meetings are called casually because the cost is hidden. The calendar shows one hour. The cost is larger. It includes every person in the room. It includes the preparation that may have been done poorly or not at all. It includes the half hour before the meeting, when concentration is weakened because interruption is near. It includes the half hour after, when people return to work and must reconstruct thought.
Work requiring judgment does not resume at command. The analyst cannot always reenter the problem at once. The writer cannot always recover the paragraph. The manager cannot always return to a hard decision with the same clarity. The engineer, salesperson, designer, trainer, accountant, and supervisor all pay the tax of interruption.
The calendar may still look productive. It is full. It is orderly. It shows attention to many subjects. But an orderly calendar may conceal a disorderly use of time.
A meeting should therefore be treated as an expenditure. The question is not whether the organization can afford the hour. The question is whether the hour will produce a result worthy of the people removed from other work.
The Test Is the Result
A useful meeting changes what happens next.
It changes a decision.
It changes an assignment.
It changes a date.
It changes a sequence.
It changes a standard.
It changes responsibility.
It changes what will be done, what will not be done, or who will do it.
This is the test.
If nothing changes, the meeting has not done managerial work. It may have informed, though information can often be written. It may have comforted, though comfort is not performance. It may have allowed people to speak, though speech is not contribution unless it improves judgment or action.
The test should be applied before, during, and after the meeting.
Before the meeting, it asks whether people need to gather at all.
During the meeting, it protects the discussion from wandering.
After the meeting, it shows whether time was well spent.
This standard is especially important because many meetings are defended by the importance of the subject. Budget is important. Staffing is important. Customers are important. Quality is important. Strategy is important. None of this proves that a meeting is required.
An important subject may require a decision. It may require written analysis. It may require one manager to act. It may require a conversation with one person. It may require no immediate action at all.
The subject does not justify the meeting. The needed result does.
The Purpose Must Be Written First
Poor meetings often begin with a poor invitation.
The invitation names a subject instead of work to be done.
Budget.
Staffing.
Operations.
Customer complaints.
Project update.
These are not purposes. They are territories. Each can invite almost endless talk.
A purpose states the result required.
Decide which budget requests will be approved this month.
Choose whether temporary help is needed for the June deadline.
Set the operating rule for Friday cutoff exceptions.
Identify the causes of late customer responses and assign correction work.
Confirm whether the launch date stands and name the remaining work.
The difference is discipline. A subject invites comment. A purpose requires judgment.
Before the invitation is sent, the purpose should be written in one sentence. That sentence should answer: What must be true when the meeting ends?
If the sentence cannot be written, the meeting is not ready. The person calling it has more thinking to do.
This written purpose need not be elaborate. It may be no more than a plain sentence in the invitation. But it changes the meeting before the meeting begins. It tells people why their time is being claimed. It tells them what preparation is expected. It gives the chair a standard. It gives the meeting an end.
A meeting without such a purpose is open to anyone’s concern. The strongest voice may define it. The oldest irritation may take it over. The most recent event may displace the reason for gathering. Time then goes not to the work but to whatever happens to enter the room.
Preparation Is Part of the Meeting
Many meetings are called to avoid preparation.
“Let’s talk this through” can be a sound request. Some problems require conversation before the shape of the answer is visible. But often the phrase means something else. It means the issue has not been framed, the facts have not been sorted, and the choices have not been named.
The group is then asked to pay for one person’s unfinished thinking.
Writing is the remedy. Not long writing. Not formal writing. Clear writing.
Before a meeting is called, the responsible person should be able to state the issue, the known facts, the missing facts, the choices, the constraint, and the intended result. A half page often suffices.
The purpose of this writing is not paperwork. It is thought.
Writing forces selection. It shows whether the issue is real. It separates fact from preference. It reveals whether a decision is needed or whether one person simply needs to act. It also prevents the meeting from becoming a reading room for the unprepared.
Preparation belongs not only to the person calling the meeting. It belongs to everyone invited. If numbers must be reviewed, they should be reviewed before the meeting. If a document must be read, it should be read before the meeting. If objections must be raised, they should not wait until the last ten minutes.
A meeting is too expensive to become the place where preparation first occurs.
Attendance Must Be Earned
The invitation list should be built from contribution, not courtesy.
Organizations often invite too many people because exclusion feels dangerous. Someone may feel ignored. Someone may need to know. Someone may object later. Someone may have something to add.
This is a weak test.
A person should attend only when presence can improve the result. The person owns the decision. The person has facts not otherwise available. The person must carry out part of the work. The person will be affected in a way that must be understood before action.
Everyone else can receive the record.
This is not disrespect. It is respect. A capable person spared an unnecessary meeting has been given back time for contribution.
Over-invitation also injures the meeting itself. The larger the room, the more explanation is required. The more explanation offered, the more comment invited. The more comment invited, the harder it becomes to decide. People begin to speak because they are present, not because they can improve the result.
Some meetings properly require many people. A safety issue, a production stoppage, a system conversion, a customer failure, or a policy change may require broad knowledge and coordinated action. But broad attendance should be justified by the work, not by habit or politeness.
The question is not, Who might be interested?
The question is, Whose presence will improve the decision or the execution?
Authority Must Be in the Room
A meeting called for decision requires authority.
This does not mean rule by command. It means the room must know who is responsible for the decision. A group may advise. A group may challenge assumptions. A group may supply facts. A group may reveal consequences. But a group cannot finally be responsible in the same way an accountable manager can be responsible.
When everyone owns the decision, no one owns the decision.
Before a decision meeting begins, the decision owner should be named. The room should know who decides, who advises, who provides facts, and who acts after the decision.
This prevents two common failures.
The first is false democracy. Every preference is treated as equal, though one person must answer for the result.
The second is false agreement. Everyone leaves satisfied, but no one has accepted obligation. At the first obstacle, the agreement dissolves.
A decision meeting should end in one of three ways.
The decision is made.
The decision awaits one missing fact, and a named person will provide it by a named date.
The issue no longer requires decision.
There should be no fourth ending.
“Good discussion” is not an ending. “More to come” is not an ending. “Let’s revisit this” is not an ending unless the missing work, owner, and date are named.
Meetings multiply when authority is absent. The same question returns because no one settled it.
Information Should Travel in Writing
No organization should assemble people merely to hear what could have been read.
This is one of the most common abuses of the meeting. A person reads slides aloud. A manager walks through updates. A project lead narrates facts that could have been distributed. Some people know the facts already. Some need only part of them. Some do not need them at all. All pay for the slowest form of transmission.
Information should travel in writing.
Facts can be written.
Numbers can be written.
Progress can be written.
Risks can be listed.
Options can be compared.
Objections can be requested.
The meeting should begin where writing stops being enough.
What choice must be made?
What risk must be owned?
What fact is disputed?
What standard must be enforced?
What sequence must change?
What work must begin?
There are exceptions. A complicated matter may require explanation. A sensitive change may require questions. A true emergency may require immediate assembly. But exceptions should not become routine.
Status is the worst offender. Status reporting is often necessary. Status meetings often are not.
A proper status report answers: Is the work on track? What changed? What is blocked? What decision is needed? What help is requested?
Items on track need no speech. Exceptions deserve attention. A meeting should be reserved for exceptions, decisions, conflicts, and commitments. It should not make every person listen to every other person’s report.
The Meeting Must Be Conducted
A meeting requires a chair, not merely a host.
A host welcomes people. A chair protects the work.
The chair begins with the purpose. The chair keeps the discussion attached to that purpose. The chair stops repetition. The chair distinguishes fact from opinion. The chair sends side issues elsewhere. The chair calls attention back to the decision. The chair closes with assignments.
This is not domination. It is responsibility.
Without a chair, the meeting obeys the strongest voice, the oldest complaint, the newest anxiety, or the issue introduced last. The purpose is displaced. Time is spent because no one has accepted responsibility for the use of time.
Plain sentences are enough.
That is a separate issue.
The decision before this meeting is narrower.
The same point has been made.
The fact needed is not here.
Who will get the fact, and by what date?
The decision owner should now choose.
Such sentences may seem abrupt in organizations accustomed to wandering meetings. They are not abrupt. They are economical. The discourtesy lies in taking time from several people without protecting the use of it.
Good chairmanship teaches good attendance. People learn to arrive prepared, speak to the point, and expect an ending.
Poor chairmanship teaches waste. People learn that meetings are places where time has little value and speech has little cost.
The Meeting Must End in Work
Many meetings lose their value at the end.
The discussion has improved the issue. The facts are clearer. Agreement has begun to form. Then the hour ends. People leave for the next obligation. No one states precisely what changed.
This is failure at the decisive moment.
A meeting must end in work.
What was decided?
What was rejected?
What remains open?
Who owns each action?
When is each action due?
Who must be informed?
What should not be reopened?
Assignments must be personal, concrete, and dated.
Not “Finance will review.”
Maria will send the revised cost estimate by Thursday at noon.
Not “Sales will follow up.”
David will call the customer by Wednesday and record the answer.
Not “The team will consider alternatives.”
Rina will prepare two alternatives and recommend one before Monday.
A collective assignment is often no assignment. A vague date is often no date.
The last minutes should be reserved for this work. A meeting that uses all its time for talk and leaves no time for assignment has used the time badly.
The record should preserve the result, not the conversation.
The decision made.
The reason, when the reason will be needed later.
The action assigned.
The owner.
The date.
The open question.
The record should be short and sent promptly. Delay allows memory to improve itself. People remember selectively. Absent people hear different versions. Decisions return disguised as new questions.
A decision not recorded is only partly made.
Standing Meetings Must Be Reapproved
The standing meeting is dangerous because it no longer has to ask permission.
It began for a reason. A project was new. A customer situation was unstable. A department needed coordination. A manager needed visibility into exceptions. At the beginning, the meeting may have been right.
Then conditions changed. The calendar did not.
The meeting continued because it had been held before. The agenda was filled because time had been reserved. Attendance became custom. Custom became cost.
Every standing meeting should be reviewed as if it were a new request for time.
Does it still change the work?
Does it need to occur this often?
Does every person still need to attend?
Could it become exception only?
Could every other meeting become a written report?
Could the meeting be cut in half?
Should the meeting end?
Habit is not evidence of value.
A meeting that once contributed may later consume. A manager who fails to review recurring meetings allows old problems to spend present time.
The more complex the organization, the more standing meetings it will create. The more standing meetings it creates, the more management must prune. Otherwise, the calendar becomes a record of past concerns rather than present contribution.
The Wrong Meeting Hides the Real Problem
Some meetings are called because one person is failing.
One person misses deadlines. One person ignores procedure. One person resists a decision. One person does not communicate. The manager then calls a group meeting about standards, deadlines, process, or communication.
This is poor management.
When the problem belongs to one person, the conversation should usually be with that person. Group time should not be spent sending indirect messages to the person at fault while the rest sit through correction they do not need.
A group meeting is proper when the system is broken. It is improper when private performance is being disguised as a common issue.
The manager must choose the right instrument. The group meeting is not a substitute for directness.
The same is true of anxiety. A meeting is often called because people feel uneasy. A rumor has begun. A senior manager has asked a question. A number looks wrong. A customer has complained. Someone says, “We should get everyone together.”
Sometimes that is right. Often it is not.
Uneasiness is not the same as urgency. Urgency requires action within a short time. Uneasiness often seeks relief through talk. The meeting then becomes a way to reduce discomfort without assigning responsibility.
Before calling such a meeting, the manager should ask: What action can this meeting make possible that cannot be made possible by writing, by one decision, or by one direct conversation?
If there is no answer, the meeting is treating uneasiness rather than work.
The Manager Is Responsible for the Time Taken
Meetings do not improve because people are urged to be more efficient. They improve when managers set standards and keep them.
No meeting without a written purpose.
No meeting called when writing will do.
No decision meeting without a decision owner.
No attendance by courtesy.
No agenda made only of topics.
No status meeting spent reading status aloud.
No meeting ending without owners and dates.
No standing meeting continuing without review.
No group meeting used to avoid a direct conversation.
These are not tricks for saving minutes. They are disciplines of management.
The meeting is useful when it concentrates judgment on work requiring joint attention. It is wasteful when it substitutes talk for thought, attendance for contribution, agreement for responsibility, or habit for judgment.
The question at the end is the question from the beginning.
What did the meeting produce?
If it produced a decision, an assignment, a changed priority, a settled standard, or a clearer course of action, the time may have been justified.
If it produced none of these, the meeting did not serve the work. It consumed the working day.