Context
Piraeus Bank is Greece's largest bank — millions of users, legacy infrastructure, and zero tolerance for disruption. I came in as Product Designer and UX Consultant via Code.Hub, embedded across UX and Rapid Response teams. The mandate: modernize winbank (the digital banking platform) across web and mobile without breaking the trust of the people who depend on it daily.
No unified design system. Fragmented documentation. 27 parallel assignments across retail (B2C) and corporate (B2B) banking, each with its own stakeholders and technical constraints.
How I Worked
Every project started with a brief and a stakeholder workshop — requirements, technical constraints, what had already been built. From there: a UX audit of existing designs to benchmark navigation and identify drop-off points. Figma for prototyping and final UI delivery; wireframing only for flows that needed first-principles rethinking.
I built a minimal UI kit in Figma to maintain visual consistency across parallel projects without slowing the pace. Maintained a Notion documentation system tracking every decision, fix, and handoff note. Used Stark for contrast validation and structured heatmap analysis to prioritize friction areas — particularly useful where direct user testing wasn't feasible in regulated flows.
Block Winbank Credentials
The brief: give users a fast, unambiguous way to block their access credentials — available right from the login screen, at the exact moment they'd need it most. No prior research existed. I reviewed dozens of fintech and security products to identify iconography that communicates urgency without inducing panic, and tested placement options against scanning behavior patterns in high-stress states.
The entire verification flow was mapped jointly with the backend team: session management, error handling at every state, fallback paths. The final design applied the Zeigarnik Effect and Law of Minimal Effort — reducing cognitive cost and reframing the block action as something the user controls, not a failure event.
Remittance Packages
Goal: help users explore, select, and send prepaid remittances clearly — whether they're doing it for the first time or the fifteenth. The first round of prototypes ran into backend constraints I hadn't accounted for. I changed the process: from that point on, every sprint opened with a co-definition session with backend and payments teams before any screens were touched.
Progressive disclosure structured the final experience: package value visible upfront, with detail revealed in digestible steps. One interface served first-time senders and experienced users alike — no branching, no version proliferation.
Results
Nine months. 27 assignments. 20 projects shipped across web and mobile. Support ticket volume reduced through clearer credential and remittance flows. The product team shifted from reactive firefighting to structured sprint cadences over the course of the engagement — that process change mattered as much as the screens.
What I Learned
Meet feasibility before you meet the canvas. Every iteration that skips technical alignment wastes trust and time. Build structure even when no one asks for it — documentation standards, process templates, a shared kit — because that infrastructure is what lets a team scale without breaking. In a 27-project engagement, the system you build around the work matters as much as the work itself.
