• Home
  • A+W News US
  • How to Choose the Right Software System for Your Company (Part I)

How to Choose the Right Software System for Your Company (Part I)

Published on 09 November 2021

Choosing software for your business can be a daunting task, if not scary! Many business owners and managers know they need a new software system, but something is holding them back.

What prevents you from upgrading your system/process?
  1. Are the choices overwhelming?
  2. Is it the time needed to make the correct decision for your business?
  3. Is it the fear of making the wrong decision?
  4. Is it a combination of all of these factors or others?

These are legitimate fears. In an effort to help ease those fears, I will attempt to provide guidance. I cannot give you a roadmap that will pinpoint the exact software for your business because every business is different with unique circumstances. Let’s remember that no one software system fits every person or company.

Over the course of this blog series, we’ll discuss the strategy for finding the right software system for your team and company. Throughout the process, it is advisable to record your information somewhere, such as a Google Sheets or Microsoft Excel spreadsheet. These options make sorting the information quicker and easier. When you create the matrix, list software solutions providers down the y-axis and your requirements across the x-axis. Additionally, break your groupings into essential, conditional, and nice-to-have features (You’ll see these distinctions in Step 2, so be ready.). This will allow you to track left to right, up to down the best and most appropriate options for your company.

Planning Your Strategy

  1. Know Your Objective
  2. Prioritize Your Needs
  3. Create a Software Vendor Short List
  4. Validate Your Short List (a.k.a. Make Exclusions)
  5. Evaluate Your Choices
  6. Make the Decision and Negotiate

Step 1: Know Your Objectives

You can’t be successful in your software search unless you define your criteria and know what you’re looking for! To be successful, you must know what the system needs to accomplish, know your pain points (problems the new system is solving), and know the value of the solution (quantify the solution in terms of time, money, or benefits to the organization).

As you start this process, it is important to involve your team early on. They are the ones using the current software system (if one exists), know its failures, and must learn the new system. To this end, remember that change can be intimidating for most people. So, to help your team welcome in the coming change, involve them in the decision-making process, and add their needs to the list of requirements. Additionally, they should be involved in testing out the new system to ensure it functions better than the current system.

As you develop the team, you should consider the following questions:

  1. Who will do the evaluations?
  2. What is your timeline?
  3. Who is the final decision maker?

Step 2: Prioritize Your Needs

No software fits all employees or companies. Every software system has trade-offs. In some cases, multiple solutions are required to meet your needs. In this case, you must make sure that these systems can interface with each other, which can be a simple add-on to most software solutions. Keeping all of this in mind, prioritize the needs of your company by determining the most relevant features: essential, conditional, and your nice-to-haves.

Just remember before you go any farther, we all think everything is an essential item at some point. So, be careful not to throw everything into the “essential” bucket. To help with this, assemble a team of users to assist the company in moving forward.

With this team, start listing out the essential, conditional, and nice-to-have features.

  1. Essential: These are the must haves, such as optimization, cutting, scheduling/tracking, capacity planning, easy machine management, etc. If the system doesn’t have these features, the system is not feasible for your company.
  2. Conditional: These features aren’t mission critical, but would enhance the productivity of your business, such as an e-commerce feature, shower door configurator, or barcode scanning.
  3. Nice to Have: Company doesn’t need this feature to buy the software, but this feature would be nice if they existed, such as an accounting or CRM (customer relationship management) package.

Within Step 2, there are multiple questions you could ask yourself, including:

  1. What do you need the software to do?
  2. How easy to use should the software be?
  3. What’s your budget?
  4. What reports do you need the system to develop?
  5. How scalable should the software be: One facility or connecting multiple facilities?
  6. Do you want a cloud-based system or on-premises system? Windows versus Mac? SQL Server or Oracle? (More on this in Parts II & III)
  7. Do your vendors have any requirements they need met?

In Part II, we’ll discuss how to create a short list of candidates and validate that short list. Stay tuned as we work to make sense of the software buying process.

    Neuer Call-to-Action

    Our topics

    Show all

    Last posts