FigJam tips from the Atlassian design team

Quick Overview

Jade Jiang, Senior Product Designer at Atlassian, demonstrates how she integrates FigJam and Jira into her design workflow, focusing on using FigJam for rapid ideation, low-fidelity mockups using basic shapes, and effectively communicating concepts and feedback to engineers before escalating to high-fidelity designs or moving into Jira for execution.

Key Points: Jade Jiang, a Senior Product Designer at Atlassian, shares her design process utilizing FigJam for ideation and Jira for tracking work. She emphasizes using FigJam for rapid, low-fidelity mockups, often employing simple shapes like circles and scribbles to convey concepts quickly. Low-fidelity FigJam mockups save time by providing a fast visual artifact for initial feedback before committing to detailed high-fidelity work. The team uses FigJam for collaboration, enabling engineers to provide direct feedback on concepts via comments before development begins. Jira is used for formal tracking, where agents (like 'Unit Test Creator' or 'Feature Flag Cleaner') can be suggested and assigned to issues based on development needs. The process involves moving from rapid FigJam concept validation to more refined mockups, and finally into Jira tickets for actionable engineering tasks.

Context: The video features a discussion between Jay Dalal and Jade Jiang, a Senior Product Designer from Atlassian, focused on optimizing the early stages of a design workflow. The primary context is demonstrating how Atlassian designers leverage FigJam, a collaborative whiteboarding tool, to quickly iterate on and gather feedback for design concepts before formalizing them into high-fidelity designs or engineering tickets within Jira.

Detailed Analysis

Jade Jiang details her design process, which heavily incorporates FigJam for fast concept validation. She prefers starting with low-fidelity explorations in FigJam, using basic elements like colored shapes and scribbles to communicate ideas, stating this saves time compared to jumping straight into high-fidelity tools or Jira. She shows examples of these low-fidelity flows, where concepts are quickly sketched out. She also highlights the ability to use FigJam to gather feedback from stakeholders and engineers directly on the canvas, such as using comments within FigJam to discuss issues related to a specific design element before it becomes a formal Jira ticket. When moving towards execution, she shows how Jira issues are structured, noting that the development section within a Jira ticket can suggest relevant 'Agents' (AI tools or predefined actions) like 'Unit Test Creator' or 'Feature Flag Cleaner' to automate parts of the task, which helps ensure the team has a clear sense of the task's status and scope. The goal is to use FigJam for rapid iteration and alignment, ensuring that when engineers pick up the work, the concepts have already been vetted and clarified, potentially saving 30 minutes to an hour of rework.