GA 654 | Escaping Time Poverty with Peggy Sullivan
Gemba Academy Podcast: Lean Six Sigma | Toyota Kata | Productivity | LeadershipShow Notes
Most people who feel overwhelmed blame their schedule. Peggy Sullivan argues the diagnosis itself is wrong. Time poverty has nothing to do with time management and everything to do with capacity, and until you start subtracting, no amount of better planning will get you out from under it.
Peggy has spent a decade researching how people reclaim time, averaging five hours back per week for the individuals she works with. Her framework, Performance by Design, connects directly to ideas Lean practitioners already know well: eliminate the low-value work first, then protect the space you have recovered.
“I was thinking to myself that it’s time that I choose meaning over mayhem.” – Peggy Sullivan
In this episode you’ll learn:
Why capacity is the real constraint, not your calendar (3:45)
How one small change gave a senior management team three hours back (5:29)
The three elements of the Performance by Design framework (6:48)
Why subtraction must come before everything else (7:52)
How to identify the low-value habits you no longer question (10:28)
Why interruptions cost far more time than most people realize (14:12)
What choosing meaning over mayhem looks like under the hardest circumstances (18:20)
How values management differs from time management (23:34)
Why human connection is the first thing to disappear when capacity runs out (26:57)
Keep Learning
If Peggy’s case for subtracting low-value work before adding anything new resonates, the School of Lean covers the same principle at the process level, from value stream mapping to identifying and eliminating waste.
Learn More About School of Lean at gembaacademy.com/school-of-lean
Podcast Resources
Peggy on LinkedIn
Beyond Busyness
Get All the Latest News from Gemba Academy
Stay current on new courses, podcast episodes, and continuous improvement resources. Sign up for the Gemba Academy newsletter at gembaacademy.com/news
What Do You Think?
If you had to subtract one recurring commitment from your week right now, what would it be and what has kept you from doing it?
More from Gemba Academy Podcast: Lean Six Sigma | Toyota Kata | Productivity | Leadership
Most kaizen practitioners know the moment when a skeptic turns. It can take a day, a week, or nine months, but something clicks and the person who crossed their arms at the start is now telling the VP what their line accomplished. Adam Lawrence has spent decades collecting those moments, and he has built a framework around making them more likely to happen. That framework just got a significant overhaul.
Value stream mapping is one of the most familiar tools in lean practice. Christian Wolcott has spent 25 years using it with clients from Toyota suppliers to NASA, and he arrived at a question that most practitioners never think to ask: what if you mapped your own life the same way? The seed came not from a client engagement or a sensei, but from his daughter, who sketched a rough timeline on a note card after joining him on a Japan study tour. That sketch became a book, and the book became a method.
Most lean practitioners know the theory of constraints. Fewer apply it before they start fixing things. Hessam Vali, a manufacturing consultant and MES software founder based in Wichita, argues that most improvement efforts fail because they target the wrong kinks in the hose. His framework is deceptively simple: if the deepest constraint is still in place, no one will ever see your work.
Most resistance to lean is blamed on the wrong thing. Ben Morley, an Air Force pilot turned Lean Six Sigma consultant, argues the tools are never really the problem. The breakdown almost always lives somewhere between leadership buy-in and an assumption nobody thought to question. His conversation with Ron Pereira covers cockpit emergencies, a $5 million backlog that dissolved from a single customer phone call, and what a caterpillar turning to soup has to do with organizational transformation.
Most continuous improvement practitioners are using AI the same way they use Google, and getting roughly the same quality of results. David Osagie-Igiehon has taken a different approach. He builds custom agents trained on lean principles, CI methodology, and the specific knowledge domains his work demands, and the gap in output quality is significant. What he describes is less about automation and more about compressing the time it takes to do rigorous work.