BNP Paribas Fortis · Service design and UX · 2018-2019

The bank had the data.
The merchants had the questions.

The POC gave the figures. It did not give the answer. I turned it into a tool that puts the decision keys in the retailer's hands: what is moving in their shop, the action to try to lift revenue, and what it brought in. Léonidas said yes before the product was developed.

Try the prototype

901directly addressable merchants
15 → 2steps to grant access
6/6merchants validated the concept
0calculation left to the merchant
01The market segment

Easy Banking Business is open to the contract holder, not to the person who runs the shop.

  • What these numbers measure: access to the portal, not interest in a service that did not exist yet.
  • What they hide: access is personal.

So the service was aimed at a user without the key. Handing over that key without a banking procedure became a design problem in its own right.

02Targeting

The target: several outlets, no tool to read them together.

  • A refusal qualifies better than a yes: the best-equipped segment declines, and its reason points to where the service is useful.
  • What the target does not have: no data practice. It compares its stores from memory, or not at all.

She had never had these indicators: her position in her sector, what the neighbourhood buys, her average basket. With no practice in data, the product will have to conclude for her.

03User roles

One service, three jobs, three expectations.

  • The role that decides is not the role that executes: one arbitrates between shops, the other acts on his own.
  • What separates them is neither age nor sector, but the power each has over the product, the contract holder is not even an occupation.

So the settings are not an admin screen. They are a feature, and every threshold states plainly what it changes in the reports.

04The benchmark

Two players on this ground, no competitor in Belgium.

  • Proximus sells geolocation: who walks past the window. The bank sees what was actually bought.
  • BBVA already earns real revenue from it, but in Spain. A foreign bank does not take this market, it proves the market exists.

So the ground was free. What remained was the real obstacle, and it was not competitive: opening the service to the people who run the shop.

05What the data could do

Two sources in the same hand.

  • The raw material is vast: business accounts on one side, card payments on the other. Raw, it answers nothing.
  • The work was to aggregate it for him: the merchant has neither the time nor the practice to look for the useful cross-readings.
  • That is what the workshop was for: the aggregations named one by one, then sorted into four categories.

Aucun des acteurs du benchmark ne tient les deux sources à la fois. C'est le seul avantage que le projet peut revendiquer sans le documenter davantage.

06The value proposition

The Ad-Lib: the value proposition in one sentence.

Product or service

Our goal-oriented report, built into Easy Banking Business

Customer segment

helps chain managers who run several outlets

Job to be done

who want to keep control of their business, learn and act, then measure the effect of what they did,

Customer pain

by sparing them any calculation to do themselves

Customer gain

and by giving them the crossing of customers, neighbourhood and sector, plus the ranking of their own shops,

Competing proposition

unlike catalogue-of-metrics dashboards, which deliver the data and leave the conclusion to the user.

What stayed out, and why

  • The MVP tests one thing only: does a merchant come back to read what the bank tells him about his business?
  • The marketing campaign: four pieces of content ready, which do not prove market appetite.
  • The market study: the tab is already in the nav, the design comes with traction.

The scope was not settled in a document. It was settled on the wall, in front of the POC printouts, and it never reopened.

07The design pivot

Free exploration becomes four goal-driven reports.

  • Free exploration is not for our persona: research showed it: he has no practice with big data.
  • Hence the goal-oriented approach: data sorted by type of need, with its KPI and the action to take.

We remove nothing, we combine. Choosing which cross-readings matter is our job, not the merchant's.

08The MVP

A scoped MVP, ready to prototype.

Pain points turned into added value, and gains created by the right aggregation of the data. Those gains, nobody could have asked for.

What am I actually going to use this data for?

Noted in the interviews: the figures were accurate and readable, but the interpretation was still left to do. Without training in statistics, a merchant has no reference points to do it alone.

Every chart comes with its conclusion written out.

  • An alert with the number, the reason, the hypothesis to test, the estimated gain.
  • Never a bare chart, never a statistical term, never a meaning carried by colour alone.
  • The product takes a position: it says what is moving, why, and what it is worth.

Only card transactions go into the calculation.

Not cash, not payments taken elsewhere. And for comparisons, only the bank's own customers. A figure whose base you do not know is worth nothing.

Every figure says where it comes from.

  • A help icon on every indicator, the calculation set out in plain words.
  • The thresholds are the ones the contract holder set themselves.
  • The uncertainty is stated in the product, not in a footnote.

I get statistics, not new customers.

Banking data is anonymous and aggregated. It will never give a name, an address, a way to contact anyone in particular. The objection is real and there is no way round it.

No names. Movement, and what it means.

  • Won, loyal, lost, with the sentence that adds them up.
  • “Your growth rests on new customers, not on loyalty.”
  • The answer is partial, and the page says so.

Are these really the right competitors?

The POC left two comparison columns to configure yourself. Choosing your comparables means deciding the result, and nobody redoes that work every month.

The reference point is no longer a choice. It is your sector, all of it.

  • Six local sectors, yours marked, and your position inside it.
  • You are never compared to a named chain: you are placed inside an aggregate.

The tool lives inside Easy Banking Business. The target cannot get in.

Access runs through the bank's secure environment, reserved for the contract holder.

One address to pass on. Two actions.

  • The banking core is untouched: it is the entry point that moves onto the business contract, which already exists.
  • The contract holder copies the address tied to their contract and sends it.
  • The guest opens it, on their phone, with nothing to install.
09Validation

Six out of six on the fit, one retailer committing, and the steering committee's go.

Problem-solution fit: reached. Six merchants out of six validated the concept.

One retailer commits. Léonidas comes in as pilot client before development, subject to price: pricing belongs to marketing, not to design.

The steering committee said go. The agile team moved straight on to estimates, story mapping and the production roadmap.

Try the prototype

10The handover

What went to the client.

  • The research report, the concept report, and the navigable prototype.
  • The access journeys, written as user stories, down to the invitation link.
  • The scope, with what falls outside it and why.

The online prototype replays this concept with the decisions taken during the assignment. That is the version that stands.

See the result

Contact

Do you have underused data and a service to prove? Let's talk.

For a role or an engagement, write to me. CV (PDF)

hello@christophevanengelen.com View my LinkedIn profile

I reply within one business day.