Every performance review promise has a capacity bill

A performance review ends with a sensible development action: lead a client discussion, coach a colleague, take responsibility for a wider portfolio, or improve commercial judgment. The employee accepts it. The manager records it. The review is marked complete.

The work has just begun. Someone must make room for the assignment, provide the authority to do it, and review what happens. A development promise commits organizational capacity even when no training invoice follows.

For founders, CEOs, and HR leaders in Dubai and Abu Dhabi, this is a practical test of the review system. Can the business show how the commitment will happen alongside the work it has already sold, scheduled, or promised?

The commitment spends more than the employee’s time

A stretch assignment can require a manager’s preparation, a colleague’s handover, access to a customer, a decision that sits outside the employee’s authority, and time to correct an early mistake. Recording only the employee’s action leaves those dependencies unowned.

I would treat a development commitment as a small operating decision. The question is what the business is prepared to authorize so that someone can practice a new responsibility under useful conditions.

That is an important part of performance management and review design: making the action after the conversation credible.

Keep three records connected

The performance record explains the assessment of work already done: expectations, relevant evidence, context, and the judgment reached.

The development commitment defines the work through which a capability will be practiced and reviewed.

The authorization record identifies who approved the time, spending, access, or responsibility needed to carry it out.

These records can sit in the same system. They serve different decisions. A strong rating does not by itself approve a budget. A place on a course does not by itself establish readiness for a larger role. A development action becomes usable when its dependencies are explicit.

A six-field development commitment record

The following record is an Element MEA operating framework that a leadership team can adapt to its context. It is deliberately small enough to use during a real management conversation.

1. Observable work

Name the responsibility the person will practice and the evidence that could demonstrate progress. “Improve stakeholder management” is too broad to schedule or review. “Prepare and lead the next cross-functional delivery review, with the manager observing the decision process” gives both people something concrete to work with.

2. Assignment and boundaries

Identify the project, customer, operating cycle, or team in which the work will happen. State the start and end points. An assignment needs a defined place in the business rather than a standing expectation to find extra work.

3. Capacity decision

Record what will stop, move, be covered, or receive additional resources. Name the person authorized to make that trade-off. If capacity has not been agreed, mark it unresolved rather than reporting the development action as active.

4. Decision authority

Write down what the employee can decide, what requires approval, and when an escalation is needed. Giving someone accountability without corresponding access or authority creates avoidable dependence on the manager.

5. Support owner

Identify the person who will provide access, observe the work, and give feedback. Put the first support conversation in the calendar. “The manager will support” leaves too much room for competing priorities to take over.

6. Review date and next decision

Choose when the work will be reviewed and what decision that review will support: continue, adjust the assignment, provide further practice, or consider a different responsibility. Completion should be based on relevant work evidence. Attendance alone answers a narrower question.

An illustrative example: the account manager and the planning cycle

This example is fictional and illustrates the record; it is not a client case or a claim of results.

An account manager is expected to become more confident leading client planning. The manager agrees an eight-week assignment covering one planning cycle for an existing account.

The employee will prepare the agenda, coordinate input from delivery colleagues, lead the discussion, and document the decisions and follow-up owners. The manager will observe the first meeting and review the preparation beforehand.

The capacity decision is explicit: one internal status report is retired for the assignment period, and the manager protects time for preparation. The account manager can coordinate internal input and propose actions; commercial commitments outside existing authority still require the usual approval.

At the agreed review, the manager examines the preparation, handling of competing inputs, clarity of decisions, and quality of follow-through. The next decision concerns the employee’s scope of responsibility and any further practice needed.

The development commitment is now connected to real work, an authorized trade-off, and observable evidence.

Give each party an accountability it can actually hold

The line leader owns the business assignment and capacity decision within their authority. Where another leader owns the customer, resource, or budget, that approval must be visible.

The employee owns the agreed preparation, practice, and evidence of learning, and raises a dependency when it prevents the work from proceeding.

HR owns the quality and consistency of the review process, equips managers to use it, and brings unresolved dependencies to the right forum. An HR reminder cannot substitute for an operating leader’s resource decision.

The sponsor or reviewer owns the agreed observation and feedback. That contribution is work too, and needs room in the calendar.

A useful leadership check after the review cycle

Take a small operational sample of development commitments. This is a management check, not a statistical audit or a maturity score. Ask whether each record has an assignment, an approved capacity decision, usable authority, a support owner, and a review date.

Then check the first scheduled conversation. A calendar entry and a named piece of work provide a stronger starting point than another reminder to update the form.

If the same dependency recurs across teams, bring it into the operating model. Repeated requests for a manager’s approval may point to unclear decision rights. Repeated cancellations may point to an unrealistic span of responsibility or an unresolved capacity constraint.

Where the project should leave the business

A performance review project can leave behind more than a revised template: role-relevant expectations, evidence standards, manager guidance, calibration decisions, and a practical route from development commitments to authorized work.

Where the difficulty extends across functions, an HR consulting engagement can clarify the roles, interfaces, and management responsibilities around that cycle.

My test is whether the business can run the process when the adviser steps out. The record should be understandable, the owners should be named, and the next conversation should be capable of happening.

Discuss a performance review project with Element MEA. Start with the management decision your current cycle is struggling to support.

Source and authorship

CIPD’s performance management factsheet describes performance management as an ongoing cycle and emphasizes managers’ role, appropriate resources, and organizational support. The six-field record, fictional example, and operating recommendations above are Element MEA’s practical interpretation, rather than a CIPD-endorsed model.

By Mayank Sharma, Managing Partner, Element MEA. Built inside, not beside.