What Leaders and Managers Can Learn from Irresistible
The one-on-one ended four minutes ago, but the manager is still at his desk, phone in hand, scrolling the team chat app to see if anyone reacted to the reorg announcement he posted an hour ago. A thumbs-up appears. Then nothing for six minutes. He refreshes anyway, waiting for the next reaction the way a gambler waits for the next card. His actual task, reviewing two candidates' final interview notes before end of day, stays untouched in another window. He tells himself he's "reading the room," but the room is one green dot at a time, and the checking has become the point. Downstairs, his own reports are doing the same thing with his messages. What looks like attentive leadership is partly a loop with no natural stopping point. Recognizing that loop for what it is changes how he leads next.
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
The chat app was not built to save you time
Every reaction, read receipt, and typing indicator in your team's messaging tool was designed to make the app worth reopening, not to make your day shorter. That design applies to a manager checking on morale exactly as it applies to anyone else.
A manager opens the team channel between meetings "just to stay in the loop," sees three new messages and one reaction, and spends the next ten minutes composing a reply, reacting back, and rereading the thread, none of which the original message actually required.
Batch channel replies into two or three set windows a day, and close the app the rest of the time instead of leaving it open in a background tab.
Three different pulls on your attention
An unpredictable reply, a visible reaction count, and a channel that never runs out of new messages each hook you differently, so treating all messaging fatigue as one problem misses the fix.
A manager decides the fix is muting all notifications, but the real driver is checking for reactions to their own posts, an urge notifications were never causing in the first place. Messages pile up unread and the manager checks manually even more often to compensate.
Turn off reaction counts and read receipts where your tool allows it, since removing the visible number often does more than muting the alert.
Rebuilding how your team communicates
Since these pulls are engineered to beat individual discipline, the fix that holds is changing team defaults, not asking each person to have more willpower.
A manager privately commits to checking messages twice a day, but the team still expects instant replies because no one told them the norm changed, so the manager quietly breaks the commitment within a week to avoid seeming unresponsive.
Set an explicit, shared team norm for expected response times, and put it in writing so no one has to guess.
The tools keep getting better at pulling you back
Messaging and collaboration tools update constantly, and each update tends to add features that make the app more engaging, not less. A team norm that works well against today's version of a tool may need revisiting after the next redesign, so this is a standing part of managing a team, not a one-time policy you write and forget.
Recognizing the engineered pull can make a manager want to disengage from messaging entirely, but genuine urgent issues do arrive that way. The tension resolves by separating true urgency, defined in advance with the team, from the ordinary flow of updates, and only breaking your own response windows for the first kind.
Name one thing, honestly
If your team could not see when you were online, would your own checking habits change, and what does your answer say about who the checking is really for?
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
Set an explicit, shared team norm for expected response times, and put it in writing so no one has to guess.