Figma sets aside time every year to work on small quality-of-life changes and bug fixes rather than headline features. The program is called Little Big Updates, and Vice President of Product Sho Kuwamoto describes it as central to how the company builds its editor.
Origins in a weekly shipping rhythm
The practice dates to Figma's early days, when the team shipped updates for designers as fast as it could produce them. The normal cadence was one release per week. On one occasion the team had a batch of four and shipped one per day from Monday through Thursday. Users compared it to unwrapping a present each day, and the name Little Big Updates stuck.
Kuwamoto frames the obligation in terms of investment: designers spend upwards of 40 hours a week in Figma, and for many, learning the tool is part of mastering their craft. Large, stage-ready features are tempting to pursue, but fixes and improvements users didn't know they needed often matter more.
Why the small stuff gets deprioritized
Product work usually means adding capabilities—the iPhone gained multiple lenses, spreadsheets gained graph generation. A quality-of-life update instead makes an existing capability slightly better. Such changes are hard to prioritize because they are hard to market; as Kuwamoto puts it, you don't get a billboard for making a function take one fewer click. Yet work on the actions users repeat most often can produce more impact than a flashy feature nobody uses.
His canonical example is paste. Paste once dropped content at a random spot on the screen, frustrating people every time they used it—hundreds of times a day. Nobody hands out awards for fixing paste, he says, but the fix has likely done more for real workflows than many announced features. A similar case: selecting text when switching between frames no longer requires a dance of double-clicking.
When you celebrate the small things and give each one their moment, it gives people a chance to recognize how important each one is.“When you celebrate the small things and give each one their moment, it gives people a chance to recognize how important each one is.”
Two tracks for prioritization
Big and small features are handled on different principles. Big ones—such as AI in FigJam—require deliberation about which improvements matter most and how they fit together; some must wait until complementary work is ready, an exercise Kuwamoto likens to packing the big suitcases into a car first. Small features invert this. Teams shouldn't agonize over ordering and decisions should be as decentralized as possible, because each team knows better than anyone which fixes will make the most impact.
Hospitality as a product model
Kuwamoto points to restaurateur Danny Meyer, whose writing on hospitality focuses not on decor or menus but on treating people well. Software people love follows the same logic: noticing and fixing the problems users hit. The test is whether users feel the product has their back, not merely that it helps them do their job.
From this fall's batch, he singles out two changes:
- Select and copy from version history. Version history is usually visited after something has gone wrong. Copying previously required duplicating the file, even though right-clicking a layer in the layers panel already allowed copy and paste—something most people, Kuwamoto included, didn't know. The update moved that function to a more obvious place and took about 10 lines of code, saving users hours of recreating work they thought was lost.
- Component modal and playground. Where users once dropped an icon into a document and configured it afterward, a preview window now shows component configurations and their descriptions before a choice is made.
Keeping the program honest as Figma grows
Growth brings pressure to make everything bigger—to report 30 updates this year after 20 last year, "while standing on our heads"—and Kuwamoto warns that one-upmanship can endanger the spirit of Little Big Updates. Figma weighs intuition alongside metrics: helping as many people as possible have a good day matters more than moving a number from 0.89 to 0.91. Individual stories are also easier to use when motivating the team than a diluted collective version. He cites testimonials from teachers using FigJam in classrooms, including for kids who have trouble relating to other kids, as the kind of narrative that guides future product decisions.
Figma shipped 42 Little Big Updates this fall.




