Research and user tasks
Video interviews with customers, sales or support staff, a look at analytics and at the questions arriving by email. The output is a short list of the tasks the site or app must support best.
The most expensive fix is the one made after development. Moving a button or reordering steps takes minutes in a prototype and days in a working application. Suppose a private clinic in Maribor wants online booking for check-ups. Management pictures a calendar of free slots, while patients first want to know whether they need a referral and what to bring. Gaps like that surface after five conversations with real users and a clickable prototype. So we do not begin design with colours; we begin with the tasks people need to complete.
What you get is not just an attractive picture but a tested design that developers can build without guessing.
Video interviews with customers, sales or support staff, a look at analytics and at the questions arriving by email. The output is a short list of the tasks the site or app must support best.
Grey sketches of the key screens, where we debate content and order rather than colour. Changes here are cheap and fast.
A Figma prototype that behaves like a real app on phone and desktop. We use it to test, not merely to present.
Five to eight people from your target group complete a few tasks in the prototype over a video call. We watch where they stall and fix it before development.
Colours, typography, icons and imagery in line with your brand, with contrast and sizes checked against WCAG 2.1 AA.
A component library covering every state of buttons, forms and error messages, plus notes for developers. Future pages will look like part of the same whole.
Designing a smaller site takes two to four weeks, a more demanding app longer. User testing is a significant part of that time.
On a video call we set goals, users and key tasks together and agree whom we will interview.
We draw wireframes of the key screens and turn them into a clickable prototype, which we review with you.
The prototype is tested with users, findings are summarised and the design is revised. If needed, we test again.
We finish the visual design, assemble the design system and hand it to the developers, ours or yours.
The management team's opinion is not user testing. When everyone in the company knows the product inside out, nobody can see what is unclear to a newcomer. Five conversations with real users often settle a debate that has run for weeks in meetings and reveal problems no one had thought of.
Most often among your customers, invited with your permission. For new products we recruit through ads or sector groups. Participants usually receive a small thank-you, agreed in advance.
Yes. We hand over the Figma files, the design system and developer notes, and can help review whether the build matches the design.
Not necessarily. We usually work with your existing logo and colours and adapt them for the web, for instance adjusting contrast for accessibility. A full identity is best commissioned from a branding studio.
Before and after the redesign we measure a few concrete indicators: how many visitors finish a form, how many questions reach support, or how long a task takes in testing. Without measurement it is hard to say what worked.
Tell us which site or app it is, who the users are and what frustrates them today. We reply within one working day.
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
No town by that name here. Check the letters, or settle for the nearest larger place. Our engineers work only over the internet, so Kočevje and Koper get precisely the same treatment.