Digital interfaces support the tasks your users actually need to complete. Develop user journeys, information structure and interface states and test them through relevant tasks.
Develop user journeys, information structure and interface states and test them through relevant tasks.
The central objective is: Digital interfaces support the tasks your users actually need to complete.
Users do not understand the next step and internal opinions replace evidence from use.
Develop user journeys, information structure and interface states and test them through relevant tasks.
Prepare acceptance and handover: Agreed prototype with components, interaction states and a traceable developer handover.
Review clarity and usability.
Does this fit your situation?Five short answers turn an initial idea into a first brief.
Check the fit ↗An illustrative workflow for a UX/UI designer. Select a step to see what may be prepared and handed over.
Illustrative scenarios for orientation. Scope and outcomes are agreed for each assignment.
Examples, not a blanket delivery promise. Choose the outputs your project actually needs.
For a UX/UI designer, a traceable working approach matters. With VB Analyst, your task becomes a search brief with verifiable essential criteria.
Trace an observed usability barrier to a design decision; separate assumptions from tested findings.
Anonymised examples suffice for an initial assessment. References, qualifications and availability are clarified for the assignment; a tool list alone does not establish suitability.
An experienced specialist fits a well-defined package. Senior or lead experience matters more when the approach, interfaces or acceptance remain unclear. A junior profile needs a named specialist reviewer.
Applied to: Develop user journeys, information structure and interface states and test them through relevant tasks.
Hybrid work helps when decisions involve several teams or workshops. Analysis and documentation can be remote with suitable access.
Users do not understand the next step and internal opinions replace evidence from use.
For reference and preparation of your search brief.
Develop user journeys, information structure and interface states and test them through relevant tasks.
Agreed prototype with components, interaction states and a traceable developer handover.
Computer science, media informatics or interaction design; alternatively vocational IT or design training with relevant work samples.
These are possible professional routes, not a universal degree requirement. For this role we review experience with a comparable task, technical depth and the ability to document a handover. Required degrees and evidence are defined in the specific search brief.
Possible working environment; the actual combination depends on the assignment.
Connect your task to relevant capabilities. A tool selection narrows the working environment; the results explain each professional connection.
The professional connection becomes clear through tasks and possible outputs.
Develop user journeys, information structure and interface states and test them through relevant tasks.
Agreed prototype with components, interaction states and a traceable developer handover.
Plan research questions and study approaches. Analyse interviews or tests systematically.
A source-based user research report with product implications.
Align labels and messages with user tasks. Keep terminology and error messages consistent.
A tested interface content design with documented language rules.
Capability profiles for orientation. An individual’s suitability is assessed against the search brief.
Refine the selection ↗This may not be the right role if your main priority lies elsewhere. These profiles help clarify the difference.
This overview describes typical areas of responsibility. Actual scope may vary between organisations.
| Criterion | UX/UI designer | UX Researcher | Interaction Designer | Service Designer |
|---|---|---|---|---|
| Core task | Develop user journeys, information structure and interface states and test them through relevant tasks. | Plan research questions and study approaches. Analyse interviews or tests systematically. | Design states and transitions for user journeys. Test prototypes against concrete tasks. | Map touchpoints and internal workflows together. Improve gaps and handovers with stakeholders. |
| Possible outcome | Agreed prototype with components, interaction states and a traceable developer handover. | A source-based user research report with product implications. | An agreed interaction prototype with clear state rules. | A service design with traceable roles and transitions. |
| Working environment | Figma, Miro | Miro, Figma | Figma, Miro | Miro, Figma |
Unsure which role fits?Start with your goal and your team’s tasks.
Start the role finder ↗Complementary roles address adjacent tasks. They are not automatic substitutes for a UX/UI designer.
Prioritise user problems and objectives. Support product decisions with data and feedback.
A reasoned product roadmap with measurable learning questions.
Implement PHP applications, data access and interfaces with traceable validation and tests.
Tested web feature with error handling, data-flow documentation and maintenance notes.
A managed service requires defined inputs, scope and approval paths. These services provide a starting point for that definition.
Defined mobile features with device testing, state handling and a documented release.
Choose work packages ↗A usable web feature with a clear interface, tests and well-defined integrations.
Choose work packages ↗For agencies and service providers: White-label delivery can align formats, approvals and communication under your brand. Client access and responsibilities are agreed in advance.
Five questions, a reasoned assessment and a brief for your enquiry. You can change every answer.
A capacity gap does not always require a permanent role. Choose a model by responsibility, duration and desired outcome.
Which workflow should which users complete, and can relevant participants be involved?
Agreed prototype with components, interaction states and a traceable developer handover.
You can leave undecided details open. Non-confidential information is enough for initial contact.
Selected model: Project support
Discuss these requirements ↗View this model and its responsibilities ↗We clarify the task, priority and outstanding requirements with you.
Relevant experience is assessed against the assignment. Open questions and working parameters remain visible.
You decide through specialist discussions. Capacity, terms and responsibilities are agreed.
Access, the first milestone, contacts and handover are established.
Timing depends on suitable availability, selection, agreement and access. For urgent needs, separate essential initial work from later tasks. A binding start date is confirmed for the specific assignment.
Short answers for your next step. We can work through your specific situation together.
Discuss my question ↗Develop user journeys, information structure and interface states and test them through relevant tasks. One possible outcome: Agreed prototype with components, interaction states and a traceable developer handover.
Trace an observed usability barrier to a design decision; separate assumptions from tested findings.
Possible working environments include Figma, Miro. The required combination depends on your assignment. Not every listed tool is a mandatory requirement.
The profiles describe capabilities and typical assignments. Actual people, availability, terms and engagement are assessed for your specific need.
