ie8 fix
madison

Three tips for studying IT failure

By | November 14, 2011, 7:50am PST

Summary: The analysis of IT failures can yield great insight and help guide us toward success. Here is advice for anyone who wants to discuss failures in public.

Readers sometimes ask why this blog focuses on failure rather than success. It’s a great question with a simple answer: discussions about success tend toward pure public relations while detailed analysis of failure can teach us genuinely worthwhile and important lessons.

One should not study or discuss failure lightly or with disrespect. Although some situations described in this blog demonstrate outrageous waste and even abuse, many are dumb mistakes caused by well-meaning people. It is sometimes impossible for external observers to distinguish error from abuse, which is one important reason to shine the light of transparency with balanced and fair neutrality. Although sensationalism is an easy way to gain readership and attention, it devalues serious analysis.

For those interested in writing about failure, I suggest these guidelines:

1. Go with the facts. Evidence tells its own story and can sometimes take you down an uncomfortable road. Let the trail of evidence, rather than your personal preference, define the path.

2. Be fair and balanced. Stories about failure can affect those involved; for this reason, maintain an impartial and respectful attitude toward the people and companies you discuss.

3. Expect a backlash. If you write about failure, people will try to prove you wrong, so your facts must be correct and your analysis airtight; careful and accurate research is key to surviving the inevitable threats you will receive. On the other hand, when you are wrong (which is bound to happen, if you do this enough), admit it plainly and do whatever is needed to repair any damage.

The following video discusses some of these issues along with other topics related to studying IT failures. It was recorded during a recent interview appearance on The Pulse Network.

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Michael Krigsman is a recognized authority on the causes and prevention of IT failures.

Disclosure

Michael Krigsman

Michael Krigsman writes and speaks about technology in a manner that most observers consider to be fair and balanced. Michael believes that writing about IT failures, which often have complex causes, creates a unique obligation to be reasonable and accurate in both reporting and analysis.

Michael maintains active personal and professional relationships with enterprise technology buyers, vendors, analyst firms (or individual analysts), consultants, and system integrators. As CEO of Asuret, Michael sells and delivers paid services to members of these same groups.

Vendors regularly reimburse Michael's out-of-pocket travel expenses to attend industry conferences and events. Conference organizers frequently waive entry fees when Michael attends industry events. Michael often speaks at industry conferences and events.

He is a member of the Enterprise Irregulars, a loose association of consultants, investors, industry representatives, analysts, and users of enterprise software.

For daily updates on Michael's activities, follow him on Twitter.

Biography

Michael Krigsman

Michael Krigsman is CEO of Asuret, Inc., a consulting company dedicated to reducing technology implementation failures. Asuret's suite of software tools improve the success rate of enterprise software deployments by quantifying and measuring governance issues that cause most project failures. Michael led the research effort underlying Asuret's model of collective intelligence and its practical application to reducing IT failures in consulting environments. He is a recognized authority on the causes and prevention of IT failures and is frequently quoted in the press on IT project and related CIO issues. He is considered an enterprise software industry "influencer" and provides advice to technology buyers, vendors, and services firms.

Previously, Michael served as CEO of Cambridge Publications, which develops tools and processes for software implementations and related business practice automation projects. Michael has been involved with hundreds of software development projects, for companies ranging from small startups to Fortune 500 organizations. Michael graduated with an M.B.A. from Boston University and a B.A. from Bard College. He is a Board member of the America's Cup Hall of Fame and the Herreshoff Marine Museum in Bristol, RI.

Related Discussions on TechRepublic

Did you know you can take part in these discussions with your ZDNet membership?
2
Comments

Join the conversation!

Just In

RE: Three tips for studying IT failure
olddogv 5th Dec
We learn mostly from mistakes...fortunately, they do not always have to be our own.
0 Votes
+ -
I agree that your blog isn't the kind of sensationalist "entertainment" (read "troll-bait") that many other IT blogs seem to be, but I find it by far one of the most valuable.

Another good answer to "Why talk about implementation failures:" The same reason we talk about World War II, the Great Depression, Sexually transmitted diseases, child abuse, and thousands of other bad things in the world - because bad things can only be prevented when they are exposed and discussed, again and again.
0 Votes
+ -
We learn mostly from mistakes...fortunately, they do not always have to be our own.

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix
Click Here
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix
ie8 fix