Dear Bob ...
We're in the middle of a major systems replacement initiative -- we're replacing a homegrown system with a commercial application suite.
[ Find out what tips Bob Lewis offers for another tough workplace situation in his blog post, "When you've set the pattern with an employee, you have to be tough to change it" | Get sage advice on IT careers and management from Bob Lewis in InfoWorld's Advice Line newsletter. ]
Like a lot of companies, we brought in a systems integrator that has a lot of experience with the software we're putting in. Part of their sales pitch was that they work in "mixed teams" of consultants and employees so that our staff have a chance to gain expertise in the new system and in the integrator's implementation methodology.
We definitely want this to happen. And yet I'm becoming uncomfortable, because many of the employees we've assigned to these teams are becoming "methodogical purists." There are times I don't want us to follow the integrator's methodology exactly -- in particular, in situations where it insists on levels of information-gathering and mind-numbingly cumbersome analysis that would result in major cost increases compared to shortcuts that might not be quite as consensus-building, but would get the job done at a fraction of the cost.
I don't want my employees to stop learning. I just don't want them to forget what they already know.
Or am I off-base, and refusing to learn new techniques myself?
- Abandoned parent
Dear Abandoned ...
Something Michael Shermer of Skeptic magazine once said comes to mind: "The rub ... is finding that balance between being open-minded enough to accept radical new ideas but not so open-minded that your brains fall out."
The other notion that comes to mind is the Stockholm Syndrome -- the psychological effect in which hostages start to identify and empathize with their captors.
There's no simple answer here because what you're trying for is balance, moderation, and judgment, not the right answer instead of the wrong one.
That means there aren't any clear lines separating the behavior and attitudes you want from the ones you want to discourage.
The only solution I know of requires a significant investment in your time, the employees' direct manager's time if that isn't you, or both.
Start by clarifying levels of authority -- specifically, what sorts of decisions you've fully delegated to the integrator so that the project teams have authority to decide, and what sorts require your approval, where the project teams are to recommend. This provides a framework for you to involve yourself in the key decisions.