As anyone who has been a public servant for more than a decade knows, improvement initiatives seem to come and go like the tide. Total Quality Management. Zero Defects. Six Sigma. Performance Management. Business Process Management. Balanced Scorecard. The list goes on.

Usually they come in with a bang and leave with a whimper. However, they keep popping up because, at our core, we share a fundamental desire to get better. The results may be mixed, but failure to try leaves us bitter and cynical.

When Lean first started gaining popularity in government circles, I thought, "Here we go again." Now, I must admit I'm a big fan of Lean (a.k.a. Lean IT or Lean Government), and I think there's a wealth of good we can accomplish by applying Lean methodology to our operations. In fact, having worked with multiple types of Lean methodology in project teams, I'm more encouraged by it than any other government improvement effort. There certainly is potential.

Lean is the process that elevated Toyota, is embraced by private-sector companies around the globe, and seems to focus on all the right areas. It even sounds healthy. But it also sounds like the flavor of the month and runs the risk of being overemphasized, underutilized and could evolve into another bit of jargon for sales pitches.

Introducing Lean

Here's a quick introduction if you don't know much about Lean. It's about improving the processes we work in. It doesn't focus on those superfluous "efficiency savers" like furloughs, turning off lights in soda machines and canceling all out-of-state travel. Instead, Lean looks at how we do what we do and encourages us to do the most essential things faster, better and more cheaply. It's about teams of employees working to examine issues and provide solutions to customer problems, system issues and budget catastrophes.

Lean deals with the 95 percent of waste that William Edwards Deming, who many consider the Lean movement's founder, taught is in every work process. It's about reducing the time spent handing off work between units, eliminating the wasted resources seen in batch work and expanding those bottlenecks that slow processes to a crawl. It involves looking at the fundamental way that work is done by business units and improves how it's done.

Caution: Lean Back

I encourage all CIOs and IT professionals who see Lean coming to run away as fast as they can. When you hear the word Lean, you should shut down, check your BlackBerry for e-mails and do everything possible to indicate that you are distancing yourself from it -- at least for now.

My warning stems from the fact that if you engage in Lean now, you'll screw it up. There's no technology solution in Lean, at least not yet. As a guy who loves technology, it's hard to admit when it isn't the answer to efficiency problems. But more often than not, IT professionals aren't providing the solution, and it will be a very rare occasion when we can drive Lean into a business unit with great success.

Allow Lean to take root in the managers who run the day-to-day operations. Give them the space and time they need to look at their processes without putting false hope in new applications. Allow them to dig into the core of what they do without confusing system upgrades with process change. If meaningful transformation is going to happen, it probably isn't going to be the IT component alone that's the catalyst.

Let me back up such blasphemy. In 2001, a large state was trying to reduce the time citizens waited in line for automobile registrations. It had invested heavily in a new system that was going to