Skip to content after assessment

Assessment loading

If the interactive assessment does not start, you can still read the methodology and evidence below, then try again later.

Browse all assessments

Your Mental Models Quiz: Five Tools, Tested

Your Decision Thinking Audit

Your Mental Models Quiz: Five Tools, Tested

A 20-scenario self-report that groups your selected answer points across five editorial dimensions. It is not a validated measure of an underlying trait.

20 scenarios5 dimensions4 forced choicesno neutral option

Topic context from the cited source; it does not validate this questionnaire or its score thresholds.

— Rozenblit & Keil (2002)

What your answers coverFirst-principles reasoningChecking whether you truly understand something by rebuilding it from scratch.Inversion habitImagining how a plan could fail before you commit to it.Second-order thinkingTracing what happens after your decision's first, most obvious effect.Systems awarenessLooking past the obvious cause to find what's driving a problem underneath.Probabilistic framingThinking in likelihoods, and updating your beliefs when new evidence arrives.

Mental Models Assessment: Which Thinking Frameworks Are You Missing?

Twenty forced-choice scenarios are summed into editorial answer-score bands; the result does not diagnose or measure an underlying trait.

~8-10 min · Item answers and results stay on this device · Share links and invite cards carry no scores

Answer for how you actually reasoned through recent decisions — knowing a model by name isn't the same as using it.

A structured self-reflection — not a diagnostic.

This assessment is a structured self-reflection tool and educational resource — it is not a validated diagnostic and is not a substitute for clinical evaluation. Every dimension insight references peer-reviewed literature for educational context only. If a result here raises real concerns for you, take it to a qualified professional — a self-assessment is a prompt for reflection, not a verdict. Self-report instruments of this kind have no validated retest interval; the four-to-six-week Second Reading is a sensible practice, not a clinical standard.

Welcome back — you have a profile in progress.

Your profile

0 / —

Profile

Dimension profile

The Reading

Strongest dimension

Learn more →

Open the full dossier

Dimension log

This assessment is a structured self-reflection tool and educational resource — it is not a validated diagnostic and is not a substitute for clinical evaluation. Every dimension insight references peer-reviewed literature for educational context only. If a result here raises real concerns for you, take it to a qualified professional — a self-assessment is a prompt for reflection, not a verdict.

Your answers

Mental Models Assessment: Which Thinking Frameworks Are You Missing?

This literature-informed structured self-reflection adds up what you select about five thinking frameworks — first-principles reasoning, inversion, second-order thinking, systems awareness, and probabilistic framing — each grounded in peer-reviewed cognitive science. It does not measure your intelligence or predict which framework will improve a decision.

Interactive scoring requires JavaScript. You can still read every question and answer option below.

Think of something you're confident you understand well — a system, a skill, a process at work. When someone asks you to explain it in detail, what's your honest reaction?
- I just explain it — if I've got a good working grasp, second-guessing myself by re-deriving everything from scratch feels like overkill
- I explain it and it mostly holds together, though I don't usually stress-test it beforehand
- I've caught myself hitting a gap mid-explanation before, so I try to think it through in advance for anything important
- I actually try to reconstruct it unaided before I trust that I understand it — that's the only test I trust
When a problem is framed for you — by a briefing, a colleague, or a standard approach — how often do you pause to question whether the framing's core assumptions are correct before working within it?
- Almost always — I surface the assumptions before working within the frame
- Often — I question the key assumptions, though I sometimes accept smaller premises without checking
- Occasionally — I question the framing when something seems obviously wrong
- Rarely — I accept the framing as given and work within it
When you encounter a problem in an area where you are not an expert, how do you typically approach it?
- I identify what is fundamentally true about the situation before borrowing any expert framework
- I look at expert frameworks first, then test them against the fundamentals I can independently identify
- I apply the standard framework for that type of problem and adapt it if it seems off
- I apply whatever framework is most commonly recommended and trust it without independent testing
When you discover that you cannot explain something you thought you understood, what do you typically do?
- I use the gap as a starting point and rebuild my understanding from basic principles
- I re-read or revisit the explanation until my sense of understanding is restored
- I note the gap and accept it as a weak area, without a systematic attempt to rebuild
- I rarely discover this — I don't test myself, so gaps don't typically surface
When you are about to commit to an important plan or decision, how deliberately do you think through the ways it could fail before proceeding?
- I always run a deliberate failure analysis — what could go wrong and why — before committing
- I often consider failure scenarios for consequential decisions, though not always systematically
- I occasionally think about failure, mostly when something already looks risky
- Rarely — I focus on what I want to happen rather than what might go wrong
When you are confident that an approach is right, how do you usually treat that confidence as you move toward committing?
- I trust the conviction — deliberately arguing against a call I already believe in feels like undermining my own judgement
- I'll play devil's advocate if someone else pushes back, but I don't generate the case myself
- For decisions that really matter I'll try to build the counter-case myself, though I skip it on familiar calls
- I always build the strongest case against my own position before I let myself commit to it
Before launching a project or committing major resources, how often do you imagine that the project has already failed and work backward to identify why?
- I use this method regularly — imagining failure first is part of how I plan
- I do this for major commitments, though not consistently for every decision
- I have encountered this approach but rarely use it in a systematic way
- I don't use this — I prefer to focus on what will make the project succeed
When a plan or decision leads to a worse outcome than expected, how systematically do you analyse what went wrong in a way that changes your future approach?
- I always conduct a structured analysis of what specifically went wrong and update my approach accordingly
- I usually reflect on what went wrong, though my updates are not always systematic
- I note that something went wrong but rarely draw specific lessons that change how I act next time
- I move on fairly quickly — dwelling on failures feels unproductive
When making an important decision, how many steps ahead do you typically trace its consequences before committing?
- I routinely trace multiple rounds of consequences — what happens after the first effect, and what follows from that
- I usually go one or two steps beyond the immediate effect for significant decisions
- I primarily consider the direct intended effect and occasionally think one step further
- I focus on whether the primary outcome I want seems achievable — I don't routinely trace further
When you make a decision that affects others — competitors, teammates, markets, stakeholders — how much do you consider how they will adapt to your action, and how their response will then affect you?
- I always model likely responses and factor in how those responses feed back to my own situation
- I usually consider how others will respond for decisions with clear interaction effects
- I occasionally think about responses, mainly from the most obviously affected parties
- I focus on making my own action as strong as possible without routinely modelling others' responses
When an opportunity looks clearly attractive, what's your honest instinct about timing?
- Seize it — when something is clearly good, the real risk is hesitating and watching it pass to someone else
- I'll pause if something suddenly feels too good to be true, but a clean, straightforward opportunity doesn't usually trigger a second look
- For anything major I pause and dig for the downside, though smaller attractive-looking opportunities get less scrutiny
- The more obviously good it looks, the more carefully I examine it before committing
How regularly do you explicitly ask 'what am I not seeing?' or 'what would have to be true for this to go badly?' as part of your decision process?
- It is a regular, explicit step in my process for any important decision
- I do it often for significant decisions, though it is not always a formalised step
- Occasionally, when I am particularly uncertain or something external prompts it
- Rarely — I focus on what I do know and act on that rather than searching for what I might be missing
When something in your work breaks down or performs poorly, how do you typically look for the cause?
- I trace back through the system structure — feedback loops, upstream inputs, underlying conditions — to find the structural driver
- I look beyond the most obvious cause, usually going two or three levels deeper
- I identify the most proximate trigger and address it, occasionally asking what caused that
- I address the most visible symptom directly — I focus on fixing what I can see
In the domains you work in most, how aware are you of the time delays between actions and their effects — and how much do you factor those delays into your plans?
- I actively identify key delays and explicitly factor them into timelines and intervention plans
- I am usually aware of significant delays and account for them in major decisions
- I am vaguely aware that delays exist but rarely model them explicitly
- I mostly assume that effects follow actions fairly quickly and plan on that basis
When your actions produce results, how carefully do you track whether those results feed back to change the conditions you will face in the future?
- I deliberately model the feedback — I track how my outputs become inputs to my next situation
- I usually notice significant feedback loops, particularly in domains I know well
- I am sometimes aware of feedback when it is obvious, but I rarely model it deliberately
- I treat my actions and their effects as largely one-directional — I don't routinely think in terms of feedback
When you set out to change or improve a system — a team, a process, an organisation — what's your honest starting move?
- I fix what's visibly broken — getting the obvious problem sorted beats spending time mapping the whole system before acting
- I find the single strongest lever I can identify and push on it directly
- I identify the main factors in play before acting, even if I don't map everything systematically
- I map the system's key variables, relationships and feedback loops before I design any intervention
When you predict or expect something to happen, how do you typically represent that expectation in your own thinking?
- As a probability — I think about how likely something is, not just whether it will happen
- Usually as a rough probability or confidence level, at least for important predictions
- As a leaning — probably or unlikely — without attaching a specific confidence level
- As what I expect will happen — I think about outcomes, not their likelihood
When predicting or judging a specific case — a person, a project, a company — how much weight do you give to the base rate (what happens in general) versus the specifics of this instance?
- I always anchor on the base rate first and adjust from there based on what makes this case distinctively different
- I usually consider the base rate alongside the case specifics and try to balance them
- I mainly consider the specifics of this case and occasionally look up or estimate the base rate
- I focus on the specific case — if the details are compelling, I don't weight the base rate heavily
When new information contradicts what you expected or believed, what's your honest first move?
- I hold my position — changing your view every time new information shows up reads as having no real conviction in the first place
- If it's strongly contradicted I'll eventually update, but my first instinct is to look for an explanation that preserves what I already believed
- I usually update when the evidence is clearly against my view, though ambiguous evidence tends to move me less than it probably should
- I update in proportion to how unexpected the new information is, whether it confirms or contradicts what I believed
How regularly do you check whether the confidence you expressed in past predictions matched how often those predictions actually came true?
- I regularly track whether my stated confidence was accurate — I know whether I am over- or under-confident in different domains
- I occasionally review how my predictions held up, though not systematically across domains
- I sometimes notice in hindsight that I was more or less confident than I should have been, without formal tracking
- I rarely check — I focus on my reasoning process rather than tracking calibration outcomes

Appendix · Method & evidence Decisions · Case file

How this instrument works

This is a 20-item structured self-assessment of your mental models quiz, read across 5 dimensions: First-principles reasoning; Inversion habit; Second-order thinking; Systems awareness; and Probabilistic framing. Each item is a concrete scenario with four forced-choice responses — no neutral midpoint, so every answer commits to a direction — and response order is shuffled on every run to vary position; this implementation has not been tested for bias reduction. 5 of the 20 items are reverse-keyed — the attractive-sounding response is the structurally weak one — with wording intended to challenge socially desirable framing; this design has not been tested for bias reduction.

Scoring combines an overall reading with a per-dimension profile. Cascade flags compare configured dimension totals with editorial thresholds. They do not establish a compound risk and may not reflect the item-level pattern. The result bands are editorial guidance, not clinical thresholds: they organise the reading, they do not describe.

Every dimension insight cites peer-reviewed literature, and most answer reveals do — 7 sources back this instrument, each with DOI metadata supplied at build time; source relevance and claim interpretation remain editorial judgments. Compiled by the High Performance Culture editorial team. Instrument v1.1 · August 2026.

Read the full assessment methodology →

Items: 20
Dimensions: 5
Format: Forced choice, 4 options
Sources: 7
Instrument: v1.1 · August 2026

The 5 editorial answer groups

First-principles reasoning

Strength here looks like consistently testing understanding by reconstructing explanations from scratch, questioning the assumptions in inherited problem framings, and rebuilding knowledge whenever a gap surfaces — so felt familiarity and genuine mechanistic understanding stay close together.

The vulnerable pattern: trusting the sense of having understood something without testing it by reconstruction, accepting problem framings without interrogating their core assumptions, and re-reading to restore felt confidence rather than rebuilding from fundamentals when a gap surfaces.

Sample itemThink of something you're confident you understand well — a system, a skill, a process at work. When someone asks you to explain it in detail, what's your honest reaction?

First structural move: Choose one thing you feel confident you understand well and try to explain it from scratch, in plain language, without looking anything up. Note exactly where the explanation fails — that is the boundary of genuine knowledge versus felt familiarity, and it is where the work begins.

Go deeperProtocol: The Mental Models Protocol →Deep dive: Reasoning from ground truth →Glossary: First principles thinking →Glossary: Feynman technique →

Inversion habit

Strength here looks like generating failure scenarios before committing, steelmanning opposing cases before finalising a position, running pre-mortems on major projects, and extracting specific behaviour-changing lessons from negative outcomes — so counterfactual thinking is a default planning tool rather than a crisis response.

The vulnerable pattern: building plans forward from goals without generating failure scenarios, focusing on what will go right rather than what might go wrong, and moving on from negative outcomes without the structured analysis that would convert them into improved future decisions.

Sample itemWhen you are about to commit to an important plan or decision, how deliberately do you think through the ways it could fail before proceeding?

First structural move: Before your next significant commitment, spend ten minutes writing down the three most credible ways it could fail. For each failure mode, note one specific change to the plan that would reduce that risk — even if you don't make the change, the exercise reveals whether the plan has been stress-tested.

Go deeperGlossary: Inversion →Glossary: Antifragility →

Second-order thinking

Strength here looks like tracing consequences through multiple steps before committing, modelling how affected parties will adapt and how their responses feed back, treating obvious opportunities as the ones most in need of scrutiny, and explicitly searching for what might be missing before finalising a decision.

The vulnerable pattern: committing based on the primary intended outcome without tracing further consequences, optimising your own action without modelling how others will respond to it, acting quickly on attractive opportunities without examining their hidden costs, and relying on what is already visible rather than searching for what is not.

Sample itemWhen making an important decision, how many steps ahead do you typically trace its consequences before committing?

First structural move: For your next important decision, write down the direct intended effect — then ask what that effect will cause, and what that second effect will cause in turn. Write the chain at least two steps forward. The point is not prediction accuracy but the habit of looking past the first answer.

Go deeperProtocol: The Strategic Thinking Protocol →Glossary: Second-order thinking →Glossary: Nash equilibrium →

Systems awareness

Strength here looks like tracing root causes through system structure rather than stopping at proximate triggers, explicitly identifying and accounting for delays between action and effect, modelling feedback loops before designing interventions, and tracking how outputs become inputs to the next situation.

The vulnerable pattern: addressing visible symptoms without tracing their structural causes, assuming effects follow actions quickly without accounting for delays, applying interventions to the most visible lever without mapping the feedback dynamics that will shape how the system responds, and treating actions and their effects as one-directional.

Sample itemWhen something in your work breaks down or performs poorly, how do you typically look for the cause?

First structural move: The next time something breaks down, ask what caused it — then ask what caused that — and repeat the chain at least five times before deciding how to respond. Note where the chain leads; the structural cause several steps back is typically more actionable than the proximate trigger.

Probabilistic framing

Strength here looks like expressing predictions as explicit probabilities or confidence levels, anchoring on base rates before adjusting for case-specific features, updating beliefs symmetrically when new evidence arrives whether confirming or disconfirming, and tracking calibration by comparing stated confidence to outcomes.

The vulnerable pattern: thinking about what will happen rather than how likely it is, judging specific cases primarily by their similarity to familiar prototypes rather than by statistical base rates, explaining away disconfirming evidence rather than revising the underlying belief, and focusing on reasoning quality without tracking whether stated confidence matches accuracy.

Sample itemWhen you predict or expect something to happen, how do you typically represent that expectation in your own thinking?

First structural move: For the next five predictions you make — large or small — write down an explicit probability alongside each one. At a set date in the future, check the outcomes. The goal is not accuracy on any single prediction but building awareness of whether your confidence level is a reliable signal.

Go deeperProtocol: The Probabilistic Thinking Protocol →Deep dive: Why experts overstate their certainty →Glossary: Bayes' theorem →

Questions, answered

Is this a diagnosis?

No. This assessment is a structured self-reflection tool, not a validated clinical instrument. Its result bands are editorial guidance, not clinical thresholds — they organise your answers into a readable profile; they do not describe a condition. If you have concerns about your health or wellbeing, speak to a qualified professional.

How were the questions designed?

Each of the 20 items presents a concrete scenario with four graded responses and no neutral midpoint, so every answer commits to a lean. Items were authored against the peer-reviewed literature listed in the evidence file on this page, and citation metadata is supplied at build time; source relevance and claim interpretation remain editorial judgments. Response order is shuffled on every run to vary position; this implementation has not been tested for bias reduction.

What happens to my answers?

Assessment answers stay on this device. Unfinished progress expires after 30 days. A completed profile and optional comparison history remain until you delete local assessment data or clear browser data. If you opt into email, your email address is sent; item answers are not. If you share a result link, total and dimension scores are included in the URL and may appear in browser, server, CDN, or analytics logs.

How often should I retake it?

The instrument keeps your previous reading and sets the two side by side when you retake — the Second Reading. There is no validated retest interval; repeat only if a raw answer-point comparison would be useful, and do not treat it as confirmed underlying change.

Why bands instead of percentiles?

Because this assessment does not collect a population score set, there is no reader population to rank you against — and we will not invent one. The 5-dimension profile groups selected answer points for editorial display; it is not a validated structural or decision-utility model.

Where does the evidence come from?

Every dimension insight cites peer-reviewed research, and most answer reveals do — 7 sources stand behind this instrument, each with DOI metadata supplied at build time; source relevance and claim interpretation remain editorial judgments. A few reveals are straightforward editorial reasoning from the same evidence base and carry no citation by design. The full list, with DOIs, is in the evidence file below.

The evidence file

7 peer-reviewed sources stand behind this instrument's items and insights.

Rozenblit & Keil (2002) — The misunderstood limits of folk science: an illusion of explanatory depth. Cognitive Science. DOI: 10.1207/s15516709cog2605_1 ✓ Crossref‑verified
Roese (1997) — Counterfactual thinking. Psychological Bulletin. DOI: 10.1037/0033-2909.121.1.133 ✓ Crossref‑verified
Frederick (2005) — Cognitive Reflection and Decision Making. Journal of Economic Perspectives. DOI: 10.1257/089533005775196732 ✓ Crossref‑verified
Sterman (2002) — All models are wrong: reflections on becoming a systems scientist. System Dynamics Review. DOI: 10.1002/sdr.261 ✓ Crossref‑verified
Sterman (2018) — System dynamics at sixty: the path forward. System Dynamics Review. DOI: 10.1002/sdr.1601 ✓ Crossref‑verified
Tversky & Kahneman (1974) — Judgment under Uncertainty: Heuristics and Biases. Science. DOI: 10.1126/science.185.4157.1124 ✓ Crossref‑verified
Moore & Healy (2008) — The trouble with overconfidence. Psychological Review. DOI: 10.1037/0033-295x.115.2.502 ✓ Crossref‑verified

Neuroscience of Discipline Habits & Behavioral Design

Willpower Test: How Strong Is Your Self-Control Architecture?
July 17, 2026August 24, 2026 Neuroscience of Discipline, Habits & Behavioral Design

A 20-scenario, evidence-based profile that maps five structural dimensions of your self-regulation – and reveals whether you are winning through habits and environment, or relying on effortful resistance, which the evidence suggests is the least durable self-control strategy.

Dive Deeper Willpower Test: How Strong Is Your Self-Control Architecture?
Mental Models & Decision Science Cognitive Biases & Heuristics

Why We Keep Throwing Good Resources After Bad: The Sunk Cost Fallacy Examined
June 18, 2026August 31, 2026 Mental Models & Decision Science, Cognitive Biases & Heuristics

The science behind sunk cost psychology: why your brain fights rational exit, what the fMRI data shows, and a 4-step protocol to override the bias.

Dive Deeper Why We Keep Throwing Good Resources After Bad: The Sunk Cost Fallacy Examined
Mental Models & Decision Science Cognitive Biases & Heuristics

Why Incompetence Feels Like Competence: The Dunning-Kruger Effect Examined
June 18, 2026August 31, 2026 Mental Models & Decision Science, Cognitive Biases & Heuristics

The Dunning-Kruger effect isn’t what you think. New evidence reveals why low performers resist feedback, and what actually fixes miscalibration.

Dive Deeper Why Incompetence Feels Like Competence: The Dunning-Kruger Effect Examined
Mental Models & Decision Science Cognitive Biases & Heuristics

What Is Choice Overload? Do Too Many Options Really Backfire? | HPC Trend Breakdown
June 18, 2026September 2, 2026 Mental Models & Decision Science, Cognitive Biases & Heuristics

Assessment loading If the interactive assessment does not start, you can still read the methodology and evidence below, then try again later. Browse all assessments This page renders as a standalone Trend Science Breakdown.

Dive Deeper What Is Choice Overload? Do Too Many Options Really Backfire? | HPC Trend Breakdown
Vagus Nerve & Nervous System Regulation Brain Health & Bio-Performance

Vagal Tone Assessment: How Resilient Is Your Nervous System?
July 17, 2026August 24, 2026 Vagus Nerve & Nervous System Regulation, Brain Health & Bio-Performance

A 20-scenario, evidence-based assessment that maps how well your autonomic nervous system recovers from stress – identifying the specific habits, practices, and patterns that shape your vagal tone across five measurable dimensions.

Dive Deeper Vagal Tone Assessment: How Resilient Is Your Nervous System?
Trust Relationship Neuroscience

Trust Architecture Quiz: How Well Do You Build and Sustain Trust?
August 18, 2026August 24, 2026 Trust, Relationship Neuroscience

This evidence-based profile evaluates how you build and maintain trust across five behavioural dimensions: how you initiate trust through vulnerability, signal competence honestly, maintain a consistent track record, repair breaches when they occur, and calibrate how far and to whom you extend trust.

Dive Deeper Trust Architecture Quiz: How Well Do You Build and Sustain Trust?