Career Pivot Decision — by an AI council
Decide whether to make a big career move — with clear eyes. Four rival AIs debate it and hand back: A stay / pivot recommendation with the real risks and the first step.
A stay / pivot recommendation with the real risks and the first step.
Signed off by an independent Final QA audit — with a “verify before you rely on this” list, never a black box.
Why this team
Career pivots get decided by whichever voice is loudest that week — fear or fantasy — so this council seats both, on purpose, plus the referees. The Optimist argues the honest best case and the Brutally Honest Friend says what colleagues will not; the Executive Coach digs for whether this is running toward something or away from something fixable — the diagnostic most pivots skip. The Risk Officer prices the runway and the downside scenario, and the Pragmatist designs the test that beats deciding from theory.
Each seat runs on a different frontier model — GPT, Claude, Gemini, Grok — so it’s a genuine cross-model review, not one AI in costumes. How a run works →
What the debate sounds like
An illustrative excerpt — A 38-year-old marketing director is considering leaving a secure corporate role to retrain as a UX designer, taking a large pay cut for an eighteen-month transition.
One question decides which conversation this is: what specifically would have to change in the current role for staying to feel right? If the honest answer is “a different manager and real creative scope”, this is an away-from move — and away-from moves imported into a new field tend to recreate the same dissatisfaction at a lower salary. If the answer is “nothing, I want to make things”, the pivot deserves the full hearing.
The part nobody has said out loud: at 38 you would enter UX as a junior in a field that has been shedding junior roles, competing with portfolios ten years hungrier. That is survivable — your marketing seniority is real leverage in product-adjacent design roles — but only if you aim there deliberately, not at generic junior postings. The fantasy version of this pivot dies in the applicant tracking system.
The downside is bounded, so bound it on paper: eighteen months of reduced income plus retraining costs is a knowable number against current savings. The unpriced risks are the other two — re-entry difficulty if the pivot fails at month twenty, and the compounding pension gap. None of these kill the plan; all of them belong in it. A pivot with a written floor is a decision; without one it is a leap.
Questions
Will the council just tell me to follow my passion — or the opposite?
Neither script: the format forces STAY, PIVOT or TEST-FIRST with the reasoning, and both cheerleading and reflexive caution get challenged in the debate. The Optimist and the Brutally Honest Friend argue against each other by design, so what survives is the case that holds under pressure from both directions.
What makes “toward versus away” the central question?
Because away-from pivots have a known failure mode: the dissatisfaction travels with you. If the real problem is a fixable feature of the current role — the manager, the scope, the hours — a pivot pays enormous costs to solve the wrong problem. The debate tests this early, and honestly answering it is half the decision.
How much financial detail should I include?
Enough to price the runway: savings, essential monthly costs, expected transition income and duration, and who else depends on the plan. The Risk Officer’s downside scenario is only as honest as those inputs — and a pivot decided without a written floor is the version most likely to end badly.
Your material is used only to run your review — never to train public models. Encrypted in transit and at rest. Security & privacy →
Want full control — pick your own minds, set the depth? Open the full council →

