Can He Fix It?
Spending money to save money — will it add up? Daniel Walters
Dave Steele has a black belt in efficiency. And it’s worth $120,000 a year.
Steele, Spokane’s former real estate and facilities director, is being paid a $94,628.16 salary — $120,000 if you include benefits — to head up the city’s newly formed Employee Led Innovation (ELI) center. His job is to do what high-priced outside consultant couldn’t: cut costs and eliminate inefficiencies, while actually improving employee morale.
Earlier this year, the city of Spokane spent up to $90,000 to turn 17 Spokane employees into “Green Belts” and “Black Belts” using a quality improvement process called Lean Six Sigma. (Getting your green belt takes two weeks of intensive training. A black belt takes four.)
Originally, Lean Six Sigma was for manufacturing. “Lean” was Toyota’s technique for cutting flab from its manufacturing line. “Six Sigma” was Motorola’s. The combination has swept through corporate America. GE swears by it. So does Samsung.
If the words “Six Sigma” bring flashbacks of high school statistics, you’re on the right track. Lean Six Sigma is heavily math-based; it’s all about splitting up processes, scrutinizing each cost, crunching the numbers and then finding ways to streamline.
“Government is very good at adding extra pieces,” Steele says. “You added one, but can we take these other three off?”
Steele works with city departments and, using Lean Six Sigma statistical wizardry, identifies processes that are too slow, too expensive or too error-ridden. Then he talks with the employees on the ground — the ones actually laying the pipe or filling out the forms — to find solutions.
By using this strategy, the city of Spokane has already whittled down its minor contract time approval time from 29 days to only 10.
Some things, like employee morale, defy quantitative analysis. For those, Steele uses surveys, ranking systems and personal conversations.
“You’re also looking for those things that drive employees crazy,” Steele says. Getting rid of those extra layers of bureaucracy — think the TPS reports from Office Space — save money, save time and improve morale. If done right, it’s a win, win, win.
Indeed, for the process to succeed, there has to be employee buy-in. There’s still some skepticism, though. “So far, most of the employees, they are waiting for more information,” Steele says. “They’re a little bit gun-shy.”
The Prototype
For those skeptical that Lean Six Sigma can work for city government, advocates love to point to Fort Wayne, Indiana.
When Graham Richard became Fort Wayne’s mayor in 2000, the city was wary of this “Six Sigma” thing he kept talking about. But soon he was the toast of national efficiency experts, an author of a book on the subject and featured in US Mayor magazine.
Over the past decade, 300 Fort Wayne employees were given Lean Six Sigma training.
“We saw savings of over $10 million specifically attributed to the Lean Six Sigma processes,” former Fort Wayne finance director Ryan Chasey says. “Keep in mind that our Six Sigma efforts were not fully geared toward cost-saving, they were also geared toward service improvement.”
In a figure that may send Spokanite hearts a-flutter, Fort Wayne decreased the time it took to fill a pothole from two days to three hours. And all this, Chasey says, without laying off a single person.
In Spokane, City Administrator Ted Danek says, Lean Six Sigma has already borne results. Danek says the city has saved $30,000 so far.
By scrutinizing the regional solid waste site system, they found that the city could save thousands of dollars by simply rejiggering the site’s security. And by selling excess refrigerant the city could make $2,000 a year.
Danek expects more savings to follow quickly: “Call me back in about four weeks,” he says. “We’ve got a huge big-dollar item that’s in the final phases.”
The Skeptics
Not everyone is as confident Lean Six Sigma can succeed. Former City Council candidate Donna McKereghan worries Spokane can’t imitate the Fort Wayne experience because, among other reasons, we don’t have a Graham Richard.
“He brought the vision, and the experience, and the passion,” McKereghan says.
But Graham Richard doesn’t accept that analysis.
“Bloom where you are,” Richard says. “Leadership can come from the civic side, from a small business group, or the city council.”
Others question whether the city, with an expected a $7 million budget shortfall, should be creating a new $94,600 job. To help pay for the new job, the city eliminated an empty traffic technician position. The remaining $45,000 will be paid from utility department budgets. Ideally, Steele will save those departments enough money to afford him.
Danek says Steele’s job requires the sort of clout that comes with a large paycheck.
“Here’s the deal, it’s a senior-level position,” Danek says. “You have a whole new system in place where folks like Dave Steele are going to have to interact with the senior executives. The person leading that should be a senior executive as well.”
Steele’s salary is not unusual for a city employee. It’s only $5,470.56 more than Steele’s salary as real estate director. It’s on the same salary bracket as the deputy director of human resources.
But it’s also a far higher salary than similar positions in Fort Wayne. By comparison, the salary for Fort Wayne’s “Quality Enhancement Manager” was only $48,516. And after 2005, after only five years, the Quality Enhancement Manager position ceased to exist. Instead, its duties were spread throughout other members of the administration.
One way Fort Wayne kept costs low, Richard says, was by creating task forces made up of volunteers from private local companies that used Six Sigma, instead of hiring outside consultants.
Richard praises Lean Six Sigma, but cautions against seeing it as a panacea, as opposed to what is: a tool. “It’s like saying, gee, everyone should use a hammer or a saw,” Richard says. “It’s important not to focus on the tools, but what is the outcome we want.” The city’s strategic plan — the destination — is more important than how you get there, he suggests.
For some processes, he says, using Six Sigma process is too slow, too in-depth, and too intensive to be efficient.
Meanwhile, Fort Wayne aerospace scientist Jeff Pruitt, who also blogs at fortwaynepolitics.com, says Spokane’s program should have more accountability than Fort Wayne’s.
“I see [Lean Six Sigma] as a path to give money to more consultants to waste taxpayer money,” Pruitt says “There needs to be some up-front outline of what the program intends to accomplish.”
True to his Lean Six Sigma training, Steele says the best way measure the success — or failure — of the Spokane’s new program is, well, to actually measure it.
“I think the only way you can truly show the results is to be able to quantify it,” Steele says. “I want to see one project a month come out of the ELI center that has a positive impact. … I think I will be able to identify exactly what we’ve done.”
- Login or register to post comments
- Printer-friendly version
- Send to friend












Mr Steel wasn't involved in the Minor Contracts Team
Initially I wasn't going to respond to this article but after several calls from the REAL team members, I decided that I needed to help folks see the work that this team did to save the City time, money and reduce errors; and to clear up a few misconceptions of my own. I am the consultant that facilitated the Minor Contracts team, and I did the City's initial Lean training to start their Lean improvements.
The Team members won't respond because they are afraid - saying to me and I quote "It angers me that people are forced to remain silent because they fear for their jobs, or their reputation" and "the public deserves the truth and the team deserves the respect". Yes they do.
The team had a specific goal: Create a system that eliminates delays in the Minor Contract Process by reducing the number of times a minor contract was handled. Develop, Implement and fine tune it. (A minor contract is any contract under $46,300 - those above go up to City Council.)
They did this and a lot more. A contract had to be written for anything and everything- by the Attorney, and signed by the City administrator. When was the last time you hired your attorney to write a contract for everything you bought and had the Company President sign it? They did because the rules made them. (This includes some under $100! and 60% were under $3000) "Merlin" commented that the City shouldn't be run like a business - but he still wants good practices doesn't he? In this Lean team event, The Team's Attorney developed standard fill-in-the-blank templates that the department can now use, eliminating paper, time, and the Attorney's requirement to write them one-by-one. These were put on the internal web, for the initiator to fill in themselves, (eliminated rework, redundancies, errors) and they can email these to the vendor for signature (save paper, time and postage costs). The City's signing authority was given to the department heads to sign that the contract is needed, for anything under $10,000. (City Administrator - use to have to sign 100%. This reduced his reading and signing by nearly 2/3. ) The team found that the law allowed under $3000 can be a simple purchase order, and the contract wasn't even needed- so they changed that ruling (with Mayor's approval). This reduced the Legal department's workload by 1/3. They wrote instructions, and did training- reducing errors and time. The time before to get a contract was 6 weeks, now down to 10 days; reduced the number of reviews by 50% - and eliminated the 11 spreadsheets that folks had to maintained to see where it went and who had it next, they reduced process delays by 90%, Increase accuracy by 95-100%, reduce total time spent in the process over all by eliminating steps, reviews and rework, which increased the time employees can devote to other mission-critical work and many other things - and it helped morale. And they did all of this improvement work in just 4 days! That is a Lean Team. (Yes it was Lean - a Kaizen event is Lean).
As for the other side to this: The article said regarding Steele's job -“His job is to do what high-priced outside consultant couldn’t: cut costs and eliminate inefficiencies, while actually improving employee morale.â€
If you look at what it cost the City for MY work with them - they could do 13 similar events a year for the same price. Was it paid back in what they will save? Yes, and quickly. I am not saying that the City shouldn't manage their improvement efforts, they should. It is your money and they are working to improve their services. I wish them well.
Can He Fix It
See my comment at www.fortwaynepolitics.com under "Spokane To Imitate Fort Wayne's Six Sigma 'Success'" john b. kalb
Minor Contract Was a Kaizen Event, Not Six Sigma!
I believe Daniel Walters was not given complete or accurate information regarding the "Minor Contract" process. This was not Six Sigma, nor was it "Lean" Six Sigma, rather a Kaizen Event whereas after an in-depth data gathering process by a designated team leader, a group of eight employees spent four days locked in a room analyzing the facts and worked toward a "Leaner" process. Not only was the event overwhelmingly successful, it did not require Black Belts, Green Belts, or belts of any color, simply employees with a strong desire to improve an ineffective and outdated system. Plus, the cost was next to nothing compared to Six Sigma.
J. Skog
Did Six Sigma have anything to do with Minor Contract Process
Interesting, J. Skog.
I definitely had the impression, from talking to both Ted Danek and Dave Steele, that Lean Six Sigma was at least a catalyst to examining the minor contract process. The strategy and philosophy employed with the minor contract examination, from what I gather, is similar to the strategy Steele hopes to employ with the Employee Led Innovation initiative.
Jonathan Brunt from the Spokesman paraphrases Danek as saying much the same thing:
"Danek said Six Sigma has already made the city more efficient, leading the city to streamline its approval process for contracts that don’t require City Council support from an average of 29 days to 10 days."
I'll give them a call to find out how much of a role Lean Six Sigma had, if at all, in reforming the minor contract process.
Thanks for letting me know.
Daniel, from my limited
Daniel, from my limited knowledge, there are similarities between the two, but it was my understanding the Lean (Kaizen Event) for Minor Contracts preceeded any Six Sigma project -- however, I could be wrong. And Mr. Danek and Steele are correct in that the Minor Contract process did indeed make the city more efficient. The point I was trying to stress is this process, (again, to my knowledge), wasn't Six Sigma.
Jskog
The Latest Thing
Over the decades, many attempts have been made to adapt management systems from manufacturing organizations to the operations of public bureaucracy. From Robert McNamara’s Planning, Programming, and Budgeting scheme in the Pentagon to Jimmy Carter’s Zero Base Budgeting, and a host of others, the results have been mixed at best. In fact, it has not been uncommon for such attempts to produce a variety of unintended consequences. With very wise public officials, such tools can yield a limited range of desirable outcomes. But what is normally overlooked is the difference between a manufacturing enterprise, where profit is the empirically defined bottom line, and public bureaucracy, where the politics of public opinion gets to make the final decision.
Six Sigma, for instance, defines failure to deliver what the customer wants as a “defect.†But what the public wants in a democratic society is commonly contradictory — fix the streets but lower my taxes, get better results in the public schools but don’t pay teachers for outstanding performance, remove the snow but don’t spend money on “excess†equipment that will sit idle during most winters. Even more, determining what the public wants or gauging its satisfaction requires a political process that is up to the task — one that is in touch with the shifting winds of public opinion and actually has the capacity to respond to it.
As for quantification, all quantitative expressions begin with a conceptual, word definition of what is to be counted and how to measure it— quantification is never value neutral. Too often, that boils down to selecting what is easy to define as countable, not necessarily what is important to the process being analyzed. Virtually anything can be expressed in numbers, but that hardly makes it more accurate or more reliable.
Seeking efficiencies in government is a laudable undertaking as long as we come to grips with the reality that government is not a business — and we really don't want it to be run like one.