The Analyst

You go deep, not wide. Where others skim five topics, you spend a year on one and come out understanding it from the inside. You don't trust intuition until it's been audited, and you can hold an argument with yourself for an hour to make sure you haven't missed an objection. Systems-builder by default — you'd rather design the framework once than answer the same question fifteen times. The questions that fascinate you are the ones with multiple plausible answers, where the fun is in the disambiguation, not the conclusion. You're the person colleagues come to when the easy explanations have failed and the real complexity needs naming. Where this archetype shines: deep technical specialisation, research roles, the work of figuring out *why* a system actually behaves the way it does — not what it does, but the underlying mechanics that produce that behaviour. Your blind spot: you can over-engineer for problems that wanted a one-page memo, not a 40-page architecture document. Other people don't always need the full system to act — sometimes the rough heuristic is enough, and waiting for the complete model means missing the window. You can also lose the room when you keep adding caveats to an answer that needed to be "yes" or "no". To grow: practice giving the 80% answer fast and the 100% answer only when asked. Decisiveness is not a betrayal of rigour.