Aaron U. Bolin, Ph.D.

Two overlapping tidbits of information caught my eye this last week. First, I am trying to persuade my boss to send me to a Lean Six Sigma Master Black Belt course. In the description of the course, a Master Black Belt candidate is described as a Black Belt with an experience level equivalent to 50 process improvement projects. Second, I visited the blog of a very well-known practitioner who indicates that his experience level consists of "over 250 projects" completed. It got me thinking: I wonder how many projects I have completed? I found it surprisingly hard to count projects, even harder to count them honestly. The hard part isn't remembering the work. The hard part is determining what constitutes a project, and which projects count as personal experience. Do all projects have to be continuous process improvement to count?  Does a rapid improvement event count as a project, or should I only count full projects? If I manage the project manager (i.e., he or she works

In business projects, the metaphorical language of picking the low-hanging fruit almost always comes up. Just to be clear, the low-hanging fruit refers to the idea that the easiest or lowest cost work should get done first. Examples of low-hanging fruit include things like eliminating obvious waste, cutting overtime, reducing excessive stockpiles, and removing self-inflicted policy constraints. Good things generally happen when you pick the low-hanging fruit. First, the project team can satisfy an immediate need to be successful, if only on a small scale. Because the low-hanging fruit is so easy to get, harvesting it early in a project can generate momentum for a more sustained effort. Second, everyone on the team can agree. Because the low-hanging fruit is obvious, disagreements on the obvious course of action are normally quite easy to resolve. Third, the project team can de-clutter the solution space. Getting the little things out of the way can help the team stay focused on the