Figma/ai

110 posts

figma

How To Move Fast Toward the Right Thing | Figma Blog (opens in new tab)

AI has made software execution dramatically faster, but it has not made judgment easier. The article argues that teams must deliberately decide what is worth building, provide agents with strong context and constraints, and preserve a distinct human point of view. Otherwise, polished prototypes can create hidden tech debt and increasingly average products. ## AI Accelerates Execution, Not Clarity - AI can quickly produce polished, production-like outputs, but apparent polish may hide weak decisions and fragile implementation. - Large language models often fill in missing requirements themselves, causing prototypes to fail under real-world constraints. - **Cognitive surrender** describes accepting AI-generated decisions without scrutiny or independent deliberation. - Teams should follow a “consideration imperative”: pause to understand the problem and define the right outcome before accepting the first plausible solution. ## Context Has to Come First - Agentic engineering shifts developers from manually writing every line of code to expressing intent clearly and directing AI. - Effective intent requires: - **Deterministic layers**, such as tests, type checks, and validation, to catch model errors consistently. - **High-signal context**, including specifications and documented components. - **Clear interfaces**, so agents understand how systems and components connect. - Tools such as Figma MCP’s Code Connect can provide agents with real production components, including props and variants, rather than forcing them to infer implementation from pixels. - Investing in design systems and documented decisions gives agents a precise vocabulary and guardrails, producing more consistent output, leaner code, and less technical debt. ## Good Can Still Be Average - AI tends to generate work that resembles common patterns in its training data, or work that is “in distribution.” - Typical AI-generated results—geometric gradient logos, familiar presentation fonts, or rounded-corner cards—are competent but interchangeable. - When teams repeatedly accept adequate results, their judgment can narrow from asking “What should this be?” to choosing “Which option is least wrong?” - As AI raises the baseline of acceptable work, products can become unremarkable unless people deliberately define what makes them distinctive. ## The Point of View Needs to Be Yours - AI can improve execution, but it cannot replace a team’s responsibility to establish intent, standards, and a meaningful perspective. - Without a clear point of view, the model’s default assumptions determine both what gets built and how it looks. - Moving quickly is valuable only when speed is paired with careful consideration, strong context, and deliberate choices. Teams should treat AI as an execution partner—not as the source of product judgment. Define the problem, encode decisions in systems and safeguards, and challenge generic outputs before shipping.

figma

Measuring Time Savings From Figma Make | Figma Blog (opens in new tab)

Figma’s Data Science team found that Figma Make reduced design-task completion time by 20% and made work 16% easier. Product managers benefited most, completing tasks 23% faster and reporting a 37% improvement in ease. Because ordinary A/B tests and observational analyses could not adequately control for task complexity and user experience, Figma used a randomized controlled trial (RCT) with 100 participants. ## Why Measuring AI Time Savings Is Difficult - Productivity is influenced by confounders such as: - Job tenure and career experience - Individual design ability - Task complexity - Without controlling for these factors, it is difficult to determine whether improvements come from AI or from differences among users and tasks. ## Limitations of Common Research Methods - **Online A/B testing** - Randomly assigning users to treatment and control groups helps balance user characteristics. - However, users may perform different tasks, making it difficult to ensure that task complexity is comparable. - **Causal inference using product logs** - Methods such as propensity score matching require all relevant confounders to be present in the data. - Anonymized logs cannot capture subjective factors such as a user’s design experience. - Instrumental-variable analysis requires a valid factor that influences AI usage without independently affecting task speed; Figma could not identify one. ## The Randomized Controlled Trial - RCTs were selected because they can control confounders before data collection begins. - The study combined: - Random assignment to Figma Make and control groups - Identical tasks for all participants - Moderation by trained researchers - The study focused only on Figma Make to avoid introducing variables from multiple AI tools. - Participants included 100 people: - 50 product designers - 50 product managers - The sample size was based on effect sizes from prior industry research, including GitHub Copilot RCTs, followed by a statistical power analysis. ## Findings - Overall, Figma Make: - Made design work **20% faster** - Made work **16% easier** - Product managers experienced the largest gains: - Tasks were **23% faster** - Tasks were **37% easier** The study suggests that a carefully controlled RCT is a more reliable way to measure AI’s productivity impact when task differences and user characteristics are difficult to capture in product data. Teams evaluating similar tools should standardize tasks, randomize participants, and moderate the study to separate genuine AI benefits from other sources of variation.

figma

AI Fluency Isn’t the Finish Line | Figma Blog (opens in new tab)

AI skills are increasingly viewed as essential, but Figma argues that tool fluency is only the starting point. As AI makes it easier to generate work, the more valuable capabilities are building shared systems, guiding teams toward decisions, and creating an environment where people can experiment together. The goal is not for one person to work dramatically faster alone, but for entire teams to move faster collectively. ## Become an Internal Product Builder - Individual AI expertise has greater impact when turned into shared tools that benefit the whole team. - Useful examples include: - Prototyping agents - Brand plugins - Shared prompt libraries - Internal prototyping playgrounds - Figma researcher Shane Johnston used AI to build an interactive website for exploring the company’s AI report data, making the information accessible to cross-functional stakeholders. - Figma’s Brand Studio created an image-effect generator in Figma Make so teammates could apply custom, on-brand textures to designs with one click. - AI enables more employees—not just engineers—to identify workflow friction and build tools that solve it. - The broader opportunity is shifting from one person working “10x faster” to the entire team becoming more productive. ## Guide People to a Decision - When AI can produce dozens of possible directions quickly, evaluating and selecting among them becomes a core product skill. - Effective facilitation requires involving the right stakeholders, including: - People with dissenting or contrarian perspectives - Colleagues with historical context - Experts who can identify operational, security, or governance risks - One team discovered that an internally vibe-coded app exposed sensitive company project information, illustrating why data governance experts should be involved early. - Teams should provide context before review meetings through: - Prototype demonstrations - Loom videos - Annotated FigJam files - At Figma, these materials help shift meetings away from explaining options and toward discussing trade-offs and making decisions. - Facilitators should ensure discussions reach a clear outcome by inviting quieter participants, clarifying vague recommendations, asking forward-moving questions, and confirming next steps. ## Share Bad Ideas - AI adoption is occurring at different speeds across teams and organizations. - The report found that: - 20% of respondents said individual contributors were advancing faster than their organizations could support. - 27% said leadership was pushing AI adoption while teams struggled to keep up. - Without deliberate knowledge-sharing and collaboration, the gap between early adopters and less experienced users can continue to widen.

figma

Digital Tools, Human Expression: The Visual Identity Behind Config 2026 | Figma Blog (opens in new tab)

Config 2026’s visual identity used digital tools and AI to express human creativity rather than replace it. Figma’s Brand Studio built a system around evolution, fluidity, and harmony, combining expressive glyphs, imperfect textures, and structured compositions. The result connected AI-assisted making with craft, experimentation, and distinctly human irregularity across digital and physical conference spaces. ## A Visual System for Human–Machine Collaboration - The identity reflected three aspects of modern design: - **Evolution:** remixing and reinventing ideas into something new. - **Fluidity:** moving between design and code while starting from different points. - **Harmony:** using generative tools while maintaining human judgment. - The system combined: - Sketchy, generative, and crisp glyphs. - AI-prompted textures. - Structured, dynamic compositions. - The contrast between “wonky” results and programmatic digital processes represented how ideas can morph and multiply. - Particle glyphs suggested ideas spawning and generating, while clean rectangles represented more resolved concepts. - Glyphs were translated into 14-foot foam sculptures and installed around San Francisco’s Moscone Center. ## AI-Assisted Texture Generation - Figma’s Brand Studio created tools in Figma Make to codify three lo-fi visual effects: - Scribbly linework. - Blurred gradients. - Oval-shaped particles. - Images were processed through these tools to create compositions that felt surprising, hand-drawn, and imperfect. - A custom dithering tool applied a consistent pointillist treatment to hundreds of speaker portraits. - The textures balanced digital precision with human qualities such as irregularity, grain, and imperfection. - Animated versions of the textures appeared at the conference’s block party and on keynote screens. ## Designing Static and Motion Assets Together - The team developed motion and still graphics in parallel rather than treating animation as a final production step. - Motion influenced visual design, while design informed motion decisions. - Bringing glyphs to life helped the team discover new directions for the identity. - This iterative process reinforced Config’s theme of ideas evolving through experimentation and collaboration. Figma’s approach demonstrates how AI can support a strong visual identity when it is guided by human taste and craft. The practical lesson is to use generative tools to create possibilities, while preserving controlled imperfections and human judgment in the final system.

figma

Sightlines Issue no.1: Insights from Config | Figma Blog (opens in new tab)

Figma’s first *Sightlines* issue distills lessons from Config’s Leadership Collective about leading design, product, and engineering teams in the AI era. Although organizations are still experimenting with AI, core leadership principles remain unchanged: build curious teams, preserve quality, collaborate openly, and rely on human judgment. As AI accelerates production, taste and thoughtful editing become increasingly important differentiators. ## Navigating Leadership in the AI Era - Leaders are still determining how to integrate AI into products, teams, and workflows. - The central challenge is gaining AI’s speed without sacrificing quality. - Many leaders are learning alongside their teams rather than presenting themselves as having all the answers. ## Fundamentals That Still Matter - Strong leadership continues to depend on: - Curious, critical-thinking teams - High standards for craft - Clear judgment about what makes work effective - Leaders are encouraging a beginner’s mindset by: - Starting from first principles - Experimenting with new tools and processes - Prototyping directly with their teams ## Collaboration and Human Judgment - AI tools can encourage isolated, individual workflows, so leaders are emphasizing collaboration more strongly. - Effective practices include: - Open critiques and feedback - Showing work early - Debating outcomes collectively - As AI automates more creation, human “taste”—the ability to judge, refine, and select high-quality work—becomes the key differentiator. ## Lessons from Industry Leaders - Teo Connor of Airbnb argues that an increase in mediocre AI-generated work will make strong editing and creative judgment more valuable. - Jen Dunnam emphasizes designing for people rather than chasing tools, noting that human needs remain constant. - Ian Silber of OpenAI recommends trusting capable teams and accepting that leaders cannot oversee every detail. - Jeetu Patel of Cisco describes meticulous design as a way to demonstrate care and create an emotional connection with customers. The practical recommendation is to adopt AI with experimentation and openness while preserving the human practices that sustain quality: collaboration, critical thinking, empathy, strong standards, and continual cultivation of taste.

figma

Workflow Lab: Deploying Designs Directly with Figma Make | Figma Blog (opens in new tab)

Figma’s workflow connects design, production code, and team review so designers can handle small, high-impact improvements without waiting for engineering backlog prioritization. Using Figma Make with a real codebase, a designer can identify accessibility issues, implement craft-level fixes, and move the work toward a merged pull request. The approach keeps engineers focused on larger architectural work while preserving design nuance and collaboration. ## The Problem with Backlog-Driven Fixes - Minor accessibility and usability improvements often enter a backlog where they compete with larger engineering priorities. - Small changes may be too granular to prioritize but too valuable to ignore. - Written handoffs can lose important nuance, creating clarification cycles between designers and engineers. - The example organization, the fictional Museum of Speculative Futures, is simultaneously improving accessibility and rewriting its website architecture. ## A Shared Ownership Model - The product manager proposes that engineers continue handling the major rewrite. - The designer takes end-to-end ownership of lower-risk, craft-level changes. - Figma Make with production code enables the designer to work directly against the real website implementation. - The workflow is intended to take changes from the Figma canvas through team review and into a pull request without filing a ticket. ## Testing the Existing Experience - Before making changes, the designer uses the Figma agent to generate synthetic personas, including: - A first-time visitor planning a trip - A returning member - Someone navigating with a screen reader - These personas explore the site and surface obvious friction early. - The audit identifies several issues: - A confusing exhibition or visit-page label - A call-to-action that is easy to miss - A date picker that is difficult to understand - A blank state when search returns no results - The article emphasizes that synthetic personas do not replace real user research, but they can identify issues before in-person sessions. ## Reviewing Design Improvements - The designer addresses the findings directly on the canvas. - The designer, engineer, and product manager review the proposed changes together. - They agree on improvements such as: - Clearer navigation language - A more prominent call-to-action - A more usable date picker - The changes support the shared goal of making the site easier to navigate for people with different ways of experiencing the web. The recommended workflow is to reserve engineers’ time for substantial technical work while enabling designers to directly resolve small, accessibility-focused issues in production code. Figma Make, the Figma agent, GitHub integration, and canvas-based review create a path from design insight to implementation without losing context or waiting indefinitely in the backlog.

figma

How to Lead Design Teams Through the AI Era | Figma Blog (opens in new tab)

Jen Dunnam argues that design leaders should respond to AI-driven change with calm, deliberate experimentation rather than panic. The fundamentals of design remain human-centered, so teams should prioritize clear thinking, strong principles, and the ability to turn insights into products. Her approach emphasizes investing in emerging talent while hiring and developing designers who can challenge assumptions. ## Lead with Calm - Leaders should steady their teams instead of adding to the urgency already felt by ambitious designers. - Break AI-related change into manageable steps: - Choose an approach. - Experiment with appropriate tools. - Refine design principles. - Learn from the results. - Designers should avoid chasing every new capability simply because it is novel or impressive. - AI may transform workflows, but designing for human needs remains the central responsibility. ## Hire for Critical Thinking - Dunnam would invest more heavily in designers fresh out of school, many of whom are disadvantaged by today’s pressure to ship quickly. - Pair early-career designers with experienced practitioners who can help turn ideas into shippable products. - Look for researchers who can move beyond gathering insights and contribute decisively to product direction. - Critical thinking has become especially valuable as AI tools make polished but potentially shallow solutions easier to produce. - Interviewers should ask candidates: - Where did they disagree with a stakeholder? - How did they push back? - What product decision still bothers them? - These questions reveal whether candidates can challenge attractive but poorly reasoned solutions. Dunnam’s practical recommendation is to keep teams grounded in human-centered design, combine emerging and experienced talent, and hire people with the judgment to question what appears easy, polished, or technologically exciting.

figma

7 Questions We Had Going Into Config Leadership Collective | Figma Blog (opens in new tab)

The post captures lessons from Figma’s Config Leadership Collective, where more than 1,300 design, product, and engineering leaders discussed leading through AI-driven change. Its central argument is that successful leadership depends less on rigid processes or tool expertise and more on adaptability, human-centered design, judgment, collaborative teams, and supported experimentation. ## Leading Change Through Experimentation - Leaders are learning alongside their teams as AI rapidly changes established workflows. - Rather than adopting fixed processes, they emphasize adaptability and continuous adjustment. - Executives are experimenting directly with new tools, prototyping ideas, and sharing failures. - Teams need permission to explore, take risks, and remain enthusiastic even when experiments fail. ## Preserving Human-Centered Design Fundamentals - AI has changed methods, but core principles remain important: - Understand users and their workflows. - Continue prioritizing craft and quality. - Design for people rather than simply following new tools. - Leaders warn against “chasing the tool” at the expense of human needs and thoughtful design. ## Expertise Is Moving Toward Judgment - AI can increasingly handle execution and task completion. - Human expertise is becoming more valuable in higher-order activities such as: - Taste - Discernment - Contextual decision-making - Evaluating and editing AI-generated work - Expertise now means selecting the best answer for a particular situation, not simply knowing a single correct answer. ## Restructuring Teams for the AI Era - AI is blurring traditional boundaries between design, product, engineering, and other disciplines. - Airbnb is organizing work into small, self-contained pods that resemble startups. - These pods combine core product roles with perspectives such as data science or business expertise. - Strong editing judgment, diverse viewpoints, and constructive disagreement are treated as essential. - Effective teams should be scrappy, vocal, ambitious, and willing to challenge one another. ## Helping Teams Adopt New Tools - Adoption requires education, infrastructure, and psychological safety—not just instructions to use AI. - Expedia is building dedicated support and training to help employees become fluent with AI tools. - OpenAI recommends starting with small, low-risk tasks instead of imposing large automation programs from the top down. - A simple use case, such as summarizing a long Slack thread, can demonstrate value and encourage broader adoption. The practical recommendation is to lead AI adoption as an ongoing learning process: experiment personally, preserve user-centered standards, hire for judgment and curiosity, build cross-functional teams, and introduce tools through manageable, well-supported steps.

figma

Trust You Can Verify: Figma Is Now ISO 42001 Certified | Figma Blog (opens in new tab)

Figma has achieved ISO/IEC 42001:2023 certification, making its AI governance independently verifiable rather than based solely on company assurances. An ANAB-accredited certification body, Schellman, audited Figma’s policies, risk management, data practices, and AI development processes. The certification is intended to give customers—especially regulated organizations—stronger evidence for vendor assessments, regulatory reviews, and board reporting. ## Why Independent Verification Matters - Vendors can describe their AI controls through questionnaires, whitepapers, and documentation, but those materials remain self-reported. - ISO 42001 requires an accredited third party to evaluate whether an organization’s AI management system meets an international standard. - Figma says this provides more reliable evidence than simply claiming to practice responsible AI governance. ## Scope of Figma’s Certification - The certification covers the AI Management System governing how Figma designs, develops, and operates AI features. - It applies across: - Figma Design - Figma Make - FigJam - Dev Mode - Figma Sites - Figma Slides - Figma Draw - Figma Buzz - Figma Weave ## What the Audit Evaluated - The audit took place in two stages: - **Stage 1:** Reviewed the design of Figma’s AI Management System, including documentation, policies, and risk methodology. - **Stage 2:** Tested operational effectiveness through staff interviews, process observation, and control evaluations. - Auditors assessed 38 controls across nine areas: - AI impact assessment - Governance and accountability - AI-specific risk management - AI system lifecycle management - Data governance - Third-party AI risk - Monitoring and performance evaluation - Human oversight - Responsible use of AI systems - Figma emphasizes that the certification validates implementation, not merely the existence of written policies. ## Relevance for Customers - The certification gives customers evidence they can reference in: - Vendor risk assessments - Board reporting - Regulatory submissions - AI procurement processes - It is particularly relevant to financial services, healthcare, insurance, and public-sector organizations with strict security, privacy, and regulatory requirements. - Figma connects the certification to the EU AI Act and emerging procurement standards, which increasingly require demonstrable governance rather than vendor promises. ## Ongoing Commitment - Figma plans to continue submitting its AI governance practices to independent verification as its AI capabilities evolve. - Its certificate and broader compliance documentation are available through `compliance.figma.com`. - The certificate can also be verified through Schellman’s directory, and Figma says it will update its documentation when governance changes affect customer risk assessments. ISO 42001 certification represents a baseline for Figma’s ongoing AI governance efforts, giving customers independently audited evidence they can use when evaluating the company’s AI products.

figma

Start Anywhere, a Magazine by Figma | Figma Blog (opens in new tab)

Figma’s 2026 *Start Anywhere* magazine explores how new tools are expanding the ways people begin and develop creative work. Its central argument is that as motion, code, and AI become more integrated into the design canvas, creative workflows are converging and becoming more expressive. Rather than prescribing one starting point, Figma encourages designers of all experience levels to choose an entry point and keep exploring. ## A Magazine About Design’s Changing Landscape - The magazine was created for Config 2026 by No Ideas, featuring work by several artists and designers. - Figma’s annual publication aims to capture what matters in design beyond rapidly changing product releases. - This year’s theme reflects the difficulty—and freedom—of writing about tools that evolve quickly. - The enduring principles are curiosity, patience, and understanding what something is before focusing on what it does. ## More Materials on the Canvas - Figma Motion introduces a timeline directly into the canvas, allowing designers to work with movement alongside components, variables, and collaborators. - Motion design principles remain important even as tools become easier to use: - Timing and mechanics give movement meaning. - Foundational craft helps designers make better creative decisions. - Code is also moving into Figma’s shared multiplayer environment. - Code layers allow teams to explore design and implementation side by side, making code a more direct part of the design process. ## The Design-to-Code Loop - As work moves fluidly between code and canvas, design and development workflows increasingly converge. - The magazine examines how this connected process can: - Enable faster experimentation. - Support multiple directions in parallel. - Improve collaboration between designers, engineers, and AI-focused teams. - Carry ideas more smoothly from early exploration into production. ## AI as a New Path from Idea to Product - AI tools are changing where product work begins and how ideas move through the development process. - The magazine presents examples from four organizations using AI in different ways. - These approaches suggest that AI can influence: - Ideation and initial exploration. - Product design and iteration. - The transition from design concepts to working software. - The continuity of ideas through production. ## Imagining Future Human–Computer Interaction - The “Future states” section asks what it might mean to reduce the gap between human and machine intelligence. - Contributors imagine software that interacts in more human-centered ways, including: - Interfaces that respond to users’ emotions. - Systems that help people anticipate the consequences of decisions. - New forms of interaction beyond traditional interfaces. ## Who the Magazine Is For - The publication addresses: - Beginners with ideas but no clear starting point. - Experienced practitioners looking for new creative possibilities. - Anyone who wants to produce effective design efficiently. - Its three covers represent different prompts and entry points into the same broader questions. The practical message is to start wherever the most interesting possibility appears—whether in design, motion, code, or AI—and continue iterating. The tools may change quickly, but curiosity and strong creative fundamentals remain useful across every workflow.

figma

Principles in Motion | Figma Blog (opens in new tab)

Motion design extends graphic design into time, using rhythm, pacing, sound, and sequencing to communicate ideas. The Figma designers argue that effective motion combines clear intent with an understanding of physics and human perception. Rather than copying trends, designers should draw inspiration from nature, film, art, and real-world movement. ## Motion Turns Design into a Sequence - Graphic design communicates through static images; motion adds: - Rhythm and pacing - Transformation and character - Easing and timing - Sound and synchronization - Motion allows designers to divide a story across multiple frames instead of forcing every idea into one image. - Timing can create emotion and direct attention, much like beats structure music. - Unexpected connections between sound and image can produce “happy accidents” and richer results. ## Physics as a Foundation - Real-world physics provides a reference for making animated movement feel believable. - A bouncing ball, for example: - Moves quickly after impact - Rises and slows near its highest point - Falls again - Loses height with each bounce - Viewers often recognize when motion feels “good” because it reflects familiar physical behavior, even if they cannot explain why. ## Finding More Original Motion References - Relying only on existing motion-design examples can lead to predictable trends. - Designers can develop more distinctive work by studying: - Movement in nature - Film storytelling and editing - Gestures and forms in art and design - These broader references help motion communicate character and meaning beyond standard bouncing shapes and rectangles. ## Core Motion Principles - **Ease in/ease out:** Controls acceleration and deceleration. - **Anticipation:** Prepares the viewer for an upcoming action. - **Overshoot:** Moves slightly beyond the destination before returning. - **Follow-through:** Keeps secondary elements moving after the main action ends. - **Hold:** Pauses so viewers can process an event. - **Settle:** Adds subtle final movement as an object comes to rest. ## Transitions and Continuity - Easing determines how movement begins, changes speed, and settles. - Match cuts connect separate shots through a shared movement. - Cutting at the fastest point of an action can make transitions feel seamless. - Transitions link individual story beats and help the overall piece feel cohesive. Motion works best when designers treat time as a storytelling material. Grounding movement in physics, using sound thoughtfully, and drawing from varied real-world references can make animation clearer, more expressive, and less predictable.

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

Figma’s 2026 AI Report: Can AI Help Us Collaborate Better? | Figma Blog (opens in new tab)

AI is shifting from a tool for individual productivity into a driver of team collaboration. Figma’s research shows that 41% of respondents believe AI is already changing how teams work together, up from 7% two years ago. The report concludes that shared workspaces, stronger design judgment, and coordinated adoption matter more than simply making individuals faster. ## AI Is Moving Work from Solo to Collaborative - Figma’s report draws on 8,403 survey responses and 639 interviews across ten markets. - Designers and developers are increasingly crossing into each other’s work: - Designers participating in development rose from 21% to 41%. - Developers doing design work increased from 44% to 60%. - Seventy-six percent of product builders say at least half their work happens on the canvas, while six in ten spend most of their time there. - Unlike terminals or prompts, a shared canvas lets teams explore ideas, compare designs, give feedback, and solve problems together. ## Design and Judgment Matter More in the AI Era - AI can generate products, copy, and assets quickly, but it cannot decide what is worth building. - As creation becomes cheaper and faster, teams must focus more on product choices, differentiation, user experience, and trade-offs. - Ninety percent of respondents say design is at least as important as before AI; nearly 60% consider it more important. - Developers increasingly share this view, with 65% saying design has become more important. - Collaborative decision-making helps teams develop sharper judgment instead of optimizing only for individual output. ## Four Patterns of AI Adoption - The report identifies four organizational approaches: - **Unified:** Individuals and leadership advance AI adoption together (36%). - **Directive:** Adoption is driven from the top down (27%). - **Grassroots:** Practitioners lead adoption from the bottom up (20%). - **Nascent:** AI adoption remains at an early stage (18%). - Directive and grassroots organizations both experience friction when teams lack shared practices and communication. - The main challenge is organizational alignment, not simply access to AI tools. ## Building Shared AI Practices - Grassroots adopters should make successful workflows visible, create structure, and promote shared spaces. - Leaders introducing AI should close the gap between strategy and everyday practice. - The goal is not for one person to move faster, but for the whole organization to make better decisions and move quickly together. Teams should treat AI adoption as a collaborative design and organizational challenge: establish shared workflows, keep work visible, and use AI to improve collective judgment rather than only individual productivity.

figma

Direct Every Frame with Runway Aleph 2.0, Now in Figma Weave | Figma Blog (opens in new tab)

Runway Aleph 2.0 is now integrated into Figma Weave, giving creators precise, frame-level control over video edits. The model supports longer clips, reference images, and sequential creative decisions while preserving footage that users do not ask to change. It also enables substantial transformations—such as new camera angles, characters, or environments—without requiring a reshoot. ## More Time, More Control - Aleph 2.0 supports video clips up to 30 seconds, allowing users to direct complete scenes. - Reference images can guide the visual style and appearance of edits. - Changes are applied across relevant frames while preserving unaffected elements. - Subject-specific edits follow that subject throughout the footage. ## Sequenced Creative Workflows - The Aleph 2.0 node in Figma Weave supports connected, step-by-step workflows. - Creators can preview edits before committing them. - Multiple decisions can be refined progressively rather than being forced into a single prompt. - The workflow mirrors traditional creative development on a visual canvas. ## Extending Existing Footage - Users can alter a scene beyond the limits of the original recording. - Possible changes include: - Adjusting the camera angle - Adding new characters - Transforming the environment - Multiple creative directions can be explored side by side without restarting from scratch. - The creator defines the desired conditions, while Aleph 2.0 generates the revised video. ## Pricing and Resources - Figma says pricing will soon scale according to input length, potentially lowering costs for some use cases. - Users can learn more through Figma’s help center, community templates library, and Weavy’s knowledge center. Figma Weave users can use Aleph 2.0 to move from broad AI generation toward more controlled, iterative video direction—making it useful for experimentation, editing, and visual development without reshooting footage.

figma

You Never Stop Cultivating Taste | Figma Blog (opens in new tab)

Mastery is not just learning tools or techniques; it is developing a distinctive point of view through repeated practice and intentional choices. Figma’s Loredana Crisan argues that “taste” is cultivated continuously through care for one’s craft, empathy for users, and disciplined attention to detail. AI can expand creative exploration, but it cannot replace the judgment that makes work personal and meaningful. ## Taste Is Built Through Practice - Expertise requires understanding both the material and the tools of a craft. - Crisan compares design to piano and music composition: technical correctness matters less than knowing why choices create emotion and impact. - Taste develops through: - Consistent practice - Mentorship and critique - Feedback and collaboration - Sustained creative attention - Developing a point of view is the most time-consuming part of mastery—and it never truly ends. ## Taste Is a Form of Care - Taste is visible when work feels intentional, refined, and thoughtfully executed. - Dieter Rams’ Braun products demonstrate this principle by considering not only an object’s function but also its surroundings, physical interactions, and overall experience. - Taste is not universal popularity; different designers can have different sensibilities while showing equal intentionality. - In product design, taste appears in trade-offs such as: - Form versus function - Expressiveness versus legibility - What to include versus what to omit - Which compromises to accept or reject - Taste comes from both love of the craft and care for the people using the result. - Designers should test details across varied contexts, including screen sizes, color profiles, languages, devices, transitions, and uncommon user states. ## What Designers With Taste Demonstrate When hiring for taste, Crisan looks for three qualities: - **Discernment:** The ability to identify what is not working and explain why with nuance. - **Empathy:** Attention to the person experiencing the interface, including needs that may not be obvious. - **Creative energy:** A persistent drive to make, experiment, and pursue side projects or unresolved problems. ## AI Expands Exploration but Cannot Replace Judgment - AI may reduce the labor involved in producing work, but accepting its first output would undermine the iterative process required for quality. - Examples such as James Dyson’s 5,127 prototypes illustrate how refinement and rejection are central to creative mastery. - Better tools increase the distance a creator can travel between an idea and its execution, but the vision still comes from the creator. - AI can help generate more possibilities, while taste determines which possibilities are worth developing. - A creator’s distinctive voice emerges from accumulated, intentional decisions repeated over time. The practical recommendation is to use AI and other tools to explore broadly, while continuing to practice, critique, refine, and care deeply about both the craft and the people who experience the final result.