On 7/28/07, Tracy R Reed <[EMAIL PROTECTED]> wrote: > Very well put. Learning something new is hard for most people. I see it > every day at work. Most of my coworkers who are more familiar with > Windows are happy to let a big project depend on Windows. I have to step > in with my input to convince them otherwise and sometimes it is quite > difficult. People go with what they are already familiar with and fight > to do so.
I'm working help desk in a large company, and it's an all Microsoft shop. And I mean, if there's a Microsoft product that does what we want, that's what we get. The way it seems to happen is that someone decides we need to implement some process or handle some thing better or gain some functionality. So the assumption is always: 1) Get some piece of software, so 2) what are we going to buy? I'd like to see the process go more like: 1) What are we trying to accomplish? 2) What do we need people to do to accomplish that? 3) What mix of software and process will accomplish that? i.e., there doesn't have to be The One Product that will do the job. -todd -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
