Why is UX so often reduced to screen design?
The popularity of digital products has strongly associated user experience with websites, mobile applications and software. Job advertisements frequently combine UI and UX into one position, reinforcing the belief that UX mainly concerns the visible part of a digital product.
In practice, UX designers are often expected to:
- create wireframes,
- design forms,
- prepare prototypes,
- organise menus,
- design product pages,
- develop purchasing paths,
- improve button labels,
- design mobile versions,
- hand finished screens to developers.
This scope is necessary, but it represents only part of the work on the experience. Even the best-designed interface will not solve a problem when the process running in the background is inefficient, inconsistent or poorly organised.
A company may create a very convenient appointment booking form, but if employees do not receive the reservation information in time, the customer will still be dissatisfied. A complaint process may be easy to use, but if support staff lack authority to make a decision, the case may still take weeks.
A visually refined customer panel will also fail when the information displayed in it is outdated.
The interface is the visible part of the service, but it is not the whole service. It is the place where the user encounters a business process. If the process is badly designed, a good interface can only conceal the problem for a limited time.
UI, UX, CX and service design – what is the difference?
UI, UX, customer experience and service design are related, but they do not mean exactly the same thing. Their boundaries overlap, yet each of them concentrates on a slightly different level of the experience.
User interface – the interface layer
UI concerns the way a user interacts with a digital product. It includes button appearance, typography, colours, forms, icons, spacing, layout and the way the interface responds to user actions.
A UI designer makes the interface readable, consistent, attractive and aligned with the visual identity. This work is important, but it usually concerns the visible layer of the product.
User experience – the experience of using a product
UX describes the overall experience of using a product or a particular solution. It includes not only appearance but also clarity, logic, ease of completing a task, effort, accessibility and the feeling of control.
A UX designer checks whether users understand the product, can complete a task, know what will happen after clicking and feel that the process matches their expectations.
In practice, UX can extend beyond the interface. Nevertheless, many organisations still limit it mainly to a website or application.
Customer experience – the complete relationship with the organisation
Customer experience covers every interaction between a customer and a brand or organisation. It may begin with an advertisement, a recommendation or a search result and continue through sales, purchase, delivery, support, complaints and repeat purchases.
The customer may use many channels:
- a website,
- telephone contact,
- email,
- a mobile application,
- a physical branch,
- chat,
- social media,
- a paper form,
- direct contact with an employee.
Customer experience helps assess the consistency of all these contacts from the customer perspective. It does not always describe in detail the internal processes and resources required to deliver them.
Service design – designing the entire service system
Service design combines the user perspective with the organisational perspective. The designer investigates what the customer needs while also determining how the company can satisfy that need effectively, repeatedly and profitably.
Service design covers elements that are visible and invisible to the customer. Visible elements may include:
- the website,
- a form,
- a conversation with an employee,
- a point of sale,
- a confirmation message,
- a document,
- packaging,
- the delivery method.
Elements that remain invisible to the user may include:
- IT systems,
- information flow,
- division of responsibility,
- internal procedures,
- employee permissions,
- integrations with other systems,
- settlement methods,
- logistics,
- decision-making rules.
Service design checks whether all of these elements work together and make it possible to deliver a coherent experience.
Frontstage and backstage – two sides of one service
One of the basic ways to understand service design is to divide the service into frontstage and backstage.
Frontstage – what the customer can see
Frontstage includes every element with which the user has direct contact. It may be a website, application, employee, message, service desk, machine, form or helpline.
This is the level at which UI and UX designers most often work. Their task is to ensure that the user understands the available options and can complete the task efficiently.
Backstage – processes operating in the background
Backstage includes activities that the user cannot see but that are necessary for the service to work. Employees verify data, approve applications, prepare orders, transfer information and respond to problems there.
When a customer orders a product online, the frontstage may consist of the product page, shopping basket and payment. The backstage includes:
- updating stock levels,
- sending the order to the warehouse,
- preparing the parcel,
- integrating with the courier,
- issuing documents,
- handling returns,
- updating the order status.
If any of these elements fails, the customer experience deteriorates even when the interface itself has been designed correctly.
Service design requires the simultaneous design of the customer experience and the organisation's ability to deliver it.
Why should a service designer understand business?
A designer does not work in isolation. Every solution operates within financial, legal, organisational and technological conditions.
An idea may be attractive to users but extremely expensive to maintain. It may require additional employees, a new system or a process redesign for which the organisation is not ready.
On the other hand, a solution that is convenient for the company may transfer too much work to the customer. A form may repeatedly ask for the same information simply because the company's systems are not connected.
The designer must balance:
- user needs,
- business goals,
- technological capabilities,
- organisational limitations,
- implementation cost,
- risk,
- delivery time.
A good service designer is not only an advocate for the user. They help the organisation create customer value in a way that can be maintained.
Seven key roles of a service designer
Depending on the project stage and the situation in the organisation, a designer may perform many roles. Not all of them involve creating solutions independently. Often the more important task is enabling other people to reach a decision together.
A service designer may act as:
- a facilitator,
- a researcher,
- a co-creator,
- a communicator,
- a capability builder,
- a strategist,
- an entrepreneur.
These roles overlap and frequently appear at the same time. This is why service design requires a much broader set of skills than interface production alone.
1. The designer as facilitator
A facilitator does not impose a ready-made answer on the team. Their task is to create conditions in which different people can work together towards a valuable solution.
A service project often involves representatives of:
- management,
- sales,
- marketing,
- customer support,
- IT,
- finance,
- operations,
- logistics,
- legal teams.
Each participant sees the problem from a different angle. Sales wants to acquire the customer quickly. Support worries about the volume of enquiries. IT evaluates integration costs. Finance analyses profitability, while legal teams focus on risk.
The designer as facilitator helps reveal these perspectives and structure the discussion. The goal is not superficial agreement but a shared understanding of the problem.
What does facilitation involve?
Facilitation may include:
- running workshops,
- preparing questions,
- organising topics,
- keeping the meeting focused,
- giving quieter participants space to speak,
- resolving misunderstandings,
- visualising the discussion,
- summarising decisions,
- defining next steps.
A good facilitator separates opinions from evidence. If someone says that customers do not need a feature, the designer can ask what data supports that belief. If another person says that implementation is impossible, the facilitator can request a precise explanation of the limitation.
Why is facilitation important?
Many projects do not fail because there are no ideas. They fail because there is no agreement, responsibility is unclear or different departments pursue conflicting goals.
A service designer helps the organisation not only design a solution but also build a shared understanding of the problem.
Facilitation is especially important when:
- the project involves many teams,
- nobody feels responsible for the complete process,
- departments blame one another,
- decisions are repeatedly postponed,
- there is no common definition of success,
- participants use different terminology.
2. The designer as researcher
Service design should not begin with drawing a solution. The problem, context, user behaviour and organisational reality must be understood first.
The designer as researcher does not simply ask customers what they like. They investigate goals, fears, habits, limitations and actual behaviour.
Who should be included in the research?
Research may include:
- current customers,
- potential customers,
- people who abandon the service,
- frontline employees,
- managers,
- business partners,
- suppliers,
- employees responsible for internal processes,
- people handling complaints.
It is important not to focus only on the end user. A service may also be difficult for the employee who has to deliver it. If employees use several disconnected systems, copy data manually or lack access to information, the customer will eventually experience the consequences.
Which methods can be used?
Depending on the situation, the designer may use:
- individual interviews,
- workplace observation,
- contextual research,
- analysis of customer enquiries,
- data analysis,
- surveys,
- process mapping,
- document analysis,
- competitor reviews,
- prototype tests,
- employee workshops.
The designer should also draw on other disciplines. Psychology, sociology, behavioural economics, anthropology, management and process analysis can all help explain human behaviour.
Studying declarations and behaviour
People do not always do what they say. A customer may claim to read the terms carefully but accept them within seconds. An employee may say that the official procedure is always followed, while observation reveals the use of informal shortcuts.
The designer should study not only what people say, but also what they do and the conditions in which they make decisions.
Only the combination of several sources of evidence creates a reliable picture of the situation.
3. The designer as co-creator
Service design should not be performed by an expert working alone and presenting a finished concept to the organisation several weeks later.
A service affects many people and should be created with their involvement. Co-creation means including customers, employees and partners in the search for solutions.
The designer works not only for the user, but also with the user and with the people responsible for delivering the service.
Why is co-creation necessary?
Employees often possess knowledge that an external designer does not have. They know exceptions, unusual cases, system limitations and recurring customer behaviour. Users can reveal needs that the organisation has never recognised.
Co-creation helps to:
- understand the problem more accurately,
- use the practical knowledge of employees,
- reduce the risk of creating an unrealistic solution,
- increase acceptance of change,
- discover less obvious ideas,
- compare different perspectives,
- build ownership of the result.
What can co-creation look like?
It may take the form of:
- ideation workshops,
- joint customer journey mapping,
- prototype building,
- role-playing service scenarios,
- designing new procedures,
- analysing difficult cases,
- testing ideas with users.
Co-creation does not mean that every opinion must be implemented. The designer still has to organise the material, assess consequences and connect user needs with organisational goals.
4. The designer as communicator
Service design requires cooperation between people who speak different professional languages. Developers discuss integrations and architecture. Finance specialists analyse costs. Sales teams discuss leads and conversion. Support teams describe customer problems, while management expects information about risk and return on investment.
The designer as communicator must translate information from one area into a form that others can understand.
Communication is more than presentation
The communicator role is not limited to preparing attractive slides. The problem must be presented in a way that allows different stakeholders to understand its meaning and consequences.
The designer may use:
- customer journey maps,
- process diagrams,
- service blueprints,
- scenarios,
- personas,
- storyboards,
- prototypes,
- research recordings,
- customer quotations,
- service simulations.
Visualisation makes relationships visible that are difficult to explain in a long document. It can show that a seemingly small customer problem results from several decisions made in different parts of the organisation.
Adapting the language to the audience
The same problem should be explained differently to an operational employee, a developer and the board.
For the user, the problem may be a ten-minute wait. For the manager, the relevant issue may be the cost of service. For IT, it may be a technical dependency, while the board needs to understand the effect on customer loss.
An effective designer not only discovers problems but also helps the organisation understand them and recognise that they are worth solving.
5. The designer as capability builder
One of the most important tasks of a service designer may be increasing the organisation's ability to design better experiences independently.
In this role, the designer does not deliver only one project. They help the company learn how to:
- conduct research,
- observe users,
- map processes,
- test ideas,
- cooperate across departments,
- make decisions based on evidence,
- learn from errors.
This role matters because an individual project can quickly be changed or distorted. When the organisation understands service design principles, it can continue improving the solution after the designer leaves.
Why do organisations sometimes distrust design methods?
Some design tools may appear too soft or insufficiently concrete to employees from more traditional disciplines. Workshops, prototypes and maps can be treated as less serious than a financial spreadsheet, a technical report or a formal procedure.
The designer must therefore demonstrate that design methods lead to tangible results:
- fewer errors,
- shorter service times,
- lower costs,
- higher sales,
- fewer complaints,
- better use of resources,
- greater customer satisfaction,
- lower implementation risk.
The designer should explain the value of design in language that the organisation understands. It is not enough to discuss empathy, experience and needs. The effect on results, efficiency and growth must also be shown.
How can capabilities be built?
The designer may:
- run training sessions,
- work directly with teams,
- create guidelines and standards,
- share research tools,
- teach workshop facilitation,
- support the first independent projects,
- create knowledge libraries,
- help build multidisciplinary teams.
6. The designer as strategist
Service design should not be limited to improving existing processes. The designer can also participate in defining the direction in which the organisation develops.
Strategy answers questions such as:
- for whom the company creates value,
- which problem it wants to solve,
- how it intends to differentiate itself,
- which services it should develop,
- which activities it should stop,
- how it should respond to market changes,
- which capabilities it needs to build.
The designer brings the user perspective, experimentation and a systemic view to strategic work.
How can a designer support strategy?
The designer can help with:
- identifying emerging customer needs,
- analysing trends,
- creating new service models,
- exploring future scenarios,
- designing value propositions,
- testing new directions before major investment,
- connecting strategy with concrete customer experiences.
Organisational strategy often remains a high-level document. The designer can translate it into specific actions, processes and touchpoints.
If a company declares that it wants to be the most customer-friendly provider, the designer can help define what this means in practice:
- how quickly the company responds,
- how it resolves problems,
- how returns work,
- how employees make decisions,
- what information the customer receives,
- how the experience is measured.
The designer as strategist turns broad business declarations into real customer experiences and operating principles.
7. The designer as entrepreneur
Every service must not only be desirable for users, but also feasible and economically justified.
A service designer should understand that the organisation has to finance development, maintenance, support, technology and employees. A solution that creates customer value but continually generates losses may not be sustainable.
Which questions should the designer ask?
- What value does the solution create?
- Who is willing to pay for it?
- What costs does the service generate?
- How will the solution affect sales?
- Will it reduce service costs?
- Will it reduce errors?
- Can it be implemented in stages?
- How will the result be measured?
- What risk is associated with implementation?
- How long will the return on investment take?
The designer does not have to be a finance specialist, but should be able to participate in conversations about the business model, costs and benefits.
Design as an investment rather than a cost
If the designer speaks only about improving the experience, it may be difficult to gain support from people responsible for financial decisions. The possible effect on the following should also be shown:
- sales,
- conversion,
- customer retention,
- churn,
- service costs,
- employee time,
- complaint volume,
- operational risk,
- brand perception.
A service designer should be able to demonstrate that a good customer experience can create business value.
Service blueprint as a link between experience and process
One of the most characteristic service design tools is the service blueprint, a map showing how the service operates.
A blueprint may contain:
- customer actions,
- touchpoints,
- employee actions visible to the customer,
- employee actions performed in the background,
- supporting processes,
- IT systems,
- documents,
- information flows,
- problems and dependencies.
This makes it possible to see that one user action activates many processes across the organisation.
For example, a customer submits a complaint through a form. From the customer perspective, this involves only a few steps. In the background, the information may pass through customer support software, the warehouse, finance, the courier and the person authorised to approve a refund.
A blueprint helps identify:
- handover points,
- repeated activities,
- missing information,
- manual data entry,
- risk points,
- unclear decisions,
- dependencies between teams.
A service map shows that the customer experience is the result of the complete system, not only the interface.
Example: designing an appointment booking service
Consider a system that allows customers to book an appointment. A narrowly defined UX project may concentrate on:
- choosing a date,
- choosing a time,
- entering customer information,
- the confirmation button,
- the message displayed after booking.
Service design asks additional questions:
- Where does the system obtain available times?
- Who can change them?
- What happens when an employee becomes ill?
- How is the customer informed about a change?
- Can the appointment be rescheduled?
- How are no-shows handled?
- Does the employee see all necessary information?
- How does the data reach the billing system?
- How does telephone booking work?
- Do the website and telephone service display the same availability?
Only after answering these questions can the complete service be designed. The form itself may be only one element.
Example: designing online shopping
In an online store, the UX designer may work on the search function, filters, product page, basket and checkout form.
The service designer also analyses:
- how stock levels are updated,
- how orders reach the warehouse,
- how products are picked,
- how parcels are packed,
- how courier cooperation works,
- how returns are handled,
- how complaints are handled,
- how delays are communicated,
- how unavailable products are managed,
- how refunds are processed.
If the store displays a product as available while the warehouse does not physically have it, changing the appearance of the button will not solve the problem. The process and data integration must be corrected.
Why are the last three roles particularly difficult?
The roles of capability builder, strategist and entrepreneur require the designer to work at the level of organisational and business decisions.
It is no longer enough to show a problem in the interface. The discussion must include:
- organisational structure,
- investment priorities,
- management responsibility,
- budget,
- strategic objectives,
- profitability,
- risk,
- readiness for change.
The designer may have the necessary skills, but the organisation does not always provide access to these conversations. Designers are sometimes treated as screen producers who receive requirements and prepare visual solutions.
In such an environment it is difficult to influence processes because most key decisions have already been made. The designer can improve the appearance of the solution but cannot challenge its assumptions.
The greatest barrier in moving from UX to service design is often not a lack of tools, but the way the organisation understands the designer's role.
The glass ceiling of the UX designer
A designer may be invited only after the company has already decided:
- which product it wants to create,
- how the process should work,
- which data will be collected,
- which features will be developed,
- how the sales model will operate.
At that stage, the designer can only organise the interface. They can no longer determine whether the product solves the right problem, whether the process is necessary or whether the idea is financially sound.
This creates a self-reinforcing mechanism. The organisation sees designers as people responsible for screens and therefore invites them only to work on screens. The designer performs screen-related tasks, confirming the organisation's belief that this is the complete role.
To break this pattern, the designer must gradually demonstrate the value of a broader approach.
How can a UX designer move towards service design?
It is not always possible to take responsibility for the entire service immediately. The perspective can nevertheless be widened step by step.
Ask what happens before and after the screen
When designing a form, ask:
- Who receives the data?
- What happens to it next?
- How long does the response take?
- What happens when there is an error?
- Does the user have to provide information that the company already has?
Talk to operational employees
People who directly serve customers often understand recurring problems better than managers. They know which questions are repeated, where processes stop and which rules are routinely bypassed.
Map the complete process
Instead of designing a single screen, create a map of the entire customer journey and the backstage processes that support it.
Connect user problems with business costs
If customers do not understand a form, check how many telephone calls the problem creates and how much employee time is spent handling them.
Test ideas before a major implementation
A service prototype may include not only a screen, but also messages, procedures, conversations and employee behaviour.
Learn the language of business
A designer should understand basic concepts related to costs, revenue, margin, risk, efficiency and business models.
How can an organisation use service designers more effectively?
A designer cannot transform an organisation without support from decision-makers. The company must create conditions for work across departmental boundaries.
Useful actions include:
- involving designers early,
- providing access to users and data,
- allowing cooperation with operational employees,
- creating multidisciplinary teams,
- appointing an owner of the complete service,
- allowing ideas to be tested,
- measuring effects after implementation,
- treating research as part of decision-making.
When each department is responsible only for a small fragment of the process, the overall customer experience can easily disappear from view. Service design connects these fragments.
How can the value of service design be measured?
The value of service design can be assessed at several levels.
Customer indicators
- satisfaction,
- abandonment,
- complaint volume,
- task completion time,
- number of errors,
- ease of using the service,
- repeat purchases.
Business indicators
- sales,
- conversion,
- customer value,
- service cost,
- complaint cost,
- customer retention,
- service profitability.
Operational indicators
- delivery time,
- number of manual activities,
- number of handovers,
- number of corrections,
- employee time,
- exceptions to procedures,
- data quality.
A well-designed service can improve the customer experience and make the organisation's work easier at the same time.
Are UX and service design the same?
UX and service design are closely related, but they are not always exactly the same.
UX concentrates on the user experience. Service design additionally examines in detail how the organisation creates and delivers that experience.
A UX designer may ask:
Can the user complete the task easily?
A service designer adds:
What must happen inside the organisation so that the user can complete the task easily, effectively and consistently?
In practice, the boundary is flexible. An experienced UX designer may work with processes, research and strategy. A service designer may also design interfaces.
The title of the role matters less than the breadth of the problem and the decisions that the designer is allowed to influence.
From designing forms to designing value
Designing forms, buttons and screens remains important. Users need a clear interface. However, the visible part of a solution should not be confused with the complete experience.
A designer who wants to create effective services should look beyond:
- a single screen,
- a single channel,
- a single department,
- user declarations,
- the moment of purchase,
- the aesthetics of the solution.
They should understand people, processes, technology and business and be able to connect these elements into one coherent system.
Summary
User experience should not be limited to screen design. The interface is an important part of the experience, but behind every screen there are processes, systems, employees, decisions and organisational limitations.
Service design makes it possible to view the service as a complete system. It combines the customer perspective with the business perspective and helps create solutions that are:
- needed by users,
- feasible to implement,
- convenient for employees,
- consistent across channels,
- profitable,
- possible to maintain and develop.
A service designer may act as facilitator, researcher, co-creator, communicator, capability builder, strategist and entrepreneur. The broader the role, the greater the possible influence on the organisation.
This does not mean that every designer must immediately become an expert in management, finance and operations. It does mean that they should understand the context of their work and ask questions that go beyond the appearance of the interface.
The greatest value of a designer does not lie in drawing screens, but in helping people and organisations create services that genuinely work.
Issues: → user experience, service design, service designer, role of a service designer, UX and service design, UI UX, customer experience, user experience design, service blueprint, frontstage backstage, UX research, workshop facilitation, service co-creation, service strategy, process design, experience design.