Introduction

My goal for this project was to learn UI design beyond textbooks by studying a real product used by teams every day. Instead of designing a new screen, I wanted to understand how complex interfaces are built and how small design decisions shape the user experience.

This project was an opportunity to slow down, observe, and ask:

"How did designers turn a complex project management workflow into something that feels manageable?"

Why Did I Choose Jira's Backlog Page?

I chose Jira's Backlog page because it is packed with interactions and reusable components.

At first, it looked like a simple dashboard, but the more I explored it, the more I noticed patterns, hierarchy, and thoughtful design decisions.

I was curious to understand:

• Why is information organized this way?
• How do users manage so much data efficiently?
• What makes the interface feel familiar despite its complexity?

Breaking Down the UX Behind the UI

As I analyzed the screen, I started asking myself:

• Why is this placed here?
• What happens if it's removed?
• Where have I seen similar patterns?
• How does this interaction work?
• Who is this designed for?

This exercise helped me realize that Jira is designed for people who use it all day. Every component has a purpose, from the sidebar navigation to the sprint containers.