Performance Reviews in Belarus: Here’s What Actually Works
True story we hear at least twice a year. A US engineering manager gives a Belarusian senior dev a “3 out of 5” in an annual review. In the manager’s head, that’s a perfectly fine score — “meets expectations, room to grow.” The developer reads it as a formal warning. Maybe even the beginning of the end. Two months later, the engineer is interviewing somewhere else, and the manager has no idea why.
The rating scale was the same. The intention was the same. But the cultural weight of the number was completely different. And that’s just one example. The way feedback is delivered, how often reviews happen, what a PIP signals, what the law actually requires before you can let someone go — almost none of it maps cleanly from a US or UK playbook onto Belarus.
So here’s the practical version: how to run reviews, have productive one-on-ones, deal with underperformance, and navigate PIPs for IT teams in Belarus. Without wrecking trust or accidentally violating labor law.
How Belarusian Engineers Actually Hear Your Feedback
Belarusian professional culture falls somewhere between German directness and Russian hierarchical awareness. That’s a rough shorthand, but it helps. The following are the most common patterns that trip up international managers.
Formal feedback hits hard. Much harder than you’d expect if you’re coming from Silicon Valley, where everyone pretends a “3” is neutral. In Belarus, when you put something in writing or attach a number to someone’s work, they treat it as a definitive statement. Engineers who get a middling score in a structured review often walk away thinking the company is building a file on them. Even if you meant it as “you’re doing fine, here’s where to push.”
Public criticism is a trust-killer. This one catches remote managers off guard. You call out a missed deadline in a team Slack channel, thinking you’re being transparent. What the engineer hears is humiliation in front of peers. Keep critical feedback private, tied to specific work, and separate from the person.
Feedback is received differently depending on technical credibility. A CTO who can analyze the code and identify a specific architectural risk will be treated quite differently than a people manager who says, “The team feels your code quality has slipped.” If you’re not technical, bring someone who is. It’s not about ego. It’s about whether the engineer trusts the source.
Ask but do not tell. This may be the most useful modification a foreign manager can make. Instead of “You need to refactor this module,” try “What would you change about how this module is structured?” Same destination. But one version treats the engineer as a professional with judgment, and the other treats them as someone who needs to be corrected. Guess which one gets better results.
Review Cadence: What Actually Works
Most serious IT businesses in Belarus have already discontinued annual reviews. They are too infrequent to be beneficial, and in a culture where formal criticism is valued, an annual review feels more like a punishment than a conversation.
Here’s the three-layer cadence that works for distributed teams with Belarusian engineers.
Quarterly structured reviews. This is the backbone. Both sides prepare. You look at what was agreed last quarter, you talk about what happened, and you set goals for the next one. If you’re going to use ratings or scores at all, this is the only place they should appear. These need to be documented — partly because documentation is good management practice, and partly because Belarusian labor law will want to see a paper trail if you ever need to act on underperformance.
Monthly one-on-ones. Thirty minutes. Informal. Not a status update — that’s what standups are for. This is where you find out that someone is frustrated with the architecture decisions being made above them, or burned out after a sprint crunch, or quietly thinking about leaving because nobody’s talked to them about their career path in six months. Problems that show up in quarterly reviews as “performance issues” very often started as things someone would have told you in a one-on-one if you’d asked.
Weekly or biweekly standups for project-level stuff. Sprint retros, delivery updates, code review feedback. These are not performance reviews, and treating them like performance reviews confuses the signal and makes people defensive about the wrong things.
Why does quarterly beat annual? Because an engineer who hears “you’ve been underperforming for a year” has nowhere to go in that conversation. An engineer who hears “this quarter didn’t land — let’s figure out what happened and fix it” has a path forward. That distinction matters everywhere, but it matters especially in a culture where formal negative feedback feels like a much bigger deal than Americans tend to realize.
One-on-Ones: The Tool Nobody Uses Enough
Here’s a pattern we see constantly: a foreign manager has a Belarusian engineering team working remotely, relies on Slack and daily standups for communication, skips one-on-ones because “we talk every day anyway,” and then is surprised when a performance problem seems to come out of nowhere.
Standups tell you what people are doing. One-on-ones tell you how people are feeling about what they’re doing. That’s a completely different signal, and you cannot get it from a group setting.
A few things that make one-on-ones work with Belarusian teams specifically. Don’t cancel them. Seriously. Canceling a one-on-one tells the engineer it’s not important to you, and in a professional culture where relationships are taken seriously, that registers as a lack of respect. Let the engineer set the agenda first — you learn more when they pick the topics. Don’t ambush people with critical feedback in a one-on-one; save that for the structured quarterly review where they can prepare too. And talk about their career. Where do they want to be in two years? What skills do they want to build? Belarusian engineers take professional growth seriously, and the one-on-one is where you show that you do too.
If you’re managing a team through an EOR and don’t have an internal HR function, Recruitment.by’s HR consulting team can help you set up these rhythms. It’s not complicated, but having someone who knows the local professional culture makes the setup faster and the mistakes fewer.
Before the PIP: The Conversation You Can’t Skip
This might be the most important section in this entire post. If you take one thing away, let it be this: do not put a Belarusian engineer on a formal PIP without having had at least two prior conversations about the issue.
PIPs can occasionally emerge swiftly in US.
When performance dips, the management notices it, HR develops a plan, and the employee receives a document. That cadence, applied to a Belarusian team, feels like a betrayal. The engineer’s internal reaction is: “You never informed me of a problem, and now I’m on a formal improvement plan? You were preparing a case against me. Even if it isn’t what happened, that’s how it appears.
Before any formal PIP, honestly ask yourself: did I tell this person, clearly and specifically, what the problem is? Did I check whether something outside of work is going on — health, family, burnout? Did I actually offer help — not in a vague “let me know if you need anything” way, but specific help like training, workload adjustment, or pairing them with a stronger engineer on the area where they’re struggling? Did I give them a real timeline to improve? And did I follow up?
If all of that happened and things didn’t get better, then a PIP is the right next step. Research cited by RemoFirst suggests that PIPs with real support behind them work about 60% of the time. But that number only holds when the employee genuinely believes the PIP is a chance to get back on track, not a paper trail for firing them. If you skipped the informal stage, you’ve already told them which one it is.
PIPs in Belarus: What the Law Actually Says
This is where it gets real. If you’re used to US at-will employment, you need to recalibrate.
Belarusian labor law — specifically Article 42 of the Labour Code — doesn’t have a “poor performance” termination category the way American employment does. You can’t just decide someone isn’t working out and let them go. Grata International’s legal analysis spells it out: dismissal has to be based on specific statutory grounds. The closest one to “performance” is “systematic failure to perform duties without valid reason, where disciplinary measures have been applied previously.”
Read that last part again: “where disciplinary measures have been applied previously.” Before you can take action, you must first establish a documented trail of warnings and improvement possibilities. A well-built PIP is that trail.
What goes into a PIP that actually holds up? Specific performance gaps with dates and evidence — not “their work has been below expectations” but “missed delivery deadlines on three out of five sprint commitments in Q2, specifically on tickets X, Y, and Z.” Clear improvement targets with a timeline — 30, 60, or 90 days, depending on the situation. Real support: training, mentorship, adjusted workload. Weekly check-ins during the PIP so the engineer gets regular feedback, not silence followed by a verdict. Everything in writing. And the employee should sign or acknowledge receipt of the document.
What kills a PIP legally? Vague language. “Bad attitude” and “not a culture fit” are not enforceable under Belarusian law and will get shredded if this ever reaches a labor dispute. Punitive framing — if the PIP reads like a threat instead of a plan, it undermines the entire purpose. And issuing a PIP without prior informal feedback — legally weak and culturally tone-deaf.
If the PIP ends and improvement didn’t happen, the documentation gives you legal standing for termination. If you’re employing through an EOR or PEO, they handle the legal process — but the evidence has to come from you.
When It’s Over: How Termination Actually Works
So the PIP ran its course and things didn’t improve. Now what?
You can proceed with termination, but only if the process was clean. Rivermate’s termination guide for Belarus lays out the mechanics: one month’s notice minimum, severance of at least three average monthly salaries for employer-initiated dismissals, a written dismissal order, the employee’s employment record book returned, and final settlement — including accrued leave — paid on the last working day. Not the next pay cycle. The last day.
If you’re using an EOR, they execute the procedural steps. But they can’t manufacture a documentation trail that doesn’t exist. The quarterly reviews, the one-on-one notes, the PIP itself, the evidence that you offered support — that all has to come from the manager’s side.
If things go wrong: insufficient documentation trail, bypassing the informal feedback stage prior to the PIP, attempting to terminate someone on maternity or child care leave (legally protected, period), and failing to engage the trade union if a collective agreement mandates it. Belarus’s employment law framework protects employees strongly against arbitrary dismissal. Courts can and do restore people, including back pay for the full time they were absent. That’s not a theoretical risk. It happens.
The takeaway is simple: build the documentation from day one. If your review process is running properly, the paper trail creates itself, and you never have to scramble to reconstruct it after the fact. If you’re setting up employment in Belarus for the first time, Recruitment.by’s payroll and EOR services include compliance guidance for exactly these situations.
Small Things That Aren’t Small
These are the details that don’t make it into management textbooks but make a real difference when you’re leading a Belarusian engineering team.
Don’t give tough feedback on Friday afternoon. The engineer goes into the weekend replaying the conversation, can’t ask follow-up questions, and comes back Monday either resentful or anxious. Schedule hard conversations early in the week so there’s time to talk through it while you’re both still at work.
Watch your framing. “You failed to meet the deadline” and “The deadline slipped — what happened?” get you to the same place. But the first one sounds like an accusation, and the second sounds like a conversation. With Belarusian engineers, that difference isn’t subtle. It’s the difference between someone who gets defensive and someone who actually tells you what went wrong.
Turn your camera on. If you’re doing a quarterly review or any serious feedback conversation over video, be on camera. A voice-only call for something that matters to the engineer’s career says you didn’t think it was worth showing up for.
Send a written summary. Following each review or difficult conversation, provide a brief written summary. Belarusian professionals place a high priority on written documentation. It shows the conversation was real, not something that can be rewritten later.
Be consistent. If one person gets quarterly reviews and another doesn’t, people notice instantly. And they don’t assume it’s an oversight. They assume it’s favoritism or targeting.
Say thank you sometimes. Belarusian engineers aren’t going to ask you for recognition. But they absolutely notice when it’s missing. A message from the CTO after a strong quarter, a shoutout when someone solved a nasty bug, a note when a feature ships — it costs nothing, and it builds the kind of loyalty that a bigger paycheck somewhere else can’t easily undo. If you want a fuller picture of what keeps Belarusian IT talent around, our guide to health insurance and wellness benefits covers the structural side.
Frequently Asked Questions
The law doesn’t use the word “PIP.” But it does require that dismissal for “systematic failure to perform duties” be backed by prior disciplinary measures and proof that the person had a real chance to improve. A well-structured PIP checks all those boxes. Without one, a performance-based termination is on shaky legal ground.
Quarterly. It’s frequent enough to catch problems early and build a documentation trail, but not so frequent that it feels like micromanagement. Back it up with monthly one-on-ones and weekly standups for project stuff. Annual reviews on their own don’t cut it — culturally or legally.
Yes. Probation can last up to three months, and either side can end it with three days’ notice. But even during probation, you should document specific performance issues. “It wasn’t a fit” won’t hold up if the person challenges it.
American tech normalizes blunt, frequent feedback and treats a mediocre rating as no big deal. Belarusian engineers weigh formal feedback more heavily — a “3 out of 5” reads closer to a warning than a baseline. You can be just as honest. But keep it private, keep it specific, frame it around the work rather than the person, and whenever you can, phrase it as a question instead of a statement.
You both do. The manager identifies the problem, has the conversations, documents everything, and runs the PIP. The EOR makes sure the process complies with Belarusian law, manages the formal paperwork, handles severance, and executes the termination if it gets there. Think of it as: you own the substance, they own the compliance. More on how that split works in our EOR vs. PEO comparison.
At minimum, three average monthly salaries. The employment contract or a collective agreement might set a higher number. On top of that, any accrued leave and outstanding pay has to be settled on the last working day — not next payroll, not in two weeks. If you need to estimate the total cost, our salary benchmarks for Belarus IT are a good starting point.
Look, managing performance in Belarus isn’t harder than anywhere else. It’s just different. The law cares about documentation. The culture cares about respect and consistency. And the engineers respond to managers who are actually invested in their growth, not just tracking their output. Get that right and you hold onto people that your competitors are spending real money trying to recruit away from you.
If you’re figuring this out for the first time, Recruitment.by’s HR consulting team works with foreign companies on review processes, PIP frameworks, and termination compliance. It’s the kind of thing where having someone local saves you from the mistakes you’d only learn about the hard way.