By Gary Allemann, MD at Master Data Management*
Way back there was a joint course that combined students from the Computer Science (CS) department, which, at the time, was very focused on algorithms and programming skills, with students from the Business Information Systems (BIS) department – a more commercially oriented and less technical group.
At one stage the students were asked to do a practical task – back in the days of command line and green screen. The BIS group, by and large, delivered code with a lot of focus on the user interface. The user was given clear instructions about what needed to be captured and what it was to be used for. However in many cases, the underlying program didn’t work correctly and the results calculated and presented, however beautifully, were incorrect.
By contrast, the CS group all produced functioning code. At face value this would seem better, right? However in this case, many of the interfaces were unusable, except for the person who had written the code. In one extreme case the user was presented with a series of flashing cursors (prompts) and was required to enter the required values in the correct order with absolutely no instructions.
In light of the above example, from an IT perspective, we often make technology choices based on technical factors that make life easier for the IT department.
These may include:
- Existing vendor: It can be painful to onboard a new vendor, deal with procurement and legal, and build and manage a new relationship.
- Integration: How easily will the proposed solution “fit” into our existing landscape?
- Scalability: Can the proposed solution cope with our volumes and complexity?
- Security: Is the proposed solution secure?
In many cases, we end up with technology choices that a business-user community really struggles to understand and use. Often, we expect users to adapt and use multiple tools to do similar things but in very different ways. For occasional users in particular, these seemingly minor quirks and differences in interfaces and how they look and feel, can become major obstacles to getting their jobs done.
When business users complain that the response from IT is often “make it work”, uptake is often (unsurprisingly) poor and expensive investments are wasted.
Going back to those days – neither the BIS nor the CS choices were better. Of course, technical concerns around scalability, performance, integration, security and all-around effort to support and maintain any platform are legitimate and must be considered. But business users’ needs around adoption and usability must also be seriously considered. Both business and IT should engage in finding solutions that work and provide business-first, consistent interfaces for usability across multiple use cases.