Figma

736 posts

www.figma.com/blog/engineering

Filter by tag

figma2 min readCurated summary

Why Everyone Can (and Should) Be a Great Storyteller | Figma Blog

The article argues that storytelling and writing are not specialized talents reserved for professional writers; they are skills anyone can develop. Clear communication helps turn technical ideas, product plans, and design decisions into shared understanding and action. The difference between “good” and “bad” writers is largely practice, feedback, and willingness to revise—not innate ability. ## Why Storytelling Matters at Work - Strong products, designs, and ideas depend on people who can explain: - Why something should exist - Who it serves - How it improves people’s lives - Writing helps teams bridge the gap between imagination and execution. - At Figma, engineers write technical proposals, designers explain their decisions, and product managers create PRDs to align teams. - Companies such as Microsoft and Slack also use writing to encourage deep thinking, clear communication, and buy-in. ## Challenging the “Bad Writer” Myth - Many people mistake their rough first drafts for the polished writing they read elsewhere. - Every writer begins with imperfect work; improvement comes through: - Feedback - Editing - Deliberate practice - Writing is described as organized thinking: putting ideas on paper can clarify problems and lead to better decisions. - The ability to think clearly is a foundation for becoming a better writer. ## Overcoming the Blank Page - Speaking an idea aloud or explaining it to someone else can reveal a clearer, more natural structure. - Reading widely—including books, magazines, product packaging, and online discussions—helps develop writing ability. - Leslie Lamport’s observation captures the central lesson: without writing, people may only think they are thinking. The practical recommendation is to treat writing as a learnable muscle: read often, write imperfect drafts, seek feedback, and use storytelling to make ideas understandable and actionable.

Read original(opens in new tab)
figma2 min readCurated summary

Save Time on Building Decks—Without Sacrificing Design | Figma Blog

Figma’s Slides plugins extend the presentation tool with Figma’s design capabilities, helping teams create polished decks without sacrificing speed or visual quality. The post highlights plugins for finding assets, creating custom backgrounds, importing PDFs, and adding animation. Together, they support the full slide-building process, from initial content gathering through final presentation preparation. ## Populating Your Slides - **IconScout** provides millions of icons, illustrations, Lottie animations, and Unicons. - Users can customize assets with their own color palettes. - Reverse image search helps find visually similar graphics. - **Mesh Gradient** creates custom backgrounds and color fills. - Designers can edit grid vertices and edges. - Live previews and the ability to save or upload gradients support iterative design work. - **PDF.to.design** imports PDFs as editable designs. - Text and images can be extracted and reused in slides. - Files remain private on the user’s local machine, which helps protect sensitive information. ## Adding Power and Polish - **Jitter** is presented as a tool for animating slide designs, helping make presentations more dynamic and engaging. - The broader plugin ecosystem includes tools for visual refinement, color controls, and motion, allowing teams to tailor slides to their brand and narrative. ## Preparing to Present - The article’s final section focuses on tools for getting decks presentation-ready, continuing the workflow from asset creation and design polish to delivery. Figma recommends using Slides plugins as a practical way to speed up deck creation while preserving control over layout, branding, visuals, and storytelling.

Read original(opens in new tab)
figma2 min readCurated summary

Double Click: When Coding Becomes Conversation | Figma Blog

Vibe coding replaces much of traditional programming with an ongoing conversation with AI: users describe an idea, review the result, and iterate through prompts. It lowers the barrier to creating software and makes experimentation faster, especially for prototypes and side projects. However, the approach can become unreliable as projects grow, producing tangled code and weak internal architecture. ## From Code to Conversation - Andrej Karpathy coined “vibe coding” to describe building software by talking to AI tools such as Cursor Composer and using voice input. - The process emphasizes seeing results, describing changes, running the project, and copying or pasting outputs rather than understanding every line of code. - The idea reflects a broader history of abstraction, from punch cards to assembly, C, Python, and now AI-assisted development. ## Faster, More Accessible Prototyping - Vibe coding lets people express interactive ideas without mastering syntax or a programming language. - Charmaine Lee of Val Town compares it to casually writing in a document or creating a spreadsheet. - Figma designer Nikolas Klein argues that the main benefit is shortening the gap between imagining an interaction and seeing it work. - Replit CEO Amjad Masad reported that 75% of Replit customers never write a line of code. - Figma engineer Vincent van der Meulen used AI to create projects, including a running coach and a loading animation, despite lacking SwiftUI expertise. ## The Complexity Ceiling - Vibe coding is most effective at the beginning of a project, when requirements are simple and experimentation matters more than structure. - As complexity increases, AI-generated solutions may stop fitting together coherently. - Developers can reach a “valley of despair”: an initial burst of progress gives way to difficult debugging and maintenance. - Vincent described ending up with “spaghetti code” and no consistent internal data model after reaching roughly 80% of his goal. Vibe coding is best treated as a powerful prototyping and exploration technique, not a replacement for engineering judgment. Teams should still inspect, test, refactor, and architect AI-generated code when projects become complex or production-critical.

Read original(opens in new tab)
figma2 min readCurated summary

In Good Company: How Publishers Use Figma to Help Design the News | Figma Blog

Publishers are adapting to digital-first journalism by redesigning products, developing new visual identities, and experimenting with formats that attract and retain readers. The article argues that Figma helps media organizations coordinate designers, editors, engineers, and executives while maintaining accuracy, clarity, and accessibility. The New York Times’ redesigned app illustrates how collaborative prototyping can support a broader subscription ecosystem without losing journalism’s central role. ## The shift toward digital-first publishing - Legacy publishers face accelerating change as audiences move from print to web and mobile. - Subscription models are becoming more important amid an unpredictable advertising market, although many readers remain reluctant to pay for online news. - Media teams must build stronger relationships with readers while exploring new products and formats. - Figma supports this work by keeping multidisciplinary teams aligned during design and experimentation. ## The New York Times’ redesigned app - Relaunched in October 2024, the app reflects The Times’ strategy of connecting multiple products, including News, Games, Cooking, Audio, Wirecutter, and The Athletic. - The redesign places the **Today** section and the latest news at the center of the experience. - A top navigation system makes other verticals easier to discover, with each product receiving its own home screen. - Rather than creating one “super app” feed, the design gives each section a distinct visual identity: - Lifestyle uses image-heavy grids with headline overlays, based on a component called a “poster.” - Opinion uses stylized headlines to communicate its different editorial perspective. - The overall concept treats journalism as the central “sun,” with other products orbiting around it. ## Figma as a newsroom collaboration space - The project involved section editors, engineers, senior management, product designers, and The Times’ storytelling group. - Teams used Figma asynchronously to explore layouts combining text, images, video, and audio. - Designers could share interactive prototypes directly instead of preparing as many presentation decks or relying on screen-sharing meetings. - The shared workspace helped stakeholders see colleagues’ work immediately and participate in shaping the app’s editorial formats. The article’s broader recommendation is that collaborative design tools can help publishers manage complex digital transformations while preserving strong editorial identities.

Read original(opens in new tab)
figma3 min readCurated summary

Meet the Makers Defining Tech’s Next Chapter | Figma Blog

The post previews Config 2025 and introduces speakers exploring how technology can become more human-centered. Their work spans AI-native devices, creator tools, AI interfaces, and expressive robotics. Together, they suggest that technology’s next chapter will depend not only on technical capability, but also on accessibility, empathy, and thoughtful design. ## Config 2025 and Its Vision - Figma’s Config conference will take place in San Francisco from May 6–8 and in London on May 14. - The event will examine how AI and automation are changing the way people create and experience technology. - Figma emphasizes tools and experiences that respond to evolving human needs. - In-person London tickets are sold out, while San Francisco tickets and free virtual attendance remain available. ## Building the Next Computing Platform - Andrew “Boz” Bosworth, Meta’s CTO and Head of Reality Labs, began coding through a 4-H club and later taught Mark Zuckerberg’s AI class at Harvard. - As Facebook’s 10th engineer, he helped create the News Feed. - He now leads Meta’s work on AR glasses, mixed-reality headsets, and the metaverse. - Bosworth envisions AI-native devices and proactive, personalized assistants becoming part of everyday computing. - At Config, he will discuss Meta’s efforts to develop a new computing platform. ## Making Creator Tools More Inclusive - Ebi Atawodi, Director of Product Management for YouTube Studio, combines experience in literature, technology, and product leadership. - Her work focuses on helping creators develop ideas and reach new audiences, including through AI-powered features. - Atawodi stresses that technology must be accessible and designed for people who have historically felt excluded by products. - Her approach centers on creating tools that serve a broad range of creators rather than assuming a single user experience. ## Designing Interfaces for Advanced AI - Joel Lewenstein, Head of Product Design at Anthropic, works on the interface for Claude. - He compares designing AI systems to watching a child discover new abilities, highlighting the uncertainty and possibility of emerging technology. - AI’s growing sophistication challenges traditional assumptions about how software interfaces should work. - Lewenstein argues that strong designers are defined more by how they think than by experience in a particular industry. ## Giving Robots Personality - Dr. Madeline Gannon uses her research studio, Atonaton, to transform industrial robots into expressive, lifelike mechanical creatures. - Supported by a Knight Foundation grant, she investigates how art and empathy can influence relationships with autonomous machines. - Her work explores how easily people attribute life and intention to nonliving objects. - Rather than reproducing the complexity of the human mind, Gannon demonstrates how movement, appearance, and context can make robots feel animated. Config’s featured makers represent a broad view of technological progress: more capable devices and systems must also be accessible, intuitive, expressive, and emotionally resonant. The conference aims to explore that balance through the experiences of people actively shaping AI, design, and robotics.

Read original(opens in new tab)
figma2 min readCurated summary

Making Metrics Matter | Design Systems 104 | Figma Blog

Design systems create measurable business value, not just reusable components and documentation. Figma argues that tracking adoption, usage, consistency, and time savings helps teams prove that value and identify where systems need improvement. The evidence is significant: designers with access to a design system completed tasks 34% faster, while some companies reported time savings of up to 50%. ## Measuring the Value of Design Systems - Figma’s research found that design-system users completed tasks **34% faster** than those without access. - For a team of seven designers, this efficiency is comparable to adding **3.5 designers’ worth of capacity each week**. - Participants also felt more confident because the system helped ensure their work aligned with the broader product. - Vanguard reported design updates happening **50% faster** with effective systems. ## Adoption and Usage as Business Signals - Creating components and documentation is only the starting point; measuring actual adoption reveals whether the system is delivering value. - Headspace reported: - **20–30% time savings** on straightforward tasks. - Up to **50% savings** on complex projects through tokens and variables. - Swiggy cut feature rollout time in half after implementing stronger tracking. - These results connect design-system usage to improved consistency, efficiency, and scalability. ## Reading the Signals Organizations should choose metrics that reflect their goals, including: - **Library and component usage:** Track which components, variables, and styles are frequently used. - High usage identifies the system’s most valuable “workhorses.” - Low usage can reveal elements that need improvement, replacement, or deprecation. - Tracking time saved through component reuse provides a concrete benefit that can help secure stakeholder support. A practical approach is to measure not only what a design system contains, but how consistently and effectively teams use it.

Read original(opens in new tab)
figma3 min readCurated summary

Double click: Human Takes on Agentic AI | Figma Blog

Agentic AI could fundamentally change UX by handling tasks across apps with minimal supervision, reducing the need for users to navigate complex interfaces. Supporters see agents as a new abstraction layer that lets people focus on goals rather than buttons, menus, and tabs. However, the shift also raises concerns about designing for machines at the expense of human creativity, agency, and meaningful interaction. ## The Promise of Agentic AI - Agents can take routine work off users’ plates, such as paying bills or completing multistep tasks. - Perplexity’s Henry Modisett argues that AI should be “how something works,” not necessarily what users directly interact with. - The ideal experience resembles starting a car: users specify where they want to go without needing to understand the machinery underneath. - Agentic systems may reduce the cognitive load associated with chatbots, personalities, and complicated interfaces. ## Agents as a New Web Abstraction - Agents could operate across platforms, creating a more interoperable web that works more like human workflows. - They may reduce the need to navigate menus, manage open tabs, or repeatedly switch between applications. - Rather than one all-purpose AI, the future may involve specialized agents collaborating like a team. - This could shift users’ attention from browsing and operating software toward creating, connecting, and pursuing goals. ## Designing Websites for Machines - Maintaining and optimizing websites for AI agents could become a distinct industry. - Websites may increasingly prioritize: - Clean APIs - Machine-readable content - Clear structure - Streamlined navigation - Visual polish, animations, and pixel-perfect layouts may matter less to agents than accessibility and functional interoperability. - Designers and developers must consider whether they are primarily building for humans, machines, or both. ## Preserving Human Creativity - Optimizing exclusively for AI could flatten the web and remove creativity, depth, and intentional visual experiences. - The growth of agentic systems arrives alongside renewed interest in: - Creative coding - Handcrafted websites - Experiences that move beyond templates - The industry has an opportunity to decide which tedious work to automate while preserving the aspects of the web that feel expressive and distinctly human. ## The Value of Friction and User Control - Traditional UX often treats friction as something to eliminate, but autonomous agents complicate that principle. - Users need deliberate moments to: - Review an agent’s proposed action - Approve consequential changes - Correct mistakes - Stay aware of what the system is doing - Carefully reintroduced friction can preserve agency and trust, even when the agent performs most of the work. - Good agentic design may therefore prioritize appropriate checkpoints over completely invisible automation. Agentic AI is still in its early stages, but it is likely to reshape both web infrastructure and interface design. The strongest approach is to automate complexity while preserving human oversight, creativity, and opportunities for meaningful participation.

Read original(opens in new tab)
figma3 min readCurated summary

Sustainability Week at Figma | Figma Blog

Figma’s first Sustainability Week combined employee education, workplace initiatives, and investment in climate technology. The company is pursuing net-zero emissions by 2040 through carbon accounting, offset purchases, and support for emerging carbon-removal methods. Its central message is that meaningful climate action requires both reducing current emissions and helping promising technologies scale. ## Sustainability Week Activities - Figma hosted five days of programming focused on individual and organizational sustainability. - Employees learned about climate solutions through: - A discussion with Charm Industrial CEO Peter Reinhardt - A tour of Charm’s San Francisco facilities - Climate documentaries, books, and educational YouTube channels - The company also: - Displayed climate trivia in global offices - Offered locally grown food at its San Francisco and New York hubs - Created a sustainability wiki on Notion - Curated organizations eligible for Figma’s donation-matching program - These activities encouraged employees to focus on manageable actions such as reducing emissions, cutting waste, and conserving energy. ## Figma’s Climate Commitments - Employees began exploring carbon accounting and offsets in 2021. - The group became Figma’s official Net Zero social impact group in 2022. - Figma signed the Climate Pledge and aims to reach net zero by 2040. - The company works with Watershed to: - Measure its annual carbon footprint - Purchase carbon-removal, offset, and avoidance credits - Support projects through Watershed’s climate marketplace - Figma invested $750,000 in offset and avoidance credits through Watershed in 2024, following an earlier $500,000 investment in carbon removal. ## Carbon-Removal Technologies - Charm Industrial uses fast pyrolysis to convert organic waste, or biomass, into: - Biochar, which can improve soil and store carbon - Bio-oil, which can be injected deep underground for permanent sequestration - Figma’s 2024 climate portfolio also includes: - Wakefield’s biochar production from waste wood - UNDO’s enhanced rock weathering, which accelerates natural carbon-storage processes - Vaulted Deep’s underground storage of human organic waste - Figma has continued investing in Charm Industrial’s bio-oil sequestration technology. ## Scaling Climate Solutions - Peter Reinhardt argued that companies need a detailed technical understanding of the actions that produce meaningful climate results. - He recommended that companies: - Forecast carbon-accounting needs several years in advance - Invest strategically in smaller climate suppliers - Help emerging technologies and providers scale - Figma presents corporate climate investment as a way to support technologies that may be essential for achieving future net-zero goals. Figma’s approach combines internal behavior changes with long-term investment in carbon-removal infrastructure. Companies pursuing similar goals should measure emissions carefully, reduce what they can, and support credible technologies early enough to help them mature.

Read original(opens in new tab)
figma2 min readCurated summary

The Long and Short of It: Issue no.9 | Figma Blog

Issue no. 9 of Figma’s blog presents six “memos” about preserving craft, purpose, and creativity amid blurred roles, rapid product cycles, and emerging technology. The collection argues that digital creation should become more personal, emotionally resonant, adaptable, expressive, and inclusive. Rather than prescribing one method, the memos invite teams to question established approaches as they plan for 2025. ## Personalize the Web - Product Designer Chia Amisola argues that the internet has become increasingly standardized as it serves broader audiences. - She calls for a more personal and poetic web, inspired by the resurgence of small, handcrafted websites. - The accompanying essay, “Making space for a handmade web,” suggests that participating in this movement can begin simply by creating a site of your own. ## Build an Emotional Competitive Moat - Head of Insights Andrew Hogan argues that product differentiation cannot rely on features alone. - As software becomes more ubiquitous, emotional resonance can make an app feel distinctive and meaningful. - Teams should treat emotional response as part of product strategy and put “resonance on the roadmap.” ## Leave Room to Depart from the Roadmap - Director of Product Avantika Gomes challenges the idea that successful products must follow a fixed vision or predefined sequence of solutions. - Unexpected changes and discoveries can shape a product as much as its original roadmap. - Teams should avoid becoming overly attached to specific solutions and create room to pivot when circumstances or user needs change. ## Reclaim Creative Coding - Developer Jake Albaugh encourages developers to use the web’s expressive capabilities more fully. - He points to creative coding and the work of Henry Desroches as examples of how code can support experimentation and artistic expression, not just functional interfaces. ## The Value of Generalists - Content Strategist Carly Ayres revisits the discussion around generalists and hybrid roles. - As collaboration increasingly crosses design, development, writing, analysis, and product management, people who operate across disciplines may become especially valuable. ## Expand the Definition of Design - Another memo makes the case for greater inclusivity in design. - It suggests that the industry should reconsider narrow assumptions about who design serves and what design work includes. The collection’s practical message is to build with greater openness: make room for individuality, emotional connection, unexpected direction, creative experimentation, and broader participation. Teams planning new products should treat their process as adaptable rather than predetermined.

Read original(opens in new tab)
figma2 min readCurated summary

Documentation That Drives Adoption | Design Systems 103 | Figma Blog

Clear documentation turns a design system from an abstract set of rules into a practical tool teams can use consistently. The article argues that effective documentation must explain both how to implement components and why design decisions were made. When treated as a living resource, it improves adoption, onboarding, cross-functional communication, and product consistency. ## Documentation Bridges Design and Development - Razorpay’s teams often missed details such as button states and text-field error behavior before adopting its Blade design system. - Custom, hard-coded implementations made it easy for teams to omit important states or interactions. - Designers and developers may use different terminology, leading to: - Inconsistent naming conventions - Misaligned component properties - Different expectations about product behavior and appearance - Documentation connects design intent with technical implementation. - It should capture the reasoning behind decisions, not merely catalog available components. ## Benefits of Effective Documentation - Helps teams understand design principles and implementation details. - Encourages consistent decisions across products and platforms. - Speeds up onboarding for new team members. - Creates a shared language between designers and developers. - Reduces the risk that a carefully built design system will go unused. ## Choosing a Source of Truth - The first documentation decision is determining where information should live, rather than deciding what to write first. - Maintaining consistency becomes more difficult as design systems and organizations grow. - Static PDFs stored in shared drives quickly become outdated and disconnected from daily workflows. - Modern teams can choose among dedicated documentation sites and collaborative workspaces. - The best source of truth should fit the organization’s tools, processes, and scale. ## Custom Documentation Sites - Custom sites are particularly useful for large organizations. - They can integrate deeply with existing design and development tools and organizational processes. - A dedicated site provides a centralized, discoverable location for design principles, components, usage guidance, and implementation details. Effective design-system documentation should be centralized, searchable, and continuously maintained so that it remains aligned with both the system and the teams using it.

Read original(opens in new tab)
figma2 min readCurated summary

A first look at Config 2025: Two cities, one global community | Figma Blog

Config 2025 expands Figma’s annual product-building conference into a global, two-city event. A three-day conference in San Francisco will offer extensive programming and community spaces, while a new one-day London event will bring Config to Europe. Both events emphasize flexible participation, practical inspiration, and meaningful connections among designers, developers, and product teams. ## San Francisco Conference - Runs May 6–8, beginning with Config Commons on Howard Street near Moscone Center. - Config Commons will serve as a place to collect badges, meet attendees, and connect with the community. - Moscone Center will host: - More than 75 speakers - Over 50 sessions - Multi-track programming on May 7 and 8 - Attendees can customize their schedules by combining talks, installations, networking, and collaborative projects. - Figma is redesigning the venue to encourage more spontaneous conversations and “aha” moments. - The expanded Maker Space will include a dedicated stage for Figma community leaders to present their work. - Multiple badge check-in locations will be available at partner hotels and Config Commons. - In-person and virtual registration options are offered. ## London’s First Config Event - Takes place May 14 at ExCeL London. - The day-long program includes more than 15 speakers across 10 sessions. - In-person tickets have sold out, but virtual registration remains available. - London was selected because of its strong design history and growing technology community. - The event follows Config’s successful community connection in Singapore and extends the conference’s collaborative format to Europe. ## A More Connected Global Community - Figma’s goal is to make Config accessible to product-building communities on both sides of the Atlantic. - The two locations combine large-scale programming with spaces designed for networking, experimentation, and peer learning. - The conference format prioritizes attendee choice rather than requiring participants to follow a single schedule. Config 2025 is positioned as both a conference and a community experience. Those attending in person can expect a more interactive venue design, while virtual attendees can participate remotely from either city’s program.

Read original(opens in new tab)
figma2 min readCurated summary

Why Developers Should Embrace Creative Coding Again | Figma Blog

Creative coding once made websites distinctive, expressive, and technically ambitious, but templates and automation have made many sites predictable. The author argues that modern browsers now offer even more creative possibilities than before, yet designers and developers often remain constrained by outdated conventions. Reviving experimentation can help turn the web back into a medium for artistic expression rather than merely a container for information. ## From Handcrafted Websites to Templates - In the early 2010s, custom websites served as digital calling cards and demonstrated developers’ technical and creative skills. - Developers used emerging HTML5 capabilities such as: - Inline SVG - GSAP-powered animations - WebGL experiments - Complex CSS illustrations - Website builders and templates eventually made sophisticated features accessible to everyone. - This democratization was valuable, but it also encouraged predictable designs built around familiar patterns. ## The Browser’s Creative Evolution - Browsers now support capabilities that exceed those found in many design tools. - Important advances include: - Container queries - Advanced CSS scoping, inheritance, and responsive behavior - Dynamic units and sophisticated layouts - Improved typography, color handling, and animation - Adaptation to user preferences - Many newer designers and developers remain unaware of these features and continue working within older design paradigms. ## Modern Color and Design Possibilities - CSS supports color spaces beyond standard RGB, including: - HSL - OKLCH - These color spaces allow more vibrant and controlled gradients and transitions. - The author created a Figma plugin called **CSS color-mix()** to help connect modern CSS capabilities with design workflows. - As design and development converge, design tools can become places for experimentation rather than merely production and handoff. ## Creative Coders as Examples - Henry Desroches creates responsive websites with the precision and dimensionality of print design. - Sarah Drasner has demonstrated the expressive potential of SVG animation and illustration. - Tim Holman’s projects, including **Optical Toys** and **The Useless Web**, embrace playful experimentation. - Lynn Fisher treats viewport changes as part of the artwork, creating illustrations that transform with the browser’s width. - These creators show that templates can be starting points rather than limitations. The author encourages developers and designers to experiment with the browser’s full capabilities. By moving beyond templates and embracing creative coding, they can make websites that are more intentional, surprising, responsive, and expressive.

Read original(opens in new tab)
figma2 min readCurated summary

The New Competitive Moat is Emotion | Figma Blog

Software features are becoming easier to copy as the number of applications rapidly expands. The post argues that emotional resonance—how an app makes users feel—will become the stronger competitive moat. Product teams should therefore design deliberately for wonder, connection, reassurance, and delight, not just functionality. ## Emotional Resonance in Everyday Technology - The author’s experience as a parent shifted his view from limiting screen time to valuing technology that encourages creativity, curiosity, and connection. - Children’s products such as Pok Pok and Yoto create emotional impact through small details: - Playful sounds and character reactions - Tactile buttons with satisfying resistance - Experiences that inspire offline play - These details make the products enjoyable and worth paying for, beyond their basic educational or functional value. ## Small Design Details Create Meaning - Everyday apps can produce similar emotional responses: - An Apple Watch’s buzz and completed activity ring can make exercise feel rewarding. - Dating-app interactions, message reactions, achievement badges, and task-completion checkmarks provide encouragement. - Clear security guidance can reduce anxiety after a data breach. - Copywriting, animation, sound, motion, and haptics often matter more than the number of available features. - The most meaningful product experiences address users’ underlying emotions, such as relief, pride, comfort, excitement, or reassurance. ## Why Features Are No Longer Enough - Product teams often prioritize feature requests because they are concrete and easy to track. - Emotional outcomes are harder to quantify and may depend on users’ deeper fears, hopes, and motivations. - According to IDC, there could be twice as many applications in 2028 as in 2024. - As software becomes more abundant, competitors will be able to reproduce functionality quickly and cheaply. - A distinctive emotional experience is harder to copy because it depends on nuanced design choices and a deep understanding of users. ## Putting Resonance on the Roadmap - Teams should make emotional responses an explicit product objective rather than an accidental byproduct. - Research should look beyond what users request and examine how they feel and behave in real-world contexts. - Product decisions should intentionally support emotions such as wonder, confidence, connection, and accomplishment. The practical recommendation is to treat emotional resonance as a core product strategy. Features may attract users temporarily, but products that consistently make people feel understood, reassured, or delighted are more likely to build lasting loyalty.

Read original(opens in new tab)
figma3 min readCurated summary

The Rise of the Generalist | Figma Blog

Generalist and hybrid roles are becoming more valuable as complex product problems increasingly cross traditional disciplinary boundaries. The article argues that AI will handle more specialized tasks, making human strengths such as connecting perspectives, asking valuable questions, and exercising judgment increasingly important. This does not eliminate specialization; instead, the strongest professionals combine deep expertise with complementary skills. ## Generalists Move Beyond Startups - Startups have long depended on employees who can switch between responsibilities, such as growth, UX writing, onboarding, and marketing. - Larger companies are increasingly recognizing that complex problems rarely fit within one job category. - Emerging hybrid roles include: - Full-stack marketers combining brand and performance marketing - Product managers fluent in design systems - Sales professionals experienced with multiple customer segments ## Breadth Versus Deep Expertise - Generalist careers offer: - More opportunities to change direction over a long career - Exposure to ideas and methods from different fields - Greater adaptability as technology and job requirements change - Specialists may worry that the push toward generalization devalues years of focused expertise. - The article’s position is not that specialization should disappear, but that deep expertise becomes more valuable when paired with complementary capabilities. ## The Rise of the Multi-Specialist - The “design engineer” illustrates how combined skills can create new, highly sought-after roles. - Design engineers can: - Turn ideas into working prototypes with less communication loss - Recognize technical constraints and opportunities early - Bridge design and engineering teams - Similar combinations apply elsewhere: - Designers who understand engineering can propose more feasible solutions. - Writers familiar with implementation can produce more cohesive documentation. - These professionals are not shallow dabblers; they develop meaningful expertise in multiple connected areas. ## Hybrid Roles Are Spreading - Companies are hiring for roles such as: - Operations Generalist at Linear - People Generalist at Datadog - Software and 3D Generalists at IBM - Multifaceted brand storytellers at Anthropic - The article notes that thousands of generalist positions appear in job listings. - These roles often emerge organically as people follow curiosity and build skills to fill gaps in their existing abilities. ## Generalists in an AI-Driven Economy - As AI becomes better at specialized tasks within defined boundaries, human value shifts toward: - Connecting insights across domains - Asking questions that bridge different perspectives - Identifying what is worth building, not merely what can be built - Applying taste and judgment to limited resources and attention - Specialists provide deep domain knowledge, while generalists help translate and combine that knowledge. - The most productive intersections often occur when one field is viewed through the lens of another. The practical recommendation is to retain deep expertise while deliberately developing adjacent skills. Curiosity-driven, cross-disciplinary learning can create rare capabilities and prepare professionals for roles that may not yet formally exist.

Read original(opens in new tab)
figma2 min readCurated summary

When To Off-Road the Product Roadmap | Figma Blog

Product roadmaps provide direction, but they should not become rigid commitments. Figma’s experience building Dev Mode shows that rapidly changing technology and user feedback often require teams to abandon planned work, pivot, or restart entirely. The best products are shaped by these course corrections rather than harmed by them. ## Why Traditional Roadmaps Need Flexibility - AI tools, agents, and coding assistants are accelerating product development and raising user expectations. - Six-to-twelve-month plans can become outdated before execution is complete. - Prescriptive roadmaps risk keeping teams committed to assumptions that are no longer valid. - Modern product development requires more experimentation, iteration, and willingness to change direction. ## Dev Mode’s Pivot from Code Generation - Figma initially envisioned Dev Mode as a way to automate the conversion of designs into code. - User feedback revealed that many developers already had reusable code for their design systems. - Developers often needed help assembling existing components rather than generating new CSS or code. - Figma shifted its focus to **Code Connect**, which lets teams customize the code snippets shown in Dev Mode using their existing design-system code. - The change delayed launches and frustrated people who had invested months in the original plan, but it better addressed user needs. ## Course Correction as a Product Strength - Figma argues that great products are often defined by twists and pivots. - Loom and Slack are cited as examples of companies that began with very different product concepts before finding their current direction. - Figma avoids letting sunk costs dictate future decisions. - Teams may abandon or restart projects when research, internal testing, or beta feedback shows that the product is not working. ## Learning Through Real-World Feedback - After Dev Mode’s 2023 beta, user feedback became more important than following the original roadmap. - Figma released more than 200 fixes and new features in a single month. - Rapid iteration can be frustrating, but it helps teams move toward outcomes that genuinely work for users. - Valuable information can come from user research, internal dogfooding, rapid prototypes, and beta programs. Teams should treat roadmaps as adaptable guides rather than fixed contracts. When evidence challenges the plan, experiment quickly, revisit assumptions, and be willing to go “off-road” to build the product users actually need.

Read original(opens in new tab)