Little Big Outtakes | Figma Blog (opens in new tab)
Figma’s “Little Big Outtakes” shares the behind-the-scenes decisions that shaped 30+ small product updates. The stories show how difficult edge cases, team feedback, and disciplined scoping often produced better outcomes than simply adding more functionality. Across search, prototyping, and previews, the teams improved features by making complexity visible, validating ideas collaboratively, and prioritizing achievable impact. ## Multi-select Search: Designing for Edge Cases - Multi-select search extended Figma’s find-and-replace feature, allowing users to select specific results with `Shift + Click` or `Cmd/Ctrl + Click`. - The team discovered a major complication: users cannot independently select a parent layer and one of its children. - Selecting multiple search results could therefore include unexpected descendants, especially in deeply nested files. - To clarify the behavior, the designers added: - A visual hierarchy in the search sidebar showing parent-child relationships. - Hover-selection previews when users hold `Command` or `Shift`. - Highlights for indirectly selected items and outlines for directly selected children. - The team concluded that edge cases were not peripheral to the feature—they fundamentally defined how multi-selection needed to work. ## Overlay Blur: Turning Ideas into a Concrete Fix - Figma’s prototyping viewer previously struggled to render background blur on overlays because overlays do not have ordinary content directly beneath them. - Engineer Brandon Lin documented his proposed approaches, potential problems, and solution before implementing the fix. - Teammates suggested passing the overlay’s position into the rendering code so it could identify the correct area to blur. - The final changes associated overlays with their respective frames and ensured that multiple overlays were drawn and layered in the correct positions. - Team feedback gave Brandon confidence that his initial reasoning was sound while helping make the implementation more precise. ## On-Canvas Previews: The Value of Scoping Down - On-canvas previews let users hover over design-panel options—such as blend modes, effects, and color blend modes—to preview changes before applying them. - The original concept considered a much broader scope, including boolean operations, component properties, and font selection. - Rather than attempting to support everything, the team audited dropdown-based editor properties and assessed each option for feasibility and performance risk. - They prioritized features that would not require major geometry changes or substantial canvas modifications. - The smaller release proved powerful enough to be useful while allowing the team to deliver and refine it more quickly. Figma’s examples suggest that strong product work often comes from embracing complexity selectively: expose confusing relationships, seek feedback early, and narrow ambitious ideas to the highest-value implementation.