Little Big Updates: When going big means thinking small | Figma Blog
Figma argues that meaningful product progress often comes from small, frequent improvements rather than headline features. Because designers may spend 40 or more hours a week in Figma, reducing friction in everyday workflows can have a greater cumulative impact than adding rarely used capabilities. Its annual “Little Big Updates” initiative formalizes this focus on quality, usability, and user joy. ## Why Small Improvements Matter - Subtle changes can save users clicks, eliminate recurring frustrations, and fix long-standing bugs. - Figma users invest heavily in learning the tool, creating a responsibility for Figma to continually improve it. - Quality-of-life updates are difficult to market, but often affect the actions users perform most frequently. - A small improvement repeated hundreds of times a day can matter more than a flashy feature used occasionally. ## The Origin of Little Big Updates - Figma originally released product updates weekly. - After accumulating four updates, the team released one per day from Monday through Thursday. - Users compared the experience to opening a new present each day. - This response inspired the “Little Big Updates” format, which gives individual improvements their own attention. ## Examples of High-Impact Details - Figma fixed paste behavior that previously placed content in seemingly random locations. - Although the change was not headline-worthy, it removed a frustration users encountered hundreds of times daily. - Text selection when switching between frames was also improved, eliminating unnecessary double-clicking. - These examples show how workflow friction can be more important than feature novelty. ## Prioritizing Big and Small Features - Major initiatives, such as AI features for FigJam, require deliberate planning and coordination. - Large features may need to be sequenced carefully so related capabilities work together. - Small improvements should be prioritized differently: teams should avoid over-planning and allow decisions to remain decentralized. - Individual teams are often best positioned to identify which usability improvements will have the greatest effect. - Every team should treat product quality as an ongoing responsibility, not as a secondary concern. Figma’s recommendation is to balance ambitious new capabilities with sustained attention to everyday details. Product teams can create substantial user value by identifying frequent sources of friction and steadily removing them.
Read original(opens in new tab)