“Maximizing” means expending time and effort to Ensure you’ve solved something as best as possible.  It requires exploration and analysis to ensure “the best” option hasn’t been overlooked, and that we have confidence in our evaluation of all options.

“Satisficing” means picking the first option that satisfies the requirements. Prefer a faster decision to the best decision. It means not getting paralyzed by the pursuit of “perfect,” but it often doesn’t result in the very best solution.

People naturally tend to be Maximizers or Satisficers, although it depends on the subject.  For example, you might maximize your career, but satisfice your physical exercise.

A recent study showed something interesting: Maximizers make better choices, but Satisficers enjoy their choices more, and spend less time and create less stress in making the choice.

In software and startups we can choose when to Maximize, and when to Satisfice. It might seem like Maximizing is best, especially when you have teams of smart people who can do the maximizing. But not necessarily. 

Speed is one of the greatest competitive advantages, partially explaining why small up-starts are able to beat large incumbents. But speed requires satisficing, not maximizing. Strength in startups comes from shipping, with benefits accruing today instead of theoretical benefits in future, using customer reaction and real data to decide your next move, rather than planning many moves ahead.

Still, maximizing is best for some decisions.  Your Product & Business Strategy is rightly a slow obsession, best when taken from many angles, pounding it with devil’s advocacy, questioning every assumption, “sleeping on it” repeatedly, repeating pieces of it to customers, strangers, anyone who might have a useful reaction.  Strategy isn’t something you want to change often, with entire teams and careers to be built on top of it, so maximization is best.

For the most important decisions, Maximizing is wise. For almost anything else, Satisficing is likely wiser.