Our method

Getting the most from your teams.

With design-driven development, we first design and validate the right tool as a prototype with your teams, before a single line of code is written. Then we build it in visible stages. You keep control of the decisions. We bring the method and the expertise.

The principle

Co-design never starts from a blank page.

We listen to your business, propose solutions, put them to the test and decide with you.

A workshop around a table: a team listening to a presentation
Design workshop · Montpellier

Starting point

You know your procedures. We know IP firms.

You come with your ways of working, often manual or poorly tooled. Workshops bring decision-makers, business teams and future users together to analyse them on real cases and turn them into a product.

Spot the friction

Analyse your procedures with the teams who apply them, from everyday cases to exceptions.

Propose options

We draw on our knowledge of IP firms to flag dead ends and propose solutions, discussed in the session.

Validate before building

Test journeys and screens on a prototype. Every decision is recorded and sourced.

Phase 01 · Design together

As many sessions as needed, with the teams who do the work.

An agenda before, minutes after, mockups updated for the next session.

  1. 01

    Map what exists

    The process as it is practised today, drawn in the session with the teams: who does what, when, with which tool. The first mockups are shown from this session on.

    DeliverableMap of the current process, pain points, open questions

  2. 02

    Put everything on the table

    Real cases, exceptions, expectations. Everything is written down, then sorted between what goes into the first version and what comes later.

    DeliverableFunctional dossier and V1 scope

  3. 03

    Test the prototype

    A prototype that behaves like the application, used in the session every week. Exchanges with the IPMS are settled as the sessions go.

    DeliverableValidated prototype, data exchanges described

  4. 04

    Approve the specification

    Every decision is gathered into rules. Each one points back to the session and the minute it was taken. The teams review the document before development.

Phase 02 · Build and deliver

From prototype to production, with no black box.

  1. 01

    Validated prototype

    Priority journeys and rules reviewed with users.

  2. 02

    Visible development

    Short increments, regular demos, useful feedback.

  3. 03

    Guided acceptance

    Scenarios prepared with your teams, traceable issues and criteria.

  4. 04

    Go-live

    Cutover, data migration, training and follow-up, then support and evolutions.

The Arkyan team’s bright open space, screens and tall windows
The Arkyan team at the Montpellier office

Let’s start with a first conversation.