Practical Wisdom

The idea in plain words

Two product managers have read the same books and know the same frameworks. Faced with a difficult decision, one sees immediately that the real issue is a key engineer’s lost confidence, or a customer’s unspoken fear, or the timing relative to a competitor’s announcement. The other runs the framework and gets an answer that misses all of these. The difference is not knowledge. It is the capacity to perceive what matters in this situation and to act well on it.

Aristotle called this capacity phronesis, usually translated as practical wisdom. Every framework on this site, and every pattern and lesson, is at best an aid to it. None can replace it.

Where it comes from

In Book VI of the Nicomachean Ethics, Aristotle distinguished several kinds of knowledge. Epistēmē is scientific knowledge of things that cannot be otherwise, such as mathematics. Technē is craft knowledge, the skill of making things. Phronesis concerns action in situations that can be otherwise, involving particulars, where there is no fixed rule. It is the virtue of deliberating well about what is good to do, for oneself and others, here and now.

Aristotle made several claims that still matter. Practical wisdom concerns particulars, not only universals, so it requires experience; that is why, he observed, young people can become good mathematicians but rarely practically wise. It cannot be reduced to rules, because situations vary endlessly; the wise person sees what the situation calls for. And it is bound up with character. In Book II Aristotle described virtue as a mean between extremes, courage between cowardice and recklessness, but insisted that the mean is relative to the situation and is found by the practically wise person’s perception, not by formula.

In the twentieth century the idea was revived in several fields. Alasdair MacIntyre’s After Virtue (1981) argued that modern moral philosophy, obsessed with rules, had lost the Aristotelian understanding of virtues as excellences cultivated within practices. Donald Schön’s The Reflective Practitioner (1983) studied how architects, therapists and managers actually work, and found that they do not apply theory to problems; they reflect in action, reframing situations as they go. The philosopher Hubert Dreyfus and his brother Stuart, an engineer, described a ladder of skill in Mind over Machine (1986), from the novice who follows rules, through competence and proficiency, to the expert who sees what to do without deliberating. Their argument was partly aimed at early artificial intelligence, which tried to capture expertise in rules.

What it does to the mind

Practical wisdom is a form of perception. The expert sees the situation differently: some features stand out, others recede. This is why experienced people often struggle to explain their judgements, as tacit knowledge is involved. It is also why frameworks can harm as well as help: a framework directs attention to what it asks about and away from everything else.

Psychology has sharpened the question of when such perception can be trusted. In 2009 Daniel Kahneman, a sceptic about intuition, and Gary Klein, a defender, wrote a joint paper concluding that intuitive expertise is reliable when two conditions hold: the environment is regular enough to be learned, and the person has had extensive practice with clear, quick feedback. Firefighters and chess players meet these conditions. Stock pickers and long-range political forecasters mostly do not. Many strategic decisions sit somewhere in between.

Where it shows up

The programming languages essay treats programming as a craft as well as a science. The word processors essay closes on the idea that we become writers by writing, which is Aristotle’s point that virtues are formed by practice. Netflix’s culture deck is in effect a bet on practical wisdom over rules: hire people with judgement and give them context. Amazon’s doors assign reversible decisions to “high judgment individuals” for the same reason.

What it asks of someone deciding

Use frameworks as checklists for attention, not as decision procedures. Ask what a framework leaves out.

Trust intuition where feedback is good and be wary where it is poor. A product manager’s sense of a design in a familiar domain may be excellent; their sense of a five-year market trend may not be.

Cultivate it deliberately. Practical wisdom grows from varied experience, reflection on that experience and honest feedback. Case studies, post-mortems, mentoring and the Decide exercises are ways of compressing experience, but only if they are reflected on, not merely read.