Comments
Reading This Column Will Cost You 0.4 Micromort
Newest First  |  Oldest First  |  Threaded View
JasmineMcTigue
50%
50%
JasmineMcTigue,
User Rank: Strategist
2/14/2013 | 7:10:37 PM
re: Reading This Column Will Cost You 0.4 Micromort
You've spoken at length about the assumptions we make and the weaknesses in our own cognitive processes that lead to bad business decisions. But what's the take away here? In your example about enterprise software, you were able to achieve a business consensus by using metrics to substantiate a case. But often, despite our best efforts toward objective analysis, the real issue is goal alignment with regards to business stakeholders. Even by doing our best to make an objective, timely, and well informed analysis free of blindspots, consensus is not always so easy to achieve. The cognexus institute has a great paper on this: http://cognexus.org/wpf/wicked...

Nonetheless, your column serves to highlight the difficult challenges and endemic dangers of the modern IT landscape.

Excellent read.

Jasmine McTigue
IW Contributor
Andrew Hornback
50%
50%
Andrew Hornback,
User Rank: Apprentice
1/8/2013 | 12:55:24 AM
re: Reading This Column Will Cost You 0.4 Micromort
Try having your only documentation in source code... in a foreign language. I still have the occasional nightmare about that. Sprichst du Deutsch? Keine... en Kode.
moarsauce123
50%
50%
moarsauce123,
User Rank: Ninja
1/7/2013 | 11:57:38 PM
re: Reading This Column Will Cost You 0.4 Micromort
I agree, but this is contrary to common Agile belief where absolutely nothing gets documented because the Agile gurus insist that source code is enough documentation. Good luck wading through 100,000 lines of code when people yell at you when the system comes back up!
Andrew Hornback
50%
50%
Andrew Hornback,
User Rank: Apprentice
1/7/2013 | 3:33:48 AM
re: Reading This Column Will Cost You 0.4 Micromort
There's one Worst Practice that I would add... Biological-based Documentation. If all of the information used to build an infrastructure or maintain and operate it is locked up in the brain cells of a limited number of team members (some of whom have departed the organization), a low-impact issue with one system could cause systemic failures in the infrastructure. If it isn't documented when it's done - it's lost.

Andrew Hornback
InformationWeek Contributor


Register for InformationWeek Newsletters
White Papers
Current Issue
InformationWeek Tech Digest, Dec. 9, 2014
Apps will make or break the tablet as a work device, but don't shortchange critical factors related to hardware, security, peripherals, and integration.
Video
Slideshows
Twitter Feed
InformationWeek Radio
Archived InformationWeek Radio
Join us for a roundup of the top stories on InformationWeek.com for the week of December 14, 2014. Be here for the show and for the incredible Friday Afternoon Conversation that runs beside the program.
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.