Pajamas: Actionable Principles Update
From the perspective of a relative newbie to our beloved Pajamas - I feel we are lacking design principles that are specific enough to be used by anyone as a decision-making framework to judge whether or not a new design is representative of GitLab's experience. Right now, IMO having a principle like
Human is more of a hygiene factor in good UX design rather than something that represents how GitLab uniquely feels.
When I have designed principles in the past, my most influential bit of reading was from Luke W's "Developing Design Principles":
In order to be most effective, however, design principles need to provide teams with a way to gauge design decisions. That is, they should be specific enough to help groups of people choose between different design options. Unfortunately, many team's first tendency when creating design principles is to go too broad. Principles like "make it easy to use", "keep it fast", or "put the user first" are usually some of the most common ideas that spring to mind.
As stated in the above article, I feel like our design principles are too broad, and thus, I find it difficult to use them as a decision-making framework in my design process. For example, when I tried laddering the principles whilst designing new areas of Analytics, the results didn't yield anything unique to GitLab.
Updating our design principles to be more specific Revisit our principles by performing a cross-product UX research & design project across...
- Current design team practices - How each stage group applies principles currently
- Brand - How we position our product to customers
- Customer insights - How customers feel when using our product
- Cross-functional collaboration - How we use principles as a tool with Engineering and Product