Lefebvre Dalloz

Context

Lefebvre Dalloz was born from the merger of several publishing houses into one entity. Each house had its own sites and its own products.

I joined the product team on assignment for Frontguys, with three other designers. The portal already existed: my role was to optimize the mockups and evolve the design system components that had already been created.

Problem

Heterogeneous products, little consistency from one site to the next, and a portal that didn't guide users enough toward the right content. The experience had to be unified without losing what makes each product specific.

Approach and lessons

A weekly meeting brought design and development together: component and feature specs, progress, QA. The components were built in a React Storybook.

Solution

A shared foundation and product-specific components

The design system is built on a shared foundation of common components, completed by components specific to each product. About ten sites have been harmonized and now use these common components, along with two services: GenIA-L and the case law tool.

A configurator by profession

The configurator is a module that lets users quickly find the information or products that match their needs, depending on their profession.

Accessibility

Accessibility became a major workstream for the teams, driven by a member of the product team who was its ambassador. We started by setting the legibility rules: contrast and font sizes.

Boutique unique

A single store for the whole Lefebvre Dalloz offering: reference handbooks, books, digital solutions and subscriptions. The challenge was to make a very broad editorial offering easy to read, from the catalog all the way to the product page.

As UI Product Designer, I challenged the user journeys and wireframes, produced the high-fidelity UI mockups and handled the handoff with the developers and QA, within a team of four designers.

Results

About ten sites are now brought together under a single art direction and rely on shared components.