Revolutionizing Bug Bashes at Twitter with FigJam

Twitter's bug bashes, which are crucial for identifying and fixing software issues, were facing significant organizational challenges. The process was traditionally carried out in a Google document, requiring a written description of the bug and links to visual screenshots. This method made it difficult to get a clear, comprehensive view of the bugs at a glance. The process was not only cumbersome but also inefficient, as it involved dropping links into a Google doc, making it hard to keep all relevant data in one place. The challenge was to simplify this process, make it more organized, and improve the overall efficiency of bug bashes.

The customer in this case study is Twitter, a global platform for public self-expression and conversation in real time. Twitter provides a network where users can share and receive information instantly. The company is committed to continuous improvement and innovation, and as such, regularly conducts bug bashes to identify and fix software issues. These bug bashes involve inputs from across the organization, making it crucial to have an efficient and organized process. The solution provided by Artem Artemov, a product designer at Twitter, significantly improved the efficiency and organization of these bug bashes.

Artem Artemov, a product designer at Twitter, developed a solution to this challenge by creating a customizable bug bash template in FigJam, Figma’s new online whiteboard space. The template was designed to help people describe their bugs better, with inputs that keep everything clearly organized. It used text to annotate, stickies to denote browsers, and screenshots for context, making it easier to communicate bugs clearly. The main input for the bug bash was the 'bug card', built as a component in Figma. Using auto-layout, the text layer scaled according to the input, making the bug card feel like a customizable form. Once the bug card was complete, all the details were dropped into the 'bugs' container, a dedicated space for all the bugs associated with the bash. This provided developers with a centralized, visualized look at all the necessary information, making it easier to digest before transferring the bugs into JIRA.

• The implementation of the FigJam bug bash template significantly improved the bug bash process at Twitter. It simplified the previously clunky process, making it easier for team members to describe, communicate, and understand bugs. The template provided a centralized location for all relevant data, eliminating the need to drop links into a Google doc. The 'bug card' component made it feel like a customizable form, further enhancing the user experience. Overall, the solution improved the efficiency and organization of bug bashes, making it easier for developers to digest the necessary information before transferring the bugs into JIRA.