Transform digital services. Instantly.

Transform digital services. Instantly.

Altinn Studio

Redesigning the Deployment Experience

Redesigning the Deployment Experience

Redesigning the Deployment Experience

Altinn Studio is a platform for building and publishing digital services for citizens and businesses in Norway.


I redesigned the deployment experience to help users identify issues before publishing, better understand deployment readiness and navigate the publishing process with greater confidence.

The project focused on introducing earlier validation feedback, creating a more guided publishing workflow and simplifying environment management across the platform.

Altinn Studio is a platform for building and publishing digital services for citizens and businesses in Norway.

I redesigned the deployment experience to help users identify issues before publishing, better understand deployment readiness and navigate the publishing process with greater confidence.

The project focused on introducing earlier validation feedback, creating a more guided publishing workflow and simplifying environment management across the platform.

MY CONTRIBUTION

Workflow mapping · Interaction design · Validation experience · Error handling · Status communication

MY ROLE

UX Designer

TEAM

4 Developers · 2 Product Owners · UX Lead · Content Designer

TIMELINE

Aug 2025 - Feb 2026 (6 months)

OUTCOME

Approved for implementation

THE CHALLENGE

Users often discovered issues only after deployment had already started

Users often discovered issues only after deployment had already started

Users often discovered issues only after deployment had already started

The deployment workflow allowed users to build and deploy applications before knowing whether their latest changes contained issues.

As a result, deployment failures often became the first indication that something was wrong.

Key challenges

Understand why a deployment failed

Identify what needed to be fixed

Know whether a version was ready for deployment

Understand when a new build was ready to be deployed

INSIGHT

Users were not struggling with deployment itself

Users were not struggling with deployment itself

Journey mapping and feedback from service owners, support channels, developers and designers revealed a recurring pattern.

Most deployment failures originated earlier in the workflow, but users only became aware of them after deployment had already started.

Users were not struggling with deployment itself

The research revealed three key insights:

01

Users needed earlier feedback about validation issues

02

Users lacked clear indicators showing when a build was ready for deployment

03

Publishing and environment management represented different tasks and should be treated separately.

These findings shifted the focus from deployment actions to guidance, visibility and feedback throughout the workflow.

DESIGN DECISION #1

Introduce earlier validation feedback

Introduce earlier validation feedback

Introduce earlier validation feedback

Validation issues became visible before build, with direct links to affected areas and clear guidance on what needed to be fixed.

DESIGN DECISION #2

Separate publishing from environment management

Separate publishing from environment management

Separate publishing from environment management

Research showed that users came to the deployment page with two very different goals:

Publish a new version

Monitor and manage environments

Combining both workflows on a single page created unnecessary complexity and made it harder to focus on the next action.

I separated these tasks into dedicated tabs, allowing users to focus on publishing when creating a release and environment management when monitoring deployed versions.

The image featured in the middle of the about us page

Publish a new version

Monitor deployed versions

The image featured in the middle of the about us page
The image featured in the middle of the about us page

Publish a new version

Monitor deployed versions

The image featured in the middle of the about us page
The image featured in the middle of the about us page

Publish a new version

Monitor deployed versions

The image featured in the middle of the about us page

DESIGN DECISION #3

Turn publishing into a guided workflow

Publishing was redesigned as a clear step-by-step process that guides users from validation to build creation and finally deployment.

Instead of interpreting multiple deployment states at once, users are guided through the workflow with clear status communication and next actions.

This created a more predictable publishing experience and reduced the risk of overlooking important steps.

Turn publishing into a guided workflow

Turn publishing into a guided workflow

OUTCOME

A clearer and more
predictable deployment experience

The redesign introduced earlier feedback, clearer status communication and a more structured publishing workflow.

By addressing issues before build and deployment, the experience
helped reduce uncertainty throughout the publishing process and made it easier for users to understand what action was required next.

The solution received positive feedback from developers, the UX Lead and product stakeholders, and was approved for implementation as part of the broader Altinn Studio modernization effort.

A clearer and more
predictable deployment experience

A clearer and more
predictable deployment experience

Key improvements included:

Approved for implementation

The final solution was approved by product and engineering stakeholders.

Earlier feedback

Validation issues are surfaced before build and deployment.

Clearer workflows

Publishing and environment management were separated into dedicated experiences.

Blue Gradient

Blue Gradient

Purple Gradient

Purple Gradient

Orange Gradient

Orange Gradient

Yellow Gradient

Yellow Gradient

REFLECTION

A clearer and more
predictable deployment experience

Complex workflows require curiosity before solutions.

This project reinforced the importance of understanding the full workflow before designing individual screens.

The biggest usability issues were not caused by isolated interface problems, but by how information, validation and actions were distributed across the entire deployment process.

If I were to continue the work, I would validate the new workflow through usability testing and measure whether users are able to identify and resolve issues earlier in the process.

The project also taught me the value of involving developers continuously throughout complex system redesigns and testing ideas earlier before investing heavily in complete flows.

A clearer and more
predictable deployment experience

Back to Home