One-page summary · 3 min read
Making Work Visible
Exposing Time Theft to Optimize Work & flow
by Dominica Degrandis
The big idea
Knowledge work, especially in software and IT, is largely invisible; unlike a factory floor, you can't see where work is stuck. Teams unknowingly lose huge amounts of productivity to what DeGrandis calls time theft, and making work visible through Kanban-style boards and flow metrics exposes the problem so teams can fix it.
Too much work in progress. Unknown dependencies. Unplanned work. Conflicting priorities. Neglected work.
The book's central diagnostic framework: identifying which thief is at work is the first step to fixing flow problems.
Key ideas
Visualize work with a board
A simple To Do, Doing, Done board, physical or digital, makes invisible knowledge work visible immediately, surfacing bottlenecks that would otherwise stay hidden in people's heads or ticketing systems.
Limiting work in progress is the highest-leverage fix
Too much work in progress is framed as the biggest thief. Capping how many things a person or team works on at once reduces context-switching and speeds up real completion.
The 80% utilization trap
Pushing people or teams past roughly 80% utilization causes queues and wait times to increase sharply, so deliberately keeping slack capacity actually improves throughput.
Visibility should cascade across levels
Kanban-style boards work best used at multiple organizational levels, team, department, and company, so individual work visibly connects to broader priorities.
Standups should surface blockers, not status
Daily standups are more useful focused on what's blocked or at risk rather than each person reciting a task list.
Map the full value stream
Borrowed from Lean manufacturing, mapping a work item's full end-to-end path reveals handoffs, delays, and waste invisible when looking at any single step alone.
Try it this week
- Set up a simple To Do, Doing, Done board for your own tasks or your team's work this week, even just on sticky notes.
- Count how many things you or your team are actively working on right now, and try capping it to a smaller explicit limit.
- In your next status meeting, ask what's blocked before asking what did you do.
- Identify one piece of unplanned work that derailed your week and note where it came from.
Is it for you?
Best for
- Software and IT teams, engineering managers, and Agile or DevOps practitioners
- Anyone managing knowledge-work teams where work isn't physically visible
Less useful if
- General personal productivity or non-team, individual use; the vocabulary and examples are Kanban and sprint-specific
- Readers without any team or project-management context