Design approach

Follow a user-centred design process and aim to be as lean as possible. We design following a few simple rules:

Always ask 'why' five times

Don't jump into the details too quickly. Always understand the users' underlying motivations and needs first. Example: User come to this screen to fill out a form. Why? So they can adjust their settings. Why? So they can... etc.

Tell a story. Start with happy day scenarios

Always provide context from a user's perspective. Start by focusing on the happy day scenario. Edge cases are important, but will be checked against only later. Only few people will break the system deliberately.

Only one number 1 priority

Your design needs to communicate one main use case above all else. What do you want your users to see and do first? Reduce all other use cases by applying 'Just enough is more' to your designs.

Share your reasons, provide your rationale

When you share your designs with others, always share your rationale behind your decisions. Why did you choose this solution over another one? What areas would you like feedback on? – The more you share, the more people can help you.

Make work visible

Design walls are our new desks. They make our work visible. Collaborate with your peers on the design whenever you can.

Progress over perfection, but not below our standards

There is always a balance to strike between shipping a product, and ensuring its quality. The Atlassian Design Guidelines are our minimum acceptable quality for all designs.