Payment Experience
Making invoice payments clearer, faster and easier to trust
At Billogram, paying an invoice was not one fixed flow. It was an evolving product area shaped by different payment methods, bank integrations, regulations, customer configurations and user expectations. Over several years, I worked with the team to improve this journey—from the moment someone opened an invoice to the point where a payment was completed, scheduled, processing or had failed.
DESIGNING FOR NEW MARKETS
Learning when localisation is not enough
When Billogram expanded from Sweden into other European markets we initially approached much of the work as localisation: translating content, supporting new currencies and adapting legal and technical requirements.
We soon learned that a translated Swedish experience was not necessarily a useful local experience. Payment habits, levels of digitalisation and expectations of trust varied significantly between markets. The project became an exercise in questioning what we considered “normal” and designing a product flexible enough to work in different cultural and technical contexts.
BUILDING A DESIGN SYSTEM
Creating a shared foundation for consistency, accessibility and collaboration
As Billogram’s product grew, the interface grew with it. Components had been created at different times, by different teams and for different needs. Similar patterns behaved or looked slightly different, and design and development did not always share the same source of truth.
We began rebuilding the design system to create a more consistent product and a better way for designers and engineers to work together. The project was not only about organising components in Figma. It was about creating shared decisions that could scale across a complex platform.