← All articlesPhilosophy & policy

    Writing a compensation philosophy that survives a real exception

    8 min read

    Most philosophy documents are aspirational. A useful one tells you what to do when two of your own principles disagree.

    Most compensation philosophies are written to be circulated, not consulted. They state that the company pays competitively, rewards performance, and values internal fairness — all true, all unobjectionable, and all useless at the moment a manager asks to bring someone in 12% above the band because the search has been open for five months.

    A philosophy earns its place when it can resolve that conversation. Which means it has to do something aspirational documents avoid: state priorities, name tradeoffs, and describe what happens when principles collide.

    Say where you target and mean it

    Start with the concrete commitments. Which market do you benchmark against, and why that peer set? What percentile do you target for base, and does that differ by function or level? How do base, bonus, and equity combine into your intended total position?

    Specificity here is not bureaucratic. It is what allows someone to determine whether a proposed action is consistent with the philosophy or not. "We pay competitively" cannot be violated. "We target the 50th percentile of our defined peer set for base, with equity positioned at the 65th" can be — which is precisely what makes it useful.

    Name the tradeoffs in advance

    Every compensation philosophy contains tensions. The valuable ones say which way they lean.

    • Internal equity versus external competitiveness: when a candidate demands more than incumbents earn, which gives?
    • Performance differentiation versus range discipline: how far above the band, if at all, can exceptional performance take someone?
    • Speed of hiring versus structural consistency: how much are you willing to pay, structurally, for urgency?
    • Geographic differentiation versus one-company simplicity: do you pay for location or for the role?

    You do not need to resolve these permanently. You need to state a default and the conditions under which the default gives way. "We lean toward internal equity; external premiums above the band require evidence of a sustained market shift, not a single candidate's expectation" is a sentence that will actually be used.

    A principle that has never cost you anything has not yet been tested.

    Define the exception path

    Exceptions will happen. A philosophy that pretends otherwise gets routed around. Describe the path explicitly: who can request an exception, what evidence must accompany it, who decides, and what is recorded.

    The evidence requirement is the most important lever. If an exception request must include the internal peer comparison, the effect on adjacent levels, and a specific reason the standard placement is insufficient, a meaningful share of requests resolve themselves before they are submitted. Not because the process is a deterrent, but because assembling the evidence is often enough to reveal that the standard answer was right.

    Make it consultable

    A philosophy that lives in a slide deck from two years ago is not part of the decision process. It needs to be reachable at the moment a decision is being made and specific enough that someone can point to the relevant clause.

    The strongest test of a philosophy is retrospective: take ten real decisions from the last two quarters and ask whether the document would have predicted the outcome in each case. Where it would not, either the decisions were inconsistent or the philosophy does not describe how you actually operate. Both are worth knowing, and both are fixable.

    Make the next pay decision with the context of every one before it.

    Stratum is in private design partner access.

    Request access