Today is about speed over perfec­tion. When I was a soft­ware devel­oper and designer, one of the concepts was agile devel­op­ment. Agile Development was essen­tially a para­digm shift between the old clunky soft­ware that was released on cds and more modern web based soft­ware. The differ­ence was that the tradi­tional soft­ware was distrib­uted by a phys­i­cal medium, so they had to figure out a way to do that in mass, so they would spend a whole year and create version one of the soft­ware. They would put all in the work and then they would put all of that ncds and then they would send it to the factory and there would be a huge distri­b­u­tion process. Then another year would go by and then the next version of the soft­ware, what would come out or maybe six months would go by and they would release an update with the intro­duc­tion of the Internet.

Updating soft­ware became a lot quicker and this idea of agile devel­op­ment came about, which essen­tially was let’s release a piece of soft­ware that does all of the essen­tial oils it needs to do and then after that’s released, add in the addi­tional features. For the next version, and so what would happen is they would release version one and it would just be the bare bones and they would get feed­back and they would get bug reports and feature requests and perhaps a month later they would release the next version so you would have a version two or perhaps a one point five. This would go on and on and on. So over the course of a year they were able to do, let’s say 12 updates versus the once a year update in the old cycle. This allowed customers to, uh, get bug fixes and feature requests in a lot quicker and most impor­tantly, it allowed the devel­oper to get feed­back and imple­ment that feed­back very rapidly.

Rather than spend­ing five months on a feature that nobody wanted or cared about, they could get feed­back from their customers and give them exactly what they wanted within a very short amount of time. You don’t have to be in the soft­ware busi­ness to use this concept. If you can get out a prod­uct that is pretty darn great in about a week versus two months for some­thing that you think is perfect, you’re going to be able to make money quicker. You’re going to be able to get feed­back from the market place a lot sooner and you’re going to be able to course correct and change and fix and adjust things to have a better prod­uct. Oftentimes, when we are striv­ing for perfec­tion, it’s our own image of what that is for us, and it does­n’t have any corre­la­tion to the success in the market­place.