A guiding principle must be specific enough to divide the world into right and wrong actions, not merely directional

Victor distinguishes between vague aspirations (‘make software easier to use’) and genuine guiding principles (‘no person should be trapped in a mode’). A true principle must be specific enough to evaluate any given situation as right or wrong, yes or no. Tesler could look at any text editor interaction and ask: ‘Is this person in a mode?’ If yes, it needed fixing. Victor’s own principle — ‘creators need an immediate connection’ — allows him to evaluate any creative tool by asking: ‘Did the creator immediately see the effect of that change?’ Vague aspirations provide direction but not discrimination; they can’t guide action in the face of tradeoffs. The specificity requirement means finding a principle is an act of self-discovery, not just goal-setting.

Examples

‘I want to delight users’ is a direction. ‘No latency between a creator’s action and visible result’ is a principle: it evaluates every design decision as compliant or not.

Assessment

Take a vague creative or professional aspiration you hold (e.g., ‘make good music’) and reformulate it as a specific, evaluable principle that would let you judge any concrete decision as right or wrong.