Are You a Victim of Analysis Paralysis

Maybe it’s just the teams I’m helping but there seems to be a spate of analysis paralysis occurring in the IT world.  Of course if I was a media outlet I be calling it an breakout, nay an epidemic! No! A pandemic!! Run for the hills people we might all be infected!!!

If you are experiencing any of the following symptoms then see the guidelines below:

  • Analysis has taken more than a month already and shows no sign of ending anytime soon
  • The documentation you’ve written has fine grained details in a few areas and is completely lacking any information at all in others (especially the tricky bits)
  • Your analysis efforts are going around in circles
  • No one can decide what the “right” approach is to some of the problems

Steps for curing this disease:

  1. Stop analysing!! Right now!
  2. Write some code based on what you have done.
  3. When that code is working, go and analyse/design a little bit more.
  4. Go back to point 2

Good luck with the cure and I hope your health improves!

 

Reader Comments

Post a Comment



Welcome

As you might have guessed, this is a tech blog. I normally write about development and things that can help us do it better, specifically in the .NET space, and occasionally i'll throw in a post about whatever happens to be in my head at the time. Enjoy your visit!
And in case you were wondering, I'm a Principal Consultant for Readify, I run the Sydney Alt.Net group and I play a bit of LOTRO in my spare time (feel free to look me up)


 

My Open Source Projects

Labels

Blog Archive