Title mapping rules for Justin org - no senior or junior variants, map to the lower bound and promote later, no comp or promotions in the exercise, no zealotry where someone gets hurt

October 30, 2026 at 7:45 PMoperationallow

Situation

In the 10/23 Justin 1:1 Peter gave the mapping rules for collapsing titles: no senior or junior variants of any title; when torn, translate someone to the lower bound and keep the ability to promote them; do not bring promotions into the exercise; no salary changes, names only; have an honest conversation about who would be hurt and keep a wart (a senior prefix) rather than generate pain for a simpler map.

Reasoning

Simpler title bands make offers and pay ranges easy for HR. Mapping down then promoting keeps the scheme clean without inflating it. The aim is directional, not ideological, so morale exceptions are allowed.

Additional Context

Confirmed by Peter. Execution of the 9/7 title-collapse decision.

Observed Evidence

I am not going to be a zealot about this at all. / There is no salary changes attached to this. This is just names.

Confidence Breakdown

30/35
Evidence
18/30
Pattern
14/20
Source
6/15
Corroboration

Reasoning Depth Analysis

Org Signal:Title simplicity over title prestige.
Who Affected:Engineers in Justin org, HR.
Precedent:Map down, promote deliberately.
Consequences:Names change only.
Timing:Rollout of the 9/7 scheme.

People Involved

Source

reflection

AI Confidence

68%

Related Context

🎥
Justin and Peter weekly 1:1 10/23

fathom

if you have got a choice between putting somebody at a lower bound versus a higher, I would rather you translate them into the lower and then have the ability to give them a promotion.

Outcome

No outcome recorded yet.

Decision ID: 1e3ee47a-405e-48cf-af20-2f1e6981a610