THE CODEX JOURNAL
Give a Dubai Business Meeting a Decision It Can Actually Make
Illustrative photograph: Max Avans / Pexels · Licence
Reading tools & contents
Name what the meeting can decide
Four people meet to discuss a pilot. There is a useful exchange about the client’s needs, the consultant’s experience and what the first few weeks could look like. An hour later, everyone is pleased. When the consultant sends the proposed start date, the client replies that the person who authorizes new suppliers is traveling and has yet to see the plan.
The conversation may have been worth having. What it could decide was narrower than the invitation suggested. An exploratory meeting can identify an opportunity or make a proposal worth preparing. A decision meeting can approve an action within a defined scope. An invitation should give people a chance to know which of these they are being asked to attend.
This matters in Dubai business settings where a working group can bring together people from several organizations, offices and timezones. A person may understand the work better than anyone else at the table and still be responsible for bringing a recommendation to somebody else. Ask where the decision sits before asking for a commitment.
Give the meeting a sentence that can survive it
Try writing the proposed outcome as an ordinary sentence without a verb like “discuss” or “align.” “Decide whether to prepare a paid pilot proposal” is a possible decision. So is “choose which of two delivery sites the team should assess first.” A smaller, clearly stated decision can move more work than an impressive discussion about a broad ambition.
The sentence also helps you plan the materials. A group deciding whether to evaluate a pilot needs enough information to estimate the effort of that evaluation. It may have no need for slides explaining every part of the full engagement. A person approving delivery needs to know what resources will be used, what result the team can reasonably expect and how the scope will be reviewed.
If the person who can decide is unavailable, change the wording and the work. You may be able to improve the recommendation and name the unresolved question. The meeting can then serve the decision without pretending it has already made it.
Find the people whose time you will use
Power to approve an undertaking and knowledge of what it will take can sit with different people. Before an agreement leaves the room, check who would have to supply access, answer questions or give part of a working week. An approver can accept a price while the person delivering the necessary files knows that half of them are held by another team. Both facts belong to the assessment.
Ask what each person owns after the meeting. “The operations team will provide access” hides the question of which person is able to grant it and by when. If the responsible person is absent, the next step may be to seek a realistic date from them. That is a real outcome, even if it is smaller than a confirmed start date.
You can make participation easier by sending a brief describing the question and the inputs in advance. Someone who is joining remotely or working in a second language then has a visible reference point. They can consider what a phrase like “pilot,” “access” or “handover” means in this specific undertaking before being asked to agree to it.
Hypothetical case: one approval, two missing conditions
Leila’s small studio is invited to propose a trial service for an events company in Dubai. The account lead likes the idea, and the managing director can approve a limited budget. During the call, the group nearly agrees to a first-week start. Leila asks who can grant access to the files she needs to do the work. The account lead says IT can grant it once the event team identifies which files are in scope.
Leila writes a narrower outcome in the meeting note. The director has agreed to consider a trial within the budget discussed after seeing a one-page scope. The account lead will name the file owner, and that person will confirm what can be shared. The tentative start date depends on both. No team has to treat unconfirmed work as promised.
The note is short enough to forward to an absent colleague. When the company later approves the scope, each person can see what changed and why the start date now means something different.
Make disagreement visible before the calendar fills
People sometimes leave a conversation using the same words for different commitments. One hears “pilot” and imagines a quick demonstration. Another imagines two weeks of usable service. A recap can give both a chance to correct the difference. Include the decision, the missing conditions, the person responsible for each and when the group will check again.
This is especially helpful when a positive meeting has an audience. Someone may hesitate to challenge a broad summary in front of senior participants. A clear written recap gives them something concrete to correct. If a decision is conditional, show the condition in the same sentence. If a person owes only a recommendation, describe it accurately.
The test of a useful meeting is what a colleague can do with the record tomorrow. They should be able to identify what was decided, what remains open and whose next action is needed. That information lets the work continue after the energy in the room has passed.