John von Neumann

Synthesizes at speed, plans it out, commits with few caveats, and keeps up effortlessly.

· Colleagues joked he was the only one of them who was fully awake.
· Did the party trick of out-calculating early computers — and got your joke first.

How John liked to work

A reading of the public record — hunches, not verdicts. The line under each axis is the evidence.

When things get messy: Pull it together — not One step at a time

Game theory, bombs, computers, weather — one synthesis engine, many rooms.

Fuzzy instructions: Make the call, say so — not Ask first

Named his assumptions and computed on — corrections could catch up.

Answer format: A few good sentences — not Bullet points

When the answer is shaky: Just commit — not Say so out loud

Getting started: Agree on a plan first — not React to a draft

Being corrected: Tell me directly — not Raise it gently

Grasping a new idea: Principle first — not Example first

Axioms first; the examples were merely inevitable.

Pacing a conversation: Keep up, don't recap — not Recap to stay aligned

Meetings ran at his clock; recaps were for afterwards.

Doing more than asked: Do a bit more — not Stick to what's asked

Tone: Keep it neutral — not Match my tone

Who would complete John?

Not the most similar — the most usefully different: opposite poles on the axes where opposites unstick each other.

Charles Darwin — opposite on When things get messy, Fuzzy instructions, When the answer is shaky, Grasping a new idea, Doing more than asked
Rachel Carson — opposite on When things get messy, Fuzzy instructions, When the answer is shaky, Grasping a new idea, Doing more than asked
Maya Angelou — opposite on Fuzzy instructions, When the answer is shaky, Getting started, Grasping a new idea

Where would you land next to John?

Same axes, your answers — about two minutes, no login. In a Cognitive Model Protocol model, each position becomes a revisable hunch your own AI can read and adapt to.

Take the quiz →