Plain language – a superpower in developmental processes
for
The Directorate of Digitalisation
Graphic illustration of the project
Halogen has developed a guide that shows how to use plain language as a tool from start to finish in digitalization projects.

Have you been tasked with proofreading, but felt that you have input far beyond proofreading? The fact that language competence comes late in the process is a regular occurrence for many.

Digdir and Halogen wanted to explore the potential of including plain language earlier in digital projects. Instead of using plain language as a tool in the final phase of the project, we wanted to be involved from an early phase, and through all the steps in the process. 

From practical experience to generic method

In this context, plain language means correct, clear and user-friendly language. Through practical work with two digital products related to the life events of death and inheritance , we documented how the interaction between design, development and clear language can trigger great value in digital development projects.

The experiences are collected in a guide for the practical use of plain language in digital projects: Guidelines on plain language in the development of digital services.

The guide builds on clear language work in the Language Council, KS and Digdir.

Valuable from start to finish

During the work with the digital products, it would turn out that plain language was a superpower as a process tool. In the early phase, we saw how clear language helped the project groups to have good conversations about what they should develop, for whom and thus in which direction the project should be taken.

Clear language also proved to be a useful tool for understanding the expertise in the groups, and for distributing tasks and responsibilities. Not least, clear and distinct formulations ensured that the project groups had the same understanding of subject terms and technical expressions.

User tested early in the process

During the development runs, the UX designers (user experience designer) worked together with the content designers to use clear language in prototypes and early versions of the digital solutions. This allowed us to test on real users early on, and get feedback on whether the target groups understood what was necessary.

Marker testing is a method we use a lot to get quick feedback from users

If you have used clear language throughout the development process, there is no point in creating end products with clear language. When we work with real and user-tested content from the start, there is no transition from the development phase , where only those involved understand the whole, to the launch phase, where the products have to be translated to be understandable to the users.

In other words: You don't just save time – you create better products and services!

Male employee writes with dry erase marker on whiteboard in meeting room
Male employee writes with dry erase marker on whiteboard in meeting room
Male employee writes with dry erase marker on whiteboard in meeting room
Male employee writes with dry erase marker on whiteboard in meeting room
Male employee writes with dry erase marker on whiteboard in meeting room
Male employee writes with dry erase marker on whiteboard in meeting room
Åsmund Eikenes
Leader for Content Design
aasmund@halogen.no
Would you like to know more? Contact us!
Åsmund Eikenes
Leader for Content Design
+47 480 34 223aasmund@halogen.no