Knowledge
A useful next step starts here.
Search by what you want to understand or do.
930 elements
Confirmation bias
Your favourite explanation should not get an easier exam.
Read the idea ConceptAnchoring effect
The first number has an unfair talent for becoming the centre of the conversation.
Read the idea ConceptFraming effect
Ninety per cent success and ten per cent failure can describe the same result. Your choice may not treat them that way.
Read the idea HeuristicRun a test that could prove you wrong
A test that only your favourite explanation can celebrate is usually not much of a test.
Read the idea HeuristicEstimate before the number arrives
Give yourself a reference point before someone else — or an AI — gives you one.
Read the idea HeuristicFlip the frame, keep the facts
Change the wording without changing the decision. If your preference moves, inspect why.
Read the idea ChecklistComplete the journey with the keyboard alone
Being able to reach a button is not the same as finishing the task.
Read the idea ProtocolMake enlarged text fit the task, not just the screen
A larger sentence is not helpful when its ending disappears.
Read the idea ChecklistGive the colour a second way to speak
The meaning should survive when the colour does not.
Read the idea ProtocolKeep the field’s identity after the user starts typing
A field should not lose its name when it receives an answer.
Read the idea ProtocolMake the error show the next repair
Invalid is a verdict, not an instruction.
Read the idea ProtocolAnnounce the result without stealing the user’s place
Finished should not be a message only sight can hear.
Read the idea ChecklistLet voice commands use the label people can see
The screen says Save. The hidden name should not insist on Commit artifact.
Read the idea ProtocolMake non-essential interaction motion optional
A transition should not make someone pay a physical price for pressing a button.
Read the idea ProtocolTest the target and its neighbours, not just the icon
The finger meets the clickable area, not the design file.
Read the idea ProtocolKeep the headers attached when the table leaves your screen
Bold text is not a relationship.
Read the idea ProtocolMove from the concrete case to the rule
An example should lead somewhere, not become the whole lesson.
Read the idea HeuristicStudy for an explanation you will owe
Give the next reading session an audience.
Read the idea ProtocolDraw the process while you explain it
A sketch makes missing connections harder to hide.
Read the idea PrinciplePut the explanation beside the thing it explains
Do not make the reader carry a label across the page in memory.
Read the idea HeuristicCue the part that matters right now
An arrow can be more useful than another paragraph.
Read the idea QuestionRemove the interesting detail that teaches nothing
Would this detail earn its place if nobody found it clever?
Read the idea ProtocolOffer support according to the task, not the job title
An expert in one system can still be a beginner in this screen.
Read the idea ProtocolExplain why the wrong worked example fails
A wrong answer is useful only when the wrong turn becomes visible.
Read the idea