In 2014, Ornikar sold driving licences without a driving school licence: the commission turned down every application, the unions took it to court, and the licence only came in 2016 with the Macron law. An Ornikar student learns the theory online, takes lessons with an independent instructor and sits the test as an independent candidate. So they have to be registered with the driving licence office of their département. There are ninety-six of them, each with its own forms, its own lead times and its own reading of the same texts, which lived in the practice of the counter staff and nowhere we could read them.

A startup that has just raised has an implicit brief, the acquisition curve. The problem I saw in the tickets was elsewhere: a student who has paid and cannot get registered asks for a refund and leaves a bad review. Every cohort produced some, each more costly than a student never acquired. I put the product effort on registration.

Three stages, in this order

1By hand
Student→Support team→96 offices

An in-house support team takes every registration and carries it to the right office. Each file teaches one more rule. Not a line of code until the real rules are known.

2Automate
Student→Ornikar→96 offices

When support has no more surprises on a département, what it has learnt becomes code. Automating earlier would have encoded assumptions. The rest still goes through support, which is left with only the special cases.

3Remove the friction
Student→Ornikar→96 offices

Forms, documents, messages, redesigned without assuming anything about the person on the other side. Every step removed on the student's side is a step support had first done by hand.

The order mattered, because each phase produced the knowledge the next one needed. Support was not a cost centre, it was the product's learning organ, and I had to defend it as such in front of founders and investors who expected a curve rather than a team.

The journey, before and after

Before
After
Payment
The student pays.
The student pays.
Documents
Sent by email, checked by support, département by département.
Guided form, documents checked as they are entered.
Registration
By hand at the prefecture, weeks of back and forth.
Rules encoded per département, registered without our help.

The rule that decided the order

Until a rule has been verified on real files, it does not go into the product.

Every screen designed on an assumption about the student, a computer rather than a phone, an easy reading of administrative French, papers in order, broke on the first hundred users. The product addressed the whole population that takes the driving test: no assumption was allowed about equipment, ease with written language or the validity of papers.

What came of it

15,000paying users in eighteen months, starting from zero.
2015Strategic Design Trophy, service design category.
+1Mregistered users since, and 145 million dollars raised between 2018 and 2021, on this registration foundation.

Refunds for failed registration stopped being a cohort issue, and the registration chain grew with the cohorts instead of growing against them. The mockups of the time were in Sketch and were not kept: this page rests on the facts, without screens.