[As a small contribution to National Disability Awareness Month (October, 2018), we are reprinting an original draft of our article in Field Service Digital published earlier this year. The Field Services segment is comprised of a highly skilled and very diverse global community of mobile and office workers, each of whom deserves to be supported by a full complement of tools, resources and support so they can, in turn, support their respective customers. Please take a few moments to read our take on the need to address accessibility in Field Service Management (FSM) product software!]
Accessibility is an important component of any business offering, and it seems to be growing in importance at a relatively fast pace. For decades now, individuals with physical disabilities have benefited from sidewalk ramps and graded building entrances and exits; the sight-impaired have benefited from audible street crossing systems; and the hearing-impaired have benefited from special telephone apps; etc.
However, accessibility considerations are not only limited to the external environment; they are increasingly being – or should also be – incorporated as an integral part of product software functionalities as well – especially in the various technical support and customer services segments. And, increasingly, accessibility also plays a role in field service!
However, when evaluating the need for accessibility in the Field Service Management (FSM) software used by an organization to run its services operations, there are a number of questions that should be addressed, including:
- What is the current awareness, perceived importance, market adoption/likelihood to adopt, likelihood to consider as a sales/acquisition influencer, etc. of accessibility with respect to the potential acquisition of a specific software product (or line of products) (e.g., Service Management (SM) applications, IT Service Management (ITSM) applications, Project Services (PS) applications, etc.)?
- What is the current/emerging demand for accessibility as a build-in to the software products that an organization uses; (i.e., is it merely a “nice-to-have” or a “need to have” component)?
- What is the market’s perceived importance with respect to being simply compliant (e.g., with the Americans with Disabilities Act of 1990 (ADA) and/or other similar country-specific regulations, etc.); being usable (i.e., by any and all disabled members of the organization’s user base); and being universal (i.e., to be used by all in the organization’s workforce)?
- What is the degree to which accessibility may be used as a sales and/or marketing tool, both internally by the offering organization (e.g., to gain management buy-in from the CIO, CFO, current users, etc.) and externally among the various customer/prospect segments (e.g., to promote the fact to their respective potential user/customer base that the organization plans to support their entire workforce, including meeting the needs of the disabled individuals that will be using the software, etc.)?
Accessibility should also be defined to include both permanent (e.g., blindness, color-blindness, hearing-disabled, etc.) and temporary disabilities (e.g., broken arm, cataracts, etc.); as well as situational disabilities (e.g., working from home, “working with one arm while holding an infant in the other”; and others. For each of these cases, a set ofadditional drill-down questions will also need to be asked – and answered – as part of the organization’s due diligence in selecting an accessibility-based FSM software product, including:
- What are the existing levels of awareness of accessibility as a purchasing influencer in the software product markets that your organization supports?
- What are the current definitions/perceptions of accessibility in your relevant market space (e.g., is accessibility broadly defined, more specifically defined, all-inclusive, etc.)?
- What is the perceived importance of accessibility among the various customer organizations and users that you support?
- What is the current extent of disabled personnel/users among your customers’ respective workforces?
- What is the current degree of compliance with regulatory mandates, etc., both internally and among your customer or user base?
- What is the perceived demand and/or preference for accessibility within the market segments in which you offer your software products?
- What are the perceived benefits/advantages of building accessibility into your existing (and planned) lines of software products; what are the perceived disadvantages?
- What is the likelihood of your customer/user base considering an accessibility-based software application in the future; would they be willing to pay a premium for additional built-in accessibility functionality – and, if so, to what degree?
- What role does accessibility play as a desired attribute in the software product evaluation/selection process; for example, will an accessibility-based software product move a vendor under consideration from the acquiring organization’s “long list” to its “short list” with respect to potential purchase/acquisition?
- How important is accessibility with respect to serving as an internal and/or external sales or marketing tool?
Whatever the specific outcome is with respect to the degree to which your organization builds an accessibility component into its FSM (or other business) software, one thing is for certain – the needs, requirements, opinions and preferences of the marketplace will be largely different on virtually an individual customer or prospect basis, depending on the degree to which they place importance on accessibility. Accessibility is clearly not an issue where one-size-fits-all.
However, by properly addressing each of the above-listed considerations, your organization – whether on the FSM software product supply side or demand side – will at least be off to a good start in ensuring that its final strategy will be well thought out, and as all-inclusive as possible. The field service segment is a large, fast-growing and highly diverse community, and many believe that all parties should be empowered to perform at their best – some through the assistance of an accessibility-enabling software platform.