On Sun, 2009-10-25 at 19:24 -0400, Elizabeth Schwartz wrote: > Esther phrases it very well, and this is a good example. Just saying > "oh, anybody smart goes with Cisco" isn't going to win any converts. > As professionals, we should be able to justify a bias with facts that > explain why a choice contributes to the organization's goals. What's > the MTBF, is there 24x7 technical support, do we know of satisfied > corporate customers at our level...
I am a bit late to this thread, but if you are asked to implement what you think is not the best solution (which I am sure most of have experienced), I find that it helps if you can be clear of the consequences of the decision. Many moons ago I was asked to migrate a smaller company to an Exchange infrastructure and, while it was not my recommendation, I was very clear with the CEO of what I would need (several layers of antivirus which actually cost more than Exchange) and I estimated downtime from virus events. Because I was able to clearly explain of the impact of his decision, we were probably the only IT team that was taken out to dinner when we only had 1.5 days of downtime during the course of a year instead of having unhappy management :). cheers, ski -- "When we try to pick out anything by itself, we find it connected to the entire universe" John Muir Chris "Ski" Kacoroski, [email protected], 206-501-9803 or ski98033 on most IM services _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
