Case Study
Scaling a digital bank across markets without losing clarity.
Different regions, teams, and operating models needed to align around a more consistent product and design approach.
A digital banking case study focused on scaling product experience, ways of working, and design capability across markets.
Client
ING
Sector
Banking
Role
Design Lead
Services
UX, User Research, Team Scaling, Ways of Working, Stakeholder Alignment
Project overview
Launching and scaling a digital bank across new markets.
ING was launching a digital bank in the Philippines, with ambitions to scale across multiple markets, including China.
This wasn’t just about designing a product. It meant building the foundations for a digital banking experience across different regions, languages and cultural expectations.
At the same time, the design glossaryCapabilityCapability refers to an organisation’s ability to perform a specific function or deliver a particular outcome.Open glossary term needed to grow. A small team had to scale quickly into a multidisciplinary function that could support glossaryDeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term while shaping how design worked within the organisation.
The challenge sat across product, people and glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term. Deliver a high-quality banking experience, while building the team and ways of working needed to sustain it.
What was happening
Delivery was moving faster than the structure behind it.
Design was becoming a bottleneck. Demand was increasing, but the team, glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term and glossaryAlignmentAlignment is the shared understanding and agreement between teams, stakeholders, and objectives.Open glossary term needed to support it weren’t in place yet.
Different markets brought different expectations. Cultural nuances, language differences and local glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term all needed to be understood and reflected in the product, but there wasn’t a consistent way of doing that.
Internally, ways of working were still evolving. Teams were not always aligned, glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term lacked glossaryClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term, and design was often pulled into glossaryDeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term without the space to properly shape direction.
The risk was clear. Without structure, quality would drop, teams would become reactive, and glossaryScalingScaling is the process of growing a product or system to handle increased demand without compromising performance or experience. It applies to technology, users, and operations.Open glossary term would become harder over time.
Approach
Build the team, the process and the product together.
The focus was not just on glossaryDeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term, but on creating the conditions for delivery to succeed.
serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service was carried out across markets to understand glossaryUser BehaviourUser behaviour refers to how users interact with a product, including actions, patterns, and decision-making processes.Open glossary term, cultural expectations and local needs. This ensured the product was grounded in real user glossaryInsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term rather than assumptions carried over from other regions.
At the same time, the design team was scaled and structured to support demand. glossaryRecruitmentRecruitment is the process of finding and selecting participants for research or testing.Open glossary term, mentoring and clear role definition helped glossaryBuildA build is the process of compiling and packaging code into a runnable application.Open glossary term a team that could operate independently while maintaining glossaryConsistencyConsistency is the use of uniform patterns, behaviours, and visual elements across a product to create familiarity and predictability. It helps users learn once and apply that knowledge throughout the experience.Open glossary term.
Ways of working were introduced and refined, including the Double Diamond glossaryFrameworkA framework is a structured set of tools and conventions used to build applications more efficiently.Open glossary term, to bring more structure to how problems were understood and solved.
Close collaboration with product, engineering and senior glossaryStakeholderA stakeholder is any individual or group with an interest in a product, project, or outcome, including internal teams and external parties.Open glossary term helped align priorities, improve communication and create a more consistent approach to glossaryDeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term.
Key decisions
Invest in foundations early to enable scale.
A key decision was to focus on building strong foundations rather than chasing short-term glossaryDeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term.
That meant investing in team structure, design quality and ways of working early, even when there was pressure to move quickly.
Rather than allowing design to become a reactive glossaryServiceA service is a component or function that performs a specific task within a system.Open glossary term, it was positioned as a strategic function that could shape direction as well as support glossaryDeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term.
Cultural differences were treated as a critical factor, not an glossaryEdge CaseAn edge case is a rare or extreme scenario that falls outside typical user behaviour.Open glossary term. The approach adapted to local glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term and expectations, rather than forcing a single global glossaryModelA model is a system or representation used to process data and generate outputs, often trained to perform specific tasks.Open glossary term onto different markets.
This created a more resilient setup, where teams could scale, adapt and continue to deliver quality as the product evolved.
Solution
A scalable design function supporting a multi-market digital bank.
The result was a design team and glossaryOperating ModelAn operating model defines how an organisation delivers its products or services, including processes, roles, systems, and workflows.Open glossary term capable of supporting a growing digital bank across multiple regions.
The product experience was shaped by real user glossaryInsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term, ensuring it worked for local markets while maintaining glossaryConsistencyConsistency is the use of uniform patterns, behaviours, and visual elements across a product to create familiarity and predictability. It helps users learn once and apply that knowledge throughout the experience.Open glossary term across the wider glossaryPlatformA platform is a system or environment that enables users, services, or applications to interact, build, or operate.Open glossary term.
Design was no longer a bottleneck. Clear roles, better glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term and stronger collaboration allowed teams to move with more glossaryConfidenceConfidence is the level of certainty in a decision or outcome based on available evidence.Open glossary term and less glossaryFrictionFriction refers to anything that slows users down or makes it harder for them to complete a task. It can be caused by poor design, unnecessary steps, unclear messaging, or technical issues.Open glossary term.
The introduction of structured ways of working improved how problems were approached, making it easier to move from glossaryDiscoveryDiscovery is the phase of understanding problems, users, and opportunities before building solutions.Open glossary term through to glossaryDeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term without losing glossaryClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term.
This created a more stable foundation for both the product and the organisation, supporting continued growth and glossaryIterationIteration is the process of repeatedly improving a product through cycles of testing, feedback, and refinement.Open glossary term.
Experience map
A closer look at the work in context.

Gallery image from the ING case study.
01/04
Outcomes
A stronger team, better alignment and a platform for growth.
The design team successfully scaled from a small group into a multidisciplinary function, capable of supporting ongoing glossaryDeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term across markets.
Design quality improved, and teams were able to work more efficiently with clearer roles, responsibilities and glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term in place.
Better glossaryAlignmentAlignment is the shared understanding and agreement between teams, stakeholders, and objectives.Open glossary term across product, engineering and glossaryStakeholderA stakeholder is any individual or group with an interest in a product, project, or outcome, including internal teams and external parties.Open glossary term reduced glossaryFrictionFriction refers to anything that slows users down or makes it harder for them to complete a task. It can be caused by poor design, unnecessary steps, unclear messaging, or technical issues.Open glossary term and improved decision-making.
The product was shaped by real user needs across different regions, creating a more relevant and effective banking experience.
This established a clear foundation for future growth, both in terms of the product and the organisation behind it.
Reflection
Scaling isn’t just about product. It’s about people and structure.
This project reinforced that glossaryScalingScaling is the process of growing a product or system to handle increased demand without compromising performance or experience. It applies to technology, users, and operations.Open glossary term a product without scaling the team and glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term behind it doesn’t work.
As organisations grow, complexity increases. Without the right structure, teams become reactive, quality drops and progress slows down.
The role of design in these glossaryEnvironmentA specific setup where software runs, such as development, staging, or production.Open glossary term is not just to produce outputs, but to create glossaryClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term. To shape how teams work, how decisions are made, and how problems are approached.
Get that right, and the product improves as a result.