Performance Management in Lebanon: A Guide for SMEs
Performance management in Lebanon is often reduced to a form completed once a year. The form gets filed. Nothing changes. Managers feel they have done their duty. Employees feel they have been assessed. Neither party is particularly satisfied, and performance in the business continues to be managed as it always has been: informally, inconsistently, and mostly reactively.
This article is for Lebanese SMEs that want to build a performance system that actually works, before Q4 reviews begin and 2027 planning starts.
What performance management actually means
Performance management is the ongoing process by which a company sets expectations, monitors progress, coaches employees, conducts formal evaluations, and recognizes or develops performance over time. It is a cycle, not an event.
Four terms often get used interchangeably, but they describe different things:
- Performance management is a comprehensive system that runs continuously throughout the year.
- Performance appraisal is one formal review within that system, typically conducted annually or twice a year.
- Performance monitoring is the regular evidence-gathering component: check-ins, observations, output data, and documented feedback.
- Employee development is the support given to close performance gaps or prepare someone for expanded responsibilities.
The AUB Medical Center’s performance management manual describes this as a continuous cycle that covers planning, monitoring, coaching, formal evaluation, communication of the evaluation, and recognition or reward. All six stages matter. Companies that skip to evaluation without doing the other five stages are not managing performance. They are administering paperwork.
Why performance management breaks down in Lebanese SMEs
Most performance systems in Lebanese SMEs break down before they produce any useful result. The reasons are consistent across companies of different sizes and sectors.
Job descriptions no longer match the actual job. When a person’s responsibilities have shifted over three years, but the document has not been updated, neither the manager nor the employee has a reliable reference point for the review.
Goals are communicated verbally. A manager says, “I need you to grow the client base this year.” The employee hears that differently in January than the manager remembers saying it in December.
Different managers apply different standards. One manager rates every team member as exceeding expectations. Another rates most of their team as average. Both are wrong, and employees in both teams know it.
Feedback is delayed until year-end. By the time the annual review happens, the events being discussed are six months old, largely forgotten, and no longer correctable.
Ratings are based on relationships, tenure, or the most recent three months rather than the full year. This is called recency bias when it is accidental. When it reflects loyalty rather than performance, it has a different name entirely.
There is no documentation. Without written records, the review conversation becomes a debate about memory rather than an assessment of work.
Salary discussions dominate the meeting. The employee comes with compensation in mind. The manager is thinking about budget. Neither party is focused on the development and planning conversation, which should be the focus of the review.
Managers avoid difficult conversations. In the Lebanese SME environment, particularly in family businesses, long-standing relationships often make a critical feedback conversation feel like a personal confrontation. So it does not happen. Problems grow.
Employees do not understand how their work connects to company priorities. When the link between an individual’s daily work and the company’s direction is invisible, motivation suffers. The 2026 research from Sustainability, covering 511 employees in Lebanese family businesses, found that job satisfaction, motivation, and leadership had stronger effects on employee performance than compensation alone.
The performance management cycle Lebanese SMEs can use
1. Define the role
Before you set goals, the role itself must be clear. A one-page role description should state: the purpose of the role in one sentence, the five to seven main responsibilities, the decisions the person owns, the decisions requiring approval, who they report to, and what good performance in the role looks like at six months and twelve months.
This document is not a legal contract. It is a shared reference that the manager and employee agree on. Update it when the role changes.
2. Set three to five meaningful goals
Lebanon’s National Institute of Administration uses the SMART framework for objective-setting: Specific, Measurable, Achievable, Realistic, and Time-bound. This is a useful discipline, applied without rigidity.
Three examples suited to Lebanese SME roles:
Sales role: Increase revenue from existing clients in the Mount Lebanon territory by 15% between January and December, measured by monthly invoicing data.
Operations role: Reduce supplier delivery delays from an average of 4 days late to 2 days late by the end of Q3 by renegotiating lead times with the top 5 suppliers and updating the order schedule.
HR or administrative role: Complete updated job descriptions for all 22 positions by 31 October, reviewed and signed off by the relevant managers, stored in the shared HR folder.
Goals should connect individual work to company priorities. A goal that has no visible link to what the company is trying to achieve this year is a task, not a goal.
3. Agree on behavioral standards and competencies
Goals measure what someone delivers. Competencies measure how they deliver it.
Six competencies relevant to most Lebanese SME roles: communication (written and verbal), teamwork, customer or client handling, planning and organization, problem-solving, and leadership (for roles managing others).
Academic guidance from the American University of Beirut, referenced in their research on appraisal practices, recommends that performance standards be directly related to job responsibilities and that employees participate in defining them. A competency that a manager unilaterally defines and presents to an employee as a surprise during a year-end review is not a standard. It is a post-hoc judgment.
4. Hold short monthly or quarterly check-ins
A check-in is a 20- to 30-minute meeting between a manager and their direct report. It is not a review. It is a working conversation to keep performance on track.
Five questions for a useful check-in:
- What have you made the most progress on since we last spoke?
- Where are you running into difficulty?
- Is there anything you need from me that you are not getting?
- Are you on track with your goals for this period?
- What are your priorities for the next four weeks?
That is it. A manager who holds consistent check-ins with every direct report will rarely be surprised at a year-end review.
5. Document evidence throughout the year
Evidence is specific and factual. It includes: completed projects and their outcomes, measurable results against goals, specific incidents of strong or poor performance, written feedback from clients or colleagues, and attendance and timekeeping records.
Evidence is not: general impressions of attitude, vague references to “not being a team player,” or comparisons to what someone else would have done. These are opinions, not evidence, and they do not hold up when an employee disputes a rating.
A manager who writes three lines of notes after each check-in will have twelve months of evidence by the time the annual review arrives.
6. Conduct a balanced formal review
The formal review should not be the first time an employee hears critical feedback. If it is, the check-in process is missing.
A useful structure for formal reviews: the employee submits a self-assessment first. The manager reviews it before writing their own assessment. Both documents use the same goals and competencies set at the start of the year. The meeting is a discussion of both assessments, supported by evidence.
Guidance from the American University of Beirut’s appraisal research recommends self-evaluation as a standard component, noting that employee participation in the appraisal process produces more accepted and actionable outcomes.
A performance rating, when used, should be accompanied by a written rationale that references specific examples. “Met expectations with three clear goals achieved and two in progress” is a rating. “Average,” without further context, is not.
7. Connect the review to development and recognition
A performance review has two outputs: a backward-looking assessment of the year just completed, and a forward-looking development plan for the year ahead.
Keep salary discussions out of the same meeting where possible. When compensation is on the table, employees spend the review calculating rather than engaging. Separate the conversations: development in one meeting, compensation in another, shortly after.
Recognition deserves a moment in the review. Name the specific contributions that made a difference. This is separate from the rating. A person who met expectations and went out of their way to support a colleague during a crisis deserves to have both things said.
Goals, standards, and competencies
| Element | What it measures | Example | Common mistake |
|---|---|---|---|
| Goal | A specific, time-bound result | Reduce customer complaints by 20% in Q4 | Too vague: “improve customer satisfaction” |
| Standard | The baseline required for acceptable performance | Invoices processed within 48 hours | Not communicated until after the review |
| Competency | Behavior and skill applied consistently | Communicates clearly with clients and colleagues | Assessed on personality, not specific behavior |
How to reduce bias and favoritism
Performance ratings in Lebanese SMEs are vulnerable to the same biases that affect performance reviews everywhere, as well as to pressures specific to the Lebanese context.
Recency bias is the tendency to weight the last two months of the year over the previous ten. Counter it with documented evidence from throughout the year.
Halo effect means that one strong quality inflates the overall rating. A person who presents confidently gets rated higher across all competencies, including ones unrelated to presentation.
Horn effect is the reverse. One visible failure colors the entire assessment.
Similarity bias means managers rate people more favorably when they recognize themselves: same background, same style, same university.
Leniency or severity bias refers to managers who rate everyone above or below average regardless of actual performance. Both distort the picture.
Relationship influence is the pattern where personal loyalty, tenure, or family connection affects performance ratings more than work output. This is not unique to Lebanon, but the strength of relational networks in Lebanese business culture makes it worth naming directly. An employee who has been with a founder for twelve years and whose performance has declined deserves an honest rating, even if the conversation is difficult. Avoiding it is not kindness. It delays a problem that will eventually become a crisis.
Six practical controls:
- Use shared rating definitions so two managers describe “meets expectations” the same way.
- Require written evidence for each rating.
- Hold calibration meetings where managers review each other’s ratings before they are communicated.
- Include employee self-assessments in every review.
- Review extreme scores (all high or all low) before finalising.
- Train managers in feedback conversations before review season begins.
A practical year-end performance review agenda
A structured 45 to 60 minute meeting:
- Confirm the purpose and tone (2 minutes). Remind the employee that this is a two-way discussion, not a judgement delivered from above.
- Employee reflects first (8 minutes). “Walk me through what you are most proud of from the past year, and where you think you could have done better.”
- Review agreed goals together (15 minutes). Go through each goal. State what was achieved, what the evidence shows, and where the gap was if one exists.
- Discuss behavioural competencies (8 minutes). One or two specific examples per competency. Positive and developmental.
- Identify strengths (5 minutes). Be specific. Name the contribution and its impact.
- Address gaps with evidence (8 minutes). Stick to documented examples. Avoid general statements.
- Agree on development actions (8 minutes). What training, support, or experience will help? Who owns each action? By when?
- Set initial priorities for 2027 (5 minutes). Three goals to be finalised in January, once company direction for the year is confirmed.
- Record decisions and follow-up dates (closing). Both parties confirm what was agreed in writing before the end of the day.
Five phrases for difficult review conversations:
“The feedback I have on this is based on what we documented during the year, so let me walk you through it.”
“I want to be direct with you because I think you are capable of more than this shows.”
“You achieved the result, and I want to talk about the approach, because it created some issues for the team.”
“I understand this is not the rating you were expecting. Here is the evidence I used to reach it.”
“What support do you need from me to make next year look different?”
What performance management should not become
A yearly paperwork exercise that changes nothing. The purpose of a system is behaviour change, not documentation.
A justification for a decision already made. If a manager has decided someone’s rating before the review, the meeting is theatre.
A salary negotiation with no performance evidence. The review should produce compensation input, not replace the compensation conversation.
A forced ranking system that distributes employees into preset categories. Forcing 20% of employees into a low-performance band in a 15-person company destroys team trust.
A technology substitute for management. Software tracks performance data. It does not replace a manager who knows how to have a hard conversation. Research involving SMEs in North Lebanon, published in the Iraqi Academic Scientific Journal, found a positive relationship between digital HR practices and organisational performance. That relationship depends on the quality of the process the software supports, not the software itself.
A disciplinary surprise. An employee who receives a formal warning in a year-end review without prior documented feedback has been failed by the system, not by the review form.
Performance management for a 20-person SME
A hypothetical example to illustrate the minimum viable system.
A 20-person Lebanese services company has three department managers and no dedicated HR function. The owner handles people decisions personally. Reviews have been informal for six years.
The minimum viable system for this company:
- Updated one-page job descriptions for all 20 roles, written in a week across the three managers.
- Three goals per employee, agreed in January, written in a shared folder.
- Five shared competencies applied across all roles.
- One 20-minute check-in per month between each manager and their direct reports, with a brief note recorded.
- One formal written review per year, using a simple two-page form.
- One person (the owner’s EA or one of the managers) responsible for tracking completion, reminding managers, and filing records.
This is not a model. It is the floor. The floor is achievable in one quarter with no external system and no significant investment.
A 90-day implementation plan
Days 1 to 30: Design
Review or write job descriptions for all roles. Choose three to five goals per employee for the current period. Agree on four to six shared competencies. Create a one or two page review form. Define what each rating level means in plain language. Brief all managers on the process before it begins.
Days 31 to 60: Pilot
Run the system with one department. Conduct the first formal check-ins. Collect feedback from managers and employees. Correct any goals that are vague or unmeasurable. Train managers in feedback conversations, specifically in delivering critical feedback with evidence and without apology.
Days 61 to 90: Roll out
Launch across the company. Schedule all check-ins for the rest of the year. Monitor whether check-ins are happening or being cancelled. Review rating consistency across managers before year-end reviews begin. Record the development priorities that emerge from the first cycle.
Do you need performance management software?
No, not to start.
A spreadsheet, a shared document folder, and a consistent meeting schedule are sufficient for companies up to around thirty employees. The value of software comes later: when you have multiple branches, remote or hybrid teams, complex approval lines, and a need for automated reminders and aggregate reporting.
Research involving SMEs in North Lebanon found a positive relationship between digital HR practices and organizational performance. The important word is “support.” Digital tools support a functioning process. They do not create one. A company that has not clearly defined goals, trained managers in giving feedback, or agreed on rating language will not fix any of those problems by buying software.
Start with the process. Add tools when the process outgrows what a spreadsheet handles.
A business consultancy conversation is often useful at this stage, specifically to decide what level of structure is proportionate to the company’s size and maturity.
Frequently asked questions about performance management in Lebanon
How often should performance reviews take place?
Once a year for the formal written review, with quarterly check-ins as a minimum in between. Companies with active development goals or performance issues benefit from monthly check-ins. The annual review should never be the only structured conversation a manager has with their team. If it is, it arrives with twelve months of unaddressed problems compressed into one meeting.
How many goals should each employee have?
Three to five per year. More than five and priorities become unclear. Fewer than three and the goal-setting process adds little value. Goals should be specific enough that both the manager and the employee can assess progress independently. “Improve communication” is not a goal. “Deliver the monthly client report by the 5th of each month, with no missing data fields, for six consecutive months” is a goal.
Should salary reviews happen in the same meeting?
Separate them where you can. When salary is on the table, employees focus on the outcome rather than the conversation. The performance review becomes a negotiation rather than a development discussion. Hold the performance review first. Schedule the compensation discussion within two weeks. This structure allows you to make compensation decisions that are informed by the review without collapsing both conversations into one.
What should we do when an employee disagrees with a rating?
Hear the disagreement fully before responding. Ask what evidence the employee has for a different rating. If their evidence changes your assessment, revise it. If it does not, explain your reasoning specifically. Document both the original rating and the employee’s response. An employee who disagrees with a rating has the right to be heard. They do not have the right to change a rating that is supported by evidence simply by expressing displeasure.
Can a small business manage performance without HR software?
Yes. A shared folder containing one-page job descriptions, goal documents, and simple review forms is sufficient for most Lebanese SMEs with fewer than 30 employees. The discipline of holding check-ins and documenting feedback matters far more than the tool used to store the records. Companies that invest in software before establishing a consistent check-in culture tend to use it to produce reports on a process that is not actually happening.
How do we measure employees whose work is difficult to quantify?
Combine output measures with behavioral standards. A finance manager’s output is measurable: accuracy rates, deadline compliance, report completeness. Their behavior is also assessable: communication with other departments, responsiveness to queries, adherence to process. Use both. For roles that are genuinely hard to quantify, such as a culture or learning coordinator, use project milestones and peer feedback as proxies. Avoid leaving any role outside the performance system on the grounds that it is hard to measure. The difficulty of measurement is not a reason to avoid assessment.
Build the system before the year ends
Performance management in Lebanon does not require a transformation program. It requires four decisions to be made before December: who owns each role, what good performance in that role looks like, how progress will be tracked, and who is responsible for keeping the system running.
Between now and the end of the year, the practical steps are: review job descriptions to confirm they are current, define clear measures for each role’s goals, train your managers in giving structured feedback, run a pilot check-in cycle before the formal year-end review, and enter 2027 with written goals already agreed.
A well-run year-end review, supported by twelve months of check-ins and documented evidence, takes 45 minutes and produces useful output. A review with no preparation, no documentation, and no prior feedback takes an hour and produces a form.
If you want to design a performance management system suited to your company’s structure and stage of growth, contact the TREX team.
