April 25, 2023 28 min read

Continuous Feedback or Annual Reviews? What UAE Managers Should Do

Introduction

Quick answer: The choice of continuous feedback vs annual reviews in the UAE comes down to timing and trust. Feedback given within days of the work can still change the outcome, while feedback saved for year end mostly records it. Adobe and Deloitte both replaced the annual review with regular check-ins, but the switch only works when expectations are written down, managers are trained to give feedback, and each conversation leaves a simple record.

“The February board pack went out with errors, and that cannot happen again.”

The finance manager reads the line aloud from the box marked “Areas for development”. It is mid-November, in a glass-walled meeting room at an insurance broker in Deira, and he is twenty minutes into an analyst’s annual review.

The analyst asks which errors. He scrolls back through his email. He is not sure. Something in the commission summary, he thinks. Or was that the March pack?

She has rebuilt that template twice since February. The original file was overwritten months ago. The board member who flagged the mistake has since left the company.

For nine months she believed February had gone well. Now it sits on her rating, and neither of them can say what went wrong.

Nobody remembers February. That is the real cost of saving feedback for the annual review. By the time it arrives, the evidence, the context and the chance to fix anything have gone. This guide is about the practice of feedback rather than the paperwork: what Adobe and Deloitte changed, the three things most companies skip when they copy them, and how to deliver feedback that people from many countries hear the way you meant it.

1. Continuous Feedback vs Annual Reviews in the UAE: Why Timing Decides Everything

For decades, performance feedback was an annual event. A manager collected impressions for twelve months, wrote them up in one sitting and delivered them in one meeting. The approach assumed work stayed still long enough for a yearly verdict to be useful.

That assumption broke for three reasons. Work changes faster, so a review of January’s priorities in December often describes a job that no longer exists. Younger professionals expect to hear how they are doing more than once a year, and they leave when they do not. And in UAE offices, where one team can span eight or ten nationalities, a single annual conversation leaves too much room for each person to read the verdict through their own cultural lens.

Feedback has a short shelf life. Within a week, both people remember the meeting, the client and the numbers. After a month, details blur. After nine months, as the analyst in Deira found, the conversation turns into an argument about what happened rather than a discussion of what to do next.

Key Benefits of Continuous Feedback

  • Correction while it still matters. A mistake raised on Tuesday can be fixed before Thursday’s deadline.
  • Recognition while it means something. Thanks given the week of the win carries weight that a line in December cannot.
  • No surprises at review time. If every issue was discussed when it happened, the formal review simply confirms what both people already know.
  • Better pay and promotion decisions. A year of small, recorded conversations gives managers evidence instead of impressions.

If your real question is which review structure to run, our decision guide on the performance management system vs annual appraisals compares annual, continuous and hybrid models side by side. The rest of this post stays with the conversations themselves.

2. Performance Management Case Study: Adobe's Check-In

In 2012, Adobe announced that it was dropping its annual performance review. In its place came Check-in, a model built on regular conversations between each manager and each employee.

Check-in centres on three subjects: expectations, feedback, and growth. Managers and employees agree what is expected, talk about how the work is going on a regular basis, and discuss the employee’s development and career. Formal ratings and forced rankings were removed, and managers were given more responsibility for decisions about pay.

Three design choices stand out for anyone copying it:

  • No fixed schedule from HR. Teams decide how often to meet, based on the work. A product team in a release cycle might talk weekly. A stable function might meet monthly.
  • The employee owns part of the conversation. People are expected to bring their own questions about career and development, not just wait to be assessed.
  • The manager is trusted. Without a rating form to hide behind, managers have to explain their decisions in their own words.

What a UAE manager can take from it: the meeting matters more than the form. Adobe did not succeed because it built a new template. It succeeded because it made the regular conversation the main event.

3. Performance Management Case Study: Deloitte's Redesign

Deloitte reached a similar place by a different route. In 2015 the firm described its redesign publicly, in a Harvard Business Review article, after concluding that its old process consumed a great deal of leader time without producing much insight.

One finding drove the change. Research the firm cited showed that ratings often reveal more about the person giving them than about the person being rated. Two managers can watch the same piece of work and score it quite differently, depending on their own standards and habits.

Deloitte’s response had two parts:

  • Frequent check-ins. Team leaders were expected to check in with each team member regularly, ideally every week, focused on near-term work and priorities.
  • Performance snapshots. At the end of a project or a quarter, team leaders answered a few short questions about what they would do with each person, such as whether they would want that person on their team again, rather than rating abstract skills.

The lesson for UAE managers is about the question you ask. “Rate this person’s communication from 1 to 5” invites bias. “Would you staff this person on your next client project, and why?” invites a judgement the manager can explain and defend.

Other examples often cited: GE and Google

GE moved away from its old forced ranking approach and toward frequent, app-supported conversations between managers and employees about priorities and progress. Google is known for setting goals with Objectives and Key Results, or OKRs, which keep a short list of ambitious objectives visible to everyone and make progress easy to discuss.

None of these companies proved that annual reviews are worthless. They proved that a yearly form cannot carry the weight of feedback on its own.

4. Three Things Most Companies Skip When They Copy Adobe

Plenty of organisations announce continuous feedback, cancel the annual form and find a year later that nothing has changed. Usually they skipped one of three foundations.

Set clear expectations first

Feedback needs a reference point. If an employee does not know what a good month looks like, every comment feels like an opinion. Before the first check-in, write down three to five expectations for each role in plain language. “Board pack issued by the 5th working day, reconciled to the ledger, no restatements” gives both people something to point at. “High-quality reporting” does not.

Train managers to give effective feedback

Most managers in the UAE were promoted for technical skill, not for coaching. Asking them to hold fortnightly feedback conversations without training is like asking a strong accountant to run a sales team on day one. A half-day session covering how to describe behaviour, how to ask before telling and how to close with a next step does more for a continuous feedback culture than any new policy.

Use technology to keep a light record

Conversations that leave no trace get forgotten, which is how February disappears. The record does not need to be long. Two or three lines after each check-in, noting what was discussed and what was agreed, is enough. Keep those notes in one shared place the employee can see, not in a manager’s personal notebook.

5. How to Give Feedback Well in a Multicultural UAE Team

Here, technique starts to matter. The same sentence can sound fair to one colleague and insulting to another. These habits travel well across cultures.

Describe the work, not the person

Use a simple structure: the situation, the behaviour you saw and its impact. “In Tuesday’s client call, you corrected the client’s figures in front of their CFO, and they asked me afterwards to handle the account myself” is specific and hard to misread. “You need to be more diplomatic” leaves the listener guessing.

Correct in private, and check how people like to be thanked

Corrective feedback belongs in a one-to-one, never in a team meeting or a group chat. Public praise is not always welcome either. Some colleagues enjoy recognition in front of the team, while others find it uncomfortable. Ask once, and remember the answer.

Make it easy to respond

In many workplaces in the region, disagreeing with a manager directly feels risky. If you finish with “Any questions?”, you will often hear silence. Ask open questions instead. “How did that call look from your side?” or “What would you do differently next time?” gives the employee a safe way in.

Watch the language

English is a second or third language for many people in UAE offices. Idioms and understatement cause misunderstandings. “Not bad” might mean praise to one listener and criticism to another. Say exactly what you mean, then confirm the main point in a short written note. Where a team member is more comfortable in Arabic, offer to hold the conversation, or send the summary, in Arabic.

Respect seniority without avoiding the issue

Giving feedback to an older colleague, or to someone senior in another department, can feel awkward. Frame it as a request about the work: “Can we agree that change requests reach my team by Wednesday? Last week’s arrived on Friday afternoon and we missed the cut-off.” That keeps the respect and still names the problem.

Mind the calendar

During Ramadan, working hours in the private sector are typically two hours shorter, and many colleagues are fasting. Schedule harder conversations earlier in the day, keep them brief, and avoid the hour before the end of the shift.

Instead ofTry
“You need to communicate better.”“The site team heard about the date change from the client first. Next time, send them a two-line update the same day.”
“Great job this week.”“The way you rebuilt the commission summary overnight saved the board meeting. Thank you.”
“Any questions?”“What part of this would you approach differently?”
“This isn’t up to standard.”“The reconciliation was off by AED 14,000 on line 12. Let’s walk through how it happened.”

6. Encourage Employee Self-Evaluation

Self-evaluation turns feedback from a verdict into a conversation. When the employee speaks first, the manager learns what they already know, and the employee hears criticism as confirmation rather than a surprise.

Before each check-in, ask the employee to answer three short questions in writing:

  1. What went well since we last spoke, and what did you learn from it?
  2. Where are you stuck, and what would help?
  3. What is one thing you want feedback on?

The third question matters most. It hands part of the agenda to the employee, which is the same principle behind Adobe’s model. It also tells the manager which feedback will be welcome, which is useful in teams where people rarely ask for it directly.

For the formal review, ask for a self-rating before the manager rates. Where the two scores are far apart, you have found the conversation that most needs to happen.

7. A Feedback Rhythm Built Around the UAE Working Year

Continuous does not mean constant. It means feedback arrives at predictable moments, each with a clear purpose.

MomentTimingPurpose
In-the-moment feedbackWithin 48 hours of the eventRecognise a win or correct a mistake while details are fresh
Check-inEvery one to two weeks, 15 minutesProgress on goals, blockers, one piece of feedback each way
Look-backQuarterlyReview goals, adjust priorities, discuss development
Formal reviewOnce or twice a yearSummarise the year from recorded notes, set pay and promotion decisions

Plan around the local calendar. Hold look-backs before Ramadan and before the July and August leave season, so nothing important waits for weeks. And keep the formal review short. If the check-ins worked, it should contain no news.

8. Where Software Helps, and Where It Cannot

Software cannot give feedback for you. What it can do is make the habit easier to keep: reminders that a check-in is due, a shared place for notes, goals that both people can see, and a timeline that makes the year-end review a summary instead of an excavation.

A performance management system in Dubai built for local teams should handle check-in scheduling, notes, goal tracking and peer feedback in one place, in Arabic and English. Feedback also works better when people already feel heard, so pulse surveys and peer recognition through employee engagement software in Dubai are a natural companion. For the wider system, from 360 reviews to calibration, see our pillar guide on performance management systems in Dubai and automating appraisals across the UAE.

Workplus HCM grew out of the HR advisory work of Tuscan Consulting, which counts more than 450 clients across the Gulf. The product itself is cloud software, made in Dubai, that runs HR and payroll for UAE and GCC employers. On the performance side, it tracks goals and KPIs, stores the feedback from each check-in, runs formal appraisals and gathers 360-degree input, with an engagement module next door. Employees open their goals and check-in notes from the mobile app, and workflow automation sends the reminders managers tend to forget. Pricing is published and starts from AED 12 per employee per month, with no minimum team size, as set out on the Workplus HCM plans page.

Conclusion

Back in Deira, imagine the same analyst in a different year. The board pack error is raised the morning after it happens. She fixes the template that week, and two lines in the check-in notes record what went wrong and what changed. By November, February is a solved problem, not a mystery.

That is the practical answer to continuous feedback vs annual reviews in the UAE. Keep a formal review if you need one for pay, but let the real feedback happen within days, in plain language, with a short record. Start by asking your managers to hold one 15-minute check-in with each team member this month. When you want to see that rhythm supported by software, book a Workplus HCM demo: a free 30-minute walkthrough, followed by a two-day trial you can run with your own managers.

Frequently Asked Questions

What is the difference between continuous feedback and annual reviews?

Continuous feedback happens throughout the year, in short check-ins and in-the-moment comments, while an annual review is one formal assessment of the past twelve months. Continuous feedback can change the outcome of work in progress. An annual review mostly records what has already happened, which is why many companies now keep it only for pay decisions.

Did Adobe and Deloitte get rid of performance reviews completely?

They replaced the traditional annual review rather than abandoning performance management. Adobe moved to regular Check-in conversations about expectations, feedback and growth, without formal ratings. Deloitte introduced frequent check-ins and short performance snapshots at the end of projects or quarters, which still inform pay and promotion.

What is a good performance management case study for continuous feedback?

Adobe’s Check-in, launched in 2012, and Deloitte’s redesign, published in 2015, are the two most widely discussed. Adobe shows how far regular conversations can replace a rating form. Deloitte shows why better questions about future action produce more reliable judgements than abstract skill ratings.

How often should managers give feedback to employees?

Give quick feedback within a day or two of anything worth noting, and hold a 15-minute check-in every one to two weeks. Add a quarterly look-back at goals and development. A formal review once or twice a year then summarises the notes instead of introducing new issues.

How do you give feedback in a multicultural team in the UAE?

Be specific about the situation, the behaviour and its impact, and avoid idioms or understatement that can be misread. Give corrective feedback in private, invite the employee to speak first with open questions, and confirm the main point in a short written note. Offer Arabic where a colleague is more comfortable in it.