← Back to recent work

Pen and paper, brought onto the tool.

Senior Business Analyst and UX Lead on BBV Touch, Zürcher Kantonalbank’s advisory tool, in use across tens of thousands of advisory sessions a year. The work was to take a business unit still advising on pen, paper and slides and bring it onto a tested, streamlined in-tool flow, without bloating the platform for everyone else.

Role
Senior BA & UX Lead (Contractor)
Focus
Requirements, UAT, alignment
Context
Regulated Swiss banking

The problem

A business unit was still advising clients on pen, paper and slides. No streamlined information flow, no consistent experience, nothing that lived in the bank’s advisory tool. They needed to come onto BBV Touch, the system the rest of the advisors already ran on.

Scattered across

Pen & paper
Slide decks
Side notes

The result

Advisory off the toolNo single flow

Client advice scattered across pen, paper and slides. No single flow, and none of it inside the bank’s tool.

Straight to the business

In my dual role as Senior Business Analyst and UX Lead, I worked with the business unit. It ran as a loop: show the flow, the structure, the solution, take their corrections, show it again, until they recognised their own way of working in it.

Owns the loop

BA + UX LeadMe, directly

The advisors

Business unitRecognise their own work

Show, refine, show again, until it fit how they advise

Because the business shaped the flow, the handover held no surprises.

Testing, built into the plan

Testing time was booked in from the start, so it never got squeezed at the end. The sessions were scripted and mixed qualitative research with acceptance: agreed tasks and questions, run with the business in the room. Each was written up, presented, and folded back into the solution before handover. The largest ran in my second month, when a unit pushed for scale.

ScriptTasks & questions
Run UATWith the business
EvaluateWrite up findings
Fold backUpdate, hand off

Loop until it was ready to hand off

Scripted sessions, half qualitative research, half acceptance. Run, evaluated, folded back, and run again until it was ready to hand off.

One voice, not one build per unit

Every unit wanted its own way of working. The easy answer is a bespoke build for each, which quietly bloats the tool and the development behind it. I fitted each request to a shared pattern instead, so BBV Touch stayed one coherent tool and we could answer every business unit with one voice. This is the part that kept the platform trusted.

Each unit

Business unit
Business unit
Business unit

Fitted to

One shared toolBBV Touch

Answered with

One voice

The alternative, a bespoke build per unit, was avoided: it quietly bloats the tool.

Each unit fitted to a shared pattern, not a bespoke build. The tool stayed coherent, the bloat stayed away.

Outcome

One business unit moved fully from pen and paper to a tested, streamlined flow inside BBV Touch, handed over clean, with work contributed to several others. In a regulated bank, the quiet result is the one that matters: change that ships without breaking what the rest of the advisors already rely on.

One tool, many business units · route each request

Development load Lean
Mortgage advisory · extra step
Pension unit · own field
SME banking · own layout
Retail · reworded flow

Route everything bespoke and the tool bloats. Fit each to the shared pattern and the unit answers every business unit with one voice.

← Back to recent work

Currently available.

Product management, business analysis and customer experience across regulated banking, fintech and B2B.

Let’s talk