I have watched managers spend weeks discussing an incentive scheme and minutes preparing the conversation in which an employee learns the result. The imbalance matters. The scheme may be technically coherent, approved through the proper process and affordable within the bank's financial plan. Yet the employee encounters it through one person's explanation. If that explanation changes under questioning, the employee is unlikely to distinguish a sound design from weak implementation. My interest is in what the organisation must do before that conversation so that disappointment does not automatically become distrust.
This is especially difficult when financial production and conduct point in different directions. A relationship manager may have delivered strong income while creating concerns about customer treatment or collaboration with control colleagues. Ignoring those concerns would send a poor message. Applying an unexplained adjustment after the work has been completed creates a different problem. I do not think the choice is between paying without judgement and exercising unlimited discretion. The harder task is to make the grounds for judgement understandable before the performance period begins, then apply them through a process that can hear disagreement.
The rule needs a beginning
At Neralith Commercial Bank, our fictional 2021 review led to revised terms for 320 relationship managers in the 2022 cycle. The temptation was to make the new interpretation solve concerns arising from the preceding year as well. I opposed that approach. The bank still had to address particular conduct matters through the appropriate processes, but a prospective remuneration redesign could not conveniently replace those processes. An employee should be able to identify which terms applied to the period under discussion. That sounds elementary until a senior team wants a single, immediate response to several different problems.
The effective date was therefore a substantive part of the decision. It determined which conversations managers needed to have, what employees could reasonably have understood and how the organisation would distinguish a policy improvement from a retrospective alteration. We had to tolerate an untidy interval in which past concerns and future design were being handled separately. I found that more credible than suggesting the earlier scheme had always meant something that our own manager guidance had never explained. Consistency sometimes requires accepting complexity for a period, rather than making every account fit the latest wording.
Prospective clarity does not mean that every possible event can be reduced to a formula. Banking work involves judgement and circumstances that a scheme writer cannot fully anticipate. The terms should describe the relevant considerations, the authority making the decision and how the employee can ask for review. They should also distinguish a conduct assessment from a vague impression that someone is difficult. A manager who cannot describe the concern with sufficient specificity may need to investigate or seek advice before asserting that it justifies a remuneration consequence. Discretion should have a purpose and a process, not merely a convenient label.
Judgement needs a hearing
An employee challenging an assessment is not necessarily rejecting accountability. They may be pointing to an error, an inconsistent application or information that the decision-maker did not have. I want the organisation to hear that possibility without treating the challenge itself as further evidence of poor conduct. The review route needs enough distance from the original conversation to be meaningful. It also needs limits: who can submit information, who considers it, when a response should be expected and how confidential material will be protected. An informal promise to take another look is a fragile substitute.
In our implementation work, managers rehearsed different situations rather than memorising a standard explanation. A strong financial performer with a documented conduct concern required a different discussion from an employee whose result reflected a change in business allocation. We asked managers to explain both the outcome and the reasoning, then invited another colleague to challenge the account. The exercise exposed places where the policy language was ambiguous. It was better to find those ambiguities in preparation than to let individual employees discover them through inconsistent answers across branches.
There is also a boundary between explaining a decision and disclosing information about other people. An employee may ask why a colleague received a different result. The manager needs to explain the employee's own assessment without turning the meeting into a comparison of confidential cases. Human resources can support consistency across decisions while protecting those boundaries. I would not claim that this removes every perception of unfairness. It gives the organisation a more disciplined response than either refusing all discussion or revealing details that should not have entered the conversation.
The manager cannot be a messenger only
A common failure is to tell managers that the decision has been made elsewhere and ask them simply to deliver it. That may protect the decision-making body from difficult questions, but it leaves the employee facing someone who appears responsible and powerless at the same time. Managers need to understand the grounds, recognise the limits of their authority and know when a question requires referral. They should not invent an answer to preserve confidence in the room. An honest commitment to return with a checked response is better than an explanation that later has to be withdrawn.
This preparation requires time that is often omitted from the implementation plan. Finance and human resources may allocate substantial effort to modelling the scheme while leaving line managers to fit conversations between ordinary appointments. I regard preparation, delivery and follow-up as part of the programme's cost. The executive team should also hear patterns from those conversations. If many managers struggle with the same distinction, the problem may lie in the design or guidance rather than their communication skills. A scheme should be capable of learning from its application without changing its meaning opportunistically.
Retention pressure makes this discipline uncomfortable. In the year after our revised scheme began, twelve senior employees left. Their reasons varied. I did not describe every departure as proof that the scheme had failed, and I did not dismiss the possibility that remuneration contributed. The executive team needed an account of the commercial consequences alongside the conduct rationale. Otherwise, the people function could protect its preferred design by refusing to examine a cost that other leaders were experiencing. A considered decision can remain the right one while carrying an expense that should be acknowledged.
I now ask a simple preparation question before an incentive scheme is introduced: could a manager explain a disappointing outcome without making up a rule, revealing another employee's information or promising a review they cannot deliver? If the answer is uncertain, the work is unfinished. The eventual conversation may still be difficult. The employee may still disagree or decide to leave. What the organisation can control is whether its account is coherent, whether it listens fairly and whether the stated process is the one it actually follows. That is where the credibility of remuneration becomes a management responsibility.