'Cut the crap' and other lessons for new IT projects

NRC's knowledge management chief focused on goal rather than theories

Patricia Eng, a nuclear engineer by trade, was given the title of senior adviser for knowledge management at the Nuclear Regulatory Commission and charged with implementing a system to make technical expertise and personal experience readily available across the agency. She approached the task like an engineer, focusing on the goal rather than information technology systems.

It’s all about the destination, she said, not about making the journey in style.

“Don’t be seduced by the elegance of a given tool,” Eng said. She added that it's important to understand the process that needs to be done, decide what will work and make it simple enough that the new tool will become viral in the workplace.

She said she believes her lack of academic training in knowledge management has been an asset because the experts too often focus on the fluff of theory, paying more attention to the means than to the end.

“Cut the crap,” she said. “You just do it.”

NRC settled on the Tomoye collaboration and information management platform that enables the creation of communities of practice because it is simple to use and can do the job. It was not the only option available, but it met the agency’s needs with a minimum of complexity, linking easily to document management systems and databases and operating behind the firewall to minimize security concerns.

When you need to get from Point A to Point B, consider whether a bicycle can do the job as well as a Mercedes can, Eng advised. And don’t get drawn in by the theory of gurus.

“There are people out there who talk a lot about knowledge management but aren’t doing anything,” she said. “A lot of people will tell you in theory how to do things, but you’ll spend many moons doing nothing.”

A challenge of any IT project is ensuring that it has the backing of both top management, which must approve and fund it, and users. By focusing on the final product of a new system, you can create a business case that will satisfy management and field a tool that will be useful.

“If it works and it’s a good process, people are going to want it,” Eng said.

 

About the Author

William Jackson is freelance writer and the author of the CyberEye blog.

Reader Comments

Tue, Sep 7, 2010

Amen to what she stated! Just because M$ makes a new product does not mean it is necessary!

Mon, Sep 6, 2010 Kabbashi USA

I agree with the Eng that 'Just do it' is the proper way, but the crux of the issue is how? I wonder how KM program for such a critically sensitive area is offered to a person who have no background in KM. If you do not know the validated theory behind it, then stay away from it. The theory that backs KM initiatives is not 'crap' at all. You cannot establish a KM program with such arrogance.

Fri, Sep 3, 2010 Richard Ordowich Princeton

I agree with the style of "just do it" but then to assume that just because a tool becomes viral it achieves the goal is how most technologists approach problems. “We have a solution, a collaboration tool. “ Managing knowledge and knowledge transfer is a human activity and the culture and social environment must be considered in designing a solution. There is a balance between "fluff" and knowledge and awareness of knowledge management. Perhaps a more balanced approach of considering how knowledge is shared within the specific community, its value and benefits, form and function and then selecting the processes and tools is also an alternative. Assuming you have solved the problem because a tool has been selected is premature.

Please post your comments here. Comments are moderated, so they may not appear immediately after submitting. We will not post comments that we consider abusive or off-topic.

Please type the letters/numbers you see above