Data Science

18 posts

figma2 min readCurated summary

Measuring Time Savings From Figma Make | Figma Blog

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.

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

The case for a cooldown: Why Dependabot now waits before issuing version updates

Carlin is a GitHub Product Manager focused on GitHub Advanced Security and Dependabot. Her experience in software engineering and data science supports a data-driven approach to product management. ### Professional Background - Works on GitHub Advanced Security. - Focuses specifically on Dependabot. - Brings experience in software engineering and data science. ### Personal Interests - Lives in Washington with her partner and dog, Cookie. - Enjoys cycling and competitive board games. No technical blog post content was provided beyond this author biography.

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

Google Research at The Check Up: from healthcare innovation to real-world care settings

Google Research argues that AI is entering a new phase in healthcare: moving beyond isolated tools toward personalized care, clinical collaboration, public-health planning, and scientific discovery. The post highlights research partnerships, open models, and real-world deployments designed to make healthcare more accurate, accessible, and proactive. Google emphasizes that these advances must be developed responsibly through clinical validation, peer review, and collaboration with healthcare institutions. ## AI for Personalized Healthcare - A Fitbit collaboration studied how AI could support preventative care across the United States. - The research found that a Personal Health Agent (PHA) modeled on a collaborative health team could provide more effective long-term support than single-purpose fitness or tracking apps. - The PHA combines: - Data analysis - Medical and domain expertise - Health coaching - Large multimodal models can transform wearable data into personalized guidance about sleep, fitness, and overall health. ## AI as a Clinical Collaborator - Google’s breast cancer research with Imperial College London and the UK’s NHS used diverse datasets and expert-validated ground truth data. - The experimental system identified 25% of “interval cancers”—cancers missed during screening and later detected after symptoms appeared. - Integrated into clinical workflows, the system could reduce radiologists’ workload while maintaining safe detection performance. - Google’s diabetic retinopathy screening model has been deployed through partnerships with medical institutions in India, Thailand, and Australia. - It has supported more than one million screenings. - Patients can receive results in roughly two minutes. - AMIE, a multi-agent medical AI system, can reason across medical histories, laboratory results, and medical images to identify overlooked patterns. - Google is testing AMIE with Beth Israel Deaconess Medical Center to assist with pre-visit history-taking and flag urgent symptoms. - An IRB-approved national study with Included Health will evaluate AI-supported telehealth care. ## Open Models for Healthcare Developers - Google’s Health AI Developer Foundations (HAI-DEF) provides free open-weight models and open-source tools for building healthcare applications. - MedGemma supports: - Medical text and image interpretation - High-dimensional 3D imaging - Medical-specific speech recognition - The All India Institute of Medical Sciences is using MedGemma for outpatient triage and dermatology screening. - Singapore’s Ministry of Health is adapting the model for locally relevant primary- and specialty-care applications. - The MedGemma Impact Challenge received more than 850 submissions aimed at turning AI research into practical, human-centered healthcare tools. ## AI for Public Health - Google Earth AI combines geospatial models and datasets to study connections between environmental conditions, population behavior, and health outcomes. - Researchers at Mount Sinai and Boston Children’s Hospital/Harvard used Google data and surveys to estimate childhood MMR vaccination coverage at ZIP-code resolution. - The resulting “super-resolution” maps identified pockets of under-vaccination that corresponded with recent measles outbreaks. - Such analysis could help public-health officials target outreach and prevention efforts more effectively. ## AI for Biomedical Discovery - Co-Scientist and Gemini Deep Think are being used to generate scientific hypotheses and support research across fields including single-cell analysis, public health, and neuroscience. - Google is also exploring evolutionary coding agents that run scientific-computing experiments in parallel. - DeepSomatic, a genomic analysis tool, is designed to improve the detection of cancer-related genetic mutations across multiple cancer types. Google’s broader recommendation is to treat AI as a validated collaborator and infrastructure layer rather than a replacement for clinicians or researchers. Continued clinical testing, expert oversight, transparent publication, and open developer access will be essential to translating these systems into safe, practical benefits.

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

Academic Publications & Airbnb Tech: 2025 Year in Review

Airbnb’s 2025 research program expanded across major academic venues, with a focus on applying AI, machine learning, and data science to search, ranking, personalization, and marketplace optimization. The company strengthened its presence at KDD and CIKM while broadening into NLP, optimization, and measurement science. Its research emphasized practical systems that improve experimentation, retrieval, recommendations, ranking quality, and booking conversion. ## Research Expansion in 2025 - Airbnb presented research at established conferences including KDD and CIKM, while expanding into venues such as COLING, LION, and VLDB. - Researchers used these conferences to: - Share production-scale findings with academic and industry peers. - Develop new collaborations. - Learn about emerging methods. - Mentor early-career researchers. - The work was organized around themes including applied machine learning for search and personalization, and NLP and LLM systems in production. ## Search Ranking and Marketplace Retrieval at KDD KDD is a leading conference for data mining, knowledge discovery, and large-scale analytics. Airbnb has presented there since 2018, and its 2025 contributions focused on improving search experimentation and location retrieval. - **Interleaving and counterfactual evaluation** - Airbnb introduced techniques for evaluating search-ranking ideas before launching full A/B tests. - These methods help teams identify promising experiments more quickly. - They are especially useful for accommodation booking, where long conversion cycles can make statistical significance slow to achieve. - The goal is to accelerate experimentation without compromising evaluation accuracy. - **Extreme classification for audience expansion** - Airbnb presented a high-precision approach to retrieving relevant geographic areas in its two-sided marketplace. - The system uses categorical location cells to identify areas containing listings a guest might realistically book. - This helps balance Airbnb’s diverse global inventory with users’ preferences for location, amenities, style, and price. - Airbnb also presented work on **TSMO**, or Two-sided Marketplace Optimization, and indicated that some technologies might eventually be open-sourced. ## Search and Recommendation Advances at CIKM At CIKM 2025, Airbnb’s Relevance and Personalization team had five peer-reviewed papers accepted. The work addressed search, recommendations, ranking metrics, multimodal representations, and user comparison behavior. - **Recommendations for overly narrow searches** - Airbnb developed a system that suggests alternatives when a guest’s search returns too few accommodations. - Suggestions may include different dates, broader amenity requirements, or adjusted price ranges. - The system aims to reduce search frustration and increase booking rates. - **Map-specific ranking optimization** - Maps account for approximately 80% of Airbnb search interactions. - Traditional feed-ranking assumptions do not accurately represent how users view and interact with map results. - Airbnb introduced a map-specific version of NDCG, a ranking-quality metric. - Experiments showed that optimizing for this metric improved bookings. - **BiListing multimodal embeddings** - BiListing combines listing text and photos into unified embedding representations. - It uses large language models and pretrained language-image models as ranking signals. - The approach produced a reported 0.425% improvement in normalized discounted booking gain and generated tens of millions of dollars in incremental revenue. - **Beyond pairwise learning-to-rank** - Airbnb proposed a learning-to-rank method that models interactions between items during pairwise comparisons. - This provides a more realistic view of what users prefer when evaluating search results. - The paper also describes efficient implementation techniques and online and offline evaluation results. - **Learning to Comparison-Shop** - The LTCS system models how users compare multiple listings rather than evaluating each listing independently. - It produced statistically significant improvements of 1.7% in NDCG and 0.6% in booking conversion rate. - The work reflects Airbnb’s broader effort to make ranking models sensitive to the context of an entire results page. ## NLP and Production LLM Systems - Airbnb also highlighted NLP and production LLM research, including participation in EMNLP. - Relevant application areas include: - Customer support. - Search and discovery. - Trust and safety. - EMNLP covers language-model architectures, training strategies, safety, evaluation, datasets, and open-source tooling. Airbnb’s 2025 publications show a strong emphasis on research that translates directly into marketplace performance. The most practical opportunities involve faster experimentation, context-aware ranking, multimodal listing understanding, and recommendation systems that help guests recover from overly restrictive searches.

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

Redefining Impact as a Data Scientist | Figma Blog

Data science impact is not limited to experiments, forecasting, or optimization. In complex, high-stakes systems such as billing, data scientists can create value by making workflows understandable, validating correctness, and improving operational safety. Figma’s experience shows that effective data science may require domain modeling, cross-functional collaboration, instrumentation, and production-quality tools. ## Data Science as a Full-Stack Discipline - The role of data science varies by team: it may involve experimentation, product analysis, data modeling, instrumentation, or operational tooling. - Billing combines a user-facing product with backend infrastructure, so accuracy directly affects customer trust. - Supporting Billing required: - Building deep domain expertise - Partnering with engineers and other functions - Creating tools that explain and verify system behavior - Experimentation and opportunity analysis remained useful, but represented a smaller portion of the actual work. - Figma’s full-stack model encouraged the team to define the right data science support collaboratively rather than follow a fixed playbook. ## Explaining Complex Systems Beyond Charts and Models - Some of the most valuable data science work explains existing or historical outcomes rather than predicting future ones. - A single invoice seat charge may depend on: - Seat assignments and removals - Permission changes - Contract terms - Workspace state - Billing rules - The timing of state transitions - Figma built the **Invoice Seat Report** to reconstruct the complete reasoning behind each charge. - The application combines product events, contract metadata, billing rules, and historical state transitions, presenting the result in plain language. - Building it required: - Reconciling fragmented schemas and inconsistent historical data - Validating assumptions with engineers - Adding instrumentation where logs recorded what happened but not why - Translating billing rules into traceable and debuggable SQL transformations - The team also had to account for legacy multiyear contracts, sparse seat histories, early upgrades, and other cases that could create gaps in the data. ## Shaping Technical Direction Through Data - Data scientists can turn business rules into measurable checks that define expected system behavior. - These validations can detect drift, regressions, and anomalies in both development and production. - For Billing, automated verification is especially important because small errors in seat states or invoice calculations can affect customer charges and trust. - During Figma’s billing-model re-architecture, data science helped verify that: - Data moved correctly through pipelines - New pricing and billing logic produced intended outcomes - Customers did not enter unexpected billing states - The system could be monitored consistently across environments The practical lesson is to look beyond conventional analytics when assessing data science impact. In complex domains, building reliable data foundations, explanatory tools, and correctness checks may be more valuable than running another experiment.

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

My Journey to Airbnb: Peter Coles

Peter Coles’s career connects mathematical training, academic economics, and practical data science. After studying game theory and market design, he moved from Harvard Business School to eBay and then Airbnb, where he could apply economic models to real-world marketplaces. At Airbnb, he helped build economics and data science teams, guide policy decisions, investigate pandemic-driven changes, and measure the company’s broader impact. ## From Mathematics to Economics - Coles grew up in Milwaukee and developed an early interest in marketplaces by trying to run a neighborhood rock stand. - He studied math at Princeton after briefly pursuing ancient history. - He earned a PhD in economics at Stanford, focusing on game theory—the study of strategic decision-making. - His mentor, Jon Levin, taught him to simplify complex research problems. - While studying in Germany, Coles traveled around Europe and stayed with strangers connected to classmates, unintentionally experimenting with a model similar to Airbnb. ## Studying Markets and Market Design - At Harvard Business School, Coles researched market design and taught with Al Roth, who later won the Nobel Prize in Economics. - His work focused on “matching,” or designing systems that pair participants from two groups when prices cannot directly balance supply and demand. - He studied participant strategy, signaling, and market mechanisms, including improvements to the market for PhD economists. - He also wrote business cases about companies such as Zillow, Microsoft, and Craigslist. - Although he valued academia, he found the long research and peer-review cycle was not a good long-term fit. ## Applying Economics at eBay - In 2013, Coles joined eBay as technology and the sharing economy were rapidly expanding. - He led an economics team created by Steve Tadelis and helped combine it with another group to form eBay’s Data Labs. - One notable project, “What’s It Worth,” developed a method for estimating the fair market value of items sold on eBay. - The work combined economic reasoning, practical marketplace knowledge, and statistical modeling. ## Building Airbnb’s Economics and Data Science Functions - In 2015, Coles joined Airbnb to help address the company’s growing regulatory challenges. - He built a global team of economists and data scientists to study short-term rentals and their relationship with cities. - The team used data to inform policy discussions and evaluate Airbnb’s effects on guests, hosts, and communities. - This role allowed Coles to connect economic theory with decisions affecting a rapidly expanding platform. ## Central Strategy & Insights - As Airbnb grew, executives needed analysis that crossed organizational boundaries. - Coles and Jackson Wang founded Central Strategy & Insights, known as CSI. - The team acted as “forensic investigators,” assembling evidence and narratives from company-wide data. - During the pandemic, CSI analyzed major changes in guest travel patterns and determined what kinds of supply Airbnb would need. - The team also led business reviews and prepared analyses for shareholders before Airbnb’s IPO. ## Measuring Airbnb’s Broader Impact - Coles later returned to policy-focused work with a larger economics organization. - The team developed models to guide Airbnb’s response to governments as travel recovered after the pandemic. - Economists and analysts evaluated Airbnb’s impact on hosts, guests, and society. - Their work included the US Economic Impact Report and expanded collaboration with academic researchers using Airbnb data. Coles’s experience suggests that marketplace companies benefit from combining rigorous economic research with hands-on data science. Moving between academia and industry enabled him to turn theories about market design into practical tools for product strategy, policy, and impact measurement.

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

Businesses grow revenue on Stripe 27 percentage points faster after accepting financing through Stripe Capital

Stripe’s two-year randomized trials found that businesses accepting Stripe Capital financing grew faster than comparable businesses without financing. The 2023–2025 study showed an average 27-percentage-point growth advantage, while the fastest-improving 10% saw an average boost of 211 percentage points. The results suggest that embedded, data-driven financing can help small businesses overcome traditional lending barriers and invest in growth. ## Proving Financing Causes Growth - Stripe compared businesses that accepted Capital with similar businesses matched on credit, revenue, and longevity. - The study was conducted across two periods: - **2020–2021:** financing was associated with a 114-percentage-point average growth boost, though pandemic-era economic conditions may have influenced results. - **2023–2025:** financing still produced a strong 27-percentage-point average boost in a different economic environment. - Stripe conducted the trial at scale, serving 76,000 financed businesses in 2025 alone. ## Strongest Effects Among Small Businesses - Businesses processing **$3,000–$76,000 annually** saw average growth-rate improvements of **33–43 percentage points**. - Businesses processing less than **$52,000 annually** with top-tier credit scores saw even larger improvements of **94–106 percentage points**. - Even businesses with low or unavailable credit scores experienced **11–18 percentage-point** growth improvements. - Stripe says its data-driven process delivers financing in **1–2 days**, compared with roughly **14–40 days** at traditional banks. - Traditional bank applications are often time-consuming, and rejection rates can approach 50%, including for established businesses. ## Growth-Oriented Spending Produces Better Results - A survey of approximately 900 participating businesses found that financing use strongly correlated with outcomes. - Among businesses with top-tier credit, those using funds to launch products, start projects, or scale operations saw average growth boosts of **70–95 percentage points**. - Examples included: - MyPark used financing to deploy additional revenue-generating machines. - Xirsys expanded server infrastructure into China, India, and Japan, more than doubling annual revenue. ## Expanding Access Through Embedded Finance - The World Bank estimates a **$5.7 trillion** funding gap for SMBs in developing economies. - Platforms that already manage payments or business operations can use transaction data to make proactive financing offers. - This model broadens access beyond traditional credit scoring and may encourage owners to pursue investments they would otherwise avoid. - Marketplaces and software platforms are positioned to become important channels for closing the global SMB funding gap. Stripe’s research supports using embedded, data-based financing to provide faster access to capital, particularly for small businesses and owners pursuing concrete expansion plans. However, financing remains subject to approval and may take the form of loans or merchant cash advances depending on the market.

Read original(opens in new tab)
googleOriginal article

DS-STAR: A state-of-the-art versatile data science agent (opens in new tab)

DS-STAR is an advanced autonomous data science agent developed to handle the complexity and heterogeneity of real-world data tasks, ranging from statistical analysis to visualization. By integrating a specialized file analysis module with an iterative planning and verification loop, the system can interpret unstructured data and refine its reasoning steps dynamically based on execution feedback. This architecture allows DS-STAR to achieve state-of-the-art performance on major industry benchmarks, effectively bridging the gap between natural language queries and executable, verified code. ## Comprehensive Data File Analysis The framework addresses a major limitation of current agents—the over-reliance on structured CSV files—by implementing a dedicated analysis stage for diverse data formats. * The system automatically scans a directory to extract context from heterogeneous formats, including JSON, unstructured text, and markdown files. * A Python-based analysis script generates a textual summary of the data structure and content, which serves as the foundational context for the planning phase. * This module ensures the agent can navigate complex, multi-file environments where critical information is often spread across non-relational sources. ## Iterative Planning and Verification Architecture DS-STAR utilizes a sophisticated loop involving four specialized roles to mimic the workflow of a human expert conducting sequential analysis. * **Planner and Coder:** A Planner agent establishes high-level objectives, which a Coder agent سپس translates into executable Python scripts. * **LLM-based Verification:** A Verifier agent acts as a judge, assessing whether the generated code and its output are sufficient to solve the problem or if the reasoning is flawed. * **Dynamic Routing:** If the Verifier identifies gaps, a Router agent guides the refinement process by adding new steps or correcting errors, allowing the cycle to repeat for up to 10 rounds. * **Intermediate Review:** The agent reviews intermediate results before proceeding to the next step, similar to how data scientists use interactive environments like Google Colab. ## Benchmarking and State-of-the-Art Performance The effectiveness of the DS-STAR framework was validated through rigorous testing against existing agents like AutoGen and DA-Agent. * The agent secured the top rank on the public DABStep leaderboard, raising accuracy from 41.0% to 45.2% compared to previous best-performing models. * Performance gains were consistent across other benchmarks, including KramaBench (39.8% to 44.7%) and DA-Code (37.0% to 38.5%). * DS-STAR showed a significant advantage in "hard" tasks—those requiring the synthesis of information from multiple, varied data sources—demonstrating its superior versatility in complex environments. By automating the time-intensive tasks of data wrangling and verification, DS-STAR provides a robust template for the next generation of AI assistants. Organizations looking to scale their data science capabilities should consider adopting iterative agentic workflows that prioritize multi-format data understanding and self-correcting execution loops.

netflixOriginal article

Netflix's Metaflow Spin: Faster ML Development | Netflix TechBlog (opens in new tab)

Netflix has introduced Spin, a new functionality within the Metaflow framework designed to significantly accelerate the iterative development cycle for ML and AI workflows. By bridging the gap between the interactive speed of notebooks and the production-grade reliability of versioned workflows, Spin allows developers to experiment with stateful increments without the latency of full restarts. This enhancement ensures that the "prototype to production" pipeline remains fluid while maintaining the deterministic execution and explicit state management that Metaflow provides at scale. ### The Nature of ML and AI Iteration * ML and AI development is distinct from traditional software engineering because it involves large, mutable datasets and computationally expensive, stochastic processes. * State management is a primary concern in this domain, as reloading data or recomputing transformations for every minor code change creates a prohibitively slow feedback loop. * While notebooks like Jupyter or Marimo excel at preserving in-memory state for fast exploration, they often lead to "hidden state" problems and non-deterministic results due to out-of-order cell execution. ### Metaflow as a State-Aware Framework * Metaflow uses the `@step` decorator to define checkpoint boundaries where the framework automatically persists all instance variables as versioned artifacts. * The framework’s `resume` command allows developers to restart execution from a specific step, cloning previous state to avoid recomputing successful upstream tasks. * This architecture addresses notebook limitations by ensuring execution order is explicit and deterministic while making the state fully discoverable and versioned. ### Introducing Spin for Rapid Development * Spin is a new feature introduced in Metaflow 2.19 that further reduces the friction of the iterative development loop. * It aims to provide the near-instant feedback of a notebook environment while operating within the structure of a production-ready Metaflow workflow. * The tool helps developers manage the stateful nature of ML development, allowing for quick, incremental experimentation without losing continuity between code iterations. To improve data science productivity and reduce "waiting time" during the development phase, engineering teams should look to adopt Metaflow 2.19 and integrate Spin into their experimentation workflows.

googleOriginal article

The anatomy of a personal health agent (opens in new tab)

Google researchers have developed the Personal Health Agent (PHA), an LLM-powered prototype designed to provide evidence-based, personalized health insights by analyzing multimodal data from wearables and blood biomarkers. By utilizing a specialized multi-agent architecture, the system deconstructs complex health queries into specific tasks to ensure statistical accuracy and clinical grounding. The study demonstrates that this modular approach significantly outperforms standard large language models in providing reliable, data-driven wellness support. ## Multi-Agent System Architecture * The PHA framework adopts a "team-based" approach, utilizing three specialist sub-agents: a Data Science agent, a Domain Expert agent, and a Health Coach. * The system was validated using a real-world dataset from 1,200 participants, featuring longitudinal Fitbit data, health questionnaires, and clinical blood test results. * This architecture was designed after a user-centered study of 1,300 health queries, identifying four key needs: general knowledge, data interpretation, wellness advice, and symptom assessment. * Evaluation involved over 1,100 hours of human expert effort across 10 benchmark tasks to ensure the system outperformed base models like Gemini. ## The Data Science Agent * This agent specializes in "contextualized numerical insights," transforming ambiguous queries (e.g., "How is my fitness trending?") into formal statistical analysis plans. * It operates through a two-stage process: first interpreting the user's intent and data sufficiency, then generating executable code to analyze time-series data. * In benchmark testing, the agent achieved a 75.6% score in analysis planning, significantly higher than the 53.7% score achieved by the base model. * The agent's code generation was validated against 173 rigorous unit tests written by human data scientists to ensure accuracy in handling wearable sensor data. ## The Domain Expert Agent * Designed for high-stakes medical accuracy, this agent functions as a grounded source of health knowledge using a multi-step reasoning framework. * It utilizes a "toolbox" approach, granting the LLM access to authoritative external databases such as the National Center for Biotechnology Information (NCBI) to provide verifiable facts. * The agent is specifically tuned to tailor information to the user’s unique profile, including specific biomarkers and pre-existing medical conditions. * Performance was measured through board certification and coaching exam questions, as well as its ability to provide accurate differential diagnoses compared to human clinicians. While currently a research framework rather than a public product, the PHA demonstrates that a modular, specialist-driven AI architecture is essential for safe and effective personal health management. Developers of future health-tech tools should prioritize grounding LLMs in external clinical databases and implementing rigorous statistical validation stages to move beyond the limitations of general-purpose chatbots.

datadog3 min readCurated summary

How we optimized LLM use for cost, quality, and safety to facilitate writing postmortems

Bits AI uses large language models to generate first drafts of incident postmortems from Datadog Incident Management metadata and Slack discussions. The goal is to reduce documentation effort without replacing the human-led reflection that makes postmortems valuable. Datadog found that production-quality LLM features require extensive prompt experimentation, safeguards against hallucinations, careful model selection, and strong privacy and feedback mechanisms. ## Why LLMs Are Difficult to Use for Postmortems - Postmortems must remain factual, consistent, and useful, unlike more creative LLM applications. - LLMs can ignore instructions, produce inconsistent formatting, repeat information, or hallucinate plausible but false details. - More than 100 hours were spent refining section structures and instructions so they worked across varied incidents. - Building these systems requires a combination of software engineering, product management, data science, and technical writing. ## Balancing Structured and Unstructured Incident Data - Structured Datadog data includes incident metadata, alerts, graphs, and manually entered fields such as customer impact. - Slack discussions provide current, detailed, and unstructured context from the incident response process. - Manually maintained fields are often more reliable but can become outdated, while LLMs can continually reassess live discussions. - Combining both sources helped the model understand the full incident and prioritize information appropriately. ## Cost, Speed, and Quality Trade-offs - Datadog compared models including GPT-3.5 and GPT-4. - Results varied by as much as 50 times in cost and speed. - GPT-4 generally produced more accurate output but was substantially slower and more expensive. - Model choice therefore depended on the required balance between quality, latency, and operating cost. ## Preserving Human Control and Privacy - AI-generated drafts were intended to support authors, not become final documents automatically. - Keeping engineers involved preserves the discovery and learning process that postmortems are meant to encourage. - Because incidents may contain sensitive information or secrets, Datadog scrubbed data before sending it to an LLM. - The system was designed to ensure authors remained responsible for reviewing and improving the draft. ## Experimentation and Reliability Safeguards - A custom API extracted and structured incident data from Datadog, Slack, and other sources. - The framework enabled rapid testing of different datasets, models, input configurations, and output token limits. - Datadog refined prompts and instructions to guide the model toward useful recommendations while retaining author agency. - Lowering model temperature and tuning other parameters reduced irrelevant or fabricated content. - A related feature generated concise incident summaries for responders joining Slack channels, providing a faster testing environment for LLM-based incident analysis. ## Evaluating Generated Drafts - Datadog used both qualitative and quantitative evaluation methods. - Authors of earlier postmortems compared their human-written documents with AI-generated drafts for the same incidents. - Evaluation included criteria such as factual accuracy and conciseness, with the provided article ending before the full evaluation approach was described. - Continuous feedback was used to refine prompts, models, and the overall drafting workflow. Overall, reliable AI-assisted postmortems require more than selecting a capable model. The strongest approach combines carefully prepared incident data, privacy controls, model and prompt experimentation, systematic evaluation, and mandatory human review.

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

How Figma’s data science and user research teams weave together insights that count | Figma Blog

Figma’s data science and user research teams combined quantitative and qualitative methods to understand why notifications were not driving enough collaboration. Data revealed where users dropped out of the notification funnel, while user research explored the reasons behind those behaviors. Their synthesis showed that the biggest issue was not interaction with notifications, but that many users were never receiving them, leading to new alert types and changes to notification recipients and timing. ## Building a Cross-Functional Process - Data Scientist Caitlin Hudon and Researcher Jennifer Sanders began with a teamwide FigJam brainstorm. - They reviewed notification funnel metrics, including the percentages of users who: - Were eligible for notifications - Received them - Viewed them - Interacted with them - The team identified strategic questions, potential notification types, and data gaps. - Questions were divided according to whether data science or user research was best suited to answer them. - Caitlin and Jennifer maintained close communication while conducting their separate investigations, treating quantitative and qualitative work as complementary rather than independent. ## Understanding the Notification Funnel - Figma notifications can arrive through email, Slack, mobile devices, the file browser, the system tray, or the desktop app. - Notification events include comments, replies, reactions, invitations, editing access, and @mentions. - Users must move through several stages before engaging: - All Figma users - Users eligible for notifications - Users who receive notifications - Users who view them - Users who interact with them - Quantitative analysis showed what users were doing at scale. - User research was needed to understand why users behaved that way, since people may not always accurately explain their own motivations. ## Finding the Biggest Opportunity - The activity team initially needed to determine which stage of the funnel deserved attention. - Cross-functional analysis revealed that most users were not receiving notifications at all. - This shifted the focus away from simply improving notification engagement. - The main opportunities were to create new alert types and reconsider who should receive notifications and when. ## From Insights to Impact - Figma’s activity team began running notification experiments based on the combined findings. - A new notification type was released to address major user pain points. - The broader goal is to help teams stay connected and collaborate effectively across Figma and FigJam. The case demonstrates that product teams get stronger, more actionable conclusions when behavioral data is paired with direct user research.

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

How we use data | Figma Blog

Figma uses data in two broad ways: functional data to provide its service and analytics data to improve the product. The company emphasizes collecting only the information necessary to operate Figma, while using aggregated usage insights and experiments to guide product decisions. Examples include improving file sharing and identifying performance problems in the iOS app. ## Functional Data - Functional data supports core account and product operations. - Figma collects a relatively small amount of information at signup: - Email address - Name - Role - This information enables usernames, password-reset messages, file creation, and collaboration. - Figma generally does not require sensitive information such as identity documents or verification. - Payment information for paid plans is collected and processed by Stripe. ## Analytics Data - Analytics data describes how users access and use Figma. - It helps teams understand: - Which features users adopt - Which features they ignore - Where users encounter difficulties - How usage varies across platforms - Data scientists analyze these signals alongside user research, product intuition, and direct feedback. ## Improving Features Through Experiments - A/B testing is a central part of Figma’s product-development process. - Experiments test hypotheses and measure how proposed changes affect user behavior. - In one study, Figma examined its file-sharing modal, where users invite collaborators, manage permissions, and publish work. - Research showed that: - Only 20% of users opened the share modal during their first month. - Only half of those users successfully shared a file. - Figma simplified the interface and moved secondary functions into separate tabs. - The change produced: - A 2% increase in users sending invitations - A 2% increase in users invited to each file - No observed decline in users publishing work to Figma Community ## Identifying Performance Issues - Figma uses data to monitor application performance across platforms and prioritize improvements. - After launching the beta iOS app, the data team analyzed crashes by platform, scenario, and timing. - The analysis found that prototypes were a major source of iOS crashes. - About 25% of prototype crashes occurred within the first 10 seconds of loading. Figma’s approach combines minimal functional data collection with analytics, experimentation, and performance monitoring. The practical goal is to use data selectively to improve usability, reliability, and collaboration while limiting the amount of sensitive information required from users.

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

From experiment to launch: how data shaped a new comments experience | Figma Blog

Figma used a series of data-driven experiments to redesign its comments experience and encourage collaboration among both editors and viewers. Although comments strongly predicted team retention and growth, they were underused because users struggled to discover them. Experiments confirmed that improving visibility increased comment creation, while an intuitive-looking relocation of the comments control unexpectedly reduced discoverability. ## Collaboration and Comments - Teams that collaborate during their first month are: - 1.75× more likely to be retained. - 6.5× more likely to become customers. - Figma identified comments as a potential “front door” to collaboration because both editors and viewers can use them. - Despite their value, comments were not widely used, prompting the data science team to investigate the gap between user needs and behavior. ## Testing Comment Discoverability - Users previously entered comment mode through an icon in the upper-left corner of the editor. - Research sessions suggested that comments were valuable but difficult to find. - Figma tested a prompt encouraging view-only developers to leave comments. - After two weeks in a 50/50 experiment: - Comment creation increased by 45% in the test group. - The rate of users returning to comments the following week did not change. - The result showed that simply making comments more visible could substantially increase usage. ## An Unexpected Result - Figma hypothesized that moving the comments entry point from the left side of the menu bar to the right would improve discoverability. - The reasoning was that the left side emphasized creation tools, while the right side contained collaboration and viewing features more relevant to cross-functional users. - Among new users, the change caused a 20% decrease in comment discovery within seven days of signup. - The failed experiment demonstrated that seemingly logical product changes can significantly harm user behavior. - It also reinforced the value of controlled experiments: product hypotheses are often wrong, and teams should expect testing to disprove many ideas. Figma’s experience illustrates that effective product development depends on combining user research with rigorous experimentation. Rather than relying on intuition about interface placement, teams should validate each change with real behavioral data and use unexpected results to guide subsequent iterations.

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

Inside Figma: a Q&A with our 2021 interns and new grads | Figma Blog

The article shares career advice from four 2021 Figma interns and new graduates: Emily Jia, Langston Dziko, Daniela Velez, and Jago Pang. Their experiences show that early-career candidates should evaluate company culture, mentorship, ownership, growth opportunities, and alignment with a product’s mission—not just the role itself. Figma attracted them through its collaborative culture, enthusiasm for design, and opportunities to make meaningful contributions. ## Choosing an Early-Career Role - Emily looked for: - Data science roles matching her technical background and goals. - Fast-paced, product-focused work at growing startups. - An empathetic culture centered on communication and connection. - Daniela prioritized authenticity, community, and coworkers who cared deeply about Figma’s mission of making design more accessible. - Langston focused on career growth, asking: - Whether young engineers receive meaningful ownership. - Whether their work contributes to broader company goals. - Whether employees see opportunities to develop and stay long term. ## Using Internships and Conversations to Explore Options - Emily explored different companies through summer and off-cycle internships. - Conversations with alumni and interviewers helped her understand less obvious tradeoffs between roles. - She considered not only people’s day-to-day responsibilities, but also how they had grown in their positions—and whether she wanted a similar trajectory. - Langston used internships to identify the types of work he enjoyed and those he did not. - He also spoke with many engineers, repeatedly hearing that a supportive manager and team can matter as much as the specific project. ## Why They Chose Figma - Emily was influenced by a Figma blog post written by a software engineering new graduate. She valued that Figma gave early-career employees a platform to share their experiences. - She was especially interested in joining a growing data team making its first new-grad hires and deliberately developing its culture. - Langston was impressed by how enthusiastically Figma engineers spoke about the product. Their enthusiasm suggested he would own innovative projects while developing as an engineer. - Daniela first encountered Figma through a collaborative side project. She enjoyed the product’s collaborative design experience and connected with the company’s emphasis on individuality and community. - Jago credited Figma with helping launch his design career and wanted to support its mission of democratizing design, particularly through Figma for Education and the Figma Community team. The interview suggests that students and new graduates should use internships, informational conversations, and employee perspectives to assess both the work and the environment. The strongest early-career choice is likely to be a role offering supportive mentorship, genuine ownership, meaningful growth, and a mission the candidate cares about.

Read original(opens in new tab)