"And part of that is having every employee be the customer and utilize our services wherever you can, and if you see a problem, highlight it and tell people to get it fixed. And that’s something we do a lot."<p>If it really worked, that'd be great. Instead of yelling at people who don't use the tools and programs, I'd suggest a review of those tools and processes, and a public rundown of the findings and improvements to those services. If people are spotting problems, reporting those to be fixed, and <i>nothing gets done</i>, or perhaps they're told to go pound sand, people will quit reporting problems. That very well may be the case (I've seen it happen at companies), and the CEO/President needs to get in to that part of the company and root out if in fact there is a problem in that part of operations.<p>If there is a problem, fix <i>that</i> and promote it. If there is no problem, they need to do a better job of promoting the case studies of things that were reported/fixed/improved. This will send a bigger message than public berating for not using stuff that may be broken. Those workers still have jobs to do, and if using the PP tools doesn't get the job done, and they're now expected to do bug reports as well as use broken/poor tools, you've just made everyone's job a lot worse.