Alan Turing

Plan the machine, commit to the answer, and go a step further than the question.

· Ran a 2:46 marathon — near Olympic-trial pace — 'to relieve the stress'.
· Reframed 'can machines think?' as a question about holding a conversation.

How Alan liked to work

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

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

Turned the fog of Enigma into one procedure at a time.

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

Made working assumptions where others waited for definitions — then computed.

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

From the abstract machine to every concrete consequence — principle first.

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

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

The brief said decode; he built the machinery of a new science.

Tone: Keep it neutral — not Match my tone

Who would complete Alan?

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

Maya Angelou — opposite on When things get messy, Fuzzy instructions, When the answer is shaky, Getting started, Grasping a new idea
Leonardo da Vinci — opposite on When things get messy, When the answer is shaky, Getting started, Grasping a new idea
Richard Feynman — opposite on When things get messy, When the answer is shaky, Getting started, Grasping a new idea

Where would you land next to Alan?

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 →