THE BRIEF
THE BRIEF
MY ROLE
In this classroom project, we had two main tasks. The first was an evaluation of the communication platform - Discord through the elemental framework of strategy, scope, structure, skeleton and surface. The latter part was about switching things up; I had to redesign Discord using a design system of my choice, and I opted for the Atlassian approach.
In this classroom project, we had two main tasks. The first was an evaluation of the communication platform - Discord through the elemental framework of strategy, scope, structure, skeleton and surface. The latter part was about switching things up; I had to redesign Discord using a design system of my choice, and I opted for the Atlassian approach.
Analyzing Discord using the 5S model Understanding Atlassian’s Design System
UI Design
Prototyping
In this classroom project, we had two main tasks. The first was an evaluation of the communication platform - Discord through the elemental framework of strategy, scope, structure, skeleton and surface. The latter part was about switching things up; I had to redesign Discord using a design system of my choice, and I opted for the Atlassian approach.
THE PROCESS
THE OUTCOME
THE OUTCOME
For this project, we didn’t just want to stay at the surface level and swap the components, we wanted to dig deeper and understand what made Atlassian ‘Atlassian’. Also we thought it would be fun to see how a B2C product would fare in the world of B2B. Thus, began the process of tearing down discord according to Jesse James Garret’s 5s model and delving deep into the heart of Atlassian's design system.
Honestly, I thought the end product would be a ‘Jira’ looking discord. We expected the fun engaging discord to become a no nonsense, professional platform. But along the way we realised that even though their personalities were wildly different, ultimately at the heart both the platforms wanted to provide a similar experience with different approaches. We wanted to ensure that Discord became an Atlassian product while still delivering everything it did before.
Honestly, I thought the end product would be a ‘Jira’ looking discord. We expected the fun engaging discord to become a no nonsense, professional platform. But along the way we realised that even though their personalities were wildly different, ultimately at the heart both the platforms wanted to provide a similar experience with different approaches. We wanted to ensure that Discord became an Atlassian product while still delivering everything it did before.
Imagine a place where Atlassian takes over Discord
Imagine a place where Atlassian takes over Discord