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

It’s About Defining Business Needs

Consumed => “Business Cases Aren’t A Waste of Time” by Bart Perkins on ComputerWorld.com.

http://www.computerworld.com/s/article/351008/Business_Cases_Aren_t_a_Waste_of_Time

Left a comment:

Should IT get involved sooner rather than later? Absolutely. Even during initial high level discussions IT could help to analyze, define, prune and shape basic direction.

Most importantly, IT should there to consult and insist that the project focuses on business needs. Not wants. Not “what would be cool is…” But actual business needs! The closer the project (and IT’s involvement) starts relative to the needs’ target, the more likely the completed project is to… now get this… meet business needs.

Too often it seems, on projects both big and small, systems and sites are developed reactively based on user wants. Ultimately, that results in a lot of unnecessary work nailing down functionality that doesn’t serve the business. The  system/site  disappoints and requires still more budget and resources to be “fixed”.

Call it a business case. Call it where ever you want. But any deviation from business needs is an opportunity for the user to say, “It’s IT’s fault…” and “IT doesn’t understand the business…”. Or are you expecting the client will  say, “It’s our fault. We spoke too much about wants and not enough about needs”?

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