Design
Design Philosophy Articulation
Make your design beliefs explicit. Unarticulated philosophy leads to inconsistent decisions. Different people default to different beliefs, creating friction. This exercise captures the principles, values, and aesthetic stance that guide your team's work.
Duration
3 hours
Group Size
4-8
Category
Design
Difficulty
Easy
- Surface and articulate implicit design beliefs held by the team.
- Create shared language for design decision-making.
- Identify where team members disagree on design principles.
- Document a philosophy that guides future design choices.
- Explicit design principles the team can reference.
- Documented philosophy that guides consistent decisions.
- Shared language for design discussions and debates.
Moving past platitudes is key. Everyone believes in "good user experience." Push past generic principles to specific beliefs: "We prioritize task completion over visual delight" or "We design for expert users first." Specificity reveals actual philosophy. Psychological safety is required. If people can't share honestly, you'll get performance, not philosophy. Create safety: Philosophical differences are good; personal attacks are not. You want diverse perspectives, not false consensus. Divergence is data. Teams often want everyone to agree. Resist. Divergent philosophies reveal different mental models and priorities. Sometimes divergence should be resolved; sometimes it should be maintained as productive tension. Philosophy is beliefs about what design should do. Principles are operational rules derived from philosophy. "Design should empower users" is philosophy. "Always provide undo" is a principle derived from that philosophy.
Start the conversation
Be the first to share your thoughts, experiences, or questions!