On this page
Some of my early software work involved commercial insurance, an industry where apparently straightforward interactions can depend on substantial amounts of information, rules and professional judgement.
In the early 2000s, I worked on the user interface for an emerging insurance aggregation platform intended for professional brokers.
This wasn’t a consumer price-comparison website.
It was designed for people working within the insurance industry, where information about commercial risks, products and underwriting arrangements had to be presented in a usable form.
My contribution was specifically to the interface.
The challenge of professional software
Professional users often work with systems that contain far more complexity than is immediately visible.
In insurance, the underlying processes can involve detailed information about risks, different underwriting requirements and a variety of commercial considerations.
The interface has to support those processes without becoming an obstacle to them.
It is tempting to assume that professional users should simply be expected to understand complicated software.
I have never found that a particularly satisfactory approach.
People may be experts in insurance without having any interest in the internal architecture of an application.
Their expertise should be supported by the software, not consumed by the effort of navigating it.
That was the sort of challenge I was interested in addressing.
Later work with IW Consultancy
I subsequently undertook software development work for IW Consultancy, including work on its UnderwriteIT platform.
My involvement also extended into the product’s identity: I created the UnderwriteIT name and its branding.
Naming a product and engineering it may seem like unrelated activities.
I don’t see them that way.
A product name is one of the ways people begin to understand what a system is intended to do.
The interface then has to fulfil that expectation through the way the software behaves.
Branding cannot compensate for a difficult application, just as sound engineering alone does not necessarily make a product understandable.
Both contribute to how people perceive and use a system.
Different responsibilities, one concern
I distinguish the earlier broker aggregation project from my subsequent UnderwriteIT work because my responsibilities were different.
In one, I was specifically contributing to the user interface of a developing commercial insurance platform.
In the other, I was involved in product development as well as naming and branding.
But both required an appreciation of the relationship between specialist business processes and the people expected to work with them.
That has remained an important concern throughout my career.
What remains relevant
The technologies and interfaces of the early 2000s have changed considerably.
The underlying design challenge has not.
A professional application must account for complex rules, information and working practices.
But complexity within a business domain doesn’t have to translate directly into complexity for the user.
The purpose of interface design is not to hide the nature of the work. It is to make that work easier to understand and carry out.
That remains as relevant to modern business applications as it was to the insurance systems I worked on more than two decades ago.
Project context
Topic: Human-computer interaction
Explore further
Further reading is listed below.