The promotion over the friends you complain with

The offer letter is generous. The lead role, more money, a seat where decisions actually happen. And then the second thought lands like a dropped tray: you'd be managing Priya, Dev, and Sam — the three people who've shared your lunch table and your grievances for four years.

The raise is real. The loss is also real. Notice which one the congratulations text only mentions.

The dilemma

This is a composite — stitched from the kind of case we see often in this career category, no real person.

Maya has been an engineer on the same six-person team for four years. She's good, not loudest. When the team lead left, her director offered her the role: a 22% bump, a title, and — this is the part she says quietly — authority over Priya, Dev, and Sam. The four of them have a group chat named after a bad manager they all survived. They've split late-night deploys, covered each other's sick days, and complained, at length, about exactly the decisions Maya would now be making.

She keeps rehearsing the good reasons. The team needs someone who understands the codebase. An outside hire would take six months to trust. She'd protect them better than a stranger would. All true.

Here is the detail she hasn't said out loud to anyone. Dev was also asked to interview for the role. And the sentence that actually keeps her up isn't can I lead them — it's I can't stand the thought of Dev getting it. The raise she can take or leave. The idea of Dev at the front of the standup, running her, is the thing with teeth.

Take it and something ends. Decline it and something else does. Which ending is she actually choosing?

The read

We score every dilemma on eight fixed lenses. Four of them bite here, and two of them openly disagree.

Duty — what the work itself needs done well

Duty asks a plain question: setting aside how it feels, what does the team actually require? A lead who knows the codebase, who can shield six people through a reorg, who won't spend two quarters learning names. Maya is, on the merits, the person the work needs. That's not vanity; that's fit. Score: +3. The role is genuinely hers to do, and refusing a duty that's clearly yours has its own cost — the point 3.8 keeps making, that avoidance is not neutrality.

Motive — the engine under the choice

Motive doesn't ask whether the outcome is good. It asks what's pulling. And here the pull splits clean in two. One engine: the team will be led well. The other: Dev will not get to lead it. The first is duty. The second is comparison wearing duty's lanyard. When the strongest feeling in the room is aimed at a peer rather than at the work, motive is compromised — not damning, but contaminated. Score: -1. The craving to deny Dev is doing more steering than the desire to serve the team.

Here is the tension, and it's the whole post: duty says yes and motive says not-like-this. Maya can be the right person and be taking it for the wrong reason at the same time. Wanting the title and being right for the role are two different questions that happen to have the same answer today. Most advice scores only the first and calls the matter settled.

Detachment — can she hold the role without gripping the status?

Detachment asks whether she can do the job and drop the fruit — the applause, the being-above, the win over Dev. Make it concrete: in month two she'll have to give Dev a hard code review, or hand Dev the interesting project instead of keeping it, or back Dev's design over her own in a meeting. If the title is the point, each of those calls quietly becomes about protecting the win, and she'll find reasons to keep Dev small. If the work is the point, she can hand Dev the good project without it costing her anything. Right now the grip is on the status, and that grip is exactly the thing that would rot the first three decisions she'd make as lead. Score: 0. Neutral, and neutral is a warning.

Wider welfare — the three people she'd be leading

Wider welfare looks past Maya to the room. A lead running the team out of rivalry with Dev makes worse calls for everyone — she'll manage to prove a point, not to ship. But a lead who took it cleanly, who names to Dev what happened, who leads because the team needs it — that version genuinely serves six people better than a stranger would. The welfare is high if the motive is clean, and low if it isn't. Score: +2, conditional. This lens is downstream of the motive lens; fix the engine and the number climbs.

The verdict: Take the role — but not tonight, and not until you can say the sentence about Dev out loud and watch it stop running the decision; the job is yours to do, the reason is not yet yours to trust.

A general AI chatbot would likely have handed Maya whichever verdict she leaned toward — paste in "they need me" and it composes a promotion acceptance speech; paste in "I'd lose my friends" and it drafts the graceful decline. Agreeableness is a well-observed tendency in these models; being pleasant to the person typing is close to the product. KarmaLens runs the opposite way. The eight lenses are fixed, the scores aggregate the same way every time, and the verdict doesn't renegotiate itself when you push back — motive stayed at -1 no matter how nicely Maya rephrased the duty argument. And where scripture bites, we quote it verbatim rather than softening it into agreement. You don't get the answer you leaned toward. You get the one that survives being looked at.

The takeaway you can run tonight

Call it the peer-swap test, and it costs nothing.

Take the promotion you're weighing. Now change one variable: imagine the person who'd get it if you said no is a total stranger from another team — competent, fine, no history with you.

1. Does your yes get weaker? Then part of what you're calling ambition was aversion — you didn't want the role, you didn't want that specific person to have it.
2. Does your yes stay exactly as strong? Then the pull is the work, not the rivalry, and duty is doing the driving.

Then run the second half. Write the one sentence you haven't said out loud — Maya's was "I can't stand the thought of Dev getting it." If that sentence names a peer's face instead of the team's need, your motive lens is where the honesty is hiding.

None of this tells you to decline. Plenty of right people take the job carrying a messy reason. It tells you which lens to clean before you sign, so you're leading a team instead of winning a contest. Run the full read on your own version at /decide/career/, and browse how other committed calls landed in the gallery.

So: do you want the role — or do you just not want your friend to have it?