KPIs and 360 feedback in Egypt: start with the culture
In a high-power-distance culture, a copy-pasted 360 gets polite silence. How to run reviews, OKRs, and upward feedback in Egypt without breaking trust.
Somewhere there's a performance-review template built for a flat, say-anything office in California, and somewhere else a manager in Cairo is about to paste it onto a team that doesn't work that way at all. Egypt scores high on power distance — around 70 on Hofstede's scale — which in plain terms means hierarchy is felt, the respected boss is a benevolent authority, and the workplace runs more like a family than a debating society. Loyalty is the currency. Ask that team to anonymously rate their manager on day one and you won't get candour. You'll get silence dressed as praise, or you'll get someone who spoke honestly and now wishes they hadn't. The tools aren't wrong. The order and the framing are.
Why the copy-paste 360 fails here
A 360 assumes something specific: that people will tell the truth about someone with power over them. In a high-power-distance culture that assumption breaks quietly. Junior staff soften anything that could read as criticism of a senior; peers avoid going on record; leaders, used to feedback flowing down, aren't sure they want it flowing up. So the process runs, the forms come back full, and the data inside them is nearly worthless — everyone was polite. Worse is the version where someone was honest and it got traced back to them. Now you haven't just collected bad data; you've taught the whole team that candour is dangerous. One clumsy cycle can set a feedback culture back years.
Start with goals, not opinions
The way in isn't feedback. It's goals. Before anyone rates anyone, put clear, shared targets in place — OKRs for the team, KPIs for the role — visible to everyone and agreed up front. This changes the entire nature of a review. It stops being "what do you think of me," a question that's genuinely threatening in this culture, and becomes "did we hit the number we both signed up to." Evidence is neutral in a way opinion never is. When a review rests on a target that was transparent from the start, you can talk about a shortfall without it feeling like a personal attack on someone's standing — which is exactly the protection a hierarchical, face-conscious workplace needs.
Make 360 safe, or don't run it
Once goals are trusted, you can layer in multi-source feedback — but only with the safeguards the culture requires, and they aren't optional here. Anonymity is the whole game: not "we'd prefer you were honest," but aggregation that makes it structurally impossible to tell who said what. Frame the exercise as development, not judgment — feedback that helps someone grow, not a verdict that ranks them. And model it from the top: in a place where loyalty runs like family, a senior leader who visibly asks for feedback and takes it well does more to unlock honesty than any policy. A 360 that can be traced, or that smells like an evaluation, is a 360 nobody answers truthfully. Better not to run it at all than to run it and break trust.
The annual tribunal is the wrong shape
There's a structural mistake underneath most of this: saving feedback for one big yearly event. The annual review turns performance into a high-stakes tribunal, which in a fear-sensitive culture is the worst possible design — everything rides on one conversation, so everyone plays it safe. Flip it. Short, frequent, low-drama check-ins make feedback ordinary, and ordinary is what removes the fear. When a quick conversation happens every few weeks, no single one has to carry the weight, and honesty stops being a gamble. Culture doesn't change by decree; it changes by repetition at low stakes.
Let the system carry the awkward part
A lot of what makes this hard is interpersonal friction — the discomfort of asking, of being the one who has to collect and aggregate and anonymise. That's the part a system should absorb. With HRMira the goals live where everyone can see them, so reviews rest on evidence; 360 feedback is gathered and aggregated so no single voice is ever exposed; and check-ins run on a light, regular cadence instead of one dreaded annual event. The tool handles the mechanics that make honesty feel risky, which leaves managers free to do the human part — the actual conversation. You don't import a feedback culture. You build one, carefully, on ground that can hold it.
Frequently asked questions
Does 360-degree feedback work in Egypt?
It can, but not as a copy-paste. Egypt is a high-power-distance culture (Hofstede score around 70), where junior staff are reluctant to critique managers openly. A 360 run without genuine anonymity and a growth framing tends to produce softened, useless feedback — or fear. Done with those safeguards, it works.
How do you start performance reviews in a traditional, hierarchical company?
Start with shared goals, not opinions. Clear OKRs or KPIs turn a review into 'did we hit the target' rather than 'what do you think of me,' which lowers the personal threat in a culture where direct critique is uncomfortable. Add feedback carefully once the goal framework is trusted.
What's the difference between OKRs, KPIs and a 360 review?
OKRs and KPIs are goals and metrics — the objective evidence of what got done. A 360 review is multi-source feedback on how someone works, gathered from managers, peers and reports. The first depersonalises performance; the second adds perspective. In a hierarchical culture, lead with the goals and layer the 360 on top.
