The problem you're facing
Your users abandon, make mistakes, call support: the interface imposes the system's model instead of fitting theirs. Every friction is a recurring cost : invisible in mockups, obvious in metrics.
Our answer
We design from real users: research, tested wireframes, clickable prototypes, then high-fidelity design documented in a design system development can implement directly.
What LaMeDuSe Design takes care of
- User research and existing-product audit
- Tested wireframes and user journeys
- Clickable prototypes for validation
- High-fidelity design (mobile, tablet, desktop)
- Design system: components, tokens, documentation
- Development-ready specifications
- Accessibility (WCAG) built into the design
Our methodology
- 1
Immersion & research
Users, usage contexts, product constraints: design starts with understanding, not drawing.
- 2
Exploration & wireframes
Sketches, wireframes and journeys tested before any pixel: structure before skin.
- 3
Design & iterations
High-fidelity mockups, clickable prototypes and iterations with your user feedback.
- 4
Handover & design system
Source files, documented components and specs ready for development.
Tools & methods
Confidentiality
Source files are yours, licences verified for all assets, and confidentiality on your unannounced projects.
Hosting & handover
Deliverables integrate with your tools; for products we develop, the group's European hosting is available.
Design evolution
Design system evolution, new screens and iterations through product versions : with the same design team.
Why LaMeDuSe Design
We design the interfaces of products the group develops and operates: the design we deliver is designed to be implemented : and it is, by teams working alongside ours.
Frequently asked questions
UX handles the experience: journeys, logic, friction. UI handles the interface: colours, typography, components. One without the other gives pretty-but-unusable screens, or usable-but-inconsistent ones. We handle both, in that order.
Yes, systematically: complete Figma files, named components, tokens and documentation. Sources are yours : you're not hostage to the relationship.
Yes: we deliver in the formats development expects (specs, tokens, components), and we talk with your developers during design to avoid implementation surprises.
Depending on scope: a few weeks for a module, 2 to 3 months for a full application with research and design system. The timeline is put in writing at scoping.
Got a project in mind?
We support you from idea to delivery, with responsiveness and precision.