What Teachers Can Learn from Irresistible
It's 9:15 p.m. and tomorrow's lesson plan is half-written. The teacher opens a video platform to find one clip for the unit on ecosystems, tells herself she'll watch two minutes, and forty minutes later is three videos deep into something about someone else's classroom decorations. The autoplay countdown ticks down before she can decide not to watch the next one, and each video ends by suggesting one slightly more interesting than the last. She knows this pattern; she's watched a dozen students fall into the identical loop with the same app during independent work time, phones supposedly away, eyes flicking down anyway. She used to read that as a discipline problem in her students. Sitting here at her own kitchen table, unable to close the tab, she starts to wonder if she's been asking the wrong question about all of it.
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
Understanding what a phone in a pocket is actually doing
The apps your students reach for during a lull were built by teams focused on maximizing time spent, not on serving a ten-minute break well. That is worth naming plainly, separate from any judgment about the individual student.
A teacher confiscates a student's phone for scrolling during a quiet work period and treats it as a one-time discipline issue, without addressing that the same student will reach for the same app the moment the phone comes back, because nothing about the underlying pull has changed.
When talking with students about phone use, describe the specific design feature at work, like an endless feed with no stopping point, rather than only naming the behavior as inattentive.
Naming the specific hook instead of just "distraction"
An unpredictable notification, a public like count, and a feed that never runs out each work through a different mechanism, and treating all of them as one blob called distraction makes it harder to address any of them well.
A school adopts a blanket phone ban assuming all distraction is the same problem, but students simply move the identical checking behavior to a school-issued laptop's browser tabs, because the ban addressed the device and not the underlying pull.
Build one short lesson or advisory conversation around a single mechanism, such as the pull of an unpredictable reward, so students learn to recognize it by name.
Changing the classroom environment, not just the rule
Since these mechanisms are built to override willpower, a classroom that changes its physical and digital defaults will do more than a rule that depends on students resisting temptation unaided.
A teacher announces a no-phones policy but keeps a charging station at the front of the room in plain sight of every desk, so the pull to check a buzzing phone stays present the entire period despite the rule.
Physically separate students from phones during independent work, such as a phone caddy by the door, rather than trusting a policy alone to hold.
The tools your students use keep changing
Whatever app is pulling at your classroom this year will be replaced by a more engaging one within a few years, often built by the same teams using lessons learned from the last version. Staying current with roughly how these mechanisms work matters more than memorizing which specific app is the problem today, since the app itself is not the constant.
Naming the engineered design behind an app can tip into blaming technology for everything, when some student disengagement is genuinely about the lesson, not the phone. The tension resolves by checking your own material honestly first, and reserving the engineered-design conversation for moments when attention drops even during work you know is genuinely engaging.
Name one thing, honestly
Think of one specific moment this week when a student's attention visibly left the room. What mechanism, not just what device, might have pulled it away?
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
Physically separate students from phones during independent work, such as a phone caddy by the door, rather than trusting a policy alone to hold.