Hi Pat, I did a pretty good Team management course last November that briefly dealt with selling to your employees The main mistake people make is trying to say "hey lets do this, this way is better" As the audience will simply think "what's the use it works fine as it is" A solution is only a solution when there is a problem that needs fixing.
The key is to stop selling the solution and start selling a problem. 1 day just jump out of your chair at work, crash to floor and start screaming "its all over!, its all over now!!, this can all only be saved 1 way!!" Ok…. that's a little melodramatic just express to your team how everything will eventually be FUBAR unless action (express only simple action is needed) is taken now. If along those lines don't do the trick your stuffed lol. M@ ---------------------------------------------------------------------- >"Hi Everyone Is it me Or is there something wrong about this idea. Im having a hard time convincing my team about the benifits of modularising code, particularly the use of <cfinclude> Their main argument is that if its all in one file you can see whats going on, and they all seem to have their resolutions turned up to riduiculous levels so they can see more code on the screen. And they all seem to have a problem with going through lots of levels files to find the code they need to maintain. To me this makes absolutely no sense..."
