Skip to content

Think Through an Org or Hiring Decision

When to use this

You're sitting on an org or hiring call that won't settle. Maybe you're weighing whether to split a team in two. Maybe it's a senior hire, and two finalists pull you in different directions. The shape of the right answer is fuzzy, and you keep circling.

Used well, the AI widens the field instead of handing you one answer. You frame the question, it lays out the options, and you stress-test each one. Your leaning gets tested before you commit, so you find the trade-off you'd otherwise miss.

Work through it turn by turn, not in one prompt.

A prompt to start

Open the loop with something like this, then keep going turn by turn:

I'm working through an org/hiring decision and want you to think it through with me, not just agree.

The situation: [DESCRIBE THE DECISION IN GENERAL TERMS — NO REAL NAMES OR PERSONNEL DETAIL].
What I'm trying to achieve: [THE OUTCOME THAT MATTERS MOST].
The constraints I'm working under: [BUDGET, TIMING, WHAT I CAN'T CHANGE].

Don't jump to a recommendation. First, play back what you think the real question is — the decision under the decision. Then wait for me to confirm or correct it.

Work through it step by step

  1. Frame the real question. Let it play back the decision under the decision. Often the question you typed isn't the one that matters. Correct it until the framing feels true, then move on.
  2. Lay out the options. Ask for three or four distinct paths, not two. Push it to include the option you've been avoiding. A real choice needs more than yes-or-no.
  3. Stress each one. Take the options one at a time. For each, ask: who does this help, who does it cost, and what breaks if it goes wrong? Make it argue the case against the option it just described.
  4. Surface the second-order effects. Ask what each path does six months out. Org calls ripple — to morale, to who you can hire next, to what signal it sends. Get those on the table now.
  5. Pressure-test your leaning. Say which way you're leaning and why. Then ask it to make the strongest case that you're wrong. If your reasoning survives, act on it. If it doesn't, better to learn that now than after you commit.

What stays your call

The decision is yours, full stop. So is the read on the people involved. The AI can map options and poke holes in them. It can't feel whether someone's ready to step up, or how a team will actually take the news. It has no stake in the outcome and no relationship with anyone in the room. Use it to widen your thinking and test your logic. Then make the call the way only someone who knows these people can.

Watch out for

  • Keep real people out of a tool you don't control. Don't paste in employee names, performance details, or anything that identifies a person. Reason in general terms — "a senior IC who's ready for more" works fine, and keeps sensitive personnel detail off a system you don't own.
  • It has no context on the humans. The AI will weigh options cleanly because it doesn't know anyone. That's useful for logic and dangerous for people. The thing it can't see — how this lands for the actual person — is usually the thing that matters most.
  • A confident option list isn't a recommendation. It'll lay out paths persuasively, including ones that don't fit your reality. Treat the options as raw material for your judgment, not a verdict. Drop the ones that don't apply; add the one it missed.