Figma/ux-design

56 posts

figma

What Does the Future of Software Look Like? | Figma Blog (opens in new tab)

AI may reshape software around more human, contextual interactions rather than fixed menus and mechanical commands. The post argues that future interfaces could understand intent through voice, gesture, emotion, and situation, adapting their behavior to each person. Instead of forcing users to adapt to increasingly powerful systems, software could meet users where they are while encouraging focus, presence, and healthier technology habits. ## Ephemeral Tools - Controls appear only when users select an object and indicate what they want to do. - Contextual options replace persistent menus, panels, and modes. - A video editor, for example, might show timing, pacing, alternate cuts, and sound options around a selected clip. - This lets creators focus on decisions and intent rather than remembering how software is organized. ## Magic Marker - Users interact through a combination of voice, cursor movement, gestures, sound effects, and body language. - Someone could circle an object, drag it into position, and verbally request a change. - AI would interpret these signals together, making it feel more like collaborating with a teammate. - This reduces the need for precise prompt engineering or complex document references. ## Adaptive Presence - Intelligent systems adjust their communication style and level of assistance based on user behavior. - They might offer structured guidance when someone is confused, step back when help is unnecessary, or switch between text, voice, and visuals. - Software could change pacing, simplify language, and divide information into smaller steps. - This approach is especially valuable in healthcare and education, where differences in user readiness can have serious consequences. ## Empathetic Flows - Interfaces could infer emotional states from typing speed, stylus pressure, speech patterns, facial expressions, and repeated revisions. - A food app might reduce choices when someone appears overwhelmed. - A creative tool could become quiet when the user is concentrating, while a hotel app might stop promoting upgrades when the guest seems tired. - Rather than requiring users to explicitly state what they need, systems would respond to behavioral signals. ## Situational Cues - Sound, motion, pacing, progress indicators, and visual transitions can help users understand where they are in an experience. - Earlier digital products used cues such as dial-up sounds, progress bars, and “You’ve got mail” announcements to provide orientation. - Future interfaces should counteract the overstimulation caused by attention-driven notifications. - Persistent progress indicators, transition sounds, and consistent visual language could help users regulate their attention and nervous systems. ## Spatial Tuning - Users could control software through bodily movement instead of conventional tapping and clicking. - Examples include shaping music with hand movements, navigating augmented reality by changing body orientation, or adjusting design elements through gestures. - These interactions demand attention and presence, making them harder to rush or automate. - Technology becomes an experience that intentionally slows users down rather than continually rewarding speed. ## Mash-Ups - Future systems could combine any two inputs—files, objects, sounds, locations, or physical gestures—to create something new. - The system would synthesize the combined inputs while blending their structure, tone, and meaning. - Possible examples include merging a playlist with a city map or combining digital objects through touch or gestures. The overall recommendation is to design AI-powered software around human intent, context, emotion, and physical presence. The most successful future interfaces may be those that make technology feel less like a collection of controls and more like an adaptable, considerate collaborator.

figma

3 Ways Teams Are Building Conviction Faster With Figma Make | Figma Blog (opens in new tab)

Product teams are using Figma Make to turn abstract product ideas into interactive prototypes earlier in the process. By making concepts tangible, PMs can align designers and engineers, test assumptions, collect feedback, and build conviction before significant development begins. The article highlights examples from ServiceNow, Ticketmaster, and Affirm. ## Prototyping Instead of Relying Only on PRDs - Product managers traditionally translate customer needs, design goals, and engineering constraints into shared decisions. - Figma Make lets them create prototypes that demonstrate both a product’s appearance and behavior. - Interactive prototypes provide more useful early feedback than static mockups or abstract explanations. - Teams can identify problems, test ideas with users, and adjust direction before implementation progresses too far. - Earlier visibility helps teams make better-informed decisions and build products that more closely meet user needs. ## Bringing Complex Product Thinking Into Shared Focus - At ServiceNow, Product Director Ram Devanathan works with a design team serving multiple product groups, making dedicated design support difficult to obtain. - He needed to redesign a configuration page containing 15–20 settings, including technical options affecting incident prioritization and system load. - The initial mockup was functional but did not fully communicate the desired hierarchy, guidance, or tone. - Ram used Figma Make to transform the mockup into a clearer prototype: - Settings were grouped logically. - Simpler options appeared first. - Tooltips explained individual settings. - A warning clarified that changes required restarting the service. - The prototype gave Ram and the designer a shared, concrete representation of the intended experience. - Figma Make templates can also embed design systems and UX patterns, allowing PMs to iterate consistently without requiring designers for every early exploration. - Ram found that showing the idea directly was much more effective than describing it abstractly, helping the team reach agreement faster. ## Validating Features Before Building - The article next introduces Ticketmaster’s use of Figma Make for validating new features before development. - Ticketmaster applies prototypes to situations involving high-demand concert ticket purchases and internal dashboards for monitoring sales and troubleshooting issues. - The provided excerpt ends before explaining the specific feature-validation process or the third approach involving Affirm. Figma Make is presented less as a replacement for design or engineering and more as an early collaboration and validation tool. Product teams can use it to communicate complex behavior, explore alternatives, and secure alignment before committing substantial resources.

figma

Workflow Lab: AI Image Tooling and Interactive Prototyping in Figma | Figma Blog (opens in new tab)

Figma’s Workflow Lab demonstrates how teams can combine AI image editing, vector tools, and interactive prototyping to test conversion-focused product experiences quickly. For Trivet, a recipe app, the goal is to increase referral-program signups without disrupting the user journey. The team explores three approaches—an immersive modal, an integrated feed card, and a full-screen overlay—each using different visual strategies to balance attention and usability. ## The Signup Problem - Trivet’s referral banner is generating fewer clicks and signups than expected. - The team must determine whether the banner is: - Too subtle to attract attention - Too disruptive to support a smooth experience - The sprint tests three levels of visibility: - A modal - An in-feed card - A full-screen overlay - The team evaluates not only layout, but also tone, visual tension, and how attention affects conversion. ## Direction One: Use Visual Treatment to Spark Curiosity - A modal creates a more immersive interruption than an in-feed card. - Photography is used to support messaging about “unlocking” exclusive recipes. - Recipes are partially blurred so they appear visible but inaccessible. - Figma’s glass effect, refraction, and progressive blur create a frosted, layered surface. - The visual treatment makes the reward feel tangible while justifying the interruption. ## Direction Two: Add Personality to the Interface - The referral message is integrated directly into the feed to feel more supportive and less disruptive. - A hand-drawn cake illustration replaces photography because it requires less visual space. - Figma’s Remove background and Vectorize tools turn the raster sketch into an editable vector asset. - The designer: - Adjusts colors using brand variables found through inline fill search - Uses the Cut tool to refine edges while preserving paths - Rotates anchor points with bounding boxes to polish details - The result is a reusable, scalable illustration that adds texture and approachability to the card. ## Direction Three: Create a Full-Screen Overlay - A full-screen experience maximizes visibility and clearly signals priority. - The larger format requires photography strong enough to carry the entire interaction. - Instead of replacing an imperfect image, the designer adapts it to the layout. - The workflow uses precise image-editing tools such as Erase object to remove distracting elements, including a spoon. - This approach prioritizes visual impact, though it introduces the greatest interruption to the user experience. ## From Design Exploration to Prototyping - The workflow connects Figma Design, AI image tools, FigJam, and Figma Make. - Designers can move from visual experimentation to interactive prototypes without waiting for production assets. - A broader team—including product, content, growth, and engineering—can compare the concepts and evaluate which level of attention best supports signups. The practical recommendation is to test visual intensity against user experience rather than assuming maximum visibility will perform best. Figma’s integrated image and prototyping tools make it faster to create and compare multiple directions before committing to implementation.

figma

Why Demand for Designers Is on the Rise | Figma Blog (opens in new tab)

Companies are investing more in design, with 82% of leaders reporting that demand has either increased or remained steady. The post argues that AI is not reducing the need for designers; instead, it is increasing demand for people who can use AI tools, design AI products, and connect design with strategy and business growth. Fast-growing organizations are leading this hiring momentum, while employers increasingly favor experienced, AI-fluent candidates. ## Design hiring is increasing across industries - Nearly half of hiring managers say demand for designers has increased, and most of them report growth of at least 10%; more than a quarter report increases of 25% or more. - Technology companies lead hiring, but demand is also growing in sectors such as retail, publishing, aviation, and other non-tech industries. - Companies are hiring designers to improve digital experiences, strengthen online presence, and create new customer value. - Planned hiring varies by company growth: - 46% of fast-growing companies expect to increase hiring. - 40% of average-growth companies plan to do so. - 33% of slower-growth companies expect increased hiring. - High-growth companies view design as a way to test ideas earlier, move faster, differentiate products, and drive revenue. - Although only 20% of managers believe the overall hiring market is improving, 40% plan to add design headcount within six months. - Design job postings among Designer Fund portfolio companies reportedly rose about 60% in 2025 compared with 2024. ## AI is fueling demand for designers - Rapid advances in AI models and tools are creating demand for designers who can immediately work with evolving AI processes. - Employers want both: - Proficiency with AI tools in everyday design workflows. - Experience designing AI-powered products. - 73% of hiring managers report an increasing need for AI-tool proficiency. - 79% report an increasing need for knowledge of designing AI products. - AI fluency is increasingly treated as a hiring requirement rather than an optional advantage. - Companies are prioritizing candidates who combine technical ability, strategic thinking, experimentation, and approaches such as human-in-the-loop and human-augmented AI. ## Seniority and broader judgment matter - The article begins a discussion of companies prioritizing senior talent, particularly as teams face pressure to deliver quickly. - Hiring managers are looking for designers with strong skills, judgment, and experience—not only executional ability. - The combination of design expertise, strategic thinking, and AI capability is becoming increasingly valuable. Designers can improve their prospects by developing practical AI fluency alongside core design skills, learning how to design AI products, and demonstrating strategic judgment and business impact.

figma

Press Start: How Controllers Shaped Video Game Design—and Where Interfaces May Go Next | Figma Blog (opens in new tab)

Video game interfaces evolved from simple start screens into complex systems of menus, maps, inventories, and customization. Yet the controller’s directional inputs and buttons have remained a consistent foundation, shaping navigation patterns and preserving players’ muscle memory. The article argues that understanding how input devices define interfaces will be essential as AR, VR, and other technologies introduce new ways to interact with digital worlds. ## From Simple Screens to Complex Game Hubs - Early games such as *Tennis for Two*, *Pong*, *PAC-MAN*, and *Super Mario Bros.* offered minimal interfaces, often requiring only a coin insertion or a start button. - Modern AAA games support many features, including: - Multiple game modes - Character customization - Cosmetics stores - Maps and inventories - Quests and settings - These features have transformed games into interconnected hubs of screens, menus, and tabs. - The growth of gaming has helped make it a major cultural and economic industry, supported by livestreaming, esports, and Olympic recognition. ## Controllers as a Design Foundation - From the Atari 2600 to the PlayStation 5, controllers have consistently combined directional controls with buttons. - This consistency allows players to transfer familiar muscle memory between generations of games. - Established controller conventions create predictable navigation patterns for players. - Designers and developers benefit from these conventions because they reduce the need to create entirely new interaction models for every game. ## The Input Defines the Interface - Every platform has a dominant input method that shapes its interface: - Desktop: mouse - Mobile: fingers and touch gestures - Television: remote controls - Mouse interfaces can use small, dense controls because the pointer is fast and precise. - Touch interfaces require larger, more widely spaced controls because fingers are less precise than cursors. - Mobile design also takes advantage of gestures such as tapping, swiping, and pinching. - The article’s broader point is that interface design must reflect the physical capabilities and limitations of the device used to navigate it. ## Preparing for New Forms of Interaction - Game interfaces increasingly connect 2D navigation systems with 3D worlds. - AR and VR controllers may allow players to engage with their physical surroundings as well as digital environments. - As input methods evolve, designers will need to rethink how people move through interfaces, rather than simply adapting existing controller-based patterns. The practical recommendation is to treat input as a core design constraint. By studying how controllers shaped game navigation—and how emerging technologies change physical interaction—designers can build interfaces that feel intuitive across future platforms.

figma

How to Harness Skills That AI Can’t Automate | Figma Blog (opens in new tab)

Great products require more than AI-generated functionality; they depend on human craft, including curiosity, intuition, taste, and intention. AI accelerates prototyping and iteration, but people must decide what questions to ask, when to expand the scope, and whether an experience truly resonates. The article argues that these uniquely human skills are essential for steering AI toward thoughtful, high-quality outcomes. ## Curiosity: Starting from First Principles - Curiosity means asking “why” and “what if,” exploring multiple directions, and validating ideas through iteration. - Tools such as Figma Make, Claude, and ChatGPT make it faster to generate prototypes, campaign concepts, and alternative approaches. - AI can expand possibilities within a prompt, but it cannot independently challenge the original scope, follow an unexpected hunch, or recognize that a tangent deserves deeper investigation. - Early exploration improves confidence and reduces rework: - Figma designer Natasha Tenggoro used Figma Make to test video-playback concepts for Figma Buzz. - Prototyping exposed edge cases, clarified feasibility, and helped engineers understand the feature before implementation. - Curiosity can also lead to valuable scope expansion: - While designing icons for four new Figma products, Tim Van Damme realized the existing icon family needed a broader redesign. - He explored hundreds of variations and redesigned the suite for greater consistency, distinctiveness, scalability, and a unified Figma identity. ## Intuition: Following a Feeling - AI can help bring products to market quickly, but it cannot determine what will emotionally or practically resonate with customers. - Human designers can recognize when an interaction feels confusing even if it technically works. - Intuition may also identify qualitative improvements—such as adding white space to a crowded layout—that are difficult to express as strict requirements. - Eliel Johnson of CVS Health describes design as an active practice centered on asking whether an experience “feels good,” not merely whether it satisfies functional constraints. The practical lesson is to use AI for speed and breadth while reserving human judgment for direction, exploration, emotional resonance, and quality. Human craft is what turns technically workable output into a product people genuinely value.

figma

How To Build A Resilient Design Team | Figma Blog (opens in new tab)

Design teams must build resilience by creating psychological safety, encouraging experimentation, and preserving high standards of craft. The article argues that leaders should prepare teams to adapt to changing technologies, roles, and constraints rather than rely on a fixed playbook. Resilience comes from trust, flexibility, thoughtful capacity planning, and a willingness to question established assumptions. ## Start with Team Health - Stress, burnout, overwork, and fear prevent people from doing their best creative work. - Leaders should build trust and a shared mission while encouraging candid, non-personal critique. - Provide both synchronous and asynchronous ways for people to contribute so the loudest voices do not dominate. - Make it safe to share work at every stage, from rough sketches to polished designs. - Use regular 1:1s, career conversations, and feedback surveys to identify problems early. - Plan realistically around team bandwidth instead of overcommitting. - Model vulnerability by openly acknowledging uncertainty and personal challenges. ## Encourage Experimentation and Shifting Roles - Designers have different strengths, so teams should combine complementary skills and create opportunities for mutual learning. - Boundaries between design, research, product, and engineering are becoming more fluid. - Encourage designers to work closer to production through AI prototyping and code experimentation. - Sharing unfinished work and lessons learned—such as through Figma’s `#design-wip` channel—helps normalize experimentation. - Invite cross-functional partners into design critiques to bring broader perspectives into the process. - Balance shipping current work with inventing and testing new approaches as technology changes. ## Treat Craft as a Differentiator - High-quality, carefully executed products can distinguish a company in crowded markets, strengthen user loyalty, and drive growth. - Craft is especially valuable in enterprise software, where design quality is often neglected. - Strong execution requires attention to detail and may involve trade-offs, such as refining the user experience instead of adding more features. - Fast-moving teams must deliberately protect time for visual consistency, clarity, and overall product quality. ## Practical Recommendation Build resilience as an ongoing operating practice: protect team health, make experimentation routine, support fluid collaboration across roles, and treat quality as a strategic advantage rather than an optional extra.

figma

IDC Study Says the Global Workforce Engaged in Software Design Is Expanding | Figma Blog (opens in new tab)

IDC forecasts that the global workforce involved in software design and development will grow by more than 30%, reaching 144 million people by 2029. This expansion reflects the growing role of design as a competitive differentiator and the increasing demand for design talent. Generative AI is expected to accelerate product development while raising expectations for usability and visual quality. ## Workforce Growth in Software Design - The population of knowledge workers and developers designing digital products and interfaces is projected to grow from **107 million in 2025 to 144 million in 2029**. - The research covers multiple industries, company sizes, and roles involved in software design and product development. - IDC based its model on quantitative research involving more than 1,000 IT and business leaders. ## UX Design Leads Growth - UX professionals are expected to grow at a **7.6% compound annual growth rate** between 2025 and 2029. - This growth is expected to outpace other knowledge-worker categories. - IDC links the trend to rising demand for design-intensive digital products and solutions. ## Generative AI Raises the Bar - Generative AI will increase the speed and volume of software development. - Faster development may give users more product choices and enable better-designed digital experiences. - Designers and developers will face greater pressure to make AI-powered features highly usable, appealing, and intuitive. Overall, the study suggests that companies should treat design as a strategic capability and invest in UX talent as software development becomes faster and more AI-driven.

figma

In Good Company: How Retailers Use Figma to Elevate E-commerce | Figma Blog (opens in new tab)

The article argues that successful e-commerce depends on cohesive, trustworthy digital experiences that connect customer needs, operational systems, and brand values. It highlights how Nuuly, Ruggable, and GitHub use Figma to improve collaboration, maintain consistency, and create more engaging shopping experiences. Nuuly’s example shows how thoughtful design systems can simplify highly complex business processes for customers and employees alike. ## Nuuly: Simplifying Clothing Rental - Nuuly aims to make clothing rental an everyday habit, giving subscribers flexibility to experiment with their style. - Its business requires complex behind-the-scenes systems for: - Circular inventory management - Cleaning and repairs - Rental logistics - Nuuly built two separate design systems: - One for the customer-facing experience - One for internal rental-management tools - Both systems use flexible color and typography tokens so the brand can evolve seasonally. - The “My Nuuly” feature makes more than 26 rental statuses understandable by showing customers what is happening now and what to expect next. - In 2023, Nuuly migrated to Figma and consolidated 16 fragmented design files into two shared libraries. - Figma’s prototyping and collaboration tools helped the team: - Work faster - Communicate interaction details more clearly to developers - Stay aligned across departments - Content, photography, and other teams also adopted Figma, FigJam, and Figma Slides for brainstorming, reviews, and customer-journey improvements. ## Ruggable: Creating Consistent Digital Experiences - Ruggable’s UX leadership encountered siloed workflows across social advertising, the homepage, and product-detail pages. - These disconnected processes produced inconsistent digital experiences. - The article presents Ruggable as an example of how shared design practices can connect marketing and e-commerce touchpoints, though the supplied text ends before describing its specific solutions. ## GitHub and Design Business Company: Designing for Developers - The article also introduces a collaboration between GitHub and Design Business Company. - Their goal was to create a storefront specifically tailored to developers. - The partnership illustrates how brands can use design to add personality and delight while remaining aligned with their audience’s expectations. By combining scalable design systems with cross-functional collaboration, retailers can make complicated services feel simple, improve internal efficiency, and deliver a more consistent brand experience across every digital surface.

figma

How Headspace Built an AI Companion that Fosters Trust and Transparency | Figma Blog (opens in new tab)

Headspace built Ebb as an AI companion for reflection between therapy sessions—not as a replacement for human care. Because mental-health AI carries significant safety and trust risks, the team prioritized clinical grounding, transparency, user autonomy, and careful cross-functional design. Early alignment workshops, iterative prototyping, and explicit interface guidelines helped shape Ebb into a friendly but clearly non-human companion. ## Defining Ebb’s Role - Headspace created Ebb in response to growing use of general-purpose AI for emotional support. - The companion was intended to: - Support reflective practices between therapy sessions. - Help people who may be unable to access or afford therapy. - Complement, rather than replace, human care. - The team first clarified the complete user experience and business objectives through FigJam workshops. - This early alignment helped address internal concerns and ambiguity around using AI in mental health. ## Building a Non-Human, Approachable Identity - The team explored names including Odom, Ibo, and Scribe before choosing **Ebb**. - The name suggests the fluidity and changing nature of emotions. - Designers avoided a gendered human name to reduce stereotypes that associate caregiving with women. - Ebb was designed as a friendly, human-adjacent entity without a specific gender. - Brand, product, illustration, animation, and copy teams used FigJam “playgrounds” to explore how Ebb could look and sound. ## Iterative Collaboration and Prototyping - Headspace followed a “build-to-learn” approach, bringing brand and product teams together early. - The teams tested approximately six brand identities before selecting a direction. - Figma allowed designers to apply different visual treatments directly to product screens. - Sharing prototypes in one workspace kept teams connected and enabled rapid iteration. - The team deliberately stress-tested ideas before rejecting them. ## Designing for Trust and Safety - Ebb was trained with input from clinical psychologists, providing a strong scientific foundation. - Designers focused on reducing adoption barriers by helping users understand: - That Ebb is an AI system. - How it can support them. - How their information and conversations are handled. - The interface was designed to make users feel safe expressing themselves. - Users retain agency to exit and delete conversations at any time. - A central principle was that AI should never be invisible: members should always know whether they are interacting with AI or a human. - The team’s broader guidelines emphasized differentiating AI from human-delivered care, reinforcing privacy and safety, supporting member choice, and creating a reflective environment. Headspace’s approach suggests that mental-health AI should be designed transparently and collaboratively, with safety and user control treated as foundational product requirements rather than features added later.

figma

Version Control: How a UX Writer Weighs One Word Against Another | Figma Blog (opens in new tab)

A UX writer explains how a seemingly simple menu label for Figma’s offline prototyping feature revealed deeper questions about user expectations and product behavior. The team tested technically accurate, goal-oriented, and action-focused wording, but each option created confusion about what would happen after clicking. The central lesson is that UX copy must connect users’ intentions with the system’s actual behavior. ## The Challenge: Explaining Offline Prototyping - Users wanted a way to present prototypes reliably without an internet connection. - Engineers built an initial version that loaded prototype content in advance. - The remaining challenge was finding a few words that accurately explained the feature without requiring technical knowledge. - The writer argues that language exposes underlying product assumptions: choosing a verb forces the team to clarify what the system is really doing. ## Version One: “Preload Prototype” - “Preload prototype” accurately described the technical behavior: - Prototypes normally load screen by screen. - The feature gathers the necessary content upfront and retains it for later presentation. - However, “preload” implies that loading happens before the prototype appears, like “preheating” an oven. - Users had already loaded the prototype, so the prefix “pre-” did not match their experience. - Alternatives such as: - “Load full prototype” - “Load all screens” - “Load all assets” - These labels created a trust problem: users might reasonably assume that a prototype shown on screen was already fully loaded. - The wording needed to communicate that the initial load was incomplete without making the product seem unreliable. ## Version Two: Focusing on the User’s Goal - The team shifted from describing the technical process to describing the intended outcome: - “Present prototype offline” - “Prepare to present offline” - These phrases connected more directly to the user’s motivation: presenting without an internet connection. - However, “Present prototype offline” suggested that clicking the option would immediately begin presenting, even though it only prepared the prototype. - “Prepare to present offline” was more accurate but ambiguous: - Users would not know what preparation involved. - They would not know how far in advance to select it. - Both options might have worked within a larger workflow with explicit preparation steps, but they felt too imposing and unclear for a simple toggle menu. ## Language as an Interface to Computing - UX writing treats menu labels as actions or intentions: - Imperatives tell the program what to do. - Phrases can also express what the user wants to accomplish. - Terry Winograd’s principle that “people act through language” captures the problem: words connect a user’s mental model to a computer’s behavior. - When the wording, user intention, and system result are out of alignment, the interaction becomes confusing. - The article’s third iteration begins by examining what users can actually control, but the provided text ends before that approach is explained.

figma

The Long and Short of It: Issue no.9 | Figma Blog (opens in new tab)

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.

figma

The Best Advice to Bring to Work in 2025 | Figma Blog (opens in new tab)

The article gathers practical workplace advice from leaders at Ableton, Snapchat, Coda, and other companies. Their principles emphasize finding inspiration beyond familiar sources, automating low-value work, shortening users’ path to meaningful results, designing meetings around clear purposes, and maintaining momentum through difficult work. Together, they argue that effective work depends less on rigid formulas than on experience-based judgment. ## Look Beyond Design for Inspiration - Pablo Sánchez of Ableton recommends drawing ideas from emotions, memories, science, nature, and other fields—not just existing design conventions. - Designing for yourself first can produce work with genuine personal energy that resonates with users. - Ableton’s Note app borrowed from Brutalist architecture rather than traditional music software, creating a stripped-down experience focused on immediacy. ## Automate Work That Gets in the Way - Product managers should focus primarily on understanding customers, delivering value, and enabling sound decisions—not perfecting internal artifacts. - When documentation, reviews, or OKRs consume as much time as product development, teams should delegate or automate them. - Peter Yang uses AI to synthesize brainstorms, summarize customer feedback, and improve product requirement documents. ## Accelerate Users’ Time to “Magic” - Products should help new users reach their first meaningful “aha moment” quickly instead of overwhelming them with tutorials. - The goal is to move people from following instructions to confidently creating and sharing something of their own. - Snapchat’s Lens Studio team mapped the user journey and reduced the path from download to first submitted project from 19 steps to four milestones. ## Cultivate Different Types of Meetings - Coda’s Shishir Mehrotra distinguishes three meeting categories: - **Cadence meetings:** Regular staff meetings, standups, and syncs that track progress against goals. - **Catalyst meetings:** Decision-making forums, product reviews, and design critiques that resolve questions and drive change. - **Context meetings:** All-hands meetings, off-sites, and orientations that share information, establish context, and build connections. - Teams need a healthy balance, since too many catalyst meetings can cause burnout. ## Keep Moving Through Difficult Work - Dan Mall compares difficult progress to the tedious parts of training that are usually omitted from an exciting montage. - His advice is to build momentum to counteract the discouragement and monotony that can accompany worthwhile goals. The broader recommendation is to focus attention on meaningful outcomes: use unconventional sources of inspiration, remove unnecessary effort, guide users quickly toward value, give meetings a clear purpose, and keep building momentum when progress feels slow.

figma

Breaking In: A Guide To Landing Your First Product Design Role | Figma Blog (opens in new tab)

Figma’s guide explains how aspiring product designers can land their first role by presenting strong work, communicating their thinking, and showing how they learn from challenges. It emphasizes that a portfolio should be personal but focused on clear storytelling, accessible navigation, and evidence of design impact. The strongest projects are those where candidates can explain their decisions, trade-offs, constraints, and outcomes. ## Crafting a Portfolio - Portfolios do not need to follow one prescribed format or use a specific website builder. - The priority is to: - Showcase your best work. - Tell compelling project stories. - Make the portfolio easy to navigate. - Represent your individual perspective and skills. ### Lead with Your Best Work - Your first project creates the initial impression, so lead with work that best demonstrates your: - Design skills - Creativity - Process - Product impact - If choosing between projects, feature the one you can discuss most naturally and explain most compellingly. - Strong case studies should include: - A clear problem statement - Important project milestones - An insightful conclusion - Relevant metrics and learnings - What you would change in retrospect - A project does not need to have been an overwhelming success. Honest reflection and lessons learned can create a stronger narrative. - Explain the reasoning behind design decisions, not just the final visuals. - Discuss the trade-offs, advantages, disadvantages, constraints, and implications of choices involving colors, components, styles, and copy. - Figma designer Tammy Taabassum argues that explaining “why” demonstrates product thinking more effectively than simply showing “what” was designed. ## Figma’s Early-Career Opportunities - Figma welcomes interns and new graduates onto its product design team. - Early-career designers are encouraged to contribute actively and bring new ideas rather than merely observe. - The guide is intended to explain what Figma looks for and how aspiring designers can prepare for its interview process. A practical approach is to build a portfolio around a few well-developed case studies, prioritize the work you can explain most clearly, and make your decision-making and learning as visible as the final design.

figma

Crafting the Visual Identity for Config 2024 | Figma Blog (opens in new tab)

Figma’s Brand Studio created Config 2024’s visual identity as an immersive extension of the Figma brand. Inspired by the redesigned Figma canvas and Figma Slides, the team developed a flexible, shape-based system that could work across a massive physical and digital conference experience. The result balanced visual variety with practical UX needs for more than 10,000 in-person attendees and a larger virtual audience. ## Balancing Form and Function - The team drew inspiration from switching between different modes of making, such as creating, sharing, and presenting work. - They developed a visual language centered on shapes that could: - Shift and transform - Amplify creative ideas - Reveal unexpected perspectives - Represent collaboration and multiple modes of creation - Three large physical supergraphics formed the conference’s central installations. - Attendees used them as seating, photo backdrops, and meeting points. - The identity was designed not only for visual impact but also for usability. - It supported complex experiences such as registration and navigating popular talks. - The system helped guide attendees through the event while maintaining a cohesive look. - Simple primitive shapes served as the foundation for more complex graphic structures. ## Designing at Scale - Config required a large volume of assets across physical spaces, digital surfaces, signage, merchandise, and other touchpoints. - The team created a modular system that could remain consistent without becoming repetitive. - Its core shapes came directly from the Figma toolbar: - Rectangle - Circle - Polygon - These basic forms reflected the starting point of the design process in Figma and became components of larger supergraphics. - The team built a reusable component library in Figma to generate variations efficiently. - Each supergraphic included three variants, allowing shapes to be presented from different angles and creating visual variety across the conference. Figma’s approach demonstrates how a strong event identity can combine expressive branding with a practical, reusable design system. By treating simple interface primitives as flexible building blocks, the team created a conference experience that could scale across environments while remaining recognizably Figma.