ai-tools

8 posts

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

4 New Ways to Go From Idea to Product With AI Tools | Figma Blog (opens in new tab)

AI tools are reshaping product development by enabling teams to prototype, test, and refine ideas earlier and across both code and design. The article argues that working prototypes can expose problems that static mockups miss, while preserving design context throughout the path to production. It illustrates this shift through examples from FloQast, Merkle, Affirm, and Accor. ## AI-enabled product workflows - Product teams are: - Prototyping earlier instead of relying solely on traditional requirements documents. - Testing ideas in code before finalizing designs. - Exploring more possibilities at greater scale. - Carrying design-system context into implementation. - Figma presents these practices as ways to balance faster iteration with deliberate product decisions. ## Testing constraints in code AI coding tools make it easier for non-developers and product teams to build functional prototypes involving: - Multi-step workflows. - Conditional behavior based on user permissions or data. - Actions that trigger subsequent actions. - Realistic backend logic and data relationships. A prototype can then be moved into Figma with Codex to Figma for collaborative exploration and refinement. If implementation work continues in code, teams can move the design back through MCP while retaining the relevant design context. ## FloQast’s complex workflow prototype ### The challenge - FloQast needed to redesign an accounting workflow for investigating discrepancies. - Users previously had to move between multiple pages to: - Find an issue. - Investigate it. - Resolve it. - The team wanted one page where users could see tasks, identify blocked work, and take action. - Because the workflow depended on interconnected steps, real data, and business logic, a static mockup could not fully validate the concept. ### The unlock - UX manager Benjamin Ellis built a working prototype with an AI coding tool. - The prototype included: - A simulated backend. - Realistic data based on an actual customer’s workflows. - Clickable scenarios where completing one task affected the next. - Testing the workflow revealed interactions that appeared sound in a design mockup but failed when subjected to realistic conditions. ### The impact - The team and designer committed to a direction only after testing it against real scenarios. - They identified interaction problems earlier. - The approach reduced later surprises and increased confidence in the final design. ### When this approach is useful - When behavior depends on permissions, data, or sequential actions. - When a small fix is faster to make directly in code. - When designers and developers need a working example to scope a complex experience together. ## Exploring with AI on the canvas The next section introduces using AI directly in the Figma canvas to explore product possibilities. The provided excerpt ends before describing the specific workflow or company example. Teams should use code-backed prototypes when logic and real data are central to the experience, then bring those prototypes into collaborative design tools to refine decisions with greater confidence.

gitlab

GitLab and Vertex AI on Google Cloud: Advancing agentic development (opens in new tab)

GitLab is partnering with Google Cloud to combine the GitLab Duo Agent Platform’s lifecycle-wide orchestration with Vertex AI’s managed foundation models and enterprise controls. The integration gives development teams context-aware agents for planning, coding, security, and delivery while keeping workflows within GitLab’s governed system of record. Customers gain model flexibility, stronger governance, and reduced complexity compared with managing disconnected AI tools. ## Agents Across the Software Development Lifecycle - GitLab Duo Agent Platform coordinates specialized agents across planning, development, code review, security, and delivery. - Unlike standalone coding assistants, GitLab agents can access issues, merge requests, pipelines, vulnerabilities, and codebases. - GitLab Duo Planner Agent can analyze backlogs, divide epics into tasks, and support prioritization. - Security Analyst Agent can triage vulnerabilities, explain risks, and recommend remediation priorities. - Built-in flows connect agents into end-to-end processes, reducing manual handoffs. - Agentic Chat provides natural-language access to project context and multi-step reasoning within GitLab. ## Vertex AI as the Model and Infrastructure Layer - Vertex AI supplies the foundation models and related services used by GitLab agents. - Newer models improve reasoning, tool use, and long-context understanding, supporting workloads such as backlog analysis and monorepo security reviews. - Vertex AI Model Garden offers Gemini, third-party, and open-source models, allowing customers to balance performance, cost, and regulatory requirements. - GitLab supports Bring Your Own Model configurations, enabling organizations to use approved providers and gateways. - Vertex AI abstracts LLM hosting, including infrastructure management, security, governance, and model-version delivery. ## Enterprise Governance and Operational Benefits - GitLab’s AI Gateway mediates model access, helping administrators track connections and maintain governance. - Developers remain in GitLab while inference follows existing Google Cloud security and policy controls. - Platform teams can standardize which models support recommendations, analysis, and remediation. - Security teams can manage findings and proposed fixes in the same environment, reducing context switching and unmanaged workflows. - Using Vertex AI through GitLab can align AI usage with existing Google Cloud contracts, controls, and procurement policies. - The approach helps reduce duplicate spending and fragmented “shadow AI” toolchains. ## Practical Outcome for Google Cloud Customers The integration is intended to increase developer productivity without requiring teams to evaluate, host, or manage individual language models. GitLab provides the governed DevSecOps control plane, while Vertex AI supplies scalable, flexible model infrastructure, enabling organizations to adopt more capable agentic workflows while maintaining enterprise security and control.

grammarly

From Idea to Demo in Two Days: Inside Superhuman’s 2025 Global Hackathon (opens in new tab)

Superhuman’s 2025 hackathon brought together nearly 500 employees to prototype innovative product features by leveraging cutting-edge AI coding tools like Claude Code and Cursor. By integrating AI-driven agents and keyboard-centric workflows, teams demonstrated how rapid experimentation can bridge functional gaps across mail, documentation, and collaboration platforms. The event highlighted a significant shift toward "vibe-coding" and accessible development, where cross-functional teams and non-engineers could ship functional MVPs in just 48 hours. ## Superhuman Command Everywhere (SCE) * This project extends the Superhuman Mail Command Center to the browser, allowing users to trigger Grammarly features, set reminders, and snooze items from any web page. * The tool enables keyboard-only navigation for AI agents; for example, users navigate Grammarly’s Proofreader cards using "J" and "K" and accept or dismiss suggestions with "E" and "D." * Developers used AI tools to quickly interpret an unfamiliar codebase, allowing engineers without frontend expertise to "vibe-code" a working MVP within a few hours. ## Whiteboarding in Coda * This feature introduces a native canvas within Coda documents where users can draw freely, add shapes, and import images for brainstorming and diagramming. * The prototype includes an AI diagramming tool that generates editable visual versions of diagrams based on plain-text descriptions. * Built by a solo team member with no formal coding background, the project utilized Claude Code and Cursor to focus on UX refinement and smooth interactions rather than just technical functionality. ## Superhuman Listening * This system centralizes fragmented customer feedback from tools like Gong, Salesforce, and Zendesk into a single, queryable source of truth. * By linking unstructured data to product roadmaps in Coda, the tool helps sales engineers and product managers determine if specific customer feedback is already being addressed. * Technical challenges included using LLM APIs to extract urgency and sentiment, though the team noted the difficulty of filtering "noise" from high-volume sources like Zendesk tickets. ## Inclusive Language Agent * Developed by a team of linguists, this agent identifies non-inclusive phrasing or unconscious bias in professional writing. * The goal is to provide real-time suggestions that improve workplace culture and customer trust by making word choices more inclusive and intentional. The results of this hackathon suggest that AI-assisted development tools are significantly lowering the barrier to entry for complex product builds. For organizations aiming to accelerate innovation, encouraging "maker" identities across all departments and utilizing AI to bridge technical skill gaps can surface high-value solutions that traditional product cycles might miss.

grammarly

Agentic AI vs. generative AI: What’s the Difference and When to Use Each (opens in new tab)

While generative AI focuses on creating content like text and images through prompt-based prediction, agentic AI represents a shift toward autonomous goal achievement and execution. By combining the creative output of large language models with a continuous loop of perception and action, these technologies allow users to move from simply generating drafts to managing complex, multi-step workflows. Ultimately, the two systems are most effective when used together, with one providing the ideas and the other handling the coordination and follow-through. ### Distinguishing Creative Output from Autonomous Agency * Generative AI functions as a responder that produces new content—such as text, code, or visuals—by predicting the most likely next "token" or piece of data based on a user’s prompt. * Agentic AI possesses "agency," meaning it can take a high-level goal (e.g., "prepare a client kickoff") and determine the necessary steps to achieve it with minimal guidance. * While tools like Midjourney or GitHub Copilot focus on the immediate delivery of a specific creative asset, agentic systems act as proactive partners that can use external tools, manage schedules, and make independent decisions. ### The Underlying Mechanics of Prediction and Action * Generative models rely on Large Language Models (LLMs) trained on massive datasets to identify patterns and chain together original sequences of information. * Agentic systems operate on a "perceive, plan, act, and learn" loop, where the AI gathers context from its environment, executes tasks across different applications, and adjusts its strategy based on the results. * The generative process is typically a direct path from input to output, whereas the agentic process is iterative, allowing the system to adapt to changes and feedback in real-time. ### Practical Applications in Content and Workflow Management * Generative use cases include transforming rough bullet points into polished emails, summarizing long documents into flashcards, and adjusting the tone of a message to be more professional. * Agentic use cases involve higher-level orchestration, such as monitoring document revisions, consolidating feedback from multiple stakeholders, and automatically sending follow-up reminders. * In a project management context, an agentic system can draft a project plan, identify owners for specific tasks, and update timelines as milestones are met or missed. ### Navigating Technical and Operational Limitations * Generative AI is susceptible to "hallucinations" because it prioritizes probabilistic output over factual reasoning or logic. * Agentic AI introduces complexity regarding security and permissions, as the system needs authorized access to various apps and tools to perform actions on a user's behalf. * Current agentic systems still require human oversight for critical decision-making to ensure that autonomous actions align with the user's intent and organizational standards. To maximize efficiency, you should utilize generative AI for the creative phases of a project—such as brainstorming and drafting—while delegating administrative overhead and coordination to agentic AI. As these technologies continue to converge, the focus of AI utility is shifting from the volume of content produced to the successful execution of complex, real-world results.

gitlab

Announcing general availability for GitLab Duo Agent Platform (opens in new tab)

The GitLab Duo Agent Platform has reached general availability, marking a shift from basic AI code assistance to comprehensive agentic automation across the entire software development lifecycle. By orchestrating intelligent agents to handle complex tasks like security analysis and planning, the platform aims to resolve the "AI paradox" where faster code generation often creates downstream bottlenecks in review and deployment. ### Usage-Based Economy via GitLab Credits * GitLab is introducing "GitLab Credits," a virtual currency used to power the platform’s usage-based AI features. * Premium and Ultimate subscribers receive monthly credits ($12 and $24 respectively) at no additional cost to facilitate immediate adoption. * Organizations can manage a shared pool of credits or opt for on-demand monthly billing, with existing Duo Enterprise contracts eligible for conversion into credits. ### Agentic Chat and Contextual Orchestration * The Duo Agentic Chat provides a unified experience across the GitLab Web UI and various IDEs, including VS Code, JetBrains, Cursor, and Windsurf. * The chat utilizes multi-step reasoning to perform actions autonomously, drawing from the context of issues, merge requests, pipelines, and security findings. * Capabilities extend beyond code generation to include infrastructure-as-code (IaC) creation, pipeline troubleshooting, and explaining vulnerability reachability. ### Specialized Foundational and Custom Agents * **Foundational Agents:** Pre-built specialists designed for specific roles, such as the Planner Agent for breaking down work and the Security Analyst Agent for triaging vulnerabilities. * **Custom Agents:** Developed through a central AI Catalog, these allow teams to build and share agents that adhere to organization-specific engineering standards and guardrails. * **External Agents:** Native integration of third-party AI tools, such as Anthropic’s Claude Code and OpenAI’s Codex CLI, provides access to external LLM capabilities within the governed GitLab environment. ### Automated End-to-End Flows * The platform introduces "Flows," which are multi-step agentic sequences designed to automate repeatable transitions in the development cycle. * The "Issue to Merge Request" flow builds structured code changes directly from defined requirements to jumpstart development. * Specialized CI/CD flows help teams modernize pipeline configurations and automatically analyze and suggest fixes for failed pipeline runs. * The Code Review flow streamlines the feedback loop by providing AI-native analysis of merge request comments and code changes. To maximize the impact of agentic AI, organizations should move beyond basic chat interactions and begin integrating these specialized agents into their broader orchestration workflows to eliminate manual handoffs between planning, coding, and security.

figma

Double Click: You Can Just Do Things—But Should You Always? | Figma Blog (opens in new tab)

AI tools are creating a renewed sense of possibility, making it easier for people—even nontechnical users—to build, write, design, and research. Figma’s article celebrates the excitement behind the “you can just do things” mantra while questioning whether constant creation may also become exhausting. Its central tension is whether AI is ushering in a creative golden age or overwhelming people with too many possibilities. ## The “You Can Just Do Things” Mantra - The phrase has become a tech-world rallying cry alongside: - “Move fast and break things” - “Don’t ask for permission” - “It’s time to build” - “Founder mode” - “Fuck around and find out” - AI-powered tools make the idea feel more attainable than ever by lowering the barriers to execution. - Writing assistants, design generators, and research platforms allow more people to create without specialized technical skills. - The article connects this mindset to earlier advocates such as Steve Jobs and contemporary online creators. ## The Thrill of Discovery - The current AI boom is compared to the early 2010s, when discovering apps such as Instagram and Uber felt especially exciting after the App Store’s emergence. - Michael Mignano of Lightspeed Venture Partners observes that people are once again hearing about impressive new products every day. - Crucially, these recommendations increasingly come from ordinary friends—not only people working in technology. - This suggests AI products are becoming broadly accessible and relevant beyond the traditional tech community. ## Possibility Versus Overload - The proliferation of AI tools creates a powerful sense that almost anything can be attempted. - At the same time, the sheer number of available tools and projects may become mentally exhausting. - The article asks whether high agency and constant experimentation empower people or pressure them to stay perpetually productive. - It frames the issue as a balance: embracing AI’s creative potential without feeling obligated to act on every possible idea. People should take advantage of AI’s expanded creative possibilities while resisting the expectation to “do everything.” The most sustainable approach is selective experimentation—use tools that meaningfully support a goal rather than treating constant activity as the goal itself.

figma

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

Figma’s Issue No. 8 reflects on how its community shaped the company’s 2024 releases and culture. The year included 180 product updates, a major Config conference, expanded tools for developers and product teams, and a refreshed brand identity. The central message is that Figma builds products through continuous dialogue with the people who use them. ## A Year Shaped by the Community - Figma published 180 new releases in 2024. - More than 10,000 people attended Config. - Over 220 Friends of Figma groups operated worldwide. - The company emphasizes that users do more than receive new features: they influence how those features evolve in practice. ## Expanding Figma’s Products - Figma refined its UI3 interface to give users more control. - AI tools were reworked with a more deliberate approach. - Dev Mode was enhanced to improve connections between design and code. - Figma Slides was launched to support presentations and give design work a broader stage. - The company highlights that the design process continues after launch, when users apply new tools to real workflows. ## Config and the Future of Product Building - Config 2024 was Figma’s largest conference yet, held in San Francisco with more than 10,000 attendees. - Figma points readers toward talks and advice from Config speakers. - Featured guidance focuses on creating memorable presentations and sessions that genuinely inspire audiences. - Early-bird tickets for Config 2025 were already available. ## A New Brand and Web System - As Figma expanded toward developers, marketers, and broader product teams, it updated its visual identity. - The redesign introduced a new typeface and a refreshed brand system. - Figma used its own tools to audit and rebuild its web system. - The process included streamlining components, improving workflows, refining variables and styles, and preparing the system for future growth. ## Design Inspiration and Cross-Functional Collaboration - Community templates for Figma Slides offer ways to create more engaging presentations. - Ableton Note designer Pablo Sánchez shares seven principles for designing surprising and memorable digital experiences. - One North’s Nick Villapiano argues that developers should participate actively in design rather than treating design as a handoff. - These examples reinforce Figma’s broader view that design is collaborative and extends across disciplines. Figma’s year-end message is ultimately a recommendation to keep building in conversation with users. Product launches, brand systems, developer workflows, and community events become more valuable when people actively shape how they are used.