techlist.io
KREN

Techlist.io - Korean Tech Blog Curator

datadog3 min readCurated summary

Scaling self-serve analytics: The tools empowering 5,000 employees

Datadog scaled self-serve analytics from 200 to 5,000 employees by building an open-source-based platform around three pillars: trusted data, accessible tools, and organizational knowledge. The goal is to let employees answer routine questions and make informed decisions without relying on a centralized Data & Analytics team. This approach combines a single source of truth, self-service data pipelines and transformations, data discovery, quality monitoring, and training. ## The Purpose of Self-Serve Analytics - Datadog’s mission is to “empower everyone at Datadog to make data-informed decisions on their own.” - Self-service allows Data & Analytics teams to focus on higher-value initiatives instead of handling every request. - The organization identified three primary user profiles: - **Analytics Explorers:** Need discoverable data and ready-made reports. - **Analytics Builders:** Create reports and run advanced queries. - **Analytics Experts:** Expose new data, maintain business logic, and manage quality. ## Data as a Single Source of Truth - Datadog centralizes product, operational, and business data so consumers work from the same version of reality. - Its “Bring Your Own Data” (BYOD) tool lets teams expose their own data for analytics. - The shared data layer supports BI tools, notebooks, data discovery, programmatic access, and machine-learning models. - Trust depends on: - Consistent naming and modeling conventions. - Comprehensive documentation. - Continuous data-quality monitoring. ## Self-Serve Data Intake - Teams can connect internal and third-party data sources through integrations and BYOD. - The platform provides scheduling and a user interface for exposing or requesting datasets. - Pipeline observability covers: - Pipeline execution. - Data quality. - Actionable alerts when failures occur. ## Self-Serve Transformation - Analysts manage their departments’ business logic using SQL and dbt. - The development environment integrates with workflow management, metadata, and pipeline-run systems. - Enforced conventions keep the shared modeling layer consistent and understandable as more analysts contribute. - Analysts can inspect lineage, pipeline runs, quality checks, and alerts. ## Data Discovery and Metadata - Every employee can browse datasets and fields in the central data platform. - Search capabilities help users identify which data can answer a particular question. - Metadata explains: - The dataset’s origin and owner. - Definitions and intended meaning. - Where the data is used. - Sensitivity and reliability. - This context helps employees determine whether data is both relevant and trustworthy. ## Supporting Adoption - Tools alone are insufficient; Datadog also provides data knowledge, support, and training. - The Data & Analytics organization acknowledges that self-service has limits and works to mitigate risks such as misunderstanding data or applying incorrect business logic. - Success is tracked through adoption and the effectiveness of the overall self-service strategy. Datadog’s experience suggests that self-serve analytics scales best when data is treated as a product: centralized, documented, observable, and accessible through tools designed for users with different levels of expertise.

Read original(opens in new tab)
PostgreSQLSqlDbtOpen Source Tools+4
figma2 min readCurated summary

Figma and Adobe are abandoning our proposed merger | Figma Blog

Figma and Adobe jointly ended their proposed acquisition after 15 months of regulatory review, concluding that approval was no longer achievable. Although the merger was intended to accelerate both companies’ impact, Figma will remain independent and explore future partnerships with Adobe. CEO Dylan Field framed the decision as a renewed opportunity to pursue Figma’s original mission: helping people turn ideas into digital products. ## Why the Merger Was Abandoned - The companies spent thousands of hours addressing regulators’ concerns worldwide. - Despite explaining the differences between their businesses, products, and markets, they no longer saw a viable path to approval. - The decision was made jointly, ending the pending acquisition. ## Figma’s Progress During the Review - Figma continued shipping products despite the uncertainty surrounding the acquisition, including: - Native AI features for FigJam - Dev Mode for improving the handoff between designers and developers - Variables - Advanced prototyping - The company also: - Opened new hubs in the United Kingdom and Asia - Hosted Config 2023 in San Francisco - Acquired AI startup Diagram - Added more than 500 employees ## Figma’s Independent Direction - Figma will continue operating as an independent company. - The company remains focused on eliminating the gap between imagination and reality. - Field sees the growth of the digital economy and advances in AI as making this mission more urgent and attainable. - Figma aims to support the entire product-development process on a single multiplayer canvas, from ideation through production. Figma’s practical next step is to maintain its independent momentum, deepen its design-to-development platform, and use AI and collaboration tools to help more people build digital products.

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

Deepening Figma’s commitment to climate action | Figma Blog

Figma argues that achieving net zero today is only part of climate responsibility; companies should also help scale carbon-removal technologies needed for future emissions reduction. Through its Net Zero social impact group, Figma progressed from measuring its carbon footprint to investing $500,000 in eight emerging decarbonization approaches through Watershed. The company views early investment in these technologies as essential because they require funding and demand to mature. ## Building Figma’s Net Zero Initiative - Figma’s Net Zero group began as an informal Slack channel in 2021, led by software engineers Silas Tsui and Noah Rowlett. - The group gained momentum by setting concrete goals, meeting regularly, researching vendors, and measuring Figma’s carbon footprint. - Leadership supported the initiative after the group conducted several months of due diligence. - Watershed became Figma’s partner for carbon accounting, climate disclosures, emissions reduction planning, and carbon-removal investments. ## From Carbon Measurement to Climate Action - A carbon footprint estimates an organization’s greenhouse-gas emissions in tons of effective carbon dioxide. - After establishing its baseline, Figma identified two main paths toward net zero: - Reduce emissions from its own operations. - Invest in decarbonization and carbon-removal projects. - Because Figma was relatively small—around 200 employees—and lacked specialized emissions-reduction expertise, the group initially focused on carbon removals. - Figma directed proceeds from its Swag Store toward reforestation-based carbon-removal credits. ## Figma’s Sustainability Milestones - **January 2021:** Employees form a group to explore a sustainability initiative. - **April 2021:** Figma selects Watershed for carbon accounting. - **July 2021:** The company receives its 2019 carbon footprint. - **September 2021:** Figma commits to annual carbon-removal investments based on its footprint and works toward net-zero operations for 2020. - **March 2022:** Figma pre-purchases $250,000 in removals from Charm Industrial. - **June 2022:** Figma signs the Climate Pledge, committing to net zero by 2040. - **July 2022:** The informal group becomes the official Net Zero social impact group. - **October 2023:** Figma invests $500,000 in emerging decarbonization projects through Watershed. ## Investing in Emerging Carbon Removal - Watershed’s Marketplace helps companies create portfolios of vetted carbon-removal projects and manages purchasing. - Figma’s portfolio includes eight technologies using different methods to remove and store carbon. - These approaches include bio-oil sequestration and enhanced rock weathering. - Charm Industrial, which converts agricultural waste into bio-oil, remains part of Figma’s portfolio. - The broader argument is that carbon neutrality based only on current emissions can be short-sighted: emerging removal technologies need early customers and investment to scale. Figma’s experience suggests that companies can begin with practical steps—measuring emissions, setting clear goals, and investing according to their capabilities—while contributing to the technologies required for long-term climate action.

Read original(opens in new tab)
Carbon RemovalCarbon AccountingBio Oil SequestrationEnhanced Rock Weathering+3
figma2 min readCurated summary

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

Figma’s “Rework your work” issue presents small improvements, AI, prototyping, and community creativity as ways to challenge outdated workflows. Its central argument is that meaningful progress often comes from improving everyday experiences while adopting tools and practices that expand what teams can accomplish. ## Small Improvements, Significant Impact - Product quality-of-life changes can have more impact than flashy features users rarely use. - Sho Kuwamoto argues that frequent, practical improvements—such as saving time or anticipating user needs—are foundational to a strong product experience. - Figma’s “Little Big Updates” emphasizes that subtle changes can create broad effects. ## Breaking Barriers with AI - FigJam’s generative AI features are designed to lower the barrier to visual collaboration while expanding creative possibilities. - AI can: - Generate custom templates and diagrams - Summarize board content - Sort sticky notes - These capabilities help product teams plan, synchronize, and brainstorm more efficiently. - The goal is not only automation, but making collaborative tools accessible to more people. ## Prototyping as a Core Practice - Prototyping is presented as an essential part of product development rather than a final presentation step. - Prototypes make design ideas tangible so collaborators can explore, critique, and refine them. - A strong prototyping culture gives designers more agency and helps the broader team gain insight earlier in the process. - Integrating prototypes throughout development can streamline workflows and improve decision-making. ## Supporting Community Creators - Figma’s Creator Fund provides grants for free widgets, plugins, and files created for the Figma Community. - Featured projects include: - Tools for building immersive environments - A design-to-code plugin - A text animation tool - These community-made resources have helped nearly a million people create in Figma. ## Reframing Design Careers - The “Rabbit hole” section encourages designers to focus less on proving their worth and more on letting the quality of their work speak for itself. - Figma cites its State of the Designer report, in which 69% of designers said their job prospects had improved. - Together, these ideas frame design as a field shaped by practical craft, evolving tools, and continued professional momentum. The issue recommends reworking established habits through incremental product improvements, thoughtful AI adoption, continuous prototyping, and support for creative communities.

Read original(opens in new tab)
FigmaPrototypingGenerative AIFigjam+2
figma3 min readCurated summary

Enforcing Device Trust on Code Changes | Figma Blog

Figma built a custom system to ensure that code merged into GitHub release branches originates from trusted, company-managed devices. Standard SSO, WebAuthn, dual-control approvals, and GitHub’s “Verified” commit status did not sufficiently protect against compromised tokens, SSH keys, or sessions. The team instead combined short-lived Okta Device Trust certificates with X.509/S/MIME Git commit signing. ## Protecting Production Release Branches - GitHub release branches are the source of truth for production deployments and therefore a high-value attack target. - Figma requires dual control for pull requests: the author and another engineer must approve changes. - GitHub access is protected by SSO and WebAuthn 2FA. - These controls do not fully address compromised: - Personal access tokens - OAuth tokens - SSH keys - Existing GitHub sessions ## Problems with GitHub Commit Verification - GitHub’s commit verification can provide a “Verified” status without proving that the commit came from a trusted company device. - Engineers’ personal GPG keys are outside Figma’s control and cannot be tied to a specific managed laptop. - Commits created through GitHub’s web interface or API may be signed with GitHub’s own web-flow GPG key. - An attacker using a compromised OAuth app, session, token, or SSH key could potentially create commits that GitHub marks as verified. - Building an internal verification system gives Figma more control over what qualifies as a trusted change and avoids manually monitoring every credential type. ## Okta Device Trust Certificates - Figma’s Endpoint Security Baseline includes requirements such as: - Current browser versions - The latest macOS version - Active malware protection - Figma issues X.509 device certificates to company-managed MacBooks through an Amazon Private Certificate Authority. - Certificates are distributed using JAMF and renewed every 15 days. - Each certificate attests that the device met the security baseline when the certificate was issued. - Okta Identity Engine uses these certificates to enforce device trust for sensitive services including AWS, Stripe, and Snowflake. - Because the certificates can sign data, Figma can also use them to attest to actions outside Okta. ## Signing Git Commits with Device Certificates - Figma investigated using its device trust certificates to sign Git commits through S/MIME. - GitHub’s `smimesign` utility supports X.509-based commit signing on macOS and Windows. - It uses certificates and private keys stored in the macOS Keychain or Windows Certificate Store. - Git can be configured with: ```sh git config commit.gpgsign true git config gpg.format x509 git config gpg.x509.program smimesign git config user.signingkey <your_x509_key_id> ``` - This approach initially presented a usability problem: certificates—and therefore signing keys—change every 15 days when device trust certificates renew. - The excerpt ends as Figma begins describing how it planned to dynamically select the latest signing key so engineers would not need to update their Git configuration manually. Figma’s approach strengthens commit verification by linking code signatures to short-lived certificates issued only to compliant, company-managed devices. This is more meaningful than relying solely on GitHub’s generic “Verified” status, though the provided excerpt does not include the final implementation details.

Read original(opens in new tab)
GithubGitOkta Device TrustX509 Certificates+4
figma3 min readCurated summary

Why Cultivating a Prototyping Culture Will Help You Build Better Products | Figma Blog

Prototyping should move from a last-minute design enhancement to an integral part of product development. Interactive prototypes expose navigation, usability, and feasibility problems before engineering investment, while enabling teams to explore more ideas and secure stakeholder support. The article argues that organizations need shared skills, dedicated time, and leadership support to make prototyping an everyday practice. ## Prototyping as an Early Validation Tool - A prototype is a mock-up or interactive demonstration used to test and refine a product concept. - Unlike static designs, interactive prototypes reveal how an experience actually works, including: - Navigation complexity - Interaction problems - User-testing obstacles - Gaps between design intent and technical implementation - Introducing prototypes early can reduce wasted engineering effort and streamline collaboration between designers and engineers. - Prototypes let teams evaluate an idea’s value before committing to development or visual polish. ## The Power of Rapid Experimentation - Teams can quickly generate and validate multiple concepts without creating separate development cycles. - Exploring broadly before narrowing down encourages more innovative and unconventional experiences. - Proofs of concept help designers communicate ideas clearly and gain approval from stakeholders and senior leadership. - Advanced prototyping gives designers a stronger voice in product and business decisions by allowing them to demonstrate—not merely describe—their proposals. ## Building a Prototyping Culture - The growing emphasis on prototyping resembles the adoption of design systems, which also evolved from specialized practice into an organizational capability. - Companies such as Lyft encourage designers to move beyond static mockups by using: - Videos - GIFs - Interactive prototypes - Organizations must invest time and resources in training so prototyping becomes a natural, enjoyable part of the workflow rather than an obstacle. - Successful adoption requires alignment across the company: - Individual contributors need to build prototyping expertise. - Leadership must recognize its impact on efficiency and decision-making. - Managers should explicitly make time for prototyping in the product process. - Training programs and employee initiatives can help develop prototyping skills and apply them during important product reviews. ## Rewriting the Product Development Process - Prototyping challenges the idea that product development follows a simple linear sequence. - Adding prototypes earlier introduces more iteration, but it also helps teams identify obstacles and compare alternatives sooner. - Designers can use these insights to avoid known problems and move more directly toward viable solutions. - The shift affects the entire product organization, not only the design team, because prototyping changes how teams collaborate, make decisions, and obtain buy-in. Organizations should treat prototyping as a core product-development capability: provide training, protect time for experimentation, and require interactive validation early enough to influence the product—not merely decorate the final design.

Read original(opens in new tab)
FigmaDesign SystemsPrototypingProduct Development+2
figma2 min readCurated summary

Shipping Hype: PMs on What it Takes to Bring AI Features to Market | Figma Blog

AI’s rapid rise has pressured companies to launch features quickly, but hype alone does not produce useful products. Product leaders at Figma, Asana, Duolingo, and LinkedIn argue that successful AI development starts with real user problems, clear definitions, and realistic expectations about current models. AI should be treated as a tool for improving valuable workflows—not as a solution looking for a problem. ## Start with User Problems - Teams should identify user needs before deciding whether AI belongs in the feature. - Figma PM Conor Woods recommends asking: - Can the problem benefit from a large existing data set? - Is some margin of error acceptable? - Is AI genuinely improving the experience, or merely hiding poor UX? - LLMs are well suited to tasks such as organizing information and generating summaries, but they are unreliable when perfect accuracy is required or when they must invent entirely new experiences. - AI-generated inaccuracies and hallucinations are unavoidable with current models, making AI inappropriate for high-stakes, precision-critical tasks. - Asana uses a simple test: does the feature save users meaningful time? - Its Smart Status feature drafts project updates, reducing a task from roughly 20 minutes per week to two minutes and making the return on investment immediately clear. ## Specify the Problem Precisely - Generative AI can serve many different underlying needs, which makes vague feature descriptions dangerous. - Saying “we’ll summarize text” leaves open important questions about the user’s actual goal. - A user might want a summary to: - Understand a document’s subject - Identify action items - Extract decisions or other specific information - Product teams need to define the desired outcome and detailed use case rather than relying on broad descriptions of AI capabilities. - Greater specificity helps designers, engineers, and stakeholders develop a shared understanding of what the feature should do. AI features are most effective when they address a concrete, measurable user problem and acknowledge the limits of current models. Teams should define the user outcome first, then determine whether AI is the appropriate and trustworthy way to achieve it.

Read original(opens in new tab)
AILarge Language ModelsUser ExperienceGenerative AI+2
figma2 min readCurated summary

From Slack-lash to Toggle Tax: The New Vernacular of Work | Figma Blog

The article presents a playful glossary for the changing realities of digital and hybrid work. These terms capture common frustrations, habits, and moments in modern workplaces—from endless notifications and multitasking to awkward meetings and collaborative design. Together, they suggest that humor and shared language help people navigate an increasingly virtual work environment. ## Balancing Effort and Iteration - **Fidelity Fluency:** Knowing how polished a project needs to be, and avoiding unnecessary pixel-perfect work when a rough concept is sufficient. - **WIP Waltz:** The continual cycle of revising, tweaking, and rethinking work as it develops. - **Style Guide Safari:** Exploring a design system’s typography, colors, and other visual elements to find the right creative direction. - **UI Lock Ness Monster:** A frequently discussed interface feature that is always expected in a future update but never appears. ## Digital Overload and Distraction - **Keyboard Cardio:** The frantic effort of sending emails and Slack messages, likened to an intense keyboard workout. - **Slack-lash:** The shock of being hit by a sudden flood of Slack notifications and messages. - **Tab Tsunami:** Having so many browser tabs open that the screen—and one’s attention—feels overwhelmed. - **Toggle Tax:** The mental cost of constantly switching between tasks and contexts. - **Workplace Whack-a-Mole:** Repeatedly responding to incoming tasks, alerts, and emails as soon as they appear. ## Virtual Meeting Experiences - **Icebroken:** Oversharing during an icebreaker and turning a friendly introduction into an uncomfortable moment. - **Screenshare Scramble:** Quickly hiding embarrassing or irrelevant browser tabs before sharing a screen. - **Zoombie:** Someone who appears present on a video call but is mentally disengaged. - **Zoom Zen:** The rare, highly effective meeting where the agenda is clear, participation runs smoothly, and the call ends on time. ## Collaboration and Social Validation - **Sudden Heavy Stamping:** Receiving an unexpected rush of positive reactions—such as hearts or “+1” votes—on a collaborative idea. - **Fidelity Fluency** also reflects collaborative judgment: teams must match the level of detail to the project’s actual needs rather than overinvesting in polish. The glossary turns the habits and tensions of modern work into memorable expressions. Recognizing these patterns can make digital collaboration more manageable—and encourage teams to protect focus, communicate intentionally, and find humor in workplace chaos.

Read original(opens in new tab)
FigmaDesign SystemsUser InterfaceSlack+3
figma2 min readCurated summary

Tap into Shortcuts With a New Custom Keyboard from Figma x Work Louder | Figma Blog

Mechanical keyboards offer tactile feedback, customization, and personal expression that standard keyboards lack. Figma partnered with Work Louder to apply those qualities to creative workflows, especially canvas navigation and shortcuts that often strain users’ hands. The resulting Creator Micro keyboard is designed as a tactile alternative to a trackpad, making Figma shortcuts faster, more memorable, and more enjoyable. ## Why Standard Keyboards Fall Short for Creative Work - Traditional QWERTY keyboards evolved from typewriters and were designed primarily for office writing. - Creative software introduced complex shortcuts that can force users into awkward, finger-stretching combinations. - Mechanical keyboards restore personality through customizable: - Colors and keycaps - Layouts - Lighting - Switches and tactile feedback - Figma argues that tools for creative work should support both efficiency and personal expression. ## The Figma x Work Louder Collaboration - Figma partnered with Montréal-based modular keyboard company Work Louder. - The goal was not to move Figma into hardware or make expensive equipment necessary for collaboration. - Instead, the collaboration responds to Figma users who already rely heavily on mechanical keyboards and shortcuts. - The product is a customized version of Work Louder’s Creator Micro keyboard. ## A Keyboard Designed for Canvas Navigation - Figma users spend much of their time navigating files with a mouse rather than typing. - The Creator Micro therefore functions more like an alternative trackpad than a conventional keyboard. - It includes: - 12 programmable keys - Two rotary encoders - Support for 48 different shortcuts - Figma contains more than 150 possible shortcuts, so the device focuses on frequently used commands rather than attempting to reproduce every shortcut. ## Building Muscle Memory Through Tactile Feedback - The keys are arranged in a grid, making shortcut locations easier to mentally map. - Physical buttons and rotary dials provide feedback without requiring users to look down. - Repeated tactile interactions help users develop muscle memory more quickly. - Figma and Work Louder emphasize that shortcut learning should feel enjoyable rather than like memorizing commands users may soon forget. The Creator Micro illustrates how thoughtful hardware can make digital creative work feel more physical, intuitive, and engaging. For users who rely heavily on Figma shortcuts and canvas navigation, a customizable tactile controller may offer a faster and more enjoyable workflow without changing how Figma itself is accessed.

Read original(opens in new tab)
FigmaUser ExperienceKeyboard ShortcutsMechanical Keyboards+1
figma2 min readCurated summary

Top 10 things we shipped this year | Figma Blog

Figma’s 2023 product updates focused on helping teams design and build together, from major launches like Dev Mode and variables to smaller quality-of-life improvements. Rather than ranking features strictly, the company highlights updates that improve different stages of product development. The excerpt spotlights faster font selection and more powerful component exploration. ## A Year of Design-to-Development Improvements - Figma describes 2023 as a major year, marked by: - The largest Config conference to date - The launch of Dev Mode for developer-focused workflows - Variables and advanced prototyping - More than 200 product updates, including the “Little Big Updates” - The company emphasizes that small fixes and major features both meaningfully improve users’ work. ## New Serifs in Town - Font picker previews now appear directly on the canvas. - Users can hover over typefaces and immediately see how text will look without selecting each font. - This makes comparing typefaces faster and reduces friction when choosing typography. ## The Smart Play - The component details modal and playground are available from the assets panel. - Selecting an asset opens component information and provides a link to its main library. - On Professional plans and above, the playground lets users: - Preview component variants - Test component properties - Explore variable modes - These capabilities support quicker experimentation and easier iteration within the design workflow. Overall, the featured updates show Figma’s effort to improve both everyday design tasks and the broader collaboration between designers and developers.

Read original(opens in new tab)
FigmaDesign SystemsPrototypingDev Mode+3
figma3 min readCurated summary

Figma’s 2023 Handoff | Figma Blog

2023’s tensions—especially between rapid AI adoption and renewed human connection—reinforced Figma’s belief that collaboration is essential. The company frames its year-end “Handoff” as a reflection on how teams can work together more continuously, rather than treating work as a series of disconnected transfers. Its major launches, including Dev Mode and FigJam AI, are presented as tools for reducing barriers and making collaboration more inclusive and iterative. ## A Year Defined by AI and Human Connection - 2023 was characterized both by AI’s rapid expansion and by people reconnecting after the pandemic. - Figma argues that these developments are not necessarily contradictory: technology can support more meaningful human collaboration. - The company emphasizes that people need one another to interpret challenges and understand the world around them. ## Reimagining the Handoff - In American football, a handoff is a coordinated pass between teammates; in product development, it has often meant throwing work “over the wall.” - Designers and developers traditionally work from different perspectives, despite being deeply dependent on each other. - Figma advocates for “multiplayer” work: shared spaces where people can solve problems together and understand one another’s needs. - A successful handoff should be an ongoing conversation, enabling faster iteration and better products. ## Dev Mode and Developer Collaboration - Figma launched **Dev Mode** to provide developers with a developer-focused view of design files. - The feature is intended to give developers the information and tools they need at the appropriate stage of the workflow. - Figma describes Dev Mode as a way to eliminate the traditional handoff barrier and make design-development collaboration more continuous. ## AI as a Collaborator - Figma’s new AI features in **FigJam** are designed to accelerate ideation. - The goal is not to replace human interaction, but to make meetings and collaborative moments more productive and meaningful. - Figma connects this approach to “lowering the floor and raising the ceiling”: making products more accessible while expanding what experienced users can accomplish. ## The 2023 Handoff Collection The article introduces several additional reflections and features from Figma’s year, including: - The year’s top ten product launches - How product managers brought AI features to market - Questions for rediscovering enthusiasm for technology - Guidance for more effective meetings - New workplace vocabulary - Professional career pivots - The enjoyment and culture surrounding mechanical keyboards Figma’s practical conclusion is that strong collaboration requires more than efficient workflows. Teams need shared spaces, continuous dialogue, inclusive tools, and enough practice and collective experience to play to one another’s strengths.

Read original(opens in new tab)
FigmaAIFigjamDev Mode+2
figma3 min readCurated summary

36 Questions to Fall (Back) in Love with Tech | Figma Blog

Technology once felt playful, creative, and limitless, but constant notifications, social comparison, and digital distrust have made it feel burdensome. Figma’s article explores this changing relationship through interviews with more than 20 product and technology professionals, using 36 questions inspired by the psychology of vulnerability and connection. Their stories suggest that technology remains most meaningful when it enables creativity, community, and human connection rather than merely increasing consumption or efficiency. ## Early Encounters with Technology - Many interviewees remember technology as an open frontier for experimentation and self-expression. - Cristina Cordova discovered college pathways through the College Confidential forum, finding peers and practical guidance unavailable in her family. - Kristy Tillman credits early design software with shaping her career and recalls a period of “pure creativity.” - Mig Reyes remembers customizing AOL Instant Messenger profiles as a playful way to experiment and express himself. - These experiences illustrate how early technology often encouraged curiosity, discovery, and personal agency. ## When the Digital Honeymoon Ends - The web’s promise has been complicated by advertising, fear of missing out, endless notifications, and social-media pressure. - Lauren McCann describes the alienation of seeing friends gather without her. - Shyvee Shi notes that social platforms present polished versions of people’s lives, encouraging unhealthy comparison. - Peter Yang argues that creating things is generally more valuable than passively consuming social content. - As digital tools became essential to work and daily life, they also introduced new obligations, including “Slack-lash” and constant availability. ## Technology as a Source of Community - Despite its problems, technology can create lasting relationships and communities. - Lenny Rachitsky met his wife through the dating site howaboutwe.com. - Sho Kuwamoto formed enduring friendships through the online forum Midwest Raves. - Forums, dating platforms, and other digital communities can connect people with mentors, friends, and partners who share their interests. - At its best, technology helps people overcome geographic and social barriers and build a sense of belonging. ## AI, Creativity, and the Future - AI dominates conversations about technology’s future, bringing both excitement and caution. - Mihika Kapoor sees creative AI tools as a way to help people turn ideas into reality and unlock broader innovation. - Marcel Weekes emphasizes that developers should consider whether and how something should be built—not only whether it can be built. - Automation could reduce tedious work and allow people to focus more on craft, judgment, and interesting problems. - Jenny Wen argues that technology should also make room for joy, rather than optimizing every experience solely for speed or productivity. ## Reflecting on Your Own Relationship with Tech - The article invites readers to use its 36 questions as a tool for reflection and conversation. - Questions explore first usernames, early technology experiences, online identity, creativity, connection, and hopes for the future. - Sharing these stories is intended to create the same vulnerability and intimacy that inspired the original “36 Questions That Lead to Love.” Technology is worth embracing when it helps people create, connect, and express themselves. The practical challenge is to design and use digital tools more intentionally—prioritizing human value and joy over endless consumption, engagement, and optimization.

Read original(opens in new tab)
AIAutomationSoftware DevelopmentMobile Apps+2
figma3 min readCurated summary

The Art of the Professional Pivot | Figma Blog

The article presents professional pivots as normal career adjustments rather than dramatic reinventions. Through six creatives’ stories, it shows how people can redirect their careers by reframing their approach, returning to a familiar company in a new role, or making larger changes. The central message is that pivots can help professionals align their skills and interests more effectively with their work. ## The Reframe: Small Changes with Big Effects A reframe changes how someone approaches their existing role without requiring a complete career change. - Ry Reid moved from customer support into UX writing, later working at Pinterest, Spotify, and Uber Eats. - At Uber Eats, Ry struggled to persuade colleagues through written proposals and was passed over for promotion. - A design manager suggested visualizing ideas instead of explaining them in documents. - Ry began creating rough concepts with pen and paper and Google Slides, then sharing them with colleagues. - This shift helped Ry communicate more effectively and contributed to their proposed user experience being adopted. - The experience showed that presenting an idea and polishing it into a finished design are different skills. ### Lessons from the Reframe - Accept difficult feedback and investigate why opportunities were missed. - Seek advice from mentors in adjacent disciplines. - Test a new approach in low-risk situations. - Expect some discomfort when developing unfamiliar skills. ## The Boomerang: Changing Roles in a Familiar Environment A boomerang involves making a substantial career change while returning to—or remaining within—a company whose culture and operations are already familiar. - Erica Simunovic first worked at Tatari in people operations. - After five years and completing a product design bootcamp, she returned to the same company as a product designer. - Her story illustrates how an existing relationship with an organization can reduce some of the risks of starting over in a new discipline. - The article frames this path as a way to pursue significant change while retaining familiarity with the workplace. ## The Article’s Broader Career-Pivot Framework The six profiles represent different forms of professional change: - **The reframe:** Adjusting perspective or working methods. - **The boomerang:** Taking on a new role at a familiar company. - **The unfolding:** Making a deeper, more personal leap. - **The stretch:** Exploring unfamiliar opportunities. - **The hard left:** Changing direction completely. - **The blend:** Combining experiences, skills, and professional networks. A practical approach is to begin with the smallest change that addresses the problem: seek candid feedback, experiment with adjacent skills, and use existing relationships where possible.

Read original(opens in new tab)
FigmaUser ExperienceProduct DesignSlack+2
figma2 min readCurated summary

Come together: A multiplayer guide to great meetings | Figma Blog

Great meetings are intentionally designed collaborative experiences, not merely calendar events or “glorified emails.” The article argues that successful meetings depend on four pillars: purpose, preparation, participation, and follow-up. Both facilitators and participants share responsibility for creating focused sessions that use everyone’s time and strengths effectively. ## Meetings as Designed Experiences - Meetings often fail because they lack a clear purpose, adequate preparation, active participation, or follow-up. - Effective facilitators design an experience that helps the team collaborate and accomplish concrete goals. - Participants also play an important role in making meetings purposeful and engaging. ## Before the Meeting: Plan for Success Preparation creates the conditions for inclusive and productive collaboration. ### Define the Meeting’s Goal - Clarify whether the meeting is intended to: - Track progress - Make a decision - Share information or insights - Build context across a team - Choose the meeting format based on its purpose. - Shishir Mehrotra’s framework groups meetings into: - **Cadence:** recurring staff meetings, standups, and project syncs - **Catalyst:** decision forums, product reviews, and design critiques - **Context:** all-hands meetings, off-sites, orientations, and one-on-ones - The right category helps determine the questions, participants, and structure required. ### Prepare and Share an Agenda - Circulate an agenda before the meeting, ideally a day in advance. - Include pre-read materials such as: - Project briefs - Documentation - Sketches - Other background information - Use an existing template rather than starting from a blank page. - FigJam templates can structure the discussion, collect participants’ ideas and questions ahead of time, and organize meetings around prompts or “provocations.” - Successful formats can be saved as reusable shared templates, while AI can help generate customized meeting structures. A practical meeting recommendation is to define the intended outcome first, then choose the appropriate format and share enough context for participants to contribute before the meeting begins.

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

Building a Design System That Breathes with Headspace | Figma Blog

Headspace rebuilt its design system to support rapid growth, multiple brands, and products spanning apps, wearables, and VR. Its previous system relied on hard-coded colors, manual processes, and plugins, making updates slow and creating inconsistencies. By adopting design tokens and Figma variables, Headspace created a scalable source of truth for designers and engineers that could evolve with the business. ## Challenges of the Previous System - Headspace served more than 100 million members across numerous products and partnerships. - The existing design system was manual and heavily dependent on plugins. - Hard-coded color values produced multiple hex-code variations and inconsistent experiences. - Even small palette changes could take the design systems team hours or days. - Plugins often required specialized knowledge, frequent resets, and workflows that were not intuitive for occasional users. - The system was designed for a single brand, creating problems when Headspace merged with Ginger, later rebranded as Headspace Care. ## Preparing for Multiple Brands and Future Growth - Senior product designer Steven Sczepanik audited the existing system after the merger announcement. - He rebuilt components and patterns so they were easier for designers and engineers to find and use. - The redesign established Headspace’s first formal token system. - Tokens created a shared language for foundational properties such as colors and typography. - The system was designed to support Headspace Care and future partnerships without requiring separate, disconnected systems. ## Replacing Plugins with Figma Variables - Headspace converted its color tokens and typography into Figma variables. - Variables replaced many plugin-based workflows with a native Figma solution. - Steven implemented the initial color and typography variables in about a day, compared with two years spent developing the broader previous system. - The new approach made theme changes and system-wide updates faster and more reliable. - Designers and engineers gained a more dependable source of truth for shared design decisions. ## A Design System That Can Evolve - Headspace’s design system now supports a growing ecosystem of brands, platforms, and experiences. - Centralized tokens reduce duplication and improve consistency across products. - Native variables make the system easier to maintain as the visual identity changes. - The work demonstrates that scalable design systems must accommodate organizational change, not just reuse components. Headspace’s experience suggests that teams preparing for growth should replace hard-coded values and fragile plugin workflows with structured tokens and native variables. This creates a more flexible foundation for consistent design across brands, products, and future expansion.

Read original(opens in new tab)
FigmaDesign SystemsDesign TokensDesign Variables+2