UX Design

A beautiful interface nobody can figure out how to use is not a design success, it is an expensive guess.

A beautiful interface that nobody can figure out how to use is not a design success. We validate with real users before development begins, so the effort goes where it actually pays off. 

We prototype and test before we build. Our UX designers create wireframes and interactive prototypes that are validated with real users early, so that development effort is focused on experiences that work, not just features that exist. 

How we help 

  • Wireframing and prototyping: low and high fidelity prototypes built fast enough to test multiple directions before committing to one. 
  • User testing: real users interacting with prototypes, not internal assumptions about what they will understand. 
  • Interaction design: the specific flows and states that make a complex system feel simple to use. 
  • Accessibility built in: designed to work for users with different abilities from the first wireframe, not retrofitted later. 

Technology 

  • Figma 
  • interactive prototyping tools 
  • usability testing platforms 
  • accessibility evaluation tools including axe and WAVE 
  • card sorting and information architecture tools 

 

Why it matters 

Our UX design work on the Sami Regional Education Centre website revamp and the City of Rovaniemi redesign was grounded in user testing throughout the project, not just at the end, so findings actually shaped the service rather than just documenting its problems after launch. 

The cheapest time to fix a usability problem is in a paper prototype. The most expensive time is after launch, when fixing it means re engineering live functionality. We test early specifically to keep changes cheap, even when that means testing something rough rather than waiting for it to look polished. 

Frequently asked questions

Real users, specifically because internal stakeholders already know too much about the product to spot the same confusion a first time user will hit.
It depends on complexity, but we generally recommend at least two rounds, one early on rough prototypes and one closer to final design, so findings can still change the outcome.
Primarily Figma for wireframes and interactive prototypes, chosen for how easily it supports rapid iteration and user testing.
Both. A lot of our UX work involves diagnosing why an existing product is underperforming, not just designing something new from a blank page.