Make your website or tool easier to use
People getting stuck in a form? Staff switching to a spreadsheet because a screen is hard to use? We look at the task, find the confusing steps and design a clearer way through them.
This work is often called UI/UX design. It covers what people see and how they get things done.
What we work on
Understand the task
We review the current screens and talk to the people using them where possible. We look at what they need to do and where they need help.
Plan clearer steps
We organise the information, labels, forms and actions around the task. A focused change may be enough; the whole product does not always need redesigning.
Make a clickable preview
You can click through the proposed screens before development begins. This shows the route and layout. It is a preview, not working software.
Check the design with users
We agree who can test it and which tasks they will try. Their feedback helps us revise the design before it is built.
Prepare the handover
You receive the agreed screen designs, preview, reusable design elements and notes. We can build the result or hand it over to your development team.
Example task
A clearer review screen
A team member needs to check a draft quote. The screen should make the customer, products, prices and missing details easy to find, with clear actions to edit or approve.
We design around that task and check whether people can complete it. The same approach can be used for a form, an order or a customer account.
How the work runs
Agree the problem, the screens to review, the price and the schedule.
Review the current task and speak with users where agreed.
Design a clickable preview and test the main steps.
Refine the design and hand it over for development.
Common questions
UI is the screen: its buttons, fields, text and appearance. UX is the experience of using it to complete a task. We consider both together.
Yes. We can focus on a form, payment steps, a customer screen or another agreed task. We first check what might be causing the problem.
The agreed designs in Figma, a clickable preview, reusable design elements and handover notes. The proposal names the screens and the amount of research, testing and revision included.
Yes. We agree the handover they need and discuss technical limits early, so the design fits the planned build.
We consider readable text, contrast, labels and ways to navigate without a mouse. Any accessibility target and testing plan should be agreed for the project and checked in the working product too.
We can agree follow-up tests or review usage information that is available for the project. Further changes and monthly support are optional.
Where do people get stuck?
Tell us which screen or task needs attention and who uses it. If you have examples or feedback, describe them in your message.