Visual — heroFragmented submissions → structured collection and validation. The dashboard is secondary.
Past work
Natixis — Hestia
Turning a 500-page risk report into something people can actually read.
Natixis Risk wanted to move a heavily manual reporting process into a digital product. The report was around 500 pages and depended on roughly twenty departments filling in their own Excel files before the Risk team consolidated and checked everything. There were two separate problems: errors were entering the process very early, and even a correct final report was too large to understand at the right level of detail.
(01) Collection
Fix the input before polishing the output
Redesigning the final dashboard would not stop the same mistakes arriving from every department.
So the product work started earlier in the chain. Free-form Excel submissions became a more structured flow with expected formats, checks at the right moment and a human validation step before information entered the consolidated report.
The brief
A dashboard for the executive committee
The request at the start: consolidated risk reporting for decision-makers.
What shadowing showed
The errors came before the dashboard
Reports arrived from many teams in different Excel formats. Consolidating them by hand created errors and delays.
What we built
Fix the collection first
A dynamic questionnaire, automatic checks and a human validation step, then a dashboard fed with validated data.
The goal was not to remove Risk validation. It was to stop skilled people spending time on formatting mistakes and missing fields that the product could catch earlier.
Product
Structured collection, then validation
Collect in one format
- A guided questionnaire replaces free-form Excel submissions.
- Contributors upload in the required format, with a template to start from.
Check and validate before consolidating
- Common problems are caught early by automatic checks.
- Every contribution has a visible status, and a person validates it.
(02) Dashboard
Keep the 500-page depth without showing 500 pages
The harder part was information depth. An executive needs the overall picture quickly; a Risk specialist needs to drill into the underlying detail.
The dashboard therefore works in levels: overview first, then progressively deeper views by department, category or issue. Access rules follow the same logic because not every user should see the same information.
I leave out the old time-saving and error-reduction figures: the way they were measured can no longer be checked. The work stands without them: quality control moved upstream, and a very large report became usable at different levels.
