Using 40% of Your Software?

No one ever buys anything with the intent of using a small percentage of the product. Generally, when one makes a major purchase there is a good amount of research involved and desired features are scrutinized for efficiency and effectiveness. There may be yes/no checklists involved, various conversations with the vendor and many product demonstrations. People do this because they are planning on using the features that they will be paying for. Why is it then that most companies only use 40% of the features their software contains?

Software is the core of any competitive staffing company. How well the company utilizes the software is imperative to success in business today. Too often when assessing software decision makers are blown away by colorful presentations that mean nothing to core business processes. shareit for pc  Functionality should be the basis for any software decision and not colorful diagrams or how the screen looks. Software should also contain a basic workflow that stabilizes the way in which the firm will utilize the product to accomplish tasks.

How can software productivity be measured? First, you must be able to report on the amount of time employees spend accomplishing specific tasks. Next, there should be reporting for the individual employees so that they can self-assess their productivity and plan tasks. Third, assess the time employees take to respond to customer orders and inquiries. Last, the ratio of revenue, profitability and output to employee expenses and time spent on tasks must be measured. In order to accomplish all of this you must be utilizing a fully operational CRM Model.

Customer Relationship Management (CRM) is the most misunderstood term in the industry. The true meaning of CRM is the ability to measure success across the board from Marketing to Sales, Operations and Back Office. This model can only be implemented with a fully integrated front and back office model. The various departments within a firm must share information in order to be effective. This means that invoices should be viewable from front office. Collection calls must be viewable from front office. Software is a company communication project.

Once the software model is in place and contains everything needed to run the company, it is imperative that a Software Policy Manual be created and reviewed with all employees in the company. A Software Policy Manual describes all of the major tasks that need to be completed utilizing the software and how the tasks are to be completed. It should contain “best practices” for the specific organization as every company’s process is different.

Typically, when new software is put into place the users go through a basic training. This is generally a cookie-cutter course that the vendor uses to train all of its new customers. At times the course is tailored toward the type of staffing being done. A course like this is necessary and is enough to begin the journey to software success.

If an extensive software suite is selected, and it should be, the software will contain many more features than can be covered during a basic training course. It would not make sense to include everything as users will normally absorb about 50% of basic training, often walking away a bit dazed after a couple of days of training. If more than the basics were covered it would most certainly cause user brain freeze.

The initial basic training experience can be improved in 3 ways: 1) The basic course should feature “hand-on” training; 2) No interruptions should be allowed during the training; 3) Users must begin practicing what was learned immediately after training. For new software, users should be trained as close to the live date as possible, ideally while the final data migration is being completed. The Software Policy Manual should be complete and available for reference on the “live date”.

You may also like

Leave a Reply

Your email address will not be published. Required fields are marked *