When a Barista Has to Go: Doing It Properly in the UAE

Almost nobody handles this well, and the reason is nearly always the same. The problem was obvious in June. You mentioned it once, lightly, hoping it would correct itself. It didn't, and because the café was busy you let it run through the summer. Then in October something small happens on a bad morning, you lose patience, and the whole thing gets settled in one afternoon — with no record of anything that came before it, in a conversation neither of you is ready for. The outcome may even be the right one. The way you got there is what causes the damage.

This post is about the structure: how to raise a problem early, what a written warning is for, how to keep a record while things are happening rather than reconstructing one afterwards, and why that paperwork protects the employee as much as it protects you. It deliberately states no notice period, no number of warnings and no end-of-service figure. Those are matters of law and of the individual contract — see staff contracts and visas and end-of-service gratuity for where they live — and anything specific to your situation belongs with MOHRE or an employment adviser, not with a blog post.

Why delay is the expensive part

Every month you wait makes the eventual conversation worse. The employee has had half a year of implicit confirmation that their work is acceptable, so the news lands as a reversal rather than a conclusion. Your own patience is spent, so you arrive angrier than the issue deserves. And the rest of the team has watched the whole thing: they know who is not pulling their weight, they know you know, and they have drawn their conclusions about what standards actually mean here. A late, abrupt dismissal reads to everyone else as arbitrary — which is precisely the thing that makes the good people start looking.

Performance and conduct are not the same problem

Treating these as one category is the most common mistake, and it produces responses that fit neither. Performance is a question of capability and consistency: slow on the bar, milk inconsistent, forgets the closing checks. It is usually fixable, it responds to training and clear expectations, and it needs a stated standard and time to meet it. Conduct is different in kind — it is about choices rather than ability, and no amount of training addresses it.

The distinction matters because it decides what you do next. A performance problem deserves a stated expectation and a fair window to meet it. A conduct problem deserves a proper look at what actually happened — what you can show, who saw it, what the person says when asked — before any decision. The temptation with conduct is to act immediately because you are certain. Certainty is not the same as a record.

What a written warning is actually for

Owners tend to think of a warning as a punishment, or as a box to tick on the way to a dismissal. It is neither. A warning is the moment you convert a vague dissatisfaction into something specific enough to be acted on. That is its whole function: the person finds out exactly what is wrong, exactly what acceptable looks like, and when you will both look at it again.

Which means a useful warning has four things in it and almost nothing else: what the issue is, in concrete terms rather than adjectives; what you expect instead, stated so plainly that both of you would agree later whether it happened; the date; and when you will review it. "Attitude needs to improve" fails all four tests. "The closing checklist was not completed on 3, 7 and 11 October; from now on it is completed and initialled before you leave, and we will review this in three weeks" passes them.

Give the person a copy. Keep one, signed or at least acknowledged, in their file. If they disagree with it, note the disagreement on the document rather than arguing it off the record — a warning the employee contested in writing is still a far better record than a conversation nobody wrote down. And resist stacking warnings for things you never mentioned at the time. A warning that lists six grievances from the past year tells the reader you have been collecting rather than managing.

Keep the record as it happens

The single most useful habit here costs about two minutes. When something happens, write it down that day: the date, what happened, what was said, who was there. Not a case file — three lines in a notebook or a note on your phone. Do it for the good things too, so the file is a record of a working relationship rather than a prosecution.

The reason is not legalistic, it is about accuracy. A record written in October about something that happened in June is a reconstruction, and reconstructions drift towards whatever you now believe. Contemporaneous notes protect the employee from your memory as much as they protect you from theirs. They also make the conversation easier: dates and specifics are far less combative than a general sense that things aren't working, because they can be discussed.

The conversation itself

Hold it in private, not across the bar, and not at the end of a double shift when you are both exhausted. Say the specific thing in the first thirty seconds — people brace for whatever follows a long preamble, and the preamble makes it worse. Then stop talking and let them respond. Sometimes what you get back changes the picture entirely: the closing checks have been skipped because the opener keeps leaving at a different time, or there is something going on at home. You cannot find that out while you are still explaining.

Agree what happens next out loud, then put it in writing the same day — a short message summarising what was discussed and what was agreed. Not to build a file against them; so that in three weeks you are both working from the same account of the meeting. If the standard isn't met by the review date, the next conversation is much simpler, for both of you, because nothing in it is a surprise.

If it does end in a dismissal

The private-sector employment relationship in the UAE is governed by the federal employment decree-law and the rules MOHRE issues under it, and it has been amended more than once in recent years. The framework requires a legitimate reason for dismissal, sets out specific grounds on which an employer may dismiss without notice, and expects misconduct cases to rest on a documented investigation and a written, reasoned decision. Disputes start at MOHRE rather than in court. That is the shape of it — the detail, including anything about notice, entitlements or what MOHRE must be told and when, is exactly what changes between amendments.

So the honest advice is procedural rather than specific: before you end anyone's employment, check the current position on the MOHRE website and, if there is any complication at all, pay for an hour of an employment lawyer's time. An hour is cheap against a dispute, and considerably cheaper than discovering after the fact that the way you ended it was the problem rather than the decision itself. Do not rely on what a friend's accountant told them two years ago, and do not rely on this paragraph either.

Whatever route it takes, finish it properly: settle what is owed, be straightforward about the reference, and tell the remaining team something brief and respectful rather than nothing at all. Silence gets filled with a worse story than the truth. Most of what makes people stay is the sense that the place is run fairly, which is the quiet subject of why good café staff leave.

Where MidaOne fits

Most of this is paperwork and nerve, and no software supplies either. But a recurring version of this problem is caused by not being able to see what happened, which turns a factual question into an argument about character.

MidaOne reports sales by employee and shows shift closes as expected against counted, with the difference — so a till shortfall becomes a number on a specific shift rather than a suspicion about a person. Roles and permissions are scoped by role and by branch, which means a refund or a void sits with whoever is actually authorised to do it, and the question of who did what stops being a matter of recall. Used properly that is not surveillance; it is the thing that lets you raise an issue early, with a date attached, while it is still small enough to fix. POS permissions and staff security covers how to set them up, and the rules themselves belong in the staff handbook.

Frequently asked questions

The test of whether you handled it properly is not whether the person left. It is whether, three weeks earlier, they could have told you exactly what was wrong and exactly what would fix it. If they could, you managed it. If they couldn't, you postponed it — and the paperwork at the end was never the thing that was missing.