Editor's Note: Aaron Smith joins us once again, this time explaining how you can take advantage of free or low cost software tools\u00a0-- IF you have reasonable expectations about them. That's where\u00a0the 90% rule comes in. By Aaron Smith I have seen it happen so many times throughout my career. I'm looking for a piece of software or an online service that solves a business problem. I know it's out there, and when I find it I bring it to the decision makers for review. They look at it closely, get excited about the features and possibilities, and then start asking questions. Invariably we get to a point where the managers start envisioning different aspects of the process, or brainstorming different ways it could be used. And then someone asks "Can you view the data in a standard deviation chart and compare it to the three data sets I created last week in Excel?" That's when my contented smile disappears as I answer "Well, no, but ...."\u00a0 and the whole room sighs collectively. All of a sudden my fantastic tool that was going to revolutionize how we work is out the window. What happened here? Someone decided they needed the "Perfect Tool." This is a common problem for businesses trying to adapt to changing technology. For decades, we have been building business tools to address very specific business needs. In the 80's and 90's that meant in-house development of specialized applications, defined by traditional software development guidelines and practices. What this has created is a generation of managers who are used to getting exactly what they want when they define a system requirement. It has narrowed the vision of managers everywhere as they will only accept solutions that completely address every aspect of the business. Unfortunately, unless you have a large budget to pour into development, that will never happen. The 90% Rule says "If you find a tool that can achieve 90% of the functionality of your 'Perfect Tool', you're 90% of the way to finding a solution." All too often, managers try to find tools that solve 100% of the problem, something that is often unachievable. Here are a couple of the traps that can lead to this thinking .... "That's not what we call it." You call them bugs instead of tickets, or tickets instead of tasks, or deadlines instead of milestones ... so what? It might take a week or two, but a lot of times it's easier to change the words you use to describe how you work, than to reprogram an entire application to match your existing terminology, and most of the time that's not even an option. Just because a tool refers to various aspects of your business differently than you're accustomed to doesn't mean you can't benefit from using it. People are pretty good about adjusting to these kinds of changes (that's why people make better translators than computers). "This won't work for us. Our business is unique." Not to rain on your parade, but when it comes down to it, your business isn't really that different. You offer a product or service, you deal with clients or customers, you charge a fee and create invoices, you pay bills and rent, etc. A lot of businesses sell their 'process' as what sets them apart, but that doesn't have to change just because they change that process or enhance it by making the people executing it more effective. "That's so cool! But I want to do this too, and I want it to look like this..." This is the key to the 90% rule. Being willing to make compromises on small features is the only way to get to 100% (unless, like I said above, you have the development budget to get there). If you need to view your data set vertically instead of horizontally, figure out a way to get what you want outside of the application. It's usually pretty easy to take data from one app, import it into a spreadsheet, and get what you need. But having the ability to collect, track and manipulate the data in the first place is 90% of the job. Since most small businesses don't have the budget to devote to custom development,\u00a0you are forced to adapt your processes to the tools that are available. Ultimately, no matter what tool you choose, you're making a process decision for your business. If you choose flexible solutions, are willing to adapt your internal processes to better mesh with the tools, and trust your employees to bridge the gaps, there's a lot you can achieve with what's freely available out there. * * * * * About: Aaron Smith is the owner of Mixotic Technology Solutions. Aaron started his own business after seeing so many of the businesses he had worked for struggling with their technology, trying to figure out what tools to use, how to use them, and how to train staff. He believes that companies that don't explore new technology solutions give up a competitive advantage.