Across my career at Amazon as a Lead Product Designer, tenets were not treated as decorative mission statements. They were operational decision mechanisms—pre-agreed rules that empowered designers, PMs, and software development managers (SDMs) to resolve conflicting priorities without endless meetings.
Here is my take on writing good Tenets:
Definition
Design tenets are the shared mechanism through which cross-functional teams align on user context, operational tasks, and the non-negotiable trade-offs required to ship usable software.
My Experience with Tenets
I authored, iterated, and guided teams on tenets across five distinct enterprise organizations.
RISK & TRUST ARCHITECTURE (TRMS / Buyer Risk )│ Governing automated fraud enforcement vs. customer trust
OPERATIONAL ERGONOMICS & VELOCITY (FBA / Global Selling / B2B) Prioritizing cognitive density & keyboard speed over whitespace
TRANSPARENCY & VALUE (Amazon Prime Member Engagement) │ Protecting customer trust over short-term conversion metrics.
DESIGN ORG CULTURE & MENTORSHIP (Bar Raiser & Critique Guidance) TRX Design team│Teaching designers how to write opinionated trade-offs.