Digdir

Klarspråkveileder Workshop Template

Improving the Deployment Experience

Turning Digdir’s static PDF into a collaborative workshop tool

Altinn Studio is a platform used by public sector teams to build and publish digital services.

This case shows how I worked to improve the deployment experience — a step that technically existed, but was often forgotten or misunderstood.

Turning Digdir’s static PDF into a collaborative workshop tool

TL;DR

Digdir’s plain language guidelines were methodologically strong, but existed only as a static PDF. Teams were already trying to use them digitally — without a shared way of working.

My role was to translate the guidelines into a workshop-ready Miro template that supports collaboration, reduces cognitive load, and is easy to facilitate from day one.

Digdir’s plain language guidelines were methodologically strong, but existed only as a static PDF. Teams were already trying to use them digitally — without a shared way of working.

My role was to translate the guidelines into a workshop-ready Miro template that supports collaboration, reduces cognitive load, and is easy to facilitate from day one.

CASE OVERVIEW

ORGANISATION

Digdir

PRODUCT

Klarspråkveilederen

FORMAT

PDF → Workshop material

ROLE

UX Designer

COLLABORATION

Content designer

PROCESS

Sprint-inspired approach (Jake Knapp)

STATUS

In use internally

WHY: THE PROBLEM

The challenge was not adoption, teams were already trying to use the guidelines in practice.

The problem was the format.

IN WORKSHOPS:

the PDF was copied into Miro and surrounded by sticky notes
instructions had to be read aloud and interpreted
facilitators became “teachers” instead of supporters
outputs were messy and hard to reuse

The methodology was solid, but the interaction model was accidental — not designed for collaboration.

Conceptual illustration of teams attempting to use the guidelines collaboratively without a shared structure.

HOW: UNDERSTANDING REAL USER BEHAVIOR

By observing real workshops and talking with designers and facilitators, a clear pattern emerged:

teams needed something they could work in, not just read
participants needed clarity without heavy explanations
facilitators needed structure without scripts

The core problem was not content quality, but how the content shaped behaviour during collaboration.

Observed collaboration patterns when the guidelines were used without a designed structure.

REFRAMING THE CHALLENGE

Rather than “digitising a PDF”, the task became:

How might we turn plain language from a document into a collaborative practice?

To keep the work focused and time-bound, I followed a Sprint-inspired approach, moving quickly from understanding and sketching to testing and refinement.