RM Incentives Decide Whether Customer Centricity Sticks
This is Article 6 of 6 in the Q-Lana Customer Centricity series. RM incentives decide whether customer centricity outlasts its pilot. It covers three levels of measurement, three governance meetings, a balanced scorecard and a 60-day pilot.
RM incentives decide whether a customer-centric lending model survives its pilot. Most pilots work, helped by a small team, senior attention, a clear method and the energy of something new. Then, attention moves on. The sponsor takes on a bigger problem, and the pod absorbs two new segments. Six months later, the discovery script is optional, and the toolkits have drifted. Someone then asks in a management meeting what happened to the project. The cause is rarely a loss of belief, but a gap in measurement, governance and relationship manager (RM) pay, in that order.
Measuring the Model on Three Levels
Measurement turns a lending philosophy into evidence, and a single level of measurement is never enough.
Level one shows whether clients notice
Does the client experience change? Time from problem to solution falls from 19 days to 6. Win rate moves from 41 per cent to 63. Client effort score improves from 5.1 to 6.2 on a seven-point scale. Outcome targets achieved rise from 58 per cent to 81.
Level two shows whether the portfolio improves
Does the portfolio improve? Offers inside risk appetite rise from 72 per cent to 94. RAROC gains 180 basis points. Early-warning precision moves from 0.55 to 0.78 and recall from 0.49 to 0.71. Segment non-performing loans fall from 4.8 per cent to 3.1. Average recovery rate rises from 38 per cent to 52.
Level three shows whether the bank is learning
Is the institution learning? Proposal turnaround falls from 21 days to 7. Copilot adoption rises from 20 per cent to 85. Toolkit reuse reaches 73 per cent. Data completeness moves from 61 per cent to 92. And override patterns go from untracked to tracked and trending down.
These numbers confirm that customer centricity is not leniency. It is precision.
That sentence is the answer to the only serious objection this model faces. A credit committee hearing "customer centric" hears "softer", and the level-two numbers are what settle it. Non-performing loans down. Recovery up. Offers inside appetite up twenty-two points. Nothing in that list describes a bank that started being nicer to borrowers.
One Dashboard and Three Meetings
Three levels across five segments produces a lot of numbers, and numbers nobody looks at govern nothing.
One dashboard with five views
A single dashboard carries five views. The segment view, showing where the model is working and where it is not. The relationship manager view, for coaching rather than ranking. The portfolio risk view, holding appetite utilization against outcomes. The data quality view, because everything above degrades quietly when the inputs do. And governance alerts, which are the exceptions somebody has to act on this week.
One dashboard, five audiences, same underlying data. That is what stops the monthly pack becoming three competing versions of the truth.
Three Meetings That Actually Happen
Governance in most institutions means a committee with a charter. Governance that works means three meetings that actually happen.
The solution review
Every two weeks, thirty minutes per pod. What was proposed, what was approved, what happened, which exceptions came close to a breach, and what the client feedback taught. Short, operational, and the place where drift gets caught while it is still small.
The pricing and toolkit committee
Quarterly. This one governs the library itself: RAROC performance by toolkit, loss and default trends by segment, feedback from the pods, and any changes to appetite, pricing or sector rules. Without it, toolkits calcify and stop matching the market they were built for.
The customer outcomes forum
Quarterly, at executive level. It works from the dashboard and asks three questions. Is client resilience and satisfaction improving? Is portfolio quality and profitability holding? Is the organization learning? Each segment lead brings two or three case stories, because a forum that only reads metrics loses the texture that makes them mean anything.
Two-weekly, monthly, quarterly. Constant attention, continuous flow from the front line to the board.
Designing RM Incentives Around Outcomes
Many transformations quietly stop at this point. An institution can adopt pods, libraries, scripts and dashboards, and keep a scorecard that pays on disbursement volume. When it does, everything above becomes theatre, because people are not stupid and they can read a bonus formula.
An outcome-balanced scorecard for RM incentives
An outcome-balanced model splits roughly three ways. Around forty per cent on financial performance: RAROC uplift, net revenue, retention. Around thirty-five per cent on risk discipline: offers inside appetite, early-warning accuracy, override discipline. Around twenty-five per cent on client impact: time to solution, outcome targets achieved, client effort.
The structure matters more than the weights
The exact weights matter less than the structure. What matters is that risk discipline and client impact together outweigh the volume number, because that is the moment the incentive stops fighting the method.
Governance turns intent into habit. Incentives turn habit into culture. Skip the second and the first decays the moment nobody is watching.
Building This in Your Team
The Q-Lana Financial Skills Campus is launching Customer-Centric SME and Corporate Finance, a class for RMs and credit teams. It covers the diagnosis-first conversation and the structuring decisions that follow from it. It also shows how to keep both inside the risk appetite framework. Practitioners who carry an SME book teach it on your own files.
A 60-day Pilot With one Pod

None of this needs a programme office. It requires sixty days and a willingness to be seen doing it.
|
Days |
Phase |
Main work |
Visible proof |
|
1 to 10 |
Set up |
One pod, six RMs, three toolkits, defined metrics and a
dashboard on existing data |
Dashboard live and toolkits loaded |
|
11 to 25 |
Run |
Discovery script on live clients, briefs before meetings
and a light-touch approval gate |
First deals through the new flow |
|
26 to 45 |
Review |
Solution reviews, monitoring from the cockpit and a leader
joining one clinic |
Live numbers and peer learning |
|
46 to 60 |
Prove |
Early wins, a post-implementation review and a 90 to
180-day plan |
Evidence and a scale-up plan |
Five principles for the sixty days
Five principles hold the sixty days together. Start with focus rather than scale. Use existing systems first. Prototype visibly, so people see it rather than hear about it. Measure what matters, which is time to solution, data completeness and appetite compliance. And iterate openly, including what did not work.
What to expect from the pilot
Expect time to solution to fall by 30 to 50 per cent. More than 90 per cent of pilot offers should land inside risk appetite, and client satisfaction should rise. Prove it small, then repeat it in the next pod.
What Keeps the Model Running

Two unglamorous things keep the model alive after the pilot.
Templates
Discovery scripts, client briefs, solution design sheets, covenant builders, approval memos, gatekeeper checklists, portfolio cockpits, outcome trackers, review agendas, policy revision logs. They sound like administration and they are actually the operating memory of the method. When a new relationship manager joins, the templates are what they inherit instead of folklore.
Rhythm
The same KPI framework and the same cadence, month after month, so that measurement and governance move together rather than as separate exercises that contradict each other in December.
When governance becomes rhythm, it stops feeling like extra work and becomes how the business runs.
Where This Series Ends
Six articles make one argument. Customer centricity in lending is a risk strategy. It works through an operating model that reconnects people the bank already employs. A library turns recurring client problems into pre-cleared answers. A ten-minute conversation produces a diagnosis instead of a request. An enforcement layer frees RMs instead of policing them. The model is proven on three levels, governed by three meetings and made permanent through RM incentives.
None of it requires reorganising the bank. It does require deciding that client outcomes and portfolio quality are the same problem. The first article in this series made that case, and this one closes it.
Open the Customer Centricity Dashboard
Three levels of measurement are easier to judge on a dashboard than in prose. The dashboard carries the segment, RM, portfolio, data quality and governance views. The outcomes tracker holds the client-level evidence beneath them.
All Articles in This Series
- Customer Centricity in SME Lending Is a Risk Strategy
- SME Lending Operating Model Built on Solution Pods
- Solution Toolkits Settle the Risk Before the Client Asks
- Client Discovery in Ten Minutes Changes the Credit File
- Let AI Handle Credit Policy Enforcement and Free Your RMs
- RM Incentives Decide Whether Customer Centricity Sticks (this article)
Follow Q-Lana
One short email a week on credit risk, lending and impact finance, free. Or browse more guides in the Q-Lana Knowledge Center.
Get Q-Lana Weekly
One short email a week on credit risk, lending and impact finance, free. Or browse more guides in the Q-Lana Knowledge Center.