Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Making Work Visible

Making Work Visible

Exposing Time Theft to Optimize Work & Flow
See where work gets stuck, protect capacity, and help teams finish what matters.
by Dominica Degrandis 2017 264 pages
4.09
2k+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat invisible work as a system problem, not a personal failure

The hidden workload. Dominica DeGrandis opens with a familiar scene: a build engineer troubleshooting a failed software build late at night, then tracing dependencies to find the cause. Years later, at Corbis, she saw the same pattern at organizational scale. Work waited on approvals, experts, and uninterrupted time, but those delays were largely invisible. Workers looked busy, yet customers waited and teams blamed themselves for a system that overloaded them.

Make the work legible. A kanban board is a visual way to track work as it moves through states, such as To Do, Doing, and Done. Cards show the request, its type, and relevant blockers. The central method is to expose work, limit active items, measure flow, clarify priority, and adjust using feedback. The board is a diagnostic tool, not decoration.

Analysis

The book’s strongest move is to shift the explanation from individual shortcomings to system design. That matters because people often experience queueing, interruptions, and unclear ownership as personal failure, even when the causes sit beyond their control. A visible board can create shared facts where previously there were competing stories. Still, visibility is not the same as authority: a team may see overload clearly and remain unable to refuse executive requests. The board works best when leaders treat its evidence as a basis for changing commitments, not as a new instrument for monitoring individual effort.

Limit active work before the queue steals your attention

Define the pileup. Work-in-progress, or WIP, means all work that has started but is not finished. Every new commitment adds to the pile, and each item competes for attention. DeGrandis identifies five common reasons people accept too much: loyalty to the team, fear of consequences, liking the requester, underestimating the effort, and preferring shiny new work to tedious completion.

Make capacity explicit. WIP limits cap how many items may be active in a workflow or lane. In a pull system, a worker starts another item when capacity opens, rather than having new work pushed in regardless of workload. Little’s Law describes the relationship between WIP, throughput, and average time in the system: for a stable flow, more WIP at the same throughput means longer waits. Limits make a polite refusal possible and focus attention on finishing.

Analysis

This reframes saying no as a property of workflow rather than a test of courage. That is useful in workplaces where status, hierarchy, or team loyalty make individual refusal costly. The queueing logic also explains why keeping everyone occupied can reduce total delivery: full utilization leaves no room for variation, so small disruptions create long waits. A limit should not be mistaken for a universal number, however. Work differs in size and urgency, and a team needs to review its limits against actual demand, throughput, and service obligations rather than adopt a neat-looking cap without evidence.

Map dependencies before small teams become a slow organization

Find the hidden handoffs. DeGrandis groups dependencies into three kinds: technical links where one change affects another, specialist expertise needed to proceed, and activities that must finish before the next step can begin. In one company described in the book, a product team changed a component without the visibility of another team whose product depended on it. Customers faced millions in additional costs, while the company absorbed reputational damage and lost market share.

Make connections visible. A dependency matrix places teams on both axes and marks where one team’s output affects another. Boards can also use dependency lanes, tags, or explicit handoff rules. The book illustrates how coordination grows quickly as dependencies multiply: with several required inputs, delivery depends on all of them arriving on time. Small teams may work quickly in isolation, yet their combined system can crawl if cross-team coordination is heavy.

Analysis

The key distinction is between local speed and system speed. Smaller teams can make decisions quickly, but autonomy alone does not remove the cost of shared components, scarce specialists, or sequential approvals. Mapping dependencies turns those relationships into something negotiable: teams can change interfaces, cross-train, or coordinate earlier. The probability illustration is useful as a warning, not a precise forecast. Real dependencies are not always independent, and teams can reduce risk through buffers, parallel work, or graceful failure. The practical question is which links actually delay valuable delivery, not whether every connection can be eliminated.

Make interruptions countable, then reserve capacity for them

Expose the surprise work. Unplanned work includes incidents, urgent requests, rework, and changes in direction. It can be necessary, but when it remains invisible, planned work appears mysteriously late. In an experiment with two project managers, every interruption was recorded on a sticky note for a week. The count reached 92, most of them status questions from people who could not see project progress. The board revealed both the disruption and the lack of information behind it.

Build room for reality. Teams can track unplanned items in their own lane, then compare their share with planned work. DeGrandis gives an example: if 40 of 100 completed items were unplanned, the team might reserve a similar share of its WIP capacity. Other countermeasures include a rotating person to screen interruptions, scheduled office hours, protected focus periods, and timed work sessions.

Analysis

Counting interruptions changes the conversation from “people are distracted” to “this is the demand the system is receiving.” That distinction helps teams address causes, such as missing status information, rather than simply blame those asking questions. Reserving capacity is also more credible than pretending urgent work will stop arriving. The book’s ratio uses item counts, though, and a count can disguise differences in effort: forty tiny requests are not equivalent to forty major incidents. Teams should treat the ratio as a starting signal, then refine it with impact, duration, and the value of the planned work being displaced.

Choose one priority by value lost to waiting

Replace “everything matters.” One IT operations group had 41 engineers working across 33 projects, with more than half labeled top priority. Work stayed unfinished while new projects arrived. A lead engineer ranked the projects, but a vice president challenged the ordering, exposing that the organization had no shared prioritization rule. Making priorities visible turned a hidden disagreement into a decision the group could examine.

Compare urgency and value. Cost of Delay estimates what is lost when work arrives late, including lost revenue or service value, added costs, and delays imposed on dependent work. Other options include first-in, first-out, executive ranking, and Weighted Shortest Job First, which favors work with high delay cost relative to its duration. A line of commitment marks when an item stops being a mere option and becomes agreed, active work.

Analysis

A priority list is a compact expression of strategy: it says which outcomes the organization is willing to delay. Cost of Delay can make that tradeoff more concrete than debating whether a request feels important. It also broadens value beyond immediate revenue, which matters in public services, safety, and reliability work. The method still depends on uncertain estimates and whose consequences count. A numeric ranking can create false precision or privilege easily measured benefits. Its best use is to make assumptions visible and provoke a better decision, not to pretend that every value can be reduced to one score.

Rescue aging work before it hardens into emergencies

Stale work has a cost. Neglected work includes maintenance, bugs, security improvements, unfinished feedback, and projects that no longer justify their cost. At Corbis, an old, fragile financial system remained in use because upgrades seemed risky. Its neglected configuration repeatedly caused problems that required troubleshooting. Technical debt behaves like a loan: earlier shortcuts make future changes more expensive. Low-value “zombie projects” also drain attention while remaining barely alive.

Act on age, not guilt. One operations team had nearly 100 items waiting for validation. It announced that items untouched for 14 days would close. Of 104 tickets closed, only two were requested back. The team then shortened the idle window gradually, from 14 days to 10, then 7, then 5. Aging reports help identify stuck work; teams can finish it, return it to the backlog, or cancel it instead of letting sunk costs dictate the choice.

Analysis

The validation example shows how a queue can preserve the appearance of activity after the work has lost practical value. A time limit creates a decision point and can restore feedback while details are still fresh. Gradual tightening is a sensible change strategy because it lets people adapt rather than experience a sudden rule imposed on them. Closing old items should not become an excuse to erase inconvenient obligations, however. Each category needs a clear owner and a fair appeal path, especially when work concerns security, compliance, or a customer still waiting for a promised result.

Forecast with completed work, not optimistic task estimates

Measure elapsed time. The book distinguishes lead time, from request to delivery, from cycle time, from starting work to delivery. Both are flow-time measures. Rather than add optimistic estimates for every task, teams can examine how long comparable work actually took and communicate a probability, such as the share of requests completed within a given number of days. WIP, throughput, and aging reports help reveal whether delivery is getting faster or queues are growing.

Leave room for variation. Queueing theory explains why waits rise sharply as utilization approaches full capacity, especially when demand varies. A doctor booked solid has little room for an urgent patient; a team at full utilization has little room for incidents or unexpected complexity. The book also favors smaller batches, which shorten feedback loops and reduce the amount of unfinished work waiting between stages. Flow-time measures should include weekends because customers experience elapsed time, not just scheduled workdays.

Analysis

Historical delivery data replaces confidence with calibration. It lets a team say what usually happens, while acknowledging that exceptions remain, and it makes the queue visible as a source of delay. This is more honest than treating a detailed schedule as a guarantee. The comparison only works when work items are sufficiently similar and the process is stable enough for past performance to inform future expectations. Metrics can also become targets and invite gaming. They should guide decisions about capacity and flow, not rank workers by speed or turn every unusual request into a performance failure.

Use meetings to resolve blockers, not recite status

Let the board carry status. In one 35-person group, a daily round-robin update consumed time without surfacing the real obstacles. The team began keeping its board current before the meeting and used the stand-up to ask what was blocked, what might become blocked, and what work was missing from view. The meeting ended within 15 minutes, and people used the time afterward to solve issues together.

Structure discussion around shared questions. Operations reviews offer a monthly look at throughput, flow time, blocked items, and risks. At Corbis, a cumulative flow diagram showed a spike in incoming requests and helped support a request for more staff. Lean Coffee, another format, lets participants propose and vote on topics, then discuss them in timed rounds. Both practices make conversation more focused by replacing status theater with evidence, priorities, and problems people can act on.

Analysis

Meetings improve when information is available before people enter the room and discussion is reserved for decisions that require coordination. The after-stand-up example also shows that reducing meeting time can create informal problem-solving time, not merely empty calendar space. Participatory formats such as Lean Coffee can broaden whose concerns receive attention. Yet structure alone cannot neutralize hierarchy: a senior person can still dominate a vote or dismiss inconvenient metrics. Facilitation, psychological safety, and a clear route from identified problems to accountable action matter as much as the meeting template.

Test one workflow change at a time, then keep what improves flow

Start with the current reality. DeGrandis argues against designing a perfect board before use. Put existing work on a simple board, watch where it stalls, and adjust based on what the team learns. At Corbis, measuring cycle time and showing the results to leadership proved more effective than simply complaining about overload. Small experiments can test whether a new WIP limit, interruption policy, or validation window actually improves the work.

Change without shock. The book describes a J-shaped dip in performance when people learn a new system, then gives eBay’s gradual color redesign as an example: instead of replacing yellow with white at once, designers shifted the background shade in small increments. Teams also need alignment on why work matters, not just instructions about how to process it. The goal is continuous adjustment of the system, not a one-time rollout or a hunt for perfect practices.

Analysis

This experimental stance is a useful antidote to transformation plans that promise certainty before anyone has tried the new process. Small tests make cause and effect easier to discuss, reduce the cost of a failed change, and give affected workers a role in shaping the system. The method is not automatically safe or incremental: some problems, such as a severe security exposure, demand immediate action. Nor should “experiment” become a way to postpone decisions indefinitely. The discipline is to state what is changing, what evidence would count as improvement, and when the team will decide whether to keep or revise it.

Analysis

Making Work Visible is a practical management argument presented through workplace stories, exercises, and operating concepts. Its central insight is that chronic overload is not mainly a personal time-management defect. It is a system condition produced by demand that exceeds capacity, work hidden across tools and teams, and incentives that reward starting or staying busy more than finishing valuable work. DeGrandis’s five time thieves give that condition a memorable diagnosis: excessive work-in-progress, unknown dependencies, unplanned work, conflicting priorities, and neglected work. Kanban then supplies an accessible intervention: visualize demand and states, constrain active work, measure flow, clarify priority, and adapt through feedback.

The book is strongest when it converts abstractions into visible evidence. The 92 recorded interruptions expose missing project information as well as interruption volume. The overloaded validation queue shows how work can be nominally complete yet deliver no value. Flow measures and operations reviews give teams a way to make these problems legible to leadership. The stories also reinforce a systems perspective: reducing one team’s local wait or maximizing an individual’s utilization can worsen the organization’s total delivery.

The approach has limits that make its governance assumptions important. Boards cannot themselves resolve power imbalances, insufficient staffing, or leaders who continue to inject urgent work without accepting its opportunity cost. Metrics are also selective models, not neutral reality. A count of work items can obscure differences in effort, while a focus on elapsed time can undervalue quality, safety, or learning. The author’s IT examples travel well to other knowledge work, but each setting needs its own definitions of value, urgency, and acceptable risk.

The durable lesson is therefore not “install a board.” It is to create shared visibility that changes decisions. A useful system makes overload discussable, gives teams a legitimate basis for sequencing work, and connects measured outcomes to organizational choices. Without that feedback loop, visualization risks becoming administrative theater. With it, workflow improvement becomes a repeatable inquiry into what is waiting, why it is waiting, and what the organization should stop, change, or protect.

Summary in 30 Seconds
When demand exceeds capacity, hidden queues, interruptions, handoffs, and competing priorities delay valuable work. Visualize requests and blockers, limit active items, and start new work only when capacity opens. In one week, two project managers recorded 92 interruptions, mostly status questions, revealing an information gap as well as disruption. Rank work by the value lost while it waits, track elapsed delivery times, and reserve room for unplanned demand. Small, measured workflow changes help teams improve without assuming every delay is an individual failure.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.09 out of 5
Average of 2k+ ratings from Goodreads and Amazon.

Making Work Visible receives high praise for its practical approach to implementing Kanban and improving workflow visibility. Readers appreciate its clear explanations of the "five time thieves" and strategies to combat them. Many find it valuable for both newcomers and experienced practitioners, highlighting its actionable advice and engaging writing style. Some reviewers note that while the content may be familiar to those already versed in Lean and Kanban principles, the book's focus on visualization techniques and real-world examples make it a worthwhile read. A few criticisms mention typos and repetitiveness.

Your rating:
4.53
235 ratings
Want to read the full book?

Glossary

Work-in-Progress (WIP)

Started, unfinished work

WIP is all work that has begun but has not yet been completed and delivered. It includes items being actively worked on and items stalled between steps. Tracking and limiting WIP helps teams see overload, reduce context switching, and avoid extending the time customers wait for finished work.

Kanban

Visual pull system

Kanban is a visual method for managing work as it moves through a workflow. Cards represent work items, columns show their current states, and WIP limits constrain how much work can be active. In a pull system, a new item is started when capacity becomes available rather than added regardless of the team’s workload.

Five Thieves of Time

Five sources of delay

The Five Thieves of Time are the book’s organizing model for common causes of delayed work: too much work-in-progress, unknown dependencies, unplanned work, conflicting priorities, and neglected work. The categories help teams identify why work is delayed, what evidence would reveal the problem, and where to try a countermeasure.

Cost of Delay (CoD)

Value lost through delay

Cost of Delay estimates the impact of delivering an outcome later than desired. It can include revenue or other business value lost, costs that continue while work is delayed, and the effects of delaying work that depends on it. Teams use the estimate to compare urgency and value when choosing what to do next.

Flow time

Elapsed delivery duration

Flow time is the elapsed duration from a defined start point to a defined finish point for a work item. It does not pause for weekends or other nonworking days. Historical flow times can help teams describe delivery expectations probabilistically, provided the work being compared is sufficiently similar.

Little's Law

WIP, throughput, and time

Little’s Law relates the average amount of work in a stable system to the rate at which work is completed and the average time work spends there. In practical terms, if throughput stays constant, increasing WIP increases average time in the system. The relationship depends on the system meeting the law’s assumptions.

Time Thief O’Gram

Visual risk summary

The Time Thief O’Gram is a visual summary of how often the five time thieves appear across work. Teams tag or categorize relevant items, then count and track those patterns over time. The result helps teams and leaders see sources of uncertainty and overload rather than relying only on general complaints or activity measures.

A3

Structured problem-solving page

A3 is a problem-solving and communication approach organized on a sheet of paper sized A3, approximately 11 by 17 inches. It gives a team a compact structure for describing a problem, examining causes and options, and building understanding and agreement. In the book, it is suggested as a way to discuss prioritization.

Lean Coffee

Participant-led meeting format

Lean Coffee is a structured meeting in which participants propose topics, vote on which matter most, and discuss them in timed rounds. A simple board tracks topics from discussion queue to active conversation to completion. The format gives attendees a role in setting the agenda while limiting the time spent on each topic.

Line of commitment

Point work becomes committed

A line of commitment is a marked point on a workflow board that separates optional backlog items from work the organization has agreed to pursue. Moving an item across the line signals that it has been prioritized and that people and capacity are now committed to it. The commitment makes its delay and resource costs more explicit.

Kingman's formula

Queue wait approximation

Kingman’s formula is an approximation used in queueing theory to understand how waiting time relates to utilization and variability in arrivals and service. The book uses its curve to illustrate that waits rise sharply as capacity utilization approaches 100 percent, particularly in variable environments such as technology operations.

FAQ

1. What is "Making Work Visible" by Dominica DeGrandis about?

  • Focus on Time Theft: The book explores the concept of "time theft" in knowledge work, identifying how invisible work and poor workflow practices steal valuable time from individuals and teams.
  • Five Thieves of Time: It introduces and explains the five main "thieves" that prevent effective work: Too Much Work-in-Progress (WIP), Unknown Dependencies, Unplanned Work, Conflicting Priorities, and Neglected Work.
  • Lean, Kanban, and Flow: DeGrandis provides practical guidance on using Lean, Kanban, and flow-based methods to make work visible, optimize workflow, and improve productivity.
  • Real-World Examples: The book is filled with real-life stories, exercises, and visual tools to help readers identify and address workflow problems in their own organizations.

2. Why should I read "Making Work Visible" by Dominica DeGrandis?

  • Universal Relevance: Anyone who feels overwhelmed by endless to-do lists, constant interruptions, or unclear priorities will find actionable solutions in this book.
  • Practical Tools: The book offers concrete exercises, visualizations, and board designs that can be implemented immediately to improve workflow and reduce stress.
  • Improved Team Performance: By exposing hidden work and time thieves, teams can communicate better, prioritize more effectively, and deliver higher quality results.
  • Sustainable Work Practices: DeGrandis emphasizes creating healthy, sustainable work habits that lead to less burnout and more fulfilling workdays.

3. What are the key takeaways from "Making Work Visible" by Dominica DeGrandis?

  • Visibility Drives Improvement: Making work visible is the first step to identifying problems and optimizing workflow.
  • Limit Work-in-Progress: Too much WIP is the root cause of many workflow issues; limiting WIP is liberating and essential for flow.
  • Address the Five Thieves: Recognizing and combating the five thieves of time is crucial for delivering value efficiently.
  • Use Metrics and Feedback: Data-driven metrics and regular feedback loops help teams calibrate, improve predictability, and make better decisions.
  • Change Requires Buy-In: Implementing these practices requires participation and buy-in from all levels of the organization.

4. What are the "Five Thieves of Time" described in "Making Work Visible" by Dominica DeGrandis?

  • Too Much Work-in-Progress (WIP): Taking on more work than capacity allows, leading to delays, context switching, and reduced quality.
  • Unknown Dependencies: Hidden or unrecognized dependencies between teams, people, or systems that cause unexpected delays and failures.
  • Unplanned Work: Interruptions, urgent requests, or failures that disrupt planned work and reduce predictability.
  • Conflicting Priorities: Competing demands and unclear priorities that result in multitasking, longer cycle times, and incomplete work.
  • Neglected Work: Important but unfinished or forgotten work, often maintenance or technical debt, that eventually becomes urgent or causes failures.

5. How does "Making Work Visible" by Dominica DeGrandis define and address Too Much Work-in-Progress (WIP)?

  • Definition: WIP is all the work that has been started but not yet finished; high WIP leads to longer cycle times and more context switching.
  • Consequences: Excessive WIP causes delays, increases costs, reduces quality, and irritates staff due to constant interruptions and lack of focus.
  • Root Causes: People often take on too much due to optimism, desire to please, fear of saying no, or attraction to new tasks.
  • Solution: Use Kanban boards and WIP limits to visualize and constrain the amount of work in progress, enabling teams to focus and finish tasks efficiently.

6. What practical methods does "Making Work Visible" by Dominica DeGrandis recommend for making work visible?

  • Kanban Boards: Use simple To Do, Doing, Done boards to visualize all work items and their current state.
  • Work Item Categories: Categorize work by type, urgency, or requester to clarify priorities and workflow.
  • Visual Signals: Employ colors, tags, and icons to highlight pain points, dependencies, and priorities.
  • Team Exercises: Conduct demand analysis, workflow mapping, and card design sessions to collaboratively identify and visualize work and bottlenecks.

7. How does "Making Work Visible" by Dominica DeGrandis suggest handling Unknown Dependencies?

  • Identify and Map Dependencies: Use tools like dependency matrices, swimlanes, and tags to make cross-team and cross-system dependencies visible.
  • Reduce Coordination Costs: Visualizing dependencies helps teams anticipate issues and reduces the time spent on coordination and firefighting.
  • Promote Cross-Functional Teams: Organize around product teams rather than temporary project teams to minimize hand-offs and knowledge loss.
  • Continuous Communication: Encourage regular, structured communication between teams to surface and address dependencies early.

8. What strategies does "Making Work Visible" by Dominica DeGrandis offer for dealing with Unplanned Work?

  • Visualize Interruptions: Track and display unplanned work and interruptions on Kanban boards to make their impact visible to all stakeholders.
  • Allocate Capacity: Reserve a portion of WIP or team capacity specifically for unplanned work, based on historical ratios.
  • Interruption Busters: Implement roles like a "goalie," set office hours, and use "do not disturb" times to protect focus and reduce disruptions.
  • Continuous Improvement: Regularly review the ratio of planned to unplanned work and adjust processes to minimize unnecessary interruptions.

9. How does "Making Work Visible" by Dominica DeGrandis recommend prioritizing work and resolving Conflicting Priorities?

  • Explicit Prioritization Policies: Make prioritization rules visible and agreed upon, using methods like A3 thinking, Cost of Delay (CoD), or Weighted Shortest Job First (WSJF).
  • Visualize Priorities: Clearly indicate priority levels on boards and use a "line of commitment" to signal when work is truly prioritized and ready to start.
  • Limit Top Priorities: Avoid the trap of making everything a "priority one"—focus on the most important work to reduce WIP and cycle times.
  • Facilitate Necessary Conversations: Use visual tools to provoke discussions among stakeholders and leadership about what truly matters most.

10. What metrics and feedback mechanisms does "Making Work Visible" by Dominica DeGrandis recommend for optimizing workflow?

  • Flow Metrics: Track lead time, cycle time, WIP, throughput, and aging reports to measure how work moves through the system.
  • Time Thief O’Gram: Use this tool to tag and track the frequency and impact of each time thief, providing transparency and focus for improvement.
  • Operations Reviews: Hold regular, time-boxed reviews where teams present objective metrics, discuss blocked work, and identify trends.
  • Continuous Calibration: Use metrics to set realistic expectations, improve predictability, and guide incremental changes to workflow.

11. What are some common pitfalls or "beastly practices" to avoid, according to "Making Work Visible" by Dominica DeGrandis?

  • Excluding Non-Working Time: Avoid manipulating metrics by excluding weekends or holidays, as this skews data and reduces transparency.
  • Ineffective Accounting: Relying on time sheets or activity tracking rather than value delivered can hide queues and delay improvements.
  • Gantt Charts and Overplanning: Traditional project management tools like Gantt charts often ignore wait times and dependencies, leading to unrealistic plans.
  • Individually Named Swimlanes: Focusing on individuals rather than work items discourages collaboration and hides bottlenecks.
  • Overcomplicating Tools: Using too many tools or garish visuals can create confusion and waste time; keep boards simple, beautiful, and functional.

12. What are the best quotes from "Making Work Visible" by Dominica DeGrandis and what do they mean?

  • "We can better manage what we can see." — Emphasizes the core message that visibility is the foundation for improvement and control.
  • "Too much WIP is the ringleader of all the other thieves." — Highlights that excessive work-in-progress exacerbates all other workflow problems.
  • "If everything is priority one, then nothing is a priority one." — Warns against the dilution of focus and the importance of true prioritization.
  • "Multitasking is merely the opportunity to screw up more than one thing at a time." — Critiques the myth of multitasking and advocates for focused work.
  • "Important work that is delayed becomes urgent, unplanned work." — Stresses the need to address neglected work before it turns into emergencies.

About the Author

Dominica DeGrandis is a respected expert in the field of Kanban and Lean methodologies. With extensive experience in IT operations and software development, she has become a sought-after consultant and speaker on workflow optimization and time management. DeGrandis is known for her practical, hands-on approach to implementing Kanban systems and improving team productivity. Her work focuses on making complex concepts accessible and actionable for professionals across various industries. As the author of "Making Work Visible," she has contributed significantly to the understanding and application of visual management techniques in modern workplaces. DeGrandis' insights draw from her years of working with diverse teams and organizations, helping them overcome common workflow challenges.

Download PDF

To save this Making Work Visible summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.43 MB     Pages: 21

Download EPUB

To read this Making Work Visible summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.41 MB     Pages: 28
Want to read the full book?
Follow
Listen15 mins
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...