Case 12 · Fintech · 2018
Glase
Swedish payments company SEQR became Glase. In 8 weeks I led the rebrand, design system and refresh of an app people already knew.
- Role
- Product Design Manager at SEQR / Glase, Stockholm (remote), Feb–Sep 2018, directing the design end to end and leading the UX/UI team
- Team
- 3-person UX/UI team and engineering · Adobe XD, Sketch, Zeplin
- for the rebrand, payment-app refresh and design system
- 8 weeks
- deliverables, one deadline
- 3
- SEQR becomes Glase
- 2018
01
People already knew how to pay
I’d worked with SEQR before. In 2018 the Stockholm payments company was turning into Glase, and I joined remotely as Product Design Manager. We had 8 weeks to deliver the rebrand, a payment-app refresh and a design system. The new look was the easy part. The risk was making people re-learn how to pay.
The Glase mark, cream on navy.
02
Screens waited for the system
Navy, cream and gold went in first, with type and components. Then we mapped the SEQR app to Glase, screen by screen. The 8 weeks forced a discipline I wouldn’t have picked: every call had to be “we’re changing the identity” or “we’re preserving the habit”, no middle ground.
Sign-up starts with a phone number.
The logo’s hexagon turns up in the PIN dots.
03
Familiar steps at the riskiest moments
We redrew account restore and PIN recovery in navy and cream but kept the mechanics people knew. Sign up with a number that’s already registered and the app offers to restore your account. If you’ve forgotten your PIN, you can scan your ID or contact customer service.
A registered number gets an offer to restore the account.
Forgotten PIN: two ways back in.
04
Top-up says what’s coming
We put the amount, service fee and total under the card details, so you see what it’ll cost before you press TOP UP. If the top-up needs 3D Secure, a screen says so before the bank takes over.
First the amount, in SEK.
Card entry, with a camera icon to scan the card.
3D Secure gets its own screen first.
05
What crept in
We held daily design reviews as screens came online and ran a continuity check against their SEQR versions before ship. A couple of small interaction changes slipped through the system-first approach, and we had to pull them back late.
The receipt repeats the amount, fee and total.
Looking back
We ran the continuity check before we shipped. Next time I’d run it earlier, as a formal audit with a per-flow checklist, so small interaction changes get caught before they compound instead of being pulled back late.