> The battle in an organization is convincing people to look at flow at all. I guess that's the point... an organization needs enough people to know about queu

> The battle in an organization is convincing people to look at flow at all. I guess that's the point... an organization needs enough people to know about queue theory "to look at flow" and understand that queues are ubiquitous and anticipate that these queues experience a latency phase change at some point depending on utilization (and job duration variance). If an organization doesn't have anyone who understands queue theory, then it's probably more likely to have queue-related failures.