What is information literacy skills?

Example: A senior engineer receives a Slack notification about a production anomaly while reading a news alert about an industry layoff, skimming a LinkedIn thread about AI replacing developers, and processing a calendar reminder for a meeting she does not need to attend. Her amygdala fires on all four inputs simultaneously. But she has spent twenty days building a signal detection stack. She applies her defined goal filter (Signal requires a defined goal): only the production anomaly relates to her current objective. She checks for manufactured urgency (Urgency is usually noise): the news and LinkedIn threads are emotionally charged but decision-irrelevant. She evaluates source quality (High-quality sources reduce noise filtering): the anomaly report comes from a monitoring system she trusts, with first-party data (First-party data beats second-hand reports). She waits forty-five seconds before responding (When in doubt, wait), letting her emotional reaction settle (Your emotional reaction is often noise). Then she acts — precisely, on the one thing that matters. Her four colleagues without this stack spent the next ninety minutes context-switching between all four inputs, resolved none of them, and missed the anomaly escalating into a customer-facing outage. Signal detection was not a productivity hack. It was the difference between a controlled response and a cascading failure.

This concept is part of Signal vs Noise in the How to Think curriculum.