Digitising the Canton of Fribourg’s judicial procedures.
Victor Michel took part in digitising judicial procedures in Fribourg: business analysis, BDD specifications and prototypes tried out with court clerks and jurists.
Confidential screens
GovTech · Digital justice
GovTech
digital justice in Switzerland
BDD
requirements turned into testable specifications
Business analysis · UX · Sprint facilitation
The context.
The Swiss justice system has embarked on a digital modernisation effort. As part of it, the Canton of Fribourg undertook the digitisation of judicial procedures: a GovTech project framed by federal and cantonal law. Taking a procedure online is not about scanning a form: the online service has to follow the applicable law exactly.
The future users, court clerks, jurists and other legal professionals, were not all equally at ease with digital tools. Every screen here carries legal weight: a misunderstood field or a step in the wrong order can have consequences for a procedure.
Victor Michel, now the founder of Brutux Studio, joined a multidisciplinary team of project managers, business analysts and developers. He acted as its UX and functional reference: turning requirements into workable deliverables, clearing up ambiguities and supporting users through to acceptance testing. As the project is confidential, this page describes the approach, with no screens or internal details.
The challenge: A statute is not a specification. It describes rights, deadlines and parties, but neither a screen nor a journey. The challenge was to turn judicial procedures into compliant, usable digital services that jurists, developers and end users could all understand, even though they share neither the same vocabulary nor the same priorities.
The approach.
01
Immersing in the law
Victor began by studying the applicable legislation, then held interviews with jurists and court clerks. Understanding both the legal logic and the courts’ day-to-day practice was essential before proposing any journey.
02
Modelling the procedures
The procedures in scope were modelled: steps, the successive states of a case, the parties involved, business rules. This overview gave the whole team a shared understanding of what the system had to handle, and surfaced special cases early.
03
Writing BDD specifications
Requirements were translated into user stories and acceptance criteria in BDD and Gherkin format, backed by detailed documentation. Developers thus had testable rules, each tied to the text it came from.
04
Validating with jurists, testing with clerks
Wireframes were first reviewed by jurists, who vouched for compliance. Prototypes were then tested by court clerks, to check that the screens stayed clear for the people who would use them every day.
05
Facilitating the sprints
In every sprint, Victor facilitated the discussions and resolved the functional ambiguities blocking developers. He arbitrated between what the law required and what could be delivered, keeping compliance as the non-negotiable boundary.
06
Guiding the transition
Finally, he trained end users, ran acceptance sessions and contributed to the digital transition plan. A new tool is only adopted if the people using it have been prepared to change their habits.
What this project taught
On this project, design went far beyond wireframes. Victor acted as the bridge between three cultures, legal, technical and user-facing, that do not speak the same language. The role requires accepting that ambiguity is the normal state of the work, and reducing it patiently, rule by rule, rather than hiding it behind an attractive interface. Only then can a digital public service be both compliant and genuinely used.
What it means for your project
Business software and B2B SaaS products in regulated sectors face the same difficulty: complex rules to turn into simple journeys without losing any compliance. Brutux Studio brings this combination of business analysis and UX design: process modelling, BDD specifications ready for developers, prototypes tested with real users and support through to go-live. With the discretion sensitive projects demand.