Some general considerations for small systems change

TalkBack 1 of 19:

Next »

• Thread View
• Flat View

IOW you need an architect

NOT a CIO or management drone. NOT a vendor rep. NOT your average sysadmin. NOT the customer/user. Not from one group while ignoring another.

Of course, this never happens. There usually IS an architect, but he is brought in AFTER the major decision is made (and is mostly ignored after that). The architect ends up as a glorified Project Manager - watching the project unfold instead of designing what the project is.

Ford stands as a "great" example of how to do everything wrong. I am unaware of any major purchasing decision that WASN'T made by a single management person (without consult). Usually a nice weekend in Armonk was enough . . . The Architect group was poisoned with political apparatchik appointees - since the position included a promotion. I remember architects coming to me to get my opinion - but my position as messenger precluded any chance I had to get that promotion. Sour grapes? Nah, not really. Who wanted to go to a group of IT invalids and do ALL of their work for them?

BTW General Dynamics was no better.

Posted by: Roger Ramjet   Posted on: 03/03/09  (Edited: 03/03/2009 @ 05:54) You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Five Steps to Determine When to Virtualize YourServers VMware Server virtualization isn't just for big companies. Entry-level ... Download Now
• Why Isn't Server Virtualization Saving Us More? A Few Small Changes May Dramatically Increase Your Efficiency VMware Companies have rapidly adopted server virtualization over the past few ... Download Now
• Three Steps You Need to Know to Stop Data Loss Varonis Sensitive data exposed to misuse or loss... it is the stuff of nightmares ... Download Now