Spotify: Design Tenets
Creator Foundation was a product area primarily focused on creating reusable platform capabilities for other Spotify R&D teams. While a lot of our work was internal facing, we still owned plenty of user-facing interfaces. As the design lead, it was my responsibility to define and uphold a standard of design quality. I created a set of design tenets to answer the question: How do we think about and prioritize design quality in a platform team?
Problem Statement
Creator Foundation Product Area is embracing a platform mindset—prioritizing scale and efficiency. Given this focus plus limited resources, how can we make sure we are rowing in the same direction when it comes to design quality?
Hypothesis
If we document our shared values and beliefs, then we can uphold the same standards of quality across the product area with or without design’s direct involvement.
Why tenets?
A tenet is a principle or belief. Our design tenets are things we value and see as universal truths for our PA, whether currently or aspirationally. They are not a hard set of rules to follow or break. Instead they guide us, keep our vision in mind, and help us make good decisions with minimal bias.
Tenets keep you honest. It’s easy to get caught up in group-think or distracted by the nuances of a specific project and lose sight of the overall goals. Stepping back, setting tenets, and then considering those tenets along the way (only changing them when you step back again) will help you keep track of the wider strategy.
–Joe Chung on using tenets at AWS
The tenets
#1: We keep it simple.
What does it mean?
We templatize, we reuse, and we are always on the lookout for common use cases across our internal customers. We avoid rabbit holes and the temptation to resolve every edge case. Our products are learnable, consistent, and streamlined and so are our processes. We acknowledge and consider our role in the larger ecosystem.
How do we practice it?
We guide internal customers away from needless complexity.
We default to using Encore components and deviate or customize only when it is critical to a user’s comprehension or ability to complete a task.
We take time to create excellent documentation in the interest of making our systems easy to adopt and thus facilitating scale.
#2: We understand our impact.
What does it mean?
While our work mostly supports the initiatives of our internal partners, we always think deeply about how the products we build impact the end-user experience. We don’t offload burden to our partners or end-users. We are careful to not make anyone’s job harder while keeping our business goals top of mind.
How do we practice it?
We openly discuss how our products will have an impact on the end-user experience.
We pay attention to common workflows and focus on making them easier and more streamlined.
We don’t assume that customer support teams will bail us out when our products have gaps.
#3: We trust our gut.
What does it mean?
We leverage our expertise to support our judgment. When a better method isn’t available, we rely on our informed instincts to make decisions. We know when something isn’t right, and we tell each other. We know when to scrutinize and when to roll with it.
How do we practice it?
We are discerning about when we need research and user testing vs. when we can move ahead without it when faced with limited capacity or tight timelines.
We speak up in meetings when we feel strongly while simultaneously trusting our teammates to act with positive intent.
We pull conversations to a higher level when we get stuck, relying on our mission and vision to be the tie breaker.
#4: We’re proud to show off.
What does it mean?
If Daniel asked for a demo, we’d be proud to do it. We stand behind our choices and don’t have to hedge or give disclaimers. We are innovators and experts in what we do, and we eagerly share our knowledge with teams across Spotify and beyond. We make sound choices that minimize debt and optimize for quality.
How do we practice it?
We launch products that are polished and complete, even if we’ve reduced their scope or functionality.
We jump at the chance to lend our expertise to other teams, both to teach and to provide guardrails and recommendations.
We take the opportunity to make iterative improvements to our UX and UI whenever we are building to new product requirements.
#5: We operate with integrity.
What does it mean?
We respect our users’ intelligence and autonomy and empower them to make their own informed choices regarding their privacy and security. We treat our users’ sensitive information with the utmost care. We are transparent and avoid deceptive UX tactics to manipulate user behavior. We value inclusivity.
How do we practice it?
We embrace consumer protections and strive for compliance.
We account for accessibility, cultural context, and a range of devices and internet speeds.
We don’t collect user data that we don’t need, and ensure that users can access, edit, and delete the data they provide.
Appendix
Illustrations
Bird illustrations courtesy of Icon Market on Noun Project.
Inspiration
https://stevenpcurtis.medium.com/the-boy-scout-rule-in-coding-a0b4d8130798
https://www.factoftheday1.com/p/tenets-at-amazon-a2bb8a56ae94
https://aws.amazon.com/blogs/enterprise-strategy/tenets-provide-essential-guidance-on-your -cloud-journey/
https://tarotcardsoftech.artefactgroup.com/
https://www.uxdesigninstitute.com/blog/ux-design-principles/
https://www.educative.io/answers/what-are-normans-design-principles