Summary
The design team at BBVA Mexico, with more than 170 designers, has the challenge of bringing design to the 600+ projects the organization works on at any given time for them to better achieve the goals of each project in a user-centered way. Because of the limited capacity of the design team, this meant that many projects with design needs were left unattended, managing to solve their needs with whatever resources they had at hand. To address this, Design at Scale was born, an initiative that aims to develop design capabilities in BBVA, through tools, processes and coaching that helps teams that meet certain criteria to work under a self-management model. Through their talk Nora and Giovanna will share their journey in implementing Design at Scale at BBVA.
Key Insights
-
•
Scaling design at BVVA involved enabling developers and scrum teams to do design semi-autonomously with mentorship rather than expanding the design team endlessly.
-
•
A dedicated Design at Scale (DAS) advisor acts as a mentor and counselor to multiple scrum teams, changing the traditional designer's role to a guide rather than a doer.
-
•
Projects suitable for the self-service model typically have concrete, well-defined design objectives mostly in the surface and skeleton layers of UX.
-
•
Complex projects with abstract design needs continue to require full-time dedicated designers instead of self-service approaches.
-
•
BVVA developed design training, documentation, design systems in Figma, and templated resources to support scrum teams' autonomous design work.
-
•
Screening and continuous reassessment of projects' fit for the self-service model is critical to managing complexity and ensuring quality.
-
•
Design at Scale advisors manage high cognitive loads by balancing around a limit of approximately a dozen projects per advisor at a time.
-
•
Clear, explicit communication and agreements about the self-service process reduce confusion and align expectations with scrum teams.
-
•
The self-service model fosters a positive cultural shift, improving collaboration and understanding between developers and designers.
-
•
Ideal DAS advisors are mid-level designers with humility, strong communication, negotiation skills, and a willingness to teach non-designers.
Notable Quotes
"Design changed from focusing only on visual aspects to bringing a user-centered design process involving multiple disciplines."
"Developers started doing design themselves because they needed to, but without design principles or user feedback, which worried us."
"Why don’t we help developers do better design, rather than try to be a bottleneck or endlessly grow the design team?"
"The magic happens when the designer becomes a counselor, mentor, and guide, not just a person who designs."
"We use frameworks like the Stacy matrix and layers of user experience to filter which projects can do self-service design."
"We provide very specific packages combining design objectives and channels, like creating new user flows in the mobile app."
"One design advisor might be assigned to 12 scrum teams, which requires constantly changing mindsets across very different projects."
"It's crucial to be very explicit in communication to prevent confusion about how the self-service model works compared to traditional design."
"Even though one advisor can work with many projects, managing the cognitive load is challenging and requires setting flexible workload limits."
"Developers who worked in the self-service model sometimes ask, what can I do to become a designer? That’s been fun."
Or choose a question:
More Videos
"If you really want to build culture and see how people cross collaborate, try to make lunch with your entire team every single week."
Jennifer KanyamibwaCreating the Blueprint: Growing and Building Design Teams
November 8, 2018
"We want to create clarity because lack of clarity is why we struggle with research repositories."
Brigette Metzler Dana ChrisfieldResearch Repositories: A global project by the ResearchOps Community (Videoconference)
August 27, 2020
"We converted process boxes directly into user stories to create a common language for the team."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"People appreciate when you acknowledge your limitations in blending into an organization."
John Mortimer Milan Guenther Lucy Ellis Patrick QuattlebaumPanel Discussion
December 3, 2024
"Extended radio silence to candidates was unnerving and one of the unpleasant truths we heard from teammates."
Dante GuintuHow to Crush the Talent Crunch
September 8, 2022
"We tend to confuse the experience of people with user experience, and I’m less interested in user experience than in the experience of people."
Richard BuchananCreativity and Principles in the Flourishing Enterprise
June 15, 2018
"Outsider versus insider is a cute bunny, but it’s kind of an artificial separation."
Dan WillisTheme 3: Intro
January 8, 2024
"Failure cake helped us eat our feelings and provided comfort during hard moments."
Dan WardFailure Friday #1 with Dan Ward
February 7, 2025
"Let’s shake s*** up."
Chris GeisonTheme Two Intro
March 28, 2023