UI design consulting is advisory work that decides what a product’s interface has to accomplish, settles the rules it has to obey, and judges whether a proposed design actually does the job. Vivaldi is a strategy firm, not an interface production studio. We do not staff screen design, we do not build or maintain design systems, and we do not write front-end code. We work on the decisions a screen is being asked to resolve, alongside whoever draws and builds it, and saying so in the first paragraph saves a wasted meeting.
- Desde 1999trabajos de estrategia de marca, producto y experiencia
- Más de 200estudios de caso publicados
- 10 oficinasen cuatro continentes
- 5x«Best of Consulting, Strategy and Innovation» de WirtschaftsWoche
Most firms selling UI design services are selling production capacity, and most of the time that is what a company needs. The problem we get called about is the other one: a team that can draw anything is drawing the wrong thing, because nobody senior has said what the interface is for. That question is commercial before it is visual, and it is the part we take.
One distinction before anything else, because these two words are used interchangeably and should not be. User experience (UX) design decides what should happen and in what order across the whole path a person takes, including the parts that never appear on a screen. UI design decides what the thing looks like and how its controls are laid out, which is a narrower job and a real one.
Cuando las empresas nos contratan
The pattern is consistent. There is no shortage of design talent. There is a shortage of decisions.
- A redesign is scoped as a visual refresh, and the people paying for it quietly expect a commercial result the new screens cannot produce
- Two or three digital products look like they come from different companies, and nobody can say which one is right
- An internal design team or an agency keeps producing good work that stalls in review, because the criteria for approving it were never written down
- Navigation and screen hierarchy mirror the org chart or the database, so users have to know how the business is organized before they can find anything
- An AI feature has to appear on screen, and nobody has decided how the product shows confidence, provenance and the route to correction
Why a visual refresh usually disappoints
The reasonable version of the standard argument is that a clean, consistent interface lowers effort, and lower effort raises completion. That is true. It is also a smaller effect than the budget assumes, and it is the reason redesigns are so often judged a modest success and quietly repeated three years later.
What a refresh cannot change is what the product asks of the user and what it decides on the user’s behalf. If a form asks for information the company already holds, better typography does not remove the question. If a screen presents six options because six teams each own one, a tidier grid does not resolve which two matter. If the default setting is wrong, no amount of craft rescues it, because the default is the decision most users will live with and never revisit.
So the useful sequence runs the other way. Settle what the interface is for, write down the rules it has to obey, then let a capable team design against them. Doing that costs a few weeks at the front and removes most of the arguments that otherwise surface in the third round of review, when changing anything is expensive.
What our UI design consulting includes
Four pieces of work, all advisory. None of them produces finished screens.
1. Interface intent
What each important screen is for, stated as the job the user arrived to do and the commercial outcome the business needs from it. This is written as a short document a design team can be held to, not as a mood board. It includes what the product should remember so the user is not asked twice, and what it should decide by default rather than offering as a choice.
2. The rules the interface has to obey
Principles that are specific enough to settle an argument: how much the product is allowed to ask before it gives anything back, how hierarchy is decided when two teams both want the top of the screen, how errors and empty states are expected to behave, what accessibility means here as a constraint rather than an audit at the end. These are the standards your team or your studio designs against.
3. Design review and judgment
Reviewing proposed interface work against the intent and the rules, and saying plainly whether it does the job. This is the service most clients actually want from us and the one they ask for last. An outside reviewer with no stake in the screens being approved is worth more than another round of internal opinion.
4. A brief the people who build it can use
A specification of intent, rules, priorities and success measures that an internal design team, a product studio or an agency can take and execute. We will help you pick that partner and sit in the reviews. We will not pretend to be them.
Not sure whether your problem is the interface or the model underneath?
Start with a working session on one screen that underperforms. We will establish what it is supposed to accomplish and name the decisions inside it that nobody has made.
How a UI design engagement works
- Frame. Interviews with the people who own the product, the people who support it and the people who approve design work. A walk through the current interface as a user meets it, with the analytics and support data alongside. The output is a short list of screens worth arguing about and the decisions blocking each one.
- Decide. Interface intent for those screens: the job, the outcome, what is asked, what is remembered, what is decided by default. This is where the commercial trade-offs get settled, in a room that includes commercial leadership rather than only design.
- Write the rules. The standards a design has to meet to be approved, specific enough that two people reading them reach the same verdict. Handed to whoever is producing the work, internal or external.
- Review. We judge the work as it comes back, against the rules, through the first implementation. That last part matters, because implementation is where design decisions get renegotiated without anyone noticing.
Why companies choose Vivaldi for UI design work
Mostly because of what we are not. A studio paid for screens has no incentive to tell you that the right answer is fewer of them, and an internal team is measured on shipping inside the structure it already has. We are paid for the judgment, which makes removing a feature as good an outcome for us as redesigning it.
Three practical consequences. The interface decision and the business decision get made in the same room, because they are usually the same decision wearing different clothes. The criteria for approving design work exist in writing before the work is commissioned, which is the single cheapest thing a company can do to shorten a review cycle. And we will say when the honest recommendation is to keep the interface and fix the product underneath it, which is a recommendation nobody selling design hours makes often.
The limit is real and worth repeating. If what you need is a team to design and build the screens, you need a studio or an internal capability, and we will tell you that in the first conversation rather than the fourth.
How to evaluate a UI design consultant
Incluidos nosotros. Estas son las preguntas que merece la pena plantear a todas las empresas de tu lista de finalistas.
- Ask whether they produce the screens or judge them. Both are legitimate. A firm that will not answer clearly is selling you one while charging for the other.
- Ask which metric the interface is supposed to move. Task completion, conversion, support contacts, time to first value. If the answer is engagement, ask what engagement means on this product.
- Ask what they will do with your navigation. A partner who accepts your internal structure as the organizing logic will reproduce your org chart on screen in better type.
- Ask who owns the standards after handover. A component library nobody outside the original team can extend is a deliverable, not a capability.
- Ask where they draw the line on AI features. An interface that presents model output as certainty creates a trust problem no visual treatment fixes. The design question is how confidence, correction and escalation get shown.
UI design consultancy vs digital design studio vs in-house design team?
| Criterio | UI design consultancy | Digital design studio | In-house design team |
|---|---|---|---|
| Qué decide | What the interface is for, the rules it has to obey, and whether a design meets them | What the screens look like, the component system, and the production assets | What ships next, inside the interface structure that already exists |
| Resultado típico | Interface intent, written standards, design review, a brief the builder can execute | Screen designs, design system, build-ready files | Releases, incremental optimization, pattern maintenance |
| ¿Quién lo aprueba? | El liderazgo comercial y el de producto van de la mano, porque las decisiones implican concesiones de carácter comercial | Liderazgo en diseño o en producto | Liderazgo en productos |
| Ángulo muerto | No production capacity, so someone else has to draw and build it | Will render the wrong screen very well | No es fácil cuestionar una estructura cuya medición se realiza durante el transporte. |
| Ideal para cuando | Design work keeps stalling in review, or a refresh has already failed to move anything | The intent is settled and the expression is tired | The standards are sound and the work is continuous improvement |
Trabajos relacionados
Interface questions are rarely only interface questions. Where your problem actually sits decides which of these is the right starting point.
- User experience (UX) design if the issue is the whole path a person takes to get something done, not what the screen looks like.
- Interaction design (IxD) if the question is what happens when a person acts and how the system responds over time, rather than layout and appearance.
- Verbal and visual identity design if what the interface needs is the brand system itself: the type, color, voice and visual language the product should be expressing.
- Customer experience (CX) design if the experience runs across human and digital touchpoints rather than inside a product.
- User insights and research if the honest answer is that nobody knows yet what users are trying to do here.
- Prototyping and testing if a direction needs evidence from real users before anyone commits to building it.
- Digital product creation if the question is the whole product rather than its interface.
This work sits inside our Service Design practice, which treats a service as a promise that has to survive every handoff, and it is delivered at Vivaldi, the strategy firm behind the Demand Landscape and the Interaction Field. On how generative features change what an interface has to communicate, see our view on how AI changes UX and CX design.
UI design consulting in the US and worldwide
Our experience and product strategy work runs out of ten offices on four continents, with the US team in New York. Interfaces are where a multi-market strategy gets tested bluntly: the same screen meets different payment habits, different regulatory steps and different assumptions about what a form may ask. We set interface intent for the markets you actually operate in rather than approving a US design and localizing it afterwards, because the thing that has to change is usually structural rather than linguistic.
Start with the screen your customers get stuck on
A working session on one flow that underperforms: what the interface is supposed to accomplish, and whether the cause is the screen or the product underneath it. You leave with the shape of the problem and where to start.