UI/UX
An interface in which the next action is obvious
Design here is not decoration on a mockup. It is a way to take a person through a task: a client through a request, a manager through a deal, an operator through a queue. I take the scenarios apart, and I assemble the screens, the states, and the rules by which the interface can grow.
What it takes on
- 01
Understand the scenario
Who arrives, what they want to finish, and where they drop off now.
- 02
Assemble the screens
Not only the happy path, but the empty state, the error, the long list, and the narrow phone.
- 03
Tidy an existing product
Keep the working habits people already have, and remove what makes them call support.
- 04
Fix the system in place
Repeated elements, spacing, and the states of buttons and forms, so the next screen is not a new style.
Who it is for
Teams before development
You need to agree, before any code, what is being built and what will not be on the screen.
Products with a confusing account
The functions exist, but people ask where to press.
Companies with internal systems
An employee spends the day in the interface. Beauty without speed does harm here.
If the product has not yet decided what a person does in it, a picture will not decide that. The scenario and the data come first. The visual style comes after.
What can be built
Scenarios
A role's path from entry to a finished action.
Interfaces
Sites, accounts, tables, panels, and mobile screens.
Prototype
Linked screens you can walk through before development.
Design system
Rules for the components, not one decorative frame.
Redesign
A new composition that keeps the actions people have already learned.
How it looks in practice
- 01
Development has not started
The layouts fix the first release. The development estimate is more honest after that, because the argument is about the scenario, not about surprises in the middle of the code.
- 02
The CRM is awkward to use
We look at how many clicks it takes to close an ordinary day for a manager. We simplify the card and the filters. The records are not rewritten for the sake of a new color.
- 03
The site does not bring in a request
The problem is often not the shade of the background. It is the order of the meaning: the person does not understand where they have landed. A redesign starts with the path, not with the typeface.
How development goes
- 01
Role and task
Who the user is, and which action counts as success.
- 02
The set of screens
A map, including errors and empty states.
- 03
A rough pass
Structure without decoration, so the logic can be checked.
- 04
A visual system
Grid, type, color, and components.
- 05
Specification
States the developer should not have to invent.
- 06
Support during the build
A check of the live interface against what was agreed.
Technologies
- Figma
- Prototypes
- Design systems
- Grids and interface states
You receive a map of the scenario, screens of the key states, and a description of the components. The files are handed over so a developer does not have to measure a picture by eye.
Demonstrations on this topic
Catalog storefront
A catalog in which a filter helps you choose, instead of hiding the items.
City sites
A person chooses a city and leaves a request, without entering the internal account.
Order account
The client needs the status of the order, not the company's whole board.
Slice
An independent concept for analytics. Revenue, cost, and profit are summed from sample rows.
Stall
An independent shop concept: catalog, product, cart, and a sample order with no payment.
Slot
An independent booking concept. A service, a person, and a slot that cannot be taken twice.
Route
An independent delivery concept: statuses, couriers, and an event log. The coordinates are a sample.
Hire
An independent recruiting concept: cards, stages, and a note.
Class
An independent learning concept: lessons, progress, an assignment, and a teacher view.
How to commission it
A separate scope
We take one mechanic, one link between systems, or one set of screens that can be finished and checked.
Inside a larger product
The interface, the game, or the automation sits inside a larger project. It does not live apart from the data.
Support
After handover there is a queue: fixes, new scenarios, and someone watching the system.
Questions
Can design be ordered without development?
Yes. You receive a scenario and layouts you can give to your own team. If I do the development as well, the specification takes the build into account from the start. It does not exist apart from the build.
Do you only draw a decorative first screen?
No. The first screen matters, but the handover includes the states a person will meet: an empty list, an error in a form, a long name, a phone.
Can our current style be kept?
Yes. If the style is already recognizable, new screens rest on it. I do not propose a redesign for its own sake.
How many options do you show?
As many as it takes to choose a direction, and not so many that you drown in ten equal pictures. Usually one strong direction, and a few pointed forks.
How does design connect to SEO and to forms?
The structure of the headings, the order of the meaning, and the contents of the request are designed together with the composition. A decorative page that does not make the service clear does not count as finished.