Project informations
We were in charge of revamp the entire mobile app regarding a cross-platform technology and add 8 new features
My role
Product designer
Credit
VP Digital
Laurent Bernardin
Head of digital
Marc Folliot
Project manager
Nour Ayoubi
Rob Fenton
Yohann Denechaud
Lead designer
Designer
Josselin Bodan Théo Grandin Camille Chauve Flore Thauvin Gaetan Avez
Outcomes
+800
Screen made
8
Sprints
15
Week of works
Overview
In large companies, inertia slows down decision-making, creating a gap between design and feature validation. Late feedback on mockups creates confusion, a lack of context, and a loss of focus, making project management difficult for clients.
The project, structured into five distinct groups (decision-makers, CMA, Singulier, Squad developers, and the internal team), required the establishment of a single source of truth to effectively coordinate these stakeholders with diverse knowledge and manage personnel changes during the project.
3 takeaways
01 · Rethink our methodology to increase velocity
02 · Bring back lot of projection
03 · Build adhoc deliverables to infuse design accross teams
01
Rethink our methodology to increase velocity
Look for clean and reformulate our works to be transmitted well between hierarchical levels. Rethinking the way we work. Managing the Figma design file and prototype inertia. Is it worth it for all types of projects
Even though it was simple, it had become necessary to enter the figma, we couldn't stay in the prez, especially because of their need to project ourselves. The problem is that the file has become much too difficult to understand.
Our worflow
Articulate the screen library and screenflow in this new flow
The collaboration process with CMA revolves around at least two weekly meetings dedicated to presenting the userflow and new screens. Upstream, the team prepares its iterations in the war room and then, once validated internally, integrates them directly into the screen library without going through the UI Kit.
After publishing this library, the screens are injected into the presentations and the screen flow, thus creating a single source of truth for the client. This method has the dual advantage of centralizing all feedback on a single document (the screenflow we share to the client) and simplifying updates, since any changes to the screen library are automatically propagated throughout all documents shared with the client.
02
Bring back lot of projection & context
During client presentations, we have formal support in the form of decks, which allow us to present screens in a clear and structured manner. If we need more detail, we have the option to explore the project directly in Figma.
Rather than showing the "war room," we opt for the screenflow presentation. This highlights the flows and sequence of screens, thus providing a more organized overview. In addition, we add comments, similar to what we currently do when the client makes comments. This allows us to keep track of discussions, having the context of comment and adjustments to be made.
We have a scrolling of screens in a slide format which allows us to have content that can be easily shared across teams on the client side: a familiar slide format for the teams, with the possibility of exporting it to PDF if necessary. We can add visual elements that will bring context and projection into the overall flow (trigger, links to other flows, modals, version to show iterations).
In short, it is a format that allows us to have a global overview, while remaining in the context of the flow and providing projection and reassurance for the client, without necessarily getting used to our rhythms, our speed and our jargon.
03
Infuse design & work asynchronously
After the presentation, we made the files public by sharing them with CMACGM so that they could give their feedback more calmly because they needed to discuss it among themselves given the number of POs gravitating towards each of the features.
This approach offers several advantages for the client. It allows for self-review, allowing the client to review the project at their own pace and share it with other departments for additional feedback.
It also facilitates internal discussions among the client's team members, allowing them to sit down and exchange ideas. Additionally, the client can provide consolidated feedback while maintaining the context with the screenflow. Finally, explanatory videos accompany the prototype to clarify the flow and thinking behind the design.
In the other hand, this approach allows our team to start working on another feature, while receiving quality feedback on the screenflow through comments or via email. Ultimately, we managed to meet the deadlines despite the large number of features and screens to create.
In addition, we delivered a concept book to compile and centralize our ideas not implemented during this sprint.
