There’s a phrase so embedded in modern work life that most people never question it: time management. We accept it as both a skill and a virtue. We buy systems for it, download apps for it, take courses in it.
But what if the premise is slightly off? What if “managing time” is something like “managing weather” — technically meaningful in narrow ways, but missing the point of what time actually is?
Dawna Ballard is a professor of organizational communication at the University of Texas at Austin, where she specializes in chronemics — the study of time as it relates to human communication. Her book, Time by Design: How Communicating Slow Allows Us to Go Fast, is built on a principle she calls slow communication design: the idea that how we pace our conversations and interactions shapes our speed and effectiveness far more than most productivity frameworks acknowledge.
Time and Temporality Are Not the Same Thing
Dawna draws a line between two things we tend to conflate. Time, as she uses the word, refers to everything humans design: clocks, calendars, deadlines, scheduled meetings, the shared decision to show up somewhere at a specific hour. These are technologies. Useful ones, often necessary ones, but inventions nonetheless.
Temporality is different. It’s the rhythm of things that don’t negotiate with our calendars. The arc of a good conversation — the sense that it has its own beginning, middle, and end. The time it takes to actually trust someone. The body’s insistence on sleep, regardless of what was scheduled for 6 a.m. The length of a genuine learning curve. These processes have their own pace, and they don’t defer to our Google Calendars. Slow communication is what emerges when we design our exchanges around temporality rather than forcing them into time.
The confusion, Dawna argues, is treating temporality as if it should obey time. We schedule a 30-minute meeting for something that needs an hour of unhurried conversation. We give someone a deadline for work that requires slow, iterative thinking. And we decide we’ll “get better at” sleep the same way we’d optimize a workflow. Then we wonder why we’re tired and behind.
Designing Around What Time Actually Requires
This maps directly onto something I’ve been developing in my own work through TimeCrafting. The framework isn’t about managing time in the traditional sense — it’s about designing around what time actually requires. Not herding minutes, but building a structure that creates space for what matters. The distinction between a time slot and a temporal process is the difference between a container and a living thing.
What Dawna’s research adds — and what struck me most — is how clearly this plays out in high-stakes organizational contexts. The clearest real-world case for slow communication comes from her years studying the Children’s Advocacy Centers, a global network of nonprofits that coordinate across law enforcement, social services, and the legal system to respond to child abuse cases. The stakes couldn’t be higher, and the pressure to move fast is constant.
And yet the turning point in their effectiveness came from slowing down. Agencies that committed to regular 90-minute monthly meetings — a significant ask from people under enormous pressure — discovered something counterintuitive: they got faster. Not because they found a new efficiency tool, but because those meetings built relationships. And relationships are temporal. You cannot rush them without losing what makes them work. Once the people in those rooms actually knew each other, trusted each other, understood how each other operated, the whole system moved better when speed was genuinely needed.
Slow Communication Is How Speed Gets Earned
Slow is smooth. Smooth is fast. It’s a Navy SEAL principle, and Dawna invokes it with care. It isn’t a rejection of speed. It’s a description of how speed actually gets earned.
The practical question, then, isn’t how fast can I do this — it’s what does this actually need? Some things need urgency. Others need patience, repetition, quiet attention, or the kind of unhurried presence that can’t be scheduled in 15-minute increments.
The capacity to tell the difference is, I’d argue, one of the most underrated skills in a productive life — and one that no app is going to develop for you.
Where to Start
Dawna’s practical suggestion for building that capacity is simple: keep a time diary. Not a schedule — a record of where your time actually goes. Do it for a week, or even a day. Then hold that record up against your stated goals. The gap is information. Often uncomfortable information. But it tells you something no productivity system will: whether you’re spending your fast time on quantity tasks and leaving no space for the temporal ones.
Speed, when it shows up, is a byproduct. It’s what happens when you’ve done the slow work well enough that the fast part no longer has anything in its way.
