UX design and research for digital products.

An upcoming decision is the starting point for UX consultancy. A team may want to know whether a new function is needed or whether people understand an existing journey. These are different questions. The first concerns experiences and tasks; the second concerns interaction with a specific interface.

Describe what should be decided after the study. Existing support questions, a prototype or an observed abandonment help narrow the focus. A general wish for better user experience leaves unclear which change needs examining. A bounded question makes findings easier for product, design and development to use.

User interviews can reveal how people currently work and which information they need. A usability test allows observation of how they complete a task with a product. Someone liking a function does not mean they can find it independently in a test or will need it in everyday work.

Planning therefore considers participants, starting state and task wording. Selection should match the intended use. An experienced user and a new prospect bring different knowledge. Recruitment and study delivery are agreed within the relevant scope; an expert review does not automatically include a full user study with newly recruited participants.

A UX audit needs traceable findings. “The navigation is poor” does not describe where a task fails. It is more useful to record the label someone expected, the route they took and where they needed help. The explanation remains an interpretation until sufficiently supported.

Prioritisation depends on the affected task. A rare error may be critical if it prevents completion; a frequently mentioned detail may be less urgent. Known technical dependencies also belong in the assessment. This turns a report into a justified sequence that guides the next design and development work.

A finding’s form should serve the next step. For a design change, your team needs the affected decision and context. A technical correction also needs expected behaviour. A traceable finding therefore remains useful when someone else implements it or work begins after the initial results discussion.

UX/UI design translates requirements into views and behaviour. A prototype needs a defined research question. An early design can show an information sequence; a more detailed journey can represent selection, feedback and correction. Not every investigation already requires technical implementation of every function.

At handover, it should be clear which findings have been addressed and which questions remain. Development needs states and rules extending beyond an ideal screen. Whether SAND & MEHR only investigates, also designs or subsequently develops is defined in the relevant offer. Your existing team can therefore take over the results too.