Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Where is the dividing line between complete lack of planning and analysis paralysis?

In my very short time working in the programming field, I've seen two extremes:

  • Projects where little to no planning was done and thus become maintenence nightmares.
  • Projects that are perpetually in the planning stages and don't move from there.

It seems like the latter oftentimes happen as a reaction to the former. Where is the happy medium? And more importantly, if a project is moving in one of these directions, what is the best way to move it towards said happy medium?

like image 289
Jason Baker Avatar asked Mar 18 '09 23:03

Jason Baker


People also ask

Where does analysis paralysis come from?

Analysis paralysis occurs when overanalysis or overthinking of alternatives prevents an individual or a group from making a decision. In investing, analysis paralysis can lead to missed opportunities. Psychologists say the root cause of analysis paralysis is anxiety. We fear choosing the wrong option.

What is analysis paralysis in decision-making?

Analysis paralysis (or paralysis by analysis) describes an individual or group process where overanalyzing or overthinking a situation can cause forward motion or decision-making to become "paralyzed", meaning that no solution or course of action is decided upon within a natural time frame.

What is the opposite of paralysis by analysis?

The opposite pattern to analysis paralysis would be the one defined by the term satisficing, that suggests choosing the first option that you have evaluated as reasonable enough. Actually, this is the standard pattern—human beings tend to optimize the decision-making process by following this pattern.


1 Answers

In my own personal experience, I have found that 'decisions' are my bottle neck.

If this is the case, then :

  1. List all your design options
  2. Pick an option(s) (pick a few if you can't decide on one)
  3. List the risks of the best option(s)
  4. For each risk, brainstorm a solution, then design a conclusive proof of concept and write it.
  5. If your proof of concepts proves it will NOT work, then toss that option, and pick another one.

A 'Proof Of Concept' is a minimal app to prove something. (mine are usually 1-6hrs)

If you have a situation where 2 or more options are equal, give yourself a time limit (like 5 minutes, not 2 months) and make a decision ... any decision, and don't look back.

And trust yourself to be able to deal with any problems you will hit which you did not take into account at design time.

like image 120
John MacIntyre Avatar answered Oct 12 '22 22:10

John MacIntyre