Chief Alchemist - Business Consulting For The 21st Century Via A Holistic & Intelligent Approach
Share ChiefAlchemist.com. RSS 2.0 feed for ChiefAlchemist.com. Sign up for the mailing list. Follow Chief Alchemist on Twitter. 'Like' the Chief Alchemist's page on Facebook. See what Chief Alchemist has been Q&A'ing on Quora. Chief Alchemist bookmarks & highlights on Diigo.com. Follow the Chief Alchemist on Digg.com. Chief Alchemist channel on Last.fm. Chief Alchemist on Flickr. Mark 'Chief Alchemist' Simchock on LinkedIn. Free Initial Consultation. Email Chief Alchemist. Phone Chief Alchemist.
  • Mark ‘Chief Alchemist’ Simchock
  • 'Email me.Email => ca .at. ChiefAlchemist .dot. com
  • 'Phone me.Alchemy United => 732 997-0028
  •  
  • Free initial consultation.Free => Initial Consultation
  • Please be sure to subscribe to your communication channels of choice.
  • Click To Close => The small green (consultation), red (email) or blue (phone) icons in the top upper right.
CURRENT “TOP 10” TOPICS TOOLS CLIENTS & PROJECTS SOURCES SEARCH HIDE
Business Consulting For The 21st Century Via A Holistic & Intelligent Approach

By definition a servant who says no is no servant at all

Consumed => “How to Keep Cloud Projects Agile, Simple” by David Taber on CIO.

http://www.cio.com/article/707583/How_to_Keep_Cloud_Projects_Agile_Simple

=> My value add (i.e., left a comment)…

“IT engineering exists to serve the business, not order it around. All those statements are true…”

Actually, I’m not so sure that’s true – or at least should be true. In the second decade of the 21st century IT should be working *with* the business as an equal partner, not for it. IT continues to undermine itself when it takes the (subservient) position of “service provider”. By definition a servant who says no is no servant at all.

The reality is, this is a (simple?) branding issue. That is, if IT wants to say no then the first step to pulling that off is to stop being the servant and start being the equal partner.

I’m not disputing the value of the advice given. I’m simply pointing out that it’s reactive and traditional; nor does it solve the root of the problem. That problem being the perception of IT’s roles and responsibilities relative to the ongoing success of the business.

Required.
Will not be published. Required.
Please include http://