Role of the UX/UI Designer: user flow, design and user experience
- Reworking software means taking over existing code to correct it and make it evolve.
- We start by accessing the code, then carry out a free maintainability analysis.
- Depending on the quality of the code, improvements are made using the same technology or part of the code (often the back-end) is overhauled.
- Changing service providers allows you to unlock fixes when the current team is no longer available.
- Updating a language or migrating a technology improves performance and security.
The UX/UI Designer is described as constantly in touch with :
- l’functional analyst,
- the Product Owner / Product Manager,
- then the developers as soon as the project and developments get underway.
Its role with the developers is also to’adapt its design if necessary: modify certain behaviours, clarify what it wants to represent, and “make life easier” for the team by making its intentions clearer.
Useful pages if you are looking for these profiles:
The UX/UI Designer in a development team: his mission
The UX/UI Designer has a central role: he takes concepts and needs, then translates them into concrete elements (screens, behaviours, paths). The aim is not just to produce “pretty things”, but to formalise the user experience.
It is also a role of clarification Making the intention of the functionality understandable to the team (product, analyst, developers) and presentable to the customer.
From the idea of functionality to a clear representation (e.g. Figma)
In the video, the example cited is the use of “type" software. Figma”. This type of tool provides a formal representation of :
- the organisation of screens,
- the information displayed,
- and the way the user interacts with the application.
If you're already working on mock-ups and you're wondering about putting a project created via Figma Make.
UX vs UI: what designers need to formalise
The transcript focuses on two aspects:
- UI (visual) Create the design (colours, screen compositions, details such as the roundness of buttons, etc.).
- UX (user experience) Making it easy to use and understand, and reducing friction.
In other words: the visual rendering is important, but it serves a wider purpose: to enable the user to achieve his or her objective in a straightforward way.
User flow: the first step before “designing”.”
The first thing to do before creating screens is to train the user flow the flow of actions that a user will perform in the application.
Here, we're not “creating” anything yet. We define :
- possible actions,
- the different branches (“if he does this... or that...”),
- and an overall view of the application's behaviour for each feature.
Lighting (general): this work often avoids freezing screens too early on, when the user journey and decisions have not yet been clarified.
Reducing friction: making the application easier to use
Once the itinerary has been clarified, the designer “really starts” to work on :
- make the application and information easier for the user,
- and minimise friction (which slows down, confuses or blocks).
It is this quest for simplicity that often makes the difference between a “functional” application and one that has actually been adopted.
Day-to-day collaboration: functional analyst, Product Owner, developers
The UX/UI Designer is described as constantly in touch with :
- l’functional analyst,
- the Product Owner / Product Manager,
- then the developers as soon as the project and developments get underway.
Its role with the developers is also to’adapt its design if necessary: modify certain behaviours, clarify what it wants to represent, and “make life easier” for the team by making its intentions clearer.
Useful pages if you are looking for these profiles:
Present and defend your choices to the end customer
The designer is also in contact with the end customer, the person in charge of the application. It must present what it has produced and defend your choices :
- colours,
- screen composition,
- interface details (such as rounded buttons),
- navigation logic and behaviour.
This is as much a design role as a communication role: clearly explaining “why” a choice serves the user's objective.
Keeping up to date: UX/UI standards, curiosity and references
Final point: a UX/UI Designer must remain to page, UX/UI standards are constantly evolving. The transcript highlights the importance of being curious and follow referents / mentors of the sector to offer customers the best design.
To remember
- The UX/UI Designer transforms functional ideas into formal representations (e.g. via Figma).
- He works on the UI (visual) and above all the UX (user experience).
- It begins by clarifying the user flow user actions and associated behaviours.
- Its aim is to make information simpler and limit the number of friction.
- He works continuously with the Product Owner, functional analyst and developers.
- He must present and defend his choices to the end customer.
- It remains up to date as UX/UI standards evolve.
The next stage
If you want to frame or reinforce the design part of a product (UX, UI, user flows, collaboration dev), you can :
- Book a meeting with our UX/UI experts
- Contact our UX/UI team for your development projects
- Or Discover our customised UX/UI offer to turn your career paths into interfaces
Tell us about your project
One exchange, a thousand possibilities.
Describe your vision to us using this form: we'll analyse your request and get back to you within 24 hours with personalised advice and a concrete action plan.
We have the team and the resources to help you with your projects. Give us the details in this form and we'll get back to you as soon as possible to discuss them together.
Transforms ideas for functionalities into clear representations (paths, screens) and formalises the user experience. He works on the visual side (UI) and the usage side (UX) to limit friction. UX/UI design in the conception of your application
Clarify user actions and expected application behaviour before freezing screens. This gives an overall picture of the scenarios and avoids designing too early without a logical path.
Check their ability to formalise the user flow, reduce friction and collaborate with the PO/analyst/developers, then defend their choices in front of the client. You can contact a consultant via customised UX/UI consultant
Yes, by starting with the user flow and then formalising the screens and behaviours in a tool such as Figma, to align the team and the customer. The easiest way is to make an appointment with a UX/UI designer in belgium on a niche project
Review the user flow and identify any friction, then adjust the screens and behaviours in collaboration with the developers. Targeted intervention may be all that's needed if the problem stems from the formalisation or non-aligned UI/UX choices.