Espace Territoires · Citeo

SKU PROJ-002 · Release 2024 to 2025

Espace
Territoires

Product design UX research Back office

Every declaration was paid for twice: by the local authority filling it in, then by the team validating it. Both sides tackled: 30 to 50% time saved on some declarations, 80% on internal validations, and the equivalent of one and a half full-time roles freed up each year on contract validation.

30-50% time saved on some declarations
80% time saved on internal validations
1.5 FTE full-time equivalent freed up each year on contract validation

Spec sheet

Role
Consultant Product Designer, within the Citeo mission.
Goal
Make declarations simpler for local authorities and operators, and lighter to process in the back office.
Duration
A workstream within the Citeo mission (2024 to 2025).
Team
PO, developers, QA, back-end architects and the business teams on the validation side.
Tools
Figma, Storybook, Screeb, Daxium, interviews, unmoderated tests and guerrilla testing.
Tracked indicators
Time per declaration, internal validation time, usage measured continuously (Piano Analytics, Screeb).
Industry
Circular economy: Citeo.

The problem

Espace Territoires is the tool behind Citeo's 3R vision: local authorities and companies declare their operations there to receive their funding, and account managers process them in the back office. But the journeys were heavy, field data entry (Daxium) was painful, and user and entity management relied on Salesforce, which was critical and hard to adapt.

The method

01 A dedicated journey for operators (OPC / OPR)

The first deliverable was an MVP, for private collection and reuse operators. Framing was done with the business teams, the main flows were laid out as wireframes, and the design system was audited to reuse or create components. Developers were in workshops from the first iterations. Before release, unmoderated tests with the business teams helped sharpen the wording.

Citeo's Espace Territoires: adding a user and managing access

02 Field data with Daxium

The characterization tool was explored through interviews about daily usage (long processes, heavy steps, unintuitive interfaces), cross-checked with a quantitative survey. The findings were presented to the Value Leaders, then prioritized with MoSCoW: the improvement roadmap now rests on facts.

Daxium, the field data entry tool studied during the mission (vendor demo screen)

03 Redesign user and entity management

Critical features moved out of Salesforce into internal systems that are easier to adapt. A discovery across about ten Citeo products was summarized as “Product Personas”, and the data architecture and governance model were then built with the back-end architects. Finally, a week of guerrilla testing, with prototypes in users' hands, made it possible to adjust before launch.

Tracking collections and declarations in Espace Territoires

The outcome

Ten minutes saved per declaration, meaning 30 to 50% less time on some. OCR was also built into the validation journey, and the Figma files were tidied up along the way. The access redesign and the Daxium workstream are moving forward step by step: each change is measured before deciding to continue or pivot.

They said

Matteo gave us the necessary step back by re-challenging certain decisions to make our product smoother and easier to use.
Jordan Tahraoui · Product Owner, Citeo

Other drops

SKU PROJ-003 Clearing · Gireve → SKU PROJ-004 Digital twins · CEA → SKU PROJ-005 KYC · AXA France →

Want to talk about it?