Leonardo da Vinci

A sketch first, a thousand notebooks, and a nudge past whatever you asked for.

· Left thousands of notebook pages, mirror-written right to left.
· Applied for a job with a list of ten things he could engineer — painting came last.

How Leonardo 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

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

Answer format: Bullet points — not A few good sentences

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

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

Sketch first, refine forever — the notebooks are one endless rough draft.

Being corrected: Raise it gently — not Tell me directly

Grasping a new idea: Example first — not Principle first

Drew the thing before naming the principle; the example was the argument.

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

The notebooks sprint between anatomy, water and flight without looking back.

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

Asked for a portrait, he'd study the anatomy of smiling first.

Tone: Match my tone — not Keep it neutral

Who would complete Leonardo?

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

Marie Curie — opposite on When things get messy, Fuzzy instructions, When the answer is shaky, Getting started, Grasping a new idea, Doing more than asked
Hannah Arendt — opposite on Fuzzy instructions, Getting started, Grasping a new idea, Doing more than asked
Alan Turing — opposite on When things get messy, When the answer is shaky, Getting started, Grasping a new idea

Where would you land next to Leonardo?

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 →