Kevin,Great list and great questions.

Some thoughts:

> 2. This is disruptive!  Our culture will never suppor it.

If you don't set it up so that there are incentives for the employees to support it, they won't. Remember when Lotus notes boards was going to 'replace email?' When video conferencing was going to 'replace travel'?  That only happens when people see the clear value and are given incentives to support the disruptive technology.

Is there a group that is especially collaborative in the organization? Maybe they're an early adopter group.

>9.

Great questions Kevin.  Mind if I borrow them when I speak to admins taking Clearspace training? 

Here are a few answers, some taken from internal discussions we've had at Jive about these same issues:

Correct it... together  

How about providing some quick videos they can watch, or making some elearning materials available for quick reference?

Also, if the tool you're using is intuitive and consistent, that helps a lot along the way (ie. learn how to blog and you'll automatically know 95% of how to author a document or start a discussion)

Also, have some of the younger/more technically savvy employees reach out to the tech-fearful employees who know the business and ask them to be mentors.  The mentors have the industry expertise and the mentees can use the tool to document their learning, which will eventually drive the less-tech-savy folks back to the tool (and as a mentor, it's a lot easier to ask for help when you've had the chance to help someone out in another area in which you're a pro!)

Good points, and I know I was generalizing a bit there on my last post.

That being said, age differences aside, the more process-oriented a job may be, or that an employee's personality may be, the harder it will be to get them to use a different tool.  It doesn't work to just hold up a shiny new toy.  You have to define and train on how the new tools will allow them to perform specific job functions.

And when rules are broken or privileges taken advantage of, then the specific offenders need to be dealt with individually, instead of putting the brakes on the entire program.

I had that happen a while back at a large company here in Portland, where they caught a few contractors surfing the web one weekend when they were supposed to be working overtime (not me of course ).  Instead of dealing with just those contractors, they made a company-wide, yes company-wide, decision to not allow web surfing at all, any longer.

This reminded me of a list I have used in the past to try to overcome non-specific objections to initiatives \ change.

120 Ways to Deter Innovation

Which ones do you use?

             1.   The savings are only peanuts.
             2.   That's beyond our responsibilities.
             3.   That's Joe's job, not mine!
             4.   Not enough help.
             5.   It's against company policy.
             6.   We don't have the authority.
             7.   Have you gone through proper channels ?
             8.   Lets get back to reality.
             9.   Can't teach an old dog new tricks.
             10.  Good thought, but impractical.
             11.  Let's think about it some more.
             12.  Management would never go for that.
             13.  The client won't like it.
             14.  They won't hold still for that.
             15.  Let's put it in writing.
             16.  We'll be the laughing stock.
             17.  Not that again!
             18.  Weld lose money in the long run.
             19.  We did all right without it.
             20.  Where' d you dig that one up.
             21.  It's never been tried.
             22.  Let someone else try it first.
             23.  That's been tried before.
             24.  What's the use?
             25.  Not enough time.
             26.  Too hard to sell.
             27.  I don't see the connection.
             28.  It's not practical.
             29.  What you are really saying is . .
             30.  It leaves me cold.
             31.  It won't stand up.
             32.  Let's all sleep on it.
             33.  You're right, but . . .
             34.  I'm not convinced.
             35.  We've tried that before.
             36.  We've always done it this way.
             37.  It won't work.
             38.  We can't pay for the tools.
             39.  It costs too much.
             40.  If I thought it'd work, I'd have used it.
             41.  It's not in the budget.
             42.  Where will the money come from?
             43.  You can't do that!
             44.  You should know better.
             45.  We're not ready for that.
             46.  This isn't the right time for it.
             47.  We're not considering hardware yet.
             48.  Everybody does it this way.
             49.  Too academic.
             50.  Not timely.
             51.  It's a gimmick.
             52.  It isn't progressive.
             53.  Not for us.
             54.  Too hard to administer.
             55.  No good!
             56.  Plain stupid.
             57.  Screwy.
             58.  Too radical.
             59.  Too complicated.
             60.  The idea is unsound.
             61.  It isn't feasible.
             62.  Too difficult.
             63.  Impossible!
             64.  Production won't accept it.
             65.  We can't hold up production for that
             66.  Engineering won't approve it.
             67.  My Boss won't like it.
             68.  I can't see it.
             69.  Too much trouble to get started.
             70.  So what?  We're making a profit!
             71.  We don't have the manpower.
             72.  We haven't time for detail.
             73.  The design is frozen.
             74.  Schedule won't allow any plans.
             75.  Who is going to do it?
             76.  Takes too much time.
             77.  We don't do it that way here.
             78.  Our product is different.
             79.  Too much work.
             80.  It won't apply to our problem.
             81.  Don't move too fast.
             82.  It will set a precedent.
             83.  Not enough background.
             84.  Why can't we do it another way ?
             85.  We've got something just as good now.
             86.  Don't be ridiculous.
             87.  We know all this . . .
             88.  I'm too busy to decide now.
             89.  We haven't enough facts.
             90.  What about the directive?
             91.  That will take two years to test.
             92.  It will make present equipment obsolete.
             93.  It's not permitted by specifications.
             94.  It's not according to standard changes.
             95.  We'll come back to it later.
             96.  Let's form a committee.
             97.  Cost doesn't matter.
             98.  Why change it - it works.
             99.  We can't help it - it's policy.
            100.  Forget cost - just get it out.
            101.  The way we're doing it is best.
            102.  Why?
            103.  Runs up our overhead.
            104.  That's too "ivory tower."
            105.  What do our competitors do?
            106.  What can we expect from the staff?
            107.  Has anyone else ever tried it ?
            108.  It won't work in our industry.
            109.  It won't work in my department.
            110.  No, no, no.
            111.  Too theoretical.
            112.  Personnel aren't ready for this.
            113.  The users won't go for it.
            114.  Its new.
            115.  We have too many projects now.
            116.  We don't want to do this now.
            117.  It's not standard stock.
            118.  We don't have enough volume.
            119.  Let's shelve it for the time being.
            120.  Could a vendor supply this for less ?