Impact
1: Better user experience
The user experience in a form filling situation is hard to measure and influenced by a lot of circumstances. However, the feeling of spending less time, more than time itself, is one important indicator on a better user experience.
To be presented in Altinn, the Norwegian eGovernment infrastructure for simplified electronic dialogue, governmental forms must be developed in an ELMER-adjusted form tool. In the last Altinn user survey more than 77 percent of the businesses claimed that they use less time on public forms delivering them in Altinn (Perduco, NNU 2008). The ELMER influence on the relevant form dialogues and the effect of homogeneous look and feel, represents a great share of the total user experience leading to this conclusion.
Another indication on an acceptable user situation is that business respondents have preferred extremely fast the Altinn ELMER based forms to their well known and secure paper based alternative. In 2005 ca 15 percent of “Term reports of employers’ contribution and advance tax” and 58 percent of “VAT return” forms were delivered through Altinn. In 2008 the share was respectively 82 and 85 percent.
We do not know much about the educational effects of common look and feel in forms. Most people may not (at least not consciously) remember the concept from one form to another. But we do know in general that every user with cognitive challenges, and especially the blind or weak-sighted web user, benefits from recognizable interfaces.
As we now start developing compound services in Norway, assembling forms from different agencies in one form filling process, consistent user interfaces will become even more important.
2: Better understanding and response quality
No investigation has been done to compare the quality of information submitted through an ELMER form with other web forms or the old paper based reports. But user tests show that form fillers do understand the ELMER functionality. We have indications, and it seems natural, that they do make use of the embedded “piece by piece” help functionality (user-requested help) more often than they would look up a separate guidance document.
The ELMER help text shall be “…adapted to fit the needs of the least skilled form fillers” (ELMER 4.2.3) and “…shorter, more structured and divided into smaller segments than what would have been acceptable [ … ] on paper” (ELMER 4.2.8).
Error handling is important for quality. ELMER prescribes different validation solutions for absolute errors and improbabilities. In both cases “The error message shall not primarily tell what is done wrong, but must point out how to fill it in correctly”.
As we can see from the examples above, ELMER points out the direction but leave a lot of solution choices regarding parlance and textual clearness to the developing project. Nevertheless; the right professionals, following the requirements conscientiously, will ensure a better understanding of the task and better data quality than if these matters are not considered.
Norwegian surveys, most evident from Office of the Auditor General of Norway, (Document no. 3:10 2004-2005, English version, pdf), indicates that user-friendliness traditionally was not particullary esteemed in form production in Norwegian governmental administrations and agencies.
It is our clear impression, following ELMER form development during the last five years, that more Norwegian governmental bodies now involve their information experts in form development. Usability experts seem to be more natural participants in the Norwegian web form projects than just a few years ago. The ELMER guidelines are their argument to get involved and their tool to succeed.
If the user doesn’t find all the help he needs in the form itself, he will consult telephone or mail support. In the worst case he will not complete the form or he will send a paper based one instead. If the receiver becomes aware of form misunderstandings afterwards, he may have a lot of efforts to correct mistakes during the case handling. The cost reducing potential of simplified, understandable forms for public sector is considerable.
Response quality is, of course, also a critical factor to maintain adequate public reactions and correct decisions towards businesses and citizens. Decisions based on incorrect information might be a threat to legal protection and public security.
One important issue for the future: The more we succeed in integrating and re-using collected information to increase governmental efficiency, the more important it will be that form questions were correctly understood and answered in the first place.
3: Less expensive form projects
Often public announcements of tender have stated that the system “shall be user friendly”. This of course is impossible to measure and leaves a lot of questions to clarify during the purchasing or developing project. For form solutions it is now possible and usual in Norway to state that the ELMER requirements shall be fulfilled. This saves a lot of discussions on where to place different elements and how to approach user friendliness in the project or software solution.
Track record of sharing
Sharing ELMER in every possible area is an important policy instrument to obtain recognizable form interfaces. Succeeding with ELMER depends on common look and feel. The more ELMER is used in every sector of the society, the easier will it be for form fillers to get familiar with its user interface.
The guidelines are published on www.brreg.no/elmer, in a html version and as downloadable pdf file. Detailed explanations and clarifications of each requirement category are available here as well.
Twice a year The Brønnøysund Register Centre (BRC) offers subsidized ELMER courses, going through each and every requirement with good and bad examples. A complete text-book covering form usability and ELMER is available free of charge for course participants and governmental agencies.
BRC participate in meetings and discussions with organizations preparing ELMER forms whenever wanted, in private sector as well as for governmental, regional and municipal administrations. ELMER is also presented in ICT-, communication- and eGovernment conferences.
The BRC and the business associations find it important to spread the ELMER way of thinking to other countries. This is also the reason why the NHO - Confederation of Norwegian Enterprise has contributed in translating the ELMER guidelines into English.
Also organizations and sectors not being obliged to follow ELMER, and of course governmental agencies in other countries, have a lot to learn from the concept. By bringing up a discussion about every ELMER requirement in their relevant project environments, the team participants will understand each other better, they will achieve a greater awareness of form usability and they will make better form solutions.
Lessons learnt
Lesson one:
Given the right timing, governmental agencies as well as software developers appreciate guidance and clear specifications for electronic solutions.
The very first ELMER version back in 2001 was adapted by Norwegian authorities and software developers unexpectedly fast. Mostly a feasibility sketch, in a report commissioned by the Norwegian Ministry of Trade and Industry, it was not a complete set of requirements, it was not mandatory and it was not in any way marketed towards relevant individuals or groups. Nevertheless, quite a lot of the first important Norwegian web forms ended up like the ELMER design and functionality sketches.
The explanation might be that very few experts yet had come up with a firm conviction on how to deal with electronic forms. Neither the agencies nor the software industry, at this time, had invested much time and money on competitive, sophisticated web form solutions. Norwegian ICT suppliers were eager to prepare for the public sector demands in a new, fast growing market. And most governmental administrations and agencies had no capacity to develop specifications on their own and would welcome any initiative giving a thorough and trustworthy impression.
Lesson two:
Communication skills are essential when forms are being composed, even if general requirements are drawn up in the guidelines.
It is important to be aware that ELMER does not make up for communication expertise and user testing in the individual form developing process. The requirements leave a lot of solution choices, regarding track structure, parlance and visual as well as textual clearness. Different ELMER-based solutions may still give quite different user experience.
For some projects it is still a challenge that the agencies do not sufficiently involve information skilled employees. Adjusting old paper forms to ELMER, by restructuring questions and pages to create different dialogues for diverging user groups and by transforming separate guidance documents to concise help texts for individual questions, is complicated and time consuming. It will rarely be given sufficient consideration in projects focused on urgent technical challenges, if communication expertise is not participating.
Lesson three:
Involving all relevant interest groups, across different sectors in society, makes it easier to obtain comprehensive agreement.
The web form must satisfy the needs of the information collectors, the technical systems and the form fillers. This requires cooperation between different professionals not familiar with each other’s operating conditions and not used to work together as a team.
Bringing together the policy or legal expert from public agencies, ICT professionals and information/communication specialists as well as participants from heavily form exposed companies, seem to give them all a better, common understanding of the challenges and, by that, common ideas of requirements for well working forms