Senior Product Designer currently working at Oplit

Situation

When I joined in June 2022, the PrestaShop "design system" was a set of advanced UI kits in Figma, not shared as a true library. Product designers worked with their own components, tech teams used a separate framework, and interface consistency was weak.

With multiple touchpoints (main product, help center, marketplace, academy), alignment was critical to scaling both product and brand.

Tasks & Actions

• Structured the design system team and implemented shared ownership around a unified workflow.
• Set up contribution processes, component review cycles, and regular design-tech alignment meetings.
• Built a transparent Kanban in Notion, accessible to both design and tech, to track every component request and status.
• Audited the existing system and produced actionable recommendations to realign the system for future growth.
• Pushed adoption of documentation standards, making documentation a Go/No-Go criterion for any new component.
• Introduced and started implementing design tokens, following best practices for primitive and semantic layers.

Results

• Implementation of design/tech contribution processes, documentation, comprehensive auditing, governance, and shared Kanban.
• Initial implementation of design tokens on test projects (inspired by Nathan Curtis).
• Reduction in design/documentation debt, alignment with tech on nomenclature.

Next Steps

• Ongoing documentation standardization across all components.
• Rollout of experience libraries for specialized squads, maintaining brand and UX alignment.
• Continued monitoring of DS adoption and iteration of governance processes.

Situation

PrestaShop users struggled to manage their interactions due to three separate accounts: Back Office for shop management, Marketplace account for module purchases, and User account for business care subscription invoices.

These fragmented systems created confusion, inconsistency, and inefficiency. Basic actions like updating emails or passwords required users to contact technical support, leading to unnecessary delays.

Tasks & Actions

• Led exploratory user research, competitive benchmarking, and co-creation workshops to pinpoint pain points and user needs.
• Oversaw the consolidation of disparate user databases into a single source of truth.
• Redesigned the UI to clearly distinguish personal and business information.
• Prioritized must-have features: self-service for updates, account deletion, and unified billing management.
• Streamlined onboarding by encouraging Google account creation to reduce friction.

Results

• Full user autonomy over data, eliminating dependency on support for updates.
• Data consistently synchronized across all PrestaShop services.
• Increased user satisfaction through positive feedback.
• Streamlined processes for billing and account management.

Situation

PrestaShop users faced multiple points of authentication (product, marketplace, help center, back office), with no consistent flows or shared data. The lack of synchronization between databases resulted in duplicate accounts and authentication failures.

Until recently, there were 2 connection modes (SSO & Connection by ID). The objective was twofold: increase SSO registrations & connections, and make users understand they only need one PrestaShop account.

Tasks & Actions

• Conducted an in-depth audit of existing workflows, identifying sources of confusion and friction.
• Mapped and consolidated all user data sources to a single database.
• Completely redesigned authentication screens and flows to educate users on the "single account for all PrestaShop" model.
• Prioritized SSO integration and shortened onboarding to three key steps.
• Introduced clear error messaging and education around the new account structure.

Results

• One unified interface across the product for account creation and connection.
• Support requests related to authentication dropped significantly.
• Users responded positively to the new, simplified experience.

Situation

The shop association process, particularly for open-source installations, was a major source of confusion. Merchants didn't understand why association was required and abandoned the process — especially when errors occurred.

The association exists because most users have Open Source shops installed locally on their hosting, not always identified as belonging to the owner account. Association creates this connection.

Tasks & Actions

• Conducted research to identify key pain points and abandonment triggers.
• Redesigned the flow to require only the necessary information, providing clear guidance and error correction.
• Modeled the new process on the SaaS "Edition" experience, offering seamless association for recognized shop owners.
• Prototyped the new flow (including a demonstrative video) and validated improvements with stakeholders.

Results

• Major improvement in user comprehension and reduced frustration.
• Most shop traffic now flows through the updated payment platform and onboarding.
• Unified the experience with the "Edition" SaaS model for consistency.