Many of us are faced with choices and decisions constantly in our jobs. How do we approach a problem? What should we do as a team to get the work done? How do we code or manage or test or do something else with a database?

Maybe more importantly, how long do we spend deciding?

I have seen teams spend way too long (in my opinion) debating options and examining possibilities. I've seen them take days or weeks arguing and considering edge cases and move slowly. It seems there is no shortage of reasons why something isn't done. It can drive me a little crazy.

I was listening to a podcast recently and heard about this technique, which I love.

Get a whiteboard that everyone can see (physical or virtual). One person is designated to write down all the discussion items about the issue. Each person can make an argument for or against an idea for the solution, and nobody can stop that argument from being added. However, nobody can remove anybody else's argument, and nobody can repeat an argument that is on the board.

This can shorten discussions because people can't repeat things. I've seen far too many debates (arguments) continue in a circle because people keep repeating things or circling back. When no one has anything new, we just take a vote and move on.

I am a big fan of getting things done. Even if we don't have the best, or optimum, or more efficient solution, we need to get moving. Perfect is the enemy of good enough, and far too often, I find technical people chasing perfection, or near perfection, at the expense of moving forward.

Timebox decisions and get moving. It's how you accomplish more, and it's what your employer wants.