What Leaders/Managers Can Learn from The Signal and the Noise
Desmond Okafor ran the quarterly forecast meeting the same way every time: each team lead stood up, named a number, and defended it with as much certainty as they could project, because the loudest, most confident forecast usually won the room. Desmond noticed that the manager who hedged and gave ranges was quietly right more often than the one who declared a number and never revisited it, yet the confident one kept getting praised in reviews. Watching his own team's engagement scores bounce around each month, Desmond realized he had been treating every wiggle in morale surveys as a real trend worth an all-hands response, when most of it was probably just noise. He started asking a different question in meetings: not who sounds surest, but who has actually been closest to right before, and why.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Separating real trends from monthly noise
Desmond's habit of reacting to every dip in a survey or dashboard trains the whole team to chase noise. A steadier practice is to identify the few indicators that have reliably predicted real problems before and let the rest of the monthly variation pass without a reaction.
An emerging crisis sometimes first shows up as a small, easy-to-dismiss blip, and treating everything as noise can mean missing it. Practice: before responding to a metric swing, check whether a similar move preceded a real outcome in the past.
Before responding to a metric swing, check whether a similar move preceded a real outcome in the past.
Forecasting as an ongoing conversation, not a verdict
Instead of announcing one quarterly number and being judged only against it later, Desmond can present forecasts as ranges that update as new information comes in from his team, discussed openly rather than defended as fixed. This keeps the team focused on the best current estimate instead of protecting a past guess.
Boards and stakeholders sometimes need a single committed number for planning, and constant revision can undermine confidence in leadership. Practice: publish a forecast range each quarter alongside what would move it up or down.
Publish a forecast range each quarter alongside what would move it up or down.
Rewarding accuracy over swagger
The team leads who speak with the most certainty are not always the ones whose numbers hold up, since confident delivery tends to be rewarded socially regardless of a track record. Desmond can build a habit of tracking whose forecasts have actually proven accurate over time and weighting their input accordingly.
Some quieter voices lack confidence not because they are less accurate but because they are less experienced presenting, so track record still needs to be checked directly. Practice: keep a simple running log of who predicted what, and revisit it before the next big decision.
Keep a simple running log of who predicted what, and revisit it before the next big decision.
Leading with honest uncertainty
The most trustworthy leaders treat forecasts as living estimates rather than declarations of authority, staying open to being wrong and treating each planning cycle as a chance to refine judgment. For Desmond, this means modeling calm revision in front of his team, so uncertainty becomes something the organization can work with instead of something everyone pretends not to feel.
Desmond's sharpest tension is between updating forecasts honestly and the organizational reward for sounding certain: a leader who visibly revises their view can look uncertain to a board that wants confident direction. The way through is to separate the tone of leadership from the content of the forecast, communicating decisions firmly while being explicit and specific about what evidence could still change the plan.
Name one thing, honestly
- Which of your team's regular metrics have you never actually checked against outcomes for whether they predict anything? - Do you reward the person who sounds most certain, or the one whose track record has actually held up? - Where in your own communication could stating a range instead of a single number make your team's planning more honest?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Keep a simple running log of who predicted what, and revisit it before the next big decision.