Archive for the ‘Change Management’ Category

Change: Here to Stay

Sunday, April 18th, 2010

Change is in the air. In much the same way that constraint-related concepts have become standard in manufacturing, critical chain-related concepts continue to gain popularity in the project world. Even if “Critical Chain” doesn’t become standard practice, its important elements will.

For example, consider project buffers: protection time added after project endpoints to protect project deliveries against uncertainty. This concept is known in non-Critical Chain circles as schedule margin or schedule reserve. A few years ago this was not a popular concept, but that has changed. For example, we typically regard government “best practices” as lagging indicators, but NASA (see, for example, p.44) talks a great deal about schedule margin, and the U.S. Government Accountability Office (p. 223) calls schedule reserve a “best practice.” More and more, buffering is being recognized as essential to good management.

Where are these kinds of changes leading? First, I think people will have to pay more attention to the individual concepts like buffers, resource leveling, or task gating than to the overall categories they’re put into, such as Critical Chain or Earned Value Management (EVM). Whether (for example) buffers become part of EVM, or analysis of work completed becomes part of Critical Chain, the concepts that make sense will eventually rise to the top with or without the labels. This is good news.

Second, groups of concepts that together can be applied in the real world to get practical results – methodologies – will continue to be put together into new buckets and given both old and new names. That’s inevitable: we label things, and we like to use popular labels. But it will also serve to create more confusion. Practitioners must understand what practices people refer to when they use a particular label; whether the label is CPM, Critical Chain, EVM, or Monte Carlo. A holistic view of how the methodology fits together to get results will be more and more essential.

Third, project management will continue to improve. Why do I say “continue,” when organizations like the Standish Group “continue” to tell us how poor project results are? Because, on the whole, our ability to manage projects is clearly improving. Project complexity is increasing dramatically year after year: drug development and approval, chip design, and software are far more complex than they were 20 years ago. Meanwhile, new products must hit the market more and more quickly. While project successes across industries may not be at a level we’d like or know to be possible, in a world of increasing complexity and speed, holding steady implies that improvements are going on.

Last, companies and their methodologies will have to become more and more adaptable. That’s because new ideas are going to be tried and integrated, the best will eventually float to the top, and competition will require their adoption. The best new ideas will be more and more essential, both for companies that need to complete their projects more reliably and quickly, and for vendors like ProChain that need to provide that competitive advantage. Your organization should have in place a process for ongoing project management evaluation and improvement.

Checkmate

Thursday, March 4th, 2010

I just finished reading The Checklist Manifesto by Dr. Atul Gawande (New York: Metropolitan Books, 2009). It’s a well-written, entertaining book that promotes the use of checklists to make sure that important steps are followed. He uses examples from areas as diverse as health care (he’s a surgeon), finance, and aviation to demonstrate that checklists can have a tremendous impact. He especially stressed their value for two things: making sure simple requirements aren’t overlooked, and promoting (even forcing) communication at key times.

Working with the World Health Organization, Dr. Gawande conducted a trial of a surgical checklist with eight hospitals in countries as diverse as Jordan, Tanzania, and the U.K. The results were dramatic and highly statistically significant: a 36% reduction in surgical complications and a 47% reduction in deaths. Furthermore, the checklist demonstrated value in hospitals across the economic spectrum.

Of course, many were skeptical, especially at first. Before implementation, his team monitored the omission of key steps in these hospitals, and errors were alarmingly common. Even after people saw these results, it was sometimes necessary to drag them through the process so they could see the value for themselves. Dr. Gawande makes a number of suggestions that can help make checklists easier and more effective, for example: keep them simple and unambiguous, put in only the most leveraged items, and encourage people to tailor them to accommodate local practices.

I’m a strong advocate of well-constructed checklists. We have employed them in ProChain implementations for years and have found them to be very useful in establishing culture change. They can help to make sure that people learn to communicate in the new ways. However, we’ve also found the same kinds of resistance that Dr. Gawande saw: people are openly skeptical, or they say “yes” and act “no.” Checklists can appear harder to justify for project improvements, when people’s lives don’t seem to be on the line. But consider this: if a crucial new product reaches the market earlier, that really can save lives, and it really can save jobs. Missing opportunities to gain that month could have a tremendous human impact.

Harmony

Thursday, November 19th, 2009

I just read the book WA: Transformation Management by Harmony by Yuji Kishira. It’s about critical chain, but from a Japanese perspective. It has some pretty wacky stuff, but that’s ok: I found it very interesting and entertaining.

For me, the most important idea it contains is in the title: relating the concept of Wa (harmony) to implementations of critical chain (CC) and more broadly — and only by inference – to theory of constraints (TOC). If you think in terms of a vision and a message needed to promote (sell!) an implementation internally, it’s hard to find a simple concept that everyone can grab onto and say, “yes, that helps me, I want it.” An implementation of anything does best long-term if there is value created that everyone can relate to. A major effect of a properly done implementation is a reduction in conflicts and chaos: increased harmony. Therefore “harmony” can be such a value and can form a core part of a vision.

It seems to be effective in Japan. I’m here at the TOC International Certification Organization conference in Japan (I presented on the topic of making CC stick). I talked with Yuji and heard the Japanese Director-General of the Ministry of Land, Infrastructure and Transport speak. The concept of Harmony is a big part of the culture here, and it’s the main emphasis when Japanese people talk about success stories.

Will it play in Peoria? Maybe, if we measure it and talk about it. It’s worth thinking about.

A second interesting point in the book is equating safety time with responsibility. For example: I feel responsible for finishing my task in the time I committed to, so I add safety time. Moving the safety time to the buffers spreads responsibility to the entire project team. You’re not alone, you don’t have to shoulder the on-time burden yourself, you have a team to help. Harmony again.

Want a flavor? Try this:

A Safety Bug Story Episode 1
Episode 2
Episode 3

Pssssht. Happy, happy ending.

Multitasking Game

Saturday, October 24th, 2009

Much has been written about the evils of multitasking. If you think multitasking isn’t a big deal, if you don’t see how it affects you, try this multitasking game, similar to the Confetti Factory discussed in the book. This kind of productivity improvement is at the heart of the Billion Dollar Solution. The game hasn’t been tested on all browser types, so let me know how it works on yours. Note: the approach (click-unclick-drag rather than click-drag) is a little odd, do to how Firefox works, but hopefully not too much trouble.

I’d love to expand this into a complete diatribe about multitasking, incorporating also the Mancala Game (see BDS). Maybe one day…