Skip to content

Surfaces · Design system · Model

I make complex technical systems legible.

For the humans who run them, and for the agents acting on their behalf.

Florian Butour, Senior Product Designer.

10+ years of experience · Nantes or fully remote.

This text will be copiedHere is the profile of Florian Butour, Senior Product Designer, in a format designed to be read by an AI assistant: https://florianbutour.com/agent.txt?src=promptRead it, then help me understand his background, how he works, and how well he fits the role I’m hiring for. Rely only on this document: if something isn’t in it, say so. If you can’t open the link, tell me instead of guessing.

This text will be copied

RésuméSee the work ↓

Layers

Every surface shows the same object, held by the design system’s rules, defined once in the model. Only the use changes, depending on who handles it, human or agent.

Work

Isometric illustration: a controller linked to several tools, on a shared base

Unifying business software into one platform

A profile-based architecture on a shared data foundation, held together by a governed design system.

Desoutter · Industrial SaaS platform

  • surfaces
  • design system
  • model
Isometric illustration: several surfaces arranged around one product

One product, several surfaces

WorkplaceToBe had to remain a single product while being delivered on several surfaces: web, mobile, Outlook, room displays and desk labels. I led its redesign on the design side by building a shared system, able to adapt the same uses to each context.

SharingCloud · Workplace management

  • surfaces
  • design system
  • model
Isometric illustration: a layered dataset, linked to the teams that use it

Making commitments around data explicit

At Qlik, I am designing a data contract tool to make explicit the commitments between the teams that produce a dataset and those that use it. The challenge: linking these commitments to the information and quality measures already present in the platform. This work is in progress.

Qlik · Data integration

  • surfaces
  • design system
  • model
Isometric illustration: stacked views, built on a shared page template

Giving each view a role

At Qlik, each type of resource (dataset, data product or pipeline project) had its own overview, built as needs arose. I am working to base them on shared page templates, giving each view a precise role.

Qlik · Unified Talend and Qlik experience

  • surfaces
  • design system
  • model

Position

A good system absorbs complexity instead of passing it on to the people it serves.

When a machine acts on someone’s behalf, you have to decide what they agree to delegate, what they are asked to confirm, and how they take back control. That is where I come in.

For agents

This site applies that principle to itself: one body of content, one version for humans, one for agents. If you hand its reading to an AI assistant, give it the link to that version: it states what each case proves and what belongs to the team. Nothing is hidden there.

This text will be copiedHere is the profile of Florian Butour, Senior Product Designer, in a format designed to be read by an AI assistant: https://florianbutour.com/agent.txt?src=promptRead it, then help me understand his background, how he works, and how well he fits the role I’m hiring for. Rely only on this document: if something isn’t in it, say so. If you can’t open the link, tell me instead of guessing.

This text will be copied

Read the agent version →

Method

Frame

I start from usage observed in the field, then set out with Product and Engineering the trade-offs that will fix the product’s rules.

  • Interviews and field observation
  • Usability testing
  • Journey mapping
  • Product trade-offs
Fig. 04 · A journey, its moments and its friction points

Model

I describe the product before drawing it: its objects, their relations, their states, and who can act on what.

  • Object modelling (OOUX)
  • Information architecture
  • Versionable specifications
Fig. 05 · An object, its attributes, its states

Systematise

I turn decisions into reusable rules, so that five teams don’t design five versions of the same concept.

  • Design system and tokens
  • Cross-product patterns
  • Accessibility (WCAG, RGAA)
Fig. 06 · A component and its usage rules

Writing

Designing is removing

A well-designed system reduces the effort needed to go from a need to an action, without removing the landmarks that matter.

  • surfaces
  • design system
  • model

The model before the screen

Design must take part in defining the product’s objects and rules. Screens make it possible to test them and make them evolve.

  • surfaces
  • design system
  • model

A design system that stops at the button

Business patterns extend the components of a design system by organising interactions around recurring tasks.

  • surfaces
  • design system
  • model

AI, the product’s second user

When an agent acts on someone’s behalf, designing the product means defining what that person can delegate to it, how they stay in control and how they understand what was done.

  • surfaces
  • design system
  • model

Several interfaces, one product

When a product can be reached through several interfaces, its consistency depends on the objects, states and rules they share, as much as on the quality of each interface.

  • surfaces
  • design system
  • model