UX Agency in Uppsala
A UX agency for Uppsala works with research- and knowledge-intensive organizations to make complex services understandable – without losing the precision the subject matter requires. Accessibility is treated as a design requirement, with remote user testing run against relevant target groups to make sure the content actually gets through.
Uppsala is a knowledge city. Universities, research institutes, and knowledge-intensive organizations share a common challenge: much of what they want to communicate is complex by nature. Making that kind of content understandable for users – without simplifying away what makes it accurate – is one of the hardest and most rewarding UX problems there is.
Making complex material understandable
The first thing you have to let go of is the idea that “understandable” means “shallow.” Simplifying a service isn’t about removing content, it’s about presenting it so the right person understands the right thing at the right moment.
The tools for that belong to design: a clear structure that shows what belongs together, staged information that doesn’t overwhelm, and language suited to whoever is actually reading. A research-based service may need to speak differently to an expert than to a curious member of the public, sometimes within the same interface. The precision stays intact throughout – it’s just served in a form that doesn’t require the user to already know the subject.
A concrete example: a service that needs to explain a complicated application process to applicants with no prior knowledge. Instead of dense regulatory text, it’s laid out as a clear sequence, with the most important information first, deeper detail a click away, and terms explained where they appear. The content is just as accurate as before, but the user actually gets through it. That’s the difference between being right and being understood.
Accessibility as a design requirement
For services meant to reach many people, accessibility isn’t an add-on but a baseline requirement – and since the Accessibility Act, often a legal one too.
We build accessibility in from the start instead of tacking it on afterward. Contrast, readability, clear structure, and screen reader support are planned in from when the service is designed. What’s interesting is that this and understandability pull in the same direction: a service that’s clearly structured and easy to follow is almost always more accessible too. What helps someone using a screen reader – order, clear headings, plain language – helps everyone.
For a knowledge organization, that means the work of becoming understandable and the work of becoming accessible are, in practice, the same work, not two separate projects.
Remote user testing with relevant target groups
How do you know a simplification actually works? By testing it on real users. For knowledge services, where the target group is often spread out or specialized, remote testing suits particularly well.
We let relevant participants use the service while we observe remotely, watching for where they hesitate, misunderstand, or give up. The advantage of remote is reach: we can reach exactly the target group that matters – students, patients, applicants, professionals – regardless of where in the country they are, instead of being limited to whoever happens to be nearby. The insights end up the same as with an on-site test, but recruitment becomes easier and more precise.
Since the work happens largely remotely anyway, it doesn’t matter that we at Weapp are based in Gothenburg – knowledge services suit that setup well.
What working on understandability can deliver
The benefit becomes concrete once you see what confusion actually costs. Picture a service where applicants have to fill out a complicated application, and a large share call support because they got stuck, or give up halfway through. Every call takes time away from staff, and every abandoned application is someone who didn’t make it through – even though they wanted to.
Working on understandability tackles exactly that. When the information is structured more clearly, the steps get fewer, and the language meets the user where they are, both the support load and the drop-off rate decrease. The exact outcome varies, but the direction is reliable: fewer questions about the same thing, more people completing the task on their own. For a knowledge organization, that’s a double win – less internal load and more users making it all the way through.
The point is that understandability isn’t cosmetic but something measurable, visible in call volumes and completed cases. Want to work out how your service can become both more understandable and more accessible? It’s part of our services. Get in touch and we’ll have a first conversation about where the challenges sit.
Frequently asked questions
How do you simplify a service without losing precision?
By separating language from meaning. The goal isn't to make the content shallower, but to present it so the right person understands the right thing at the right moment – with clear structure, staged information, and language suited to the reader. The precision stays intact, but it's served in a form that doesn't require the user to already be an expert. It's as much a design question as a language question.
Why does this fit Uppsala's organizations particularly well?
Uppsala has a dense concentration of universities, research institutes, and knowledge-intensive operations, where much of what needs communicating is complex by nature. The challenge of making expert content understandable for a broader audience – students, patients, the public, decision-makers – comes up again and again. That's exactly the kind of UX problem we work with.
What does accessibility as a design requirement mean?
It means accessibility gets built in from the start instead of patched on afterward. Contrast, clear structure, readability, and screen reader support are planned in from when the service is designed. For knowledge services meant to reach many people, that's both a quality issue and, since the Accessibility Act, often a legal requirement. An understandable service and an accessible service go hand in hand in practice.
Does remote user testing work just as well?
For many target groups, yes – and sometimes better. Remote testing lets us reach relevant participants regardless of where they're located, which is valuable when the target group is spread out or specialized. We let participants use the service while we observe remotely, catching where they hesitate or misunderstand. That gives the same kind of insights as an on-site test, with easier recruitment.
Do you need to be based in Uppsala to help us?
No. We're based in Gothenburg but work with organizations across the country, and knowledge services lend themselves well to remote collaboration. Remote user testing, digital workshops, and regular check-ins mean distance isn't an obstacle. The few moments where being there in person adds the most are scheduled in as needed.