Before I presented at DevLearn I posted the objections in my presentation to a forum and to try to get some new perspectives. Just today someone added a list he uses. They are particularly true and I swear I have heard them all. Thought you might enjoy them…
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 ?
