UX design agency
A wireframe that is wrong costs an afternoon. A shipped screen that is wrong costs a sprint. Our UX work gives your developers tested flows to build from.
What UX design covers
An interview, a brief and six questions
How a UX project starts
An interview before the workshop
We interview you about your business goals and motivations, the skills of your team, the roles of the stakeholders and the chain of decisions, and how often we will talk. We also ask who the user is and which personas you already have. Clients usually fall into two groups: product owners, who can be the persona themselves, and investors, who want our know-how.
A workshop brief
The brief lists the minimal set of features the product cannot do without, each tested against one question: is it the thing users need? It also holds the schedule, the stages and the state of the project, including an analysis of the previous release, your preferred technology stack and your marketing and communication strategy. We decide on the technology after the journey mapping.
Six questions about the product
Before the workshop we go through six questions. What is the biggest motivation behind the product? What problem does it solve? How will it solve that problem? How will we measure success? How do you check that there is demand? What is the value proposition?
Journey mapping workshops: when we run them
User Journey Mapping (UJM) is the workshop method behind the brief. We assess the needs and behavior of users from several perspectives. We have run it for startups with a new product and for corporations with mature systems, in different industries, for clients from Istanbul, London, Oslo and Warsaw. Our article on how to set up UJM workshops describes the preparation in detail.
Who works on your project
The Product Designer is responsible for the whole user experience. Research, information architecture and application logic are not the Visual Designer's job, with one exception: in a discovery workshop the Visual Designer defines the information architecture and the content structure together with the Product Designer.
Why choose us as your user experience design company
Who is in the room
The Product Designer takes part in the workshop whenever a project has a UI or UX layer. Head of Design Daria Gusieva leads the workshops and keeps the standard of how our design projects are run.
How the work reaches your developers
Developers get complete design documentation and support in understanding the logic and the user experience. We correct the design based on feedback from implementation.
UX for customer-facing products
BizBot
BizBot is a startup from Oslo that automates company administration. We redesigned the UX and UI of its platform, and the work also covered brand identity, the website and marketing materials, with a design system for the modules that followed.
Before designing, the team had to understand how business works in Norway, including its local legal and cultural nuances. We ran product workshops and hackathons in Warsaw, Oslo and Istanbul. The face-to-face sessions showed how well the project fitted the real work of Norwegian companies. Read the BizBot case study.
Filmgrail
Filmgrail is a white-label platform for cinemas. Since 2020 our designers have led its rebranding, with a new visual identity and logo, and redesigned all the modules and components used in its apps and on its websites. The designers are part of the Filmgrail team and work remotely from Warsaw over Slack. At the start we made several variants of the look so that the interface would be transparent and adapt to the colors of each cinema client.
What our clients say
Simon Souyris Strumse
Filmgrail CEO
“Adding Order Group specialists to our team proved to be the turning point in Filmgrail's development process.”
UX for energy and industrial systems
A customer portal for an energy trading company
All modules of the portal share visual rules and components. We mapped user flows for each role: Client, Seller, Trader and Back-office. The design system was verified technically before the build, in the first sprint.
Industrial IoT dashboards
For an operator dashboard the work starts with an analysis of the company's procedures and instructions, which we turn into user stories before any dashboard is designed. Then we interview the operators who manage the environment every day and watch a typical day and its routines. Priorities are set with the operators, because one dashboard does not fit everyone: one operator has two monitors, another four. That is why we build widgets that an operator can move, stretch and minimize. The prototype goes to users, and we implement their opinions in the next round until everyone agrees. More in our article on dashboards for industrial IoT.
Kyoto and SCADA interfaces
For Kyoto the project started with a UX/UI MVP and grew into a BMS panel built on SCADA. The panel includes augmented reality elements in the view from the operator's camera. A SCADA interface needs a conservative color palette tied to statuses, a diagram of how the devices are laid out, no animations that pull attention away and a view matched to the role. ISA-101 is the standard that describes the human-machine interface (HMI) in this field.
Zeronest
In Zeronest, the energy management system we built, the household app shows a plain description of the expected production instead of a raw weather forecast, and it works from meter data alone, so a home without solar panels can use it too. Each user sees only what their role allows.
UX inside discovery and MVP work
Design leads the Discovery phase and then runs alongside the build. At PSONI it was the main part of Discovery, and after Discovery we analyzed the code from a design point of view. At Enerace, design workshops accompanied the work on a new module from November 2024 to January 2026.
For an app that sells merchandise at live events we designed the MVP views around what a seller needs during the event, from the sales dashboard and label printing to a live view of stock levels.
Accessible UX design with Deaf and blind users
The Centrum Komunikacji application was built with accessibility as a requirement, for mobile and web, to WCAG 2.1 AA. Its users are Deaf, hard of hearing, deafblind, blind and low-vision people. Some use Polish Sign Language (PJM), some read text, some use a braille monitor or a screen reader.
Workshops and tests with these users changed the interface. The registration screens, the password requirements, the terms and the notifications have PJM videos, and a rejected application comes with the reason in a PJM video and in writing. The app bar has switches for text size and for high-contrast mode. After training, the interpreters asked for a mirrored preview of their own image, and we added it.
Screen reader tests ran through the whole project. In September 2026 a blind accessibility expert who works with the client tested the production app on iOS and Android.
UX for a service centre
Interpreter changes without interrupting the call
In longer sessions two interpreters share the room. When the interpreter changes, only the active video switches, so the conversation continues, and the active interpreter is shown first.
Priority for urgent calls
Together with the client we decided that SOS calls go to a priority queue, without automatic forwarding by a dispatcher. The user sees their place in the queue, and the interpreter sees how many people are waiting.
Machine text checked by a person
The transcription panel shows draft and approved text in different colors, and the flow is draft, correction, send. The user sees only the approved text.
Questions before you start a UX project with us
Questions about UX projects
-
Yes. The first call is a conversation about your product, and it is free. So is basic discovery, a separate single meeting. Extended discovery is a wider scope, described on the Product Discovery Workshop page.
-
A workshop takes one or two days, and the preparation takes at least one or two weeks. It works best when everyone is in one room, though video works too. Roughly 60% of a workshop follows the standard plan, and about 40% needs improvisation.
-
A written summary, a confirmed scope and estimate, journey maps and user flows, mockups or a clickable prototype, and a backlog with user stories. Basic discovery gives you the scope, the estimate and a basic mockup or proof of concept, and the full set comes out of extended discovery. You receive a map of users and flows, a set of wireframes, a UI component library, redlines (design annotations) and a clickable prototype, all editable, and your team keeps access to them after we finish.
-
Yes. Usability tests run on scenarios prepared by the designer, and prototypes are tested for UX and for WCAG accessibility. For a product that already runs, our accessibility audit is a separate service.
-
UX design covers the structure and flow of a product, and UI design covers its visual layer. Together they make up product design.
-
The number of user roles and paths, whether the product is new or a live one is being redesigned, and how much research and testing you need. Cost and time follow from that scope, and the estimate comes after basic discovery.
More on how we design
Articles on journey mapping, dashboards and SCADA interfaces
Discover what your product really needs
Your message goes to
Filip Szamborski
Co-founder & CEO
Your message goes to
Karol Oponowicz
Co-founder & Business Owner
Your message goes to
Paweł Zieliński
Co-founder & Business Owner
So far we have worked with brands like:
Thank you for your message.
We read every message ourselves and get back to you within 48 hrs on business days.
Something urgent? hello@ordergroup.co