VFITLAB
After the Lecture — Episode 2 · Lesson 5: Introduction to Intelligence

Smarter Is Not the Same as Noticing the Right Thing

A test can measure how fast a mind works on a set problem. Everyday intelligence starts earlier — with deciding which problem, detail, and point of view deserve attention at all.

Listen to the episode Watch on YouTube

The filter before the answer

Walk into a busy kitchen or a meeting that is going sideways. Hundreds of details compete: tones of voice, half-finished tasks, risks, faces, deadlines. No one can attend to all of them. Competent people do not process everything faster. They notice the few things that matter, ignore the rest, and revise that judgment as the situation changes.

That ordering is the provocation in this episode. In Dr. John Vervaeke's framework, published with Timothy Lillicrap and Blake Richards, the central cognitive job is relevance realization: the ongoing process by which a person homes in on relevant information and lets the irrelevant recede. Relevance is not a fixed label. It shifts with goals, context, and feedback — a detail that is noise in one moment can become the signal in the next.

Framed this way, intelligence is less like a warehouse of facts and more like good editing under pressure: deciding what belongs, what can be cut, and what would change the meaning if missed. We usually praise the visible answer and ignore the invisible selection that made it possible.

Four ways of knowing, one common mistake

Vervaeke's second tool is a taxonomy, often called the 4P model, set out in his work with Christopher Mastropietro and Filip Miscevic. It distinguishes four kinds of knowing that do not substitute for one another.

Propositional knowing is knowing that something is the case: facts and explanations that can be stated and checked. Procedural knowing is knowing how: riding a bicycle, interviewing a nervous candidate, or using a tool well. Perspectival knowing is knowing what a situation is like from inside a point of view — what stands out and what feels urgent. Participatory knowing is knowing through involvement: the fit, or misfit, between a person and the world they are acting in, built up as each shapes the other.

The payoff is diagnostic. Much advice fails because it delivers one kind of knowing to a problem that lives in another. Reading will not repair a procedural gap; practice with feedback will. A checklist will not give the perspectival grasp of a tense room. A person whose difficulty is participatory — the wrong role or environment — may collect facts for months and change nothing.

Flow and insight: useful clues, not magic

Flow, in Mihaly Csikszentmihalyi's research programme as described by Jeanne Nakamura and Csikszentmihalyi, is intense involvement in an activity: concentration, a merging of action and awareness, a sense of control. It is most likely when challenge and skill are both high and matched, goals are clear, and feedback is quick. That is not a promise it can be engineered on demand. It is a design hint: adjust the challenge, clarify the goal, shorten the feedback loop. Treat flow as evidence that person, task, and moment are well coupled.

Insight has a similar lesson. In a 2009 meta-analytic review, Ut Na Sio and Thomas Ormerod found a real but uneven benefit from incubation — setting a problem aside after preparation. Divergent-thinking tasks benefited more than insight tasks, longer preparation helped, and a demanding break shrank the benefit, while a low-demand activity could help. Effort matters first; it loads the problem. Stepping away can then loosen a fixed framing. Forcing a solution at exhaustion is how a bad frame stays in charge.

Where mainstream research complicates this

A fair reading has to give mainstream research its due.

Scores on cognitive ability tests are not arbitrary. Tests of different mental skills tend to correlate — the pattern behind the idea of a general factor — and general mental ability is among the strongest single predictors found for job performance and training success, with later reanalyses debating the size of the corrected effect rather than whether it exists. Schmidt and Hunter's synthesis put it at the top of the personnel-selection league table. For a well-defined problem with a right answer, test-measured ability is real. This framework does not refute it.

What it does challenge is the inference from performs well on set problems to will judge well in open situations. Set problems arrive pre-framed. Open situations require prior framing — deciding what the problem is, which evidence counts, whose perspective is missing. Research on rationality makes a parallel point. Keith Stanovich's programme distinguishes intelligence from rational thinking: in one student study, rational thinking predicted endorsement of epistemically suspect beliefs, while intelligence did not. Capable people can reason badly when reflection does not engage.

Wisdom research points the same way. In the Berlin paradigm developed by Paul Baltes and colleagues, wisdom is expert knowledge about the fundamental pragmatics of life, judged on criteria such as rich factual and procedural knowledge, lifespan context, differing values, and management of uncertainty. Studies comparing measures have found the Berlin performance measure at times uncorrelated with intelligence, though researchers caution about reliability and competing definitions. Wisdom is not a higher IQ score with grey hair; it involves judgment tests were never designed to sample.

None of this makes the framework proven. Relevance realization is a theory, not a settled measurement — a fruitful lens is not an established test. Its strength is naming work scores leave undescribed. Its risk is breadth: a concept covering framing, attention, flow, and wisdom can explain everything and predict too little. Hold it to a practical standard: does it diagnose a failure better than the language you had before?

How listeners can apply this

  1. Name the missing kind of knowing. Sort the problem before studying harder. Propositional: look it up. Procedural: practise with feedback. Perspectival: change the vantage point. Participatory: change the role, routine, or environment.
  2. Do a relevance pass. Before a work session, write in one line each: the goal, the three details most likely to matter, and what will be deliberately ignored for the next hour. Revisit when new information arrives.
  3. Design for flow, do not chase it. Choose work where challenge slightly exceeds comfort, set a clear near-term goal, and arrange fast, honest feedback. Anxiety dominating means shrink the challenge or build skill; boredom means raise the difficulty.
  4. Use incubation deliberately. Work a hard problem properly first, then take a low-demand break — a walk, routine chores — and return at a set time. Test any idea that arrives sideways rather than trusting it because it felt sudden.
  5. Add a wisdom check to big decisions. Ask what context across time changes the answer, whose differing values still count, and what stays uncertain however much analysis is added. Argue the decision from a second frame before committing.

Intelligence, on this account, is not a single number. It is the continuing work of noticing well, knowing in more than one way, and revising the frame when the frame is the problem. Less tidy than a score — and more usable.

Independent companion commentary. Not affiliated with or endorsed by Peterson Academy, and not a substitute for its courses.

Citations