← Back to Patterns

Decide on the Precedent, Not the Case

strategy77% Medium

17

Occurrences

100%

Success Rate

4.0

Avg Rating

Description

When a request arrives framed as a one-off, Peter does not evaluate the one-off. He evaluates the rule that granting it would write, and answers that instead. Peter generalized this himself on 2026-08-11: it is always about understanding precedent - whether it is a comp change or anything that structurally affects the company. It is therefore NOT a compensation pattern; the domain of the presenting request is incidental. The tell that this pattern is live is that the stated reason for the answer refers to future cases rather than to the merits of the present one.

Typical Approach

Answer the rule, not the request. State the precedent risk explicitly and as the reason - I would like to be very careful setting a precident that moving within the company gets new comp. Anchor on an existing internal instance rather than on market data, fairness, or the individuals merits, because a real comparator who was treated the same way makes the answer consistent instead of stingy - we did not change his. Refuse forward-looking statements entirely where the future cannot be priced, even hedged ones, because the hedge is what gets forgotten and the promise is what gets remembered - I would not make any future looking statements, period. Where part of the request can be separated out, defer that part rather than granting or denying it, keeping a door open without conceding the rule - I would certainly leave the stock alone for now. Where a commitment IS made, make it unconditional and repeat it so the precedent is deliberate rather than accidental - it will come with headcount, period. Act before a concrete number, artifact, or customer-facing statement exists, because after that the conversation becomes a renegotiation rather than a decision. Say out loud that the present decision is the precedent, so nobody has to infer it.

Trigger Conditions

Keywords:
precedentone-offexceptioncomp changeinternal movefuture lookingpromiseguaranteestructurallysets a rulejust this oncespecial caserelocationoffer
Constraints: the request is presented as an individual case but would generalize, the future cost cannot be bounded or priced, an existing internal instance is available as a comparator, no number or artifact exists yet, so the decision is still cheap

Last applied: September 7, 2026

Created: August 11, 2026

Example Decisions (17)

Defend the net-new engineering reqs to Greg by naming them - and pay for them with an explicit churn commitment

Sep 7, 2026 · strategy

Pending

Take the KT 9.8 one-year bridge - engineering will figure it out as long as the million dollars comes with headcount

Sep 7, 2026 · strategy

Pending

Refuse an SDLC release-cadence contract that would bind engineering - prioritization authority stays with Product

Sep 7, 2026 · strategy

Pending

Refuse to green-light the HPE indemnity escalation - this is a Bjorn call, not an Engineering call

Sep 3, 2026 · strategy

Pending

Refuse the 9.10-as-of-today letter for KT - give them 9.6 LTS now with its real support window and a required migration, and correct the numbers publicly when they turn out to be wrong

Sep 2, 2026 · strategy

Pending

Put the Core42 deployment on Ryan org to resource - Nathan stays advisor and the unfilled Forward Deployed Engineer goes on the contract list

Aug 31, 2026 · strategy

Pending

Hold the Core42 commitment at five weeks, signal two-to-three as likely, and trade the compression for topology data

Aug 31, 2026 · strategy

Pending

Do not bump the offer to save Nikola Kolev - spend the loss on learning what the real range is

Aug 31, 2026 · people

Pending

Attack the live-patching gap through Google co-development as a paid deliverable while keeping the req open - buy the timeline, do not just wait for the hire

Aug 28, 2026 · strategy

Pending

Hold the CISO requisition and the September security hire pending the Atomicorp acquisition

Aug 28, 2026 · strategy

Pending

Broken-in-production is an automatic fast path - small thing with embarrassing impact jumps the queue regardless of the size of the epic around it

Aug 28, 2026 · strategy

Pending

Trade a company-wide VP definition to get Greg to ratify the engineering ladder - structure first, names later

Aug 24, 2026 · people

Pending

Back the President on the workplace-language complaint and answer it on who is setting the culture rather than on who is right - the culture gets built intentionally, but not to the lowest common denominator

Aug 21, 2026 · people

Pending

Refuse a comp change on an internal move on precedent grounds, anchored to an existing CIQ instance - and defer the equity rather than grant it

Aug 11, 2026 · people

Pending

Treat prototypes crossing from Product into Engineering as a feature rather than a burden - the code is worth two days, the market learning is the payload, and every one arrives with headcount

Aug 11, 2026 · strategy

★★★★

Proceed with the Patrick Culp offer as US-only and say absolutely nothing about the future - if we lose him, we lose him

Aug 11, 2026 · people

★★★★

Override your own teams stated intent to delete the RL 8.6 source tree, and apologize to Google directly rather than defend the position

Aug 11, 2026 · operational

Pending

Pattern ID: d5c6731a-8916-4039-aa51-32cb96d1c5ef