"To read or not to read?"
A few years ago, I was talking to a senior leader about a conflict on the team. I mentioned the difference between affective conflict (personal, emotional) and cognitive conflict (about ideas). They paused: It had been years since they’d finished the course. They admitted they didn’t read much anymore, there just wasn’t time. I let it go. But that moment stuck with me. Since then, I’ve had a habit. As I set about doing the job, I explain the sources that have influenced my action, and ask if they've read this or that influential book. Not in a smug way, I’m genuinely curious. I’ve been trying to make sense of that. It’s not that these leaders aren’t smart or committed. They are. But there’s a gap between knowing a thing and applying it in the messy middle of real work. And maybe reading, especially the kind that invites you to slow down and reflect, feels like a luxury in the face of day-to-day urgency. On the flip side, I’ve seen what happens when ideas are half-read and hastily applied. So maybe the real question isn’t why don’t leaders read? For me, it’s not the five-point frameworks or the productivity hacks. Reading only matters if we stay with the ideas long enough to be changed by them. What’s something you read that changed how you lead? Until next time, ✉️ Enjoying The Messy Middle? If someone sent this email your way and you’d like to get it direct, you can sign up here. |