Deciding not to decide

Last week, I came face-to-face with indecision while I was working on a project for LegUp Benefits. We have two beta customers and we need to build out the software platform to replace the minimum viable product (MVP) we’ve cobbled together.

Long story short, I needed to decide which tools to build the software with. My goal was to make this decision in a few days so I could build version one before our baby arrives later this month.

After spending several days researching my options, I was unable to make a decision. So, I decided not to decide. This was uncomfortable for me. When I think about what makes a great leader, one characteristic that comes to mind is decisiveness. Decisiveness is the ability to make quick and effective decisions. 

After reflecting, I now realize that sometimes deciding not to decide is the right decision. Decisiveness doesn’t always require you to make a decision to act. It can also mean choosing to delay. What you want to avoid is the infinite deliberation that exists between these two choices. That’s no man’s land.

How do you know if deciding not to decide is the right decision? In my case, there were two reasons I felt it was appropriate to delay.

First, I didn’t lose anything by waiting. There are few-to-no consequences for me in delaying this decision. Our existing MVP is good enough for a few more months.

Second, I gained something by waiting. By delaying this decision to a later date, I’ll be able to dedicate more time to the project. This will allow me to gather the information required to make a more informed decision and increase my chances of success. I will pick this project up when I return from paternity and be in a better position to give it the time and focus it requires.

If you’re facing indecision, consider deciding not to decide.