1

In researching the 100% Utilization Fallacy, I came across the suggestion to optimize for flow efficiency (making sure the workflow for each individual customer/project/task/what have you is as quick as possible), rather than resource utilization (making sure everyone always has work to do).

However, how does one actually accomplish this? What does one mandate? What does one measure? What does one avoid?

2

Based on the information you provided:

How does one actually accomplish this?

In context of projects I suggest to start with optimizing the schedule for lead time (as opposed to minimum cost). Minimizing the lead time is a "regular scheduling objective" and as such can be scheduled using rule-based approach (simply put - easier).

Based on simple priority rules you can create resource-feasible schedules, here is a simple video with "boxes" to illustrate the process.

What does one measure?

Since the main optimization criterion is the lead time, I would measure:

  1. Time between project/task/order etc. start and end - as the main metric to optimize.
  2. "Wait time" vs. "Work time" - to get a better understanding of the optimization potential.
  3. Depending on the nature of projects/tasks/orders I would get a more deep dive into "wait" and "work" to understand their structure, reasons etc.

What does one avoid?

With overoptimizing for lead time, costs might get out of control. Having this risk I would make sure I establish some sort of control over costs to keep them reasonable.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.