--- title: "iBanFirst: product design for B2B payments · Enguerran Avril" url: https://enguerran.io/work/ibanfirst lang: en description: "Product design for B2B international payments at iBanFirst: user research, prototype tests, a shared design system and my first Lead role." author: Enguerran Avril --- [Case study](https://enguerran.io/#work) · iBanFirst · 2020–2021 # iBanFirst Designing international payments for businesses from what users actually do, and a first Lead role. - **Company**: iBanFirst, fintech for international payments and currency exchange - **Role**: Senior Product Designer, then Lead Product Designer (UX/UI) in 2021 - **Period**: 2020 – 2021 - **Where**: Paris, then Bordeaux, remote with trips to Paris - **Methods**: Session recordings, prototype tests, interviews ## At a glance ### The challenge A fintech platform for international payments and currency exchange: add and improve features, and understand how businesses really used it. ### What I did Watched real sessions in screen recordings, ran interviews and tested changes as prototypes. Mapped a client’s first weeks and audited the onboarding checklist. Contributed to the design system, then evolved it as Lead. ### The outcome Improvements shipped once users had validated them, payment flows built on shared components, and my first Lead role, in 2021. sources of evidence: recordings, interviews, tests onboarding steps mapped and audited Lead in 2021, after Senior ### Impact +20% of new clients reaching their first payment −25% support requests about payments −40% time to make a payment in a new currency How it was measured: a before/after comparison, including the time to complete the same task before and after the change. [Interactive rebuild, fictional data] The product at a glance, rebuilt for this page in the style of the screens of the time, with fictional data. It works: switch tabs, open a payment, convert an amount. Then take the tour of its pain points. ## The context: The product iBanFirst lets businesses pay and get paid abroad, hold accounts in several currencies and manage their exchange risk. I joined in 2020 as Senior Product Designer. The work was to add and improve features on the platform, and to understand better how clients used it. (image: The Accounts page: a warning that two bank credentials have expired, the iBanFirst accounts with categories and amounts, then accounts held at another bank.) Accounts: the company’s iBanFirst accounts next to accounts held at other banks and linked to the platform, with a warning when their credentials expire. ## The approach: Watching before changing Before changing a journey, I watched it. I analysed user journeys from Hotjar session recordings and heatmaps, tested changes as prototypes in Maze, four or five tests in all with 5 participants each, and ran 10 interviews. Improvements went out once users had validated them. Method What it tells Session recordings Where people hesitate or give up, in the real product. Interviews Why people do what they do. Prototype tests Whether a change works, before it is built. Here is that loop on a single question: paying in a currency the company doesn’t hold yet. [Interactive rebuild, fictional data] A session recording and a prototype test, recreated for this page with a fictional client. Watch the recording, then switch to the prototype and make the payment yourself. ## Sorting what we saw Observations from recordings, interviews and tests went on one wall, then into themes. Tries to pay before adding a beneficiary Recording Clicks a step that is not available yet Recording Not sure the funding step is done Interview What we took from it One clear action per step, in the order the client needs it. Stops at the currency list Recording Do I already have a dollar account? Interview Tell me before it creates an account Test What we took from it Say what will happen before it happens: an account in that currency will be created. Adds up balances from two banks by hand Interview Can’t tell if the supplier has been paid Interview One total, in euros Test Opens Payments to check one transfer Recording What we took from it One balance across banks and currencies, and every payment followed step by step. Balances from the other bank stop updating Recording Didn’t know the bank connection had expired Interview What we took from it Warn when a linked bank needs reconnecting. What the recordings, interviews and tests showed, recreated as an affinity wall for this page. Each note says where it came from. ## A client’s first weeks From the first transfer to the first statement: five steps, mapped from the onboarding checklist. - **What the client does**: Sends money from the company’s usual bank - **What they wonder**: Which of our accounts do I send it from? - **How it feels**: +1 (from −2 (bad) to +2 (good)) - **Where it hurt**: The step’s button says “Add your first beneficiary” - **What we changed**: One action per step, named after the step - **What the client does**: Enters the supplier’s bank details - **What they wonder**: What details do I need? - **How it feels**: 0 (from −2 (bad) to +2 (good)) - **Where it hurt**: Step numbers skip, and steps that are not open yet look like buttons - **What we changed**: Steps numbered once, in order; locked steps look locked - **What the client does**: Chooses an amount and a currency - **What they wonder**: Do I already have a dollar account? - **How it feels**: −2 (from −2 (bad) to +2 (good)) - **Where it hurt**: Nothing says what happens when you pay in a currency you don’t hold - **What we changed**: A note: an account in this currency will be created - **What the client does**: Simulates cover against currency risk - **What they wonder**: What is a hedge, and do I need one? - **How it feels**: −1 (from −2 (bad) to +2 (good)) - **Where it hurt**: “Simulate a hedging”: jargon, and a typo - **What we changed**: Plain words, and what the simulation gives you - **What the client does**: Downloads a statement for the accountant - **What they wonder**: Where do I find it? - **How it feels**: 0 (from −2 (bad) to +2 (good)) - **Where it hurt**: “Generate an extract” twice, described as a payment - **What we changed**: One step, with its own description The onboarding journey as a journey map, recreated for this page from the checklist’s real steps. The feelings curve is illustrative. ## First steps New clients were guided to their first payment by a checklist. Captured at the time, it showed small faults that add up. Fund the account from the company’s own bank, add a first beneficiary, make a first payment, then simulate a hedge against currency risk. The funding step’s button says “Add your first beneficiary”. **Fix** Every step’s button names that step’s own action. Before · capture 1 (image: Capture 1, detail: the funding step, in blue, carries the button “Add your first beneficiary”.) After · rebuilt **Onboarding** We will guide you to set up your account **Fund your account** Transfer money from an account in your company’s name at your usual bank. **Add your first beneficiary** You need a beneficiary before you can make a payment. Add a beneficiary The numbering jumps from 1 to 3. **Fix** Steps numbered once, in order, from 1 to 5. Before · capture 3 (image: Capture 3, detail: after the first step, ticked, the next one is numbered 3.) After · rebuilt **Fund your account** Transfer money from an account in your company’s name at your usual bank. **Add your first beneficiary** You need a beneficiary before you can make a payment. Add a beneficiary **Make your first payment** Pay a beneficiary, in any currency. Steps that aren’t open yet look like buttons. **Fix** Locked steps show a lock, and no button until they open. Before · capture 2 (image: Capture 2, detail: steps 3 and 4, not open yet, look like grey buttons, “Make a first payment” and “Simulate a hedging”.) After · rebuilt **Make your first payment** Pay a beneficiary, in any currency. **Simulate a currency hedge** See how a hedge protects your margins from exchange-rate swings. “Simulate a hedging”: jargon, and a grammar slip. **Fix** “Simulate a currency hedge”, with one line on what it gives you. Before · capture 2 (image: Capture 2, detail: step 4, “Simulate a hedging”, described as “Creation of your foreign exchange risk management strategy”.) After · rebuilt **Simulate a currency hedge** See how a hedge protects your margins from exchange-rate swings. “Generate an extract” appears twice, described as a payment. **Fix** One step, “Download a statement”, with its own description. Before · capture 2 (image: Capture 2, detail: steps 5 and 6 are both called “Generate an extract”, with the description “It’s time to make your first payment to a beneficiary”.) After · rebuilt **Download a statement** Get a statement of your accounts for your accountant. Five faults found on three captures of the checklist from the time. For each, the detail of the capture that shows it, then the same part of the corrected checklist, rebuilt for this page. ## The solution: Making a payment The payment flow opens from the dashboard, in a panel that shows where you are. The panel shows each step and its progress. If you pay in a currency you do not hold yet, it tells you an account in that currency will be created. (image: Empty. Add a beneficiary first.) **Empty** Add a beneficiary first. (image: Filled. Euros chosen; a note says an account in that currency will be created if needed.) **Filled** Euros chosen; a note says an account in that currency will be created if needed. (image: In progress. Details done; review and validate are left.) **In progress** Details done; review and validate are left. The real payment panel in three states. [Interactive rebuild, fictional data] The payment flow as it lived in Figma, recreated from the screens above: the frames in order, and the prototype links between them. ## The design system I contributed to iBanFirst’s design system, then evolved it as Lead. The payment flows are built from shared components: amounts with their currency, payment statuses, steps, alerts, account rows. [Interactive rebuild, fictional data] Components of the payment flows, recreated for this page in iBanFirst’s style. Change their properties and read their rules. ## Decisions that shaped it Three choices made the difference. ### Watch real sessions before redesigning. - **Why**: Recordings show where people hesitate or give up in the real product; interviews say why. - **What it led to**: Changes tested as prototypes with users, and shipped once they had validated them. ### Fix the small faults of the first steps. - **Why**: A new client’s first weeks decide whether the platform becomes a habit, and small faults add up. - **What it led to**: A map of the first weeks and an audit of the onboarding checklist, fault by fault. ### Say it before the system does it. - **Why**: Paying in a currency the company doesn’t hold yet creates an account in that currency. - **What it led to**: A payment panel that says so before you pay, and shows each step and its progress. ## The result: Becoming Lead In 2021 I became Lead Product Designer (UX/UI). I evolved the design system I had been contributing to, ran design operations day to day, and shipped key launches with product managers and engineers, validated with users along the way. The same year I moved from Paris to Bordeaux and kept working remotely, with occasional trips to the Paris office. In October 2021 I joined Ogury as Lead Product Designer. A product that got too complex, a design team to structure, a design system to set up? I can help, as a freelancer. Write to me. [enguerran.avril@gmail.com](mailto:enguerran.avril@gmail.com) [Next case study](https://enguerran.io/work/criteo/) Next case study Criteo