Introduction

Every government runs on meetings. Ministers convene cabinet sessions, permanent secretaries review implementation, directors coordinate departments, technical committees evaluate policy, and local governments bring stakeholders together to solve public problems. Yet despite the enormous amount of time invested in meetings, many public institutions continue to struggle with ineffective decision-making, poor follow-up, and slow implementation.

Donald Rumsfeld's Rumsfeld's Rules, particularly the chapter on running a meeting, offers leadership lessons that extend far beyond politics (Rumsfeld, 2013). Although written from the perspective of an American public servant who served twice as Secretary of Defense and as a senior aide to four presidents, the underlying principles travel well across systems of government, including those in Africa and the Horn of Africa, where institutions are often younger, resources are more constrained, and the cost of wasted time is felt more acutely. Rumsfeld's central provocation is not simply how meetings are conducted, but whether they should be held at all, who should attend, how discussion should be managed, and how meetings should conclude with clear actions rather than open-ended conversation.

For public servants, meetings are not an administrative ritual. They are among the government's most valuable management tools. Used well, they accelerate decisions, improve coordination, strengthen accountability, and enhance public service delivery. Used poorly, they become one of the greatest sources of wasted public resources. This piece expands on that core argument, drawing together the practical lessons of Rumsfeld's chapter with broader research on meeting behavior and organizational decision-making and situating both within the realities of public administration in developing and transitional states.

Meetings Are Among Government's Most Expensive Activities

One of the strongest messages in Rumsfeld's chapter is that time is government's most valuable resource; once wasted, it cannot be recovered (Rumsfeld, 2013). Government meetings often involve senior officials whose salaries, expertise, and responsibilities represent significant public investment. A two-hour meeting involving twenty senior officials consumes roughly forty person-hours of government capacity. If that meeting produces no decision, no accountability, and no implementation, taxpayers effectively receive no return on that investment.

This is not merely a matter of internal efficiency. Rogelberg's (2019) research on meeting science found that poorly designed meetings measurably reduce employee wellbeing and organizational performance, while well-designed ones do the opposite; the difference is almost entirely attributable to design choices leaders make before the meeting begins, not to the personalities in the room. In a government context, that opportunity cost compounds: while officials remain in conference rooms, policy implementation slows, citizens wait longer for services, procurement decisions are delayed, and development projects lose momentum.

Before scheduling any meeting, leaders should ask one fundamental question:

Does this meeting genuinely improve government performance?

If the answer is uncertain, an email, a written briefing, or a short memorandum may be a better alternative. Lencioni (2004) makes a similar point in the corporate context: most meetings fail not because people dislike meeting, but because leaders default to meeting as the answer to every coordination problem, regardless of whether the problem actually requires real-time group discussion.

Meetings Must Have a Purpose

One of the most practical lessons from Rumsfeld's chapter is simple: never hold a meeting because the calendar says so (Rumsfeld, 2013). Every government meeting should answer at least one of the following questions: Are we making a decision? Are we solving a problem? Are we coordinating implementation? Are we sharing critical information? Are we assigning responsibilities? Without a clearly defined objective, discussions naturally drift toward repetition, storytelling, and unnecessary debate.

Doyle and Straus (1976), in their classic study of meeting facilitation, similarly argue that the single greatest predictor of a productive meeting is whether participants can state its purpose in one sentence before it begins. Effective government leaders open meetings by clearly stating why participants are present, what decision must be reached, what outcomes are expected, and how long the meeting will last. Purpose creates discipline; it also gives participants a basis on which to judge, midway through the discussion, whether the conversation has drifted off course.

Invite Only Those Who Matter

Government institutions often mistake large attendance for inclusiveness. Rumsfeld (2013) argues the opposite: large meetings frequently discourage honest discussion while increasing bureaucracy. For government leaders, attendance should be determined by contribution rather than hierarchy or protocol. Useful questions to ask before finalizing an invitation list include: Who makes the decision? Who possesses essential information? Who will implement the outcome? Who must simply be informed afterward, and could that be done in writing instead?

Not everyone needs to sit around the table. Smaller meetings generally produce faster decisions, better discussion, stronger accountability, and clearer ownership. In many public institutions, the instinct to invite every stakeholder is well-intentioned but self-defeating: it produces meetings where technical experts hesitate to speak candidly in front of superiors and where the true decision is quietly made afterward, in a smaller and less accountable setting.

Listening Is a Leadership Skill

One of the chapter's strongest observations is that good meetings depend more on listening than speaking (Rumsfeld, 2013). Many officials attend meetings primarily to present their own views or to be seen contributing. Effective leaders do something different: they observe who speaks, who remains silent, who avoids disagreement, who introduces evidence, and who merely repeats previous comments.

The purpose of discussion is not to demonstrate authority; it is to improve decisions. Often the quietest technical expert in the room, rather than the most senior official, provides the most valuable insight, simply because their expertise sits closest to the problem. Government leaders should deliberately invite quieter participants into the conversation before concluding important decisions, rather than assuming silence signals agreement.

Encourage Constructive Disagreement

Healthy governments do not fear disagreement; they encourage it. One of the greatest risks inside public institutions is groupthink, a term coined by the social psychologist Irving Janis (1972) to describe the tendency of cohesive groups to suppress dissenting views in the interest of harmony, often producing badly flawed decisions as a result. When everyone in a meeting agrees immediately and without friction, leaders should become cautious rather than relieved, since consensus without scrutiny often signals that critical questions were never actually asked.

Good meetings create space for respectful challenge. Officials should feel comfortable asking whether another option has been considered, what evidence supports a given recommendation, what risks have been overlooked, and whether a better alternative exists. Constructive disagreement strengthens policy quality; personal conflict weakens institutions. Leaders must learn to distinguish clearly between the two and to protect the former even as they discourage the latter.

Respect Time

Punctuality communicates respect. Late meetings communicate indiscipline. Every minute wasted waiting for participants multiplies across everyone in attendance: if twenty officials wait fifteen minutes for a meeting to start, government loses roughly five working hours before discussion even begins (Rumsfeld, 2013). Professional government meetings should start on time, finish on time, follow the agenda, and avoid unnecessary interruptions. Leaders who consistently respect time create institutional cultures that, over time, come to respect implementation as well.

Simplicity Beats Bureaucratic Language

Government communication frequently becomes unnecessarily complicated. Officials often rely on technical jargon, acronyms, and lengthy presentations that obscure rather than clarify the decision at hand. Yet policy is valuable only when everyone in the room, and eventually the public it serves, can understand it. Meeting discussions should be concise, evidence-based, practical, and understandable to a non-specialist. Complex language rarely reflects intelligence; clear language usually does. This is especially relevant in multilingual and multi-agency settings, where a document or briefing loaded with untranslated jargon can quietly exclude the very officials who are expected to implement the decision.

Every Meeting Must End With Decisions

Many government meetings conclude without clarity. Participants leave asking what exactly was decided, who is responsible, and when implementation is expected. This uncertainty leads directly to repeated meetings that revisit the same issues without ever resolving them. Every meeting should conclude by answering four questions: What decisions were made? Who is responsible? What are the deadlines? How will progress be monitored? Accountability begins the moment responsibility becomes visible and attached to a name and a date, rather than to a vague collective commitment.

The Final Question Every Leader Should Ask

Perhaps the most valuable lesson in Rumsfeld's chapter appears at its very end: before closing the meeting, ask, "What have we missed?" (Rumsfeld, 2013). This simple question encourages participants to raise overlooked concerns, identify hidden risks, and contribute ideas they may have hesitated to share earlier in the discussion. Many important observations emerge only after participants realize the meeting is nearly complete and the pressure to conform to the room's momentum has eased. Wise leaders always leave room for one final contribution.

Implications for Government Reform

Governments are increasingly seeking faster implementation, stronger coordination, and evidence-based decision-making. Improving meetings may appear to be a modest, even mundane, administrative reform compared to restructuring ministries or overhauling procurement systems. In reality, it can meaningfully improve institutional performance at very low cost, since it requires no new budget line, only a change in leadership discipline.

Well-managed meetings reduce bureaucracy, strengthen accountability, improve communication between departments, accelerate implementation, and increase public confidence in government. This matters where limited staffing and resources make the opportunity cost of unproductive meetings especially high and where a reputation for disciplined, decisive governance can itself become a form of institutional capital. The most successful public institutions are rarely those that hold the most meetings. They are those that hold the right meetings, with the right people, focused on the right decisions, followed by timely implementation.

To end

Government meetings should never become an end in themselves. They exist to produce decisions, improve coordination, and deliver better outcomes for citizens. The lessons from Rumsfeld's Rules book remind public servants that leadership is demonstrated not by how long meetings last but by how effectively they translate discussion into action (Rumsfeld, 2013). Ultimately, the quality of governance is reflected not in the number of meetings held, but in the quality of decisions made and the results delivered. Public service is measured by implementation, and every meeting should move government one step closer to serving its citizens more effectively.

References

Doyle, M., & Straus, D. (1976). How to make meetings work: The new interaction method. Jove Books.

Janis, I. L. (1972). Victims of groupthink: A psychological study of foreign-policy decisions and fiascoes. Houghton Mifflin.

Lencioni, P. (2004). Death by meeting: A leadership fable about solving the most painful problem in business. Jossey-Bass.

Rogelberg, S. G. (2019). The surprising science of meetings: How you can lead your team to peak performance. Oxford University Press.

Rumsfeld, D. (2013). Rumsfeld's rules: Leadership lessons in business, politics, war, and life. Broadside Books.


Make sure to share your own thoughts with the author by leaving a comment below