Triage originates from French military medicine, describing the process of sorting wounded soldiers into categories—those needing immediate care, those who could wait, and those beyond help. The term has since migrated across fields (emergency medicine, software development) because it solves a fundamental allocation problem: when resources are limited, you must prioritize ruthlessly.
In modern digital life, triage becomes critical precisely because you’re drowning in signal. Emails flagged for “later,” Slack messages requiring context you’ve lost, browser tabs accumulating like sediment—these create the illusion of captured work while actually fragmenting your attention. Triage breaks this cycle by forcing a decision tree: What actually requires my attention now? What can genuinely wait? What can I discard?
The practical power lies in the sorting itself. By categorizing incoming information at the point of arrival rather than letting it accumulate, you dramatically reduce cognitive load. You’re no longer carrying the weight of “maybe important”—you’ve made an explicit judgment. This is why productive people often have ruthless criteria: Does this move me toward a goal? Does someone depend on my response? Is this genuinely novel information?
For digital productivity specifically, triage transforms the inbox from a memory device (where “flagged” items are reminders of forgotten context) into what it should be: a staging area for immediate action. A message worth keeping is either actionable today or clearly belongs in a project system with proper context.
The next practical step: audit how you currently flag or save things. Are you triaging at input time (deciding immediately), or at review time (when context is lost)? The answer typically reveals where your system breaks down.
// end