Ma Certif’ Pro Santé

The founding hypothesis. Every profession has its own framework of actions, written by its national professional council on a common methodological base (HAS). The project rested on an implicit hypothesis: common base, therefore homogeneous frameworks, therefore one interface for all.

What I demonstrated. By crossing the ANS-consolidated data with the 52 source PDFs, the hypothesis proved false: 52 frameworks, 2,951 actions, zero uniform structure. Depth varies from 3 to 5 levels depending on the profession, and the “2 actions per axis” rule everyone believed universal is not: some professions require 3, others count in points, others impose hour minimums. Consequence: impossible to hardcode the rules engine: the database had to parameterise validation profession by profession.

The choice. Rather than waiting for the 52 councils to harmonise (a 12-to-18-month effort), a pragmatic MVP common core: two minimal structural criteria with parameterisable tolerances, and a classification of the 52 frameworks into 5 statuses, materialised in an arbitration file. Result: 45 frameworks integrable in V1, 6 deferred to V2, and one framework discovered entirely missing from the consolidated data, flagged and fixed.

What it changed. The project moved from an implicit “one UI for all” to an explicit MVP scope and a parameterisable base. Not a narrowing: a numbered, arguable reading of what had been an unverified hypothesis.

The old prototype showed cold fractions, a misleading time bar (it conflated elapsed time with progress) and no visible action on arrival. The redesign: a primary CTA on arrival, a countdown instead of fake progress, axes named in plain words, a genuine moment of celebration when the cycle completes. And above all: a theme-based onboarding, so nobody is ever left alone facing 2,951 possible actions.

Rather than stacked panels, a single panel with two states (detail / edit). Attachments are all or nothing: nothing is saved before “Save”, and the guard dialog only appears if you close with changes in progress. Simpler to maintain, cleaner for accessibility.

An empty state is not an error, which is not a loading state. A reference framework still being written by the profession is a legitimate empty state: no red alert, no fake spinner. Every DSFR component choice is defended in meetings on accessibility and meaning, never on taste. Same logic for the guided tour: triggered automatically on first login, because an opt-in tour is never seen.