Competency Frameworks in Law Firms: Development Tool or Pay Algorithm?
Law firm leaders are comfortable with frameworks and checklists. They produce them for client work, for risk management, for matter planning. But when it comes to assessing partner performance, many firms reach for a competency framework and then use it in ways that often produce the opposite of what they intended.
In my long years of practice both as a consultant (and before that as a managing partner), I have worked with firms across multiple jurisdictions on partner development and evaluation systems. The first pattern I have encountered most often is this: a firm invests considerable effort in designing a thoughtful, well-structured competency framework, and then undermines it by attaching it too directly to compensation decisions. The tool that was meant to drive honest developmental conversations becomes a scoring mechanism that drives political ones.
The tool that was meant to drive honest developmental conversations becomes a scoring mechanism that drives political ones.
The second pattern is that firms develop competency frameworks for people below partner level, but when it comes to partners, they are reluctant to impose prescriptive development planning or to codify too closely how their system of compensation actually works. A non-codified or lightly covered approach to compensation works well in the rare cases of firms where the Remuneration Committee enjoys a high level of trust or where compensation is fixed mainly by formulaic means. But in many cases, a formalised system is needed.
The argument for carefully structured competency frameworks is strong. Used well, they are among the most powerful tools available to a firm for clarifying expectations, structuring feedback, and building the kind of partner capability that sustains long-term performance. The argument is about how they are used — and about the design choices that determine whether a framework illuminates or distorts.
What Competency Frameworks Actually Do Well
In legal settings, the most effective competency frameworks are tools for reflection, CPD planning, and structured career conversations. They work because they make implicit expectations explicit. Most partners know what is expected of them in technical terms; far fewer have ever had a clear conversation about what good looks like in terms of client relationship depth, talent development, internal collaboration, or leadership under pressure.
A well-designed framework surfaces these expectations and makes them discussable. It gives a managing partner or practice group leader a shared vocabulary for development conversations that would otherwise feel uncomfortably vague. It allows a partner to understand, for the first time in some cases, that supervising associates and genuinely developing them are not the same thing — and that the firm can see the difference.
This developmental orientation is not a soft option. It is, in my view, the primary purpose for which these frameworks are suited, and the one in which they consistently deliver value.
Where They Go Wrong
The risks arise when competency frameworks are connected too directly to pay. Three failure modes appear consistently across firms of all sizes.
The first is the overweighting of inputs over outcomes. Behavioural frameworks reward visible activity — coaching conversations held, training sessions delivered, business development initiatives launched. A partner who performs well against the descriptors may score more highly than their actual contribution to client retention or profitability justifies. The framework measures effort and appearance rather than impact.
The second is perceived subjectivity. Because competencies are behaviourally described and require judgment to rate, the process is inherently vulnerable to inconsistency. When ratings carry significant financial consequences, the room for perceived unfairness — or actual bias — becomes a serious governance concern. Partners who believe the process is subjective will game it or disengage from it. Either outcome is corrosive.
The third, and potentially most damaging, is gaming. Where partners understand that competency scores translate into points or pay, the incentive to manage appearances rather than substance increases steadily. The framework stops describing real behaviour and starts describing performed behaviour. At that point it has become actively harmful: it is generating misleading information while consuming significant time and goodwill.
The Right Architecture: Framework Within a Scorecard
The solution is not to abandon competency assessment but to embed it within a broader balanced scorecard — and to be precise about what each element of the scorecard is doing.
A balanced scorecard for partner evaluation typically covers financial performance, client development, people and leadership, and (in some firms) innovation or risk management. The competency framework should serve as the behavioural backbone within that structure: it defines what good looks like across those dimensions, while the scorecard balances those standards against measurable outcomes and firm-level KPIs.
Under this model, the framework does not generate scores. It provides structured evidence that informs the judgment of a credible remuneration committee — one with clear terms of reference, good information, and the authority to exercise discretion, explain decisions, and correct anomalies. The committee’s judgment drives the outcome. The framework shapes the conversation that precedes it.
Design Principles That Make the Difference
Firms that use competency frameworks successfully share several design characteristics. First, they make developmental purpose primary — not as a disclaimer, but as a genuine organisational commitment. Partners need to understand from the outset that the framework is a tool for their growth, not a pay algorithm, and that understanding needs to be reinforced consistently over time.
Second, they keep the framework proportionate. Twenty competencies rated on a five-point scale produces form-filling rather than honest reflection. A small number of meaningful dimensions, assessed in broad bands rather than fine grades, is more reliable, more credible, and more likely to generate the kind of conversation that actually changes behaviour.
Third, they anchor competencies to strategy. Each dimension should be explicitly linked to the firm’s strategic objectives, making the connection between partner behaviour and economic value visible. A competency around client relationship depth means something different — and something more urgent — when it is connected to a specific strategic goal around key account growth or sector development.
Finally, they are honest about what the framework cannot do. Hard metrics — revenue, utilisation, realisation, lock-up — provide an anchor for partner evaluation that competency assessment cannot replace. The most credible systems combine both, with judgment applied to interpret each fairly in context.
The critical design question is how much of total partner remuneration should be exposed to discretionary, competency-informed assessment versus more formulaic elements. A system is safe when the framework is embedded within a broader, partly judgment-based model. It is unsafe when it operates as a standalone pay formula that translates descriptors directly into cash.
In the second article in this series, I examine what the most important and hardest-to-measure partner competencies actually are — and why the firms that take them seriously are beginning to look to evidence-based observation methods developed in very different professional settings.