Reducing calendar hours without replacing necessary decision, coordination or relationship work can move that work elsewhere. This is a proposed process analysis, not evidence of a universal six-month pattern or slower decisions. Assess the actual cost of briefings, notes and follow-up. This article does not establish that supporting work is now nearly free or that automation reduces meetings.
An organisation does not have a meeting problem. It has a decision problem, and meetings are the visible symptom of never having specified who decides what
Here is a proposed approach. Measure meeting time and decision latency rather than assume that reducing one will not affect the other.
The four things meetings are actually doing
Deciding, which genuinely benefits from synchronous discussion when the decision is contested, ambiguous or consequential. Informing, which almost never does and which is where most of the recoverable time sits. Coordinating, which is usually a symptom of unclear ownership rather than a genuine need. Relating — building the trust that makes the other three work, which is real, underrated and the thing efficiency programmes destroy first. Cut the informing, examine the coordinating, protect the relating, and improve the deciding. That sequence matters, because organisations that start by cutting relating meetings get a short-term calendar win and a slower organisation.
| Job | Question to ask |
|---|---|
| Deciding | Who can decide, and what discussion is needed? |
| Informing | Can a short accessible update do this job? |
| Coordinating | Which dependency or owner needs clarification? |
| Relating | What relationship time should be protected? |
Qualitative summary of this article's source text, not a measured outcome or performance estimate.
What actually reduces meeting volume
Name a decider for recurring decisions where authority is unclear. This does not establish the cause of every meeting or a fifteen-minute outcome. Test written proposals where useful, preserving discussion and accessible contributions. No universal reading-speed advantage or forty-minute saving is established. Require a stated purpose for each meeting. Decision meetings need a decision; relationship-building, coordination or discussion may have other legitimate purposes. Test written updates for suitable informing work. And default expiry on recurring meetings. Every recurrence should end after a set period unless someone renews it, because the effort of cancellation is what keeps dead meetings alive.
Where the automated support actually helps
Automation may support preparation and summaries. Measure accuracy, effort and review cost in the actual team; this article does not establish a universal bottleneck or a quantified cost reduction.
Practical Guidance for Decision Process Design
- Name a decider for every recurring decision.
- Write the proposal first; read it in the room if needed.
- Require a stated purpose. Distinguish decision, coordination, informing and relationship work rather than reject every non-decision meeting.
- Expire recurring meetings by default.
- Convert informing meetings to written updates.
- Protect the relational time explicitly.
- Record the decision and the rationale, not the discussion.
- Review the calendar quarterly against decisions actually made.
The Regional Angle
The first regional factor is that decision authority in many Gulf organisations is genuinely concentrated rather than nominally so, which changes what a decision process can achieve. Naming a decider is straightforward when the answer is already known to be the owner or the chairman; the useful work is narrower and more achievable, which is to specify what can be settled without them. Most of the calendar bloat in regional companies is not contested decisions but items waiting for an availability window, and a written delegation of the smaller matters recovers more time than any meeting policy. The second concerns the role of in-person presence in regional business culture, which efficiency logic consistently misreads. Meetings here carry relational and signalling weight — attending demonstrates respect, and a decision reached without the meeting can be resented even when the outcome is identical. The workable approach is to reduce internal informing meetings aggressively while leaving external and relationship meetings alone, and to be explicit internally that the two are being treated differently rather than applying a single policy and causing offence. The third is about the written-first method and language. A pre-read culture assumes everyone reads fluently and comfortably in the document's language, which in a mixed Gulf workforce is not always true, and imposing it uniformly can systematically disadvantage people who contribute well verbally. Teams adopting written decision-making should be deliberate about this — shorter documents, key points in both working languages where it matters, and discussion time preserved for those who process better by talking.
The objection worth taking seriously
The strongest objection is that written decision-making optimises for the articulate. A well-argued document wins against a better idea expressed badly, and the people who thrive under a pre-read culture are those who write quickly and confidently in the dominant language — which correlates with background, education and native fluency rather than with judgement. Meetings, for all their inefficiency, give quieter and less fluent contributors a route in, and a shift to written process can quietly narrow whose views shape decisions while appearing more rigorous. That is a real effect and it is under-discussed in the literature on written culture. The mitigations are specific rather than abstract. Keep the discussion; the written form replaces the presentation, not the conversation. Have the author be someone other than the decision's advocate where possible. Solicit reactions individually before the group converges, which is worth doing anyway because group discussion anchors hard on whoever speaks first. And in a multilingual environment, keep documents short and allow contributions in either language. The alternative — defending meetings as an inclusion mechanism — is weaker than it sounds, because the same dynamics operate in rooms, less visibly, in favour of whoever is most senior and most comfortable interrupting.
Common Questions
Does a no-meeting day work?
Briefly. It relocates meetings rather than removing them unless the underlying decision rights are clarified.
How long should a pre-read be?
Short enough to be read in the room if necessary. Documents that assume advance reading are documents half the group will not have read.
What about meetings that exist to build relationships?
Keep them, name them honestly, and stop trying to justify them with an agenda. They are doing real work.
What should we expect over the next twelve months?
These are unverified predictions from the retained 15 September 2026 date, not measured outcomes. No standard feature, audit trend or performance advantage is established; test the proposed process against the team's own baseline.
Decision Process Design. We review decision rights alongside coordination and relationship needs. The calendar has several purposes, and no speed or meeting-volume outcome is guaranteed.