Builder's Culture: How a Designer Benefits and Influences at LogDNA

4 MIN READ
MIN READ

LogDNA is now Mezmo but the people you know and love are here to stay.

Hi. My name is Chad, and I am a lead product designer here at LogDNA. I want to take a moment and discuss something I am a part of and what I am influenced by, day to day: LogDNA's "builder culture." 

You might instantly be thinking, "what in tarnation is a builder culture?" and that's such a great question, right out of the gate. I think a builder's culture is a place where a diverse set of people, from all stages and walks of life, can get together and make stuff that matters. In this case, that "stuff" is dope-ass software for some fantastic customers.

Some key factors play into forming one of the best-in-class cultures I've ever been a part of. I believe some of those factors are:

  • Passion for the important work
  • Radical ownership
  • Assuming good intent

Passion for The Important Work

"Important work" can be tricky because different work is important to different people at different times. Here at LogDNA, I am thrilled there are always so many conversations that showcase our customers. As a UX practitioner, this is important to me. This focus on our customers helps us Loggers remember what's important to us. Our important work is taking care of the customer by enabling the successful function of their job through their tools (the software we build!). #takeworkseriously

Radical Ownership

One of the greatest feelings as a product designer is to have engineers who get it. There have been countless times where someone adjacent to the design team has taken the initiative to understand and contribute to the user experience. Examples include User Interface (UI) engineers wireframing in the browser and talking through real-time ideas with designers. Or various volunteers from many departments who come together to help define and build an accessible design system adopted across the organization. We’ve even had an Onboarding Engineer from another department come to us with hand-drawn notes of UI ideas that kick start a conversation with product management and developers. I'm going to level with you here—sometimes it feels like I'm cheating. I'm just catching everyone's ideas, feedback, and insight. It is truly remarkable to have so much support and collaboration while building novel solutions in this market. Everyone at LogDNA takes ownership of the product and wants to work together to improve it. #wejumpin

Assuming Good Intent

We all know the phrase, "you should never assume because it makes an..." you get it. However, I am here to tell you this is a bag full of nonsense! Talking to customers, synthesizing feedback from team members, working on feature projects, maintaining a design system, keeping close communication with your team, and getting your work done is stressful! There are times when there are real problems, and as Loggers, it is our time to come together and get shit done. When you are in the weeds, and someone's email is a little curt, or there are all caps slack messages frantically flying at your face, it is easy to take something personally or be caught up in something yourself and send a signal you didn't intend to send. I see it play out many different ways. Still, I am always humbled and grateful when someone like an engineering manager or another designer pulls me aside to clear the air or backtrack on sensitive topics. When I assume my teammate wants positive outcomes to their efforts (just like I do) I am able to frame a response, even in a stressful situation, that points towards the shared goals and not kick-off another corporate bickering session. It turns out when the team isn't bickering; the inverse is more likely: FUN! I have made some fantastic professional and personal connections in my last two years at LogDNA. Being on a team that is excited about your contribution is a great feeling. Individually contributing to a greater whole where I am encouraged to be my authentic self mixed with a company-wide positive approach lets everyone express themselves and connect in these really great ways. Ways that impact and feed into the work we do (see "passion for work" above) here at LogDNA. #wehavefun


Throughout this post you’ve seen hashtags that correlate to our company values:

  • We take the work, not ourselves, seriously
  • We jump in
  • We have fun

I’ve included these because we live them each and every day and they’ve massively influenced my experience at LogDNA. 

The list of contributing factors above isn't an exhaustive list of all of the reasons we have an excellent culture for builders here at LogDNA. Still, these are my current favorite things about coming to work every day. If you are a product designer and a senior user experience practitioner and if any of the anecdotes above resonate with you, I'd love for you to consider coming to benefit from this culture as well as help shape it and add your story to the mix. LFG. 



Table of Contents

    Share Article

    RSS Feed

    Next blog post
    You're viewing our latest blog post.
    Previous blog post
    You're viewing our oldest blog post.
    Mezmo + Catchpoint deliver observability SREs can rely on
    Mezmo’s AI-powered Site Reliability Engineering (SRE) agent for Root Cause Analysis (RCA)
    What is Active Telemetry
    Launching an agentic SRE for root cause analysis
    Paving the way for a new era: Mezmo's Active Telemetry
    The Answer to SRE Agent Failures: Context Engineering
    Empowering an MCP server with a telemetry pipeline
    The Debugging Bottleneck: A Manual Log-Sifting Expedition
    The Smartest Member of Your Developer Ecosystem: Introducing the Mezmo MCP Server
    Your New AI Assistant for a Smarter Workflow
    The Observability Problem Isn't Data Volume Anymore—It's Context
    Beyond the Pipeline: Data Isn't Oil, It's Power.
    The Platform Engineer's Playbook: Mastering OpenTelemetry & Compliance with Mezmo and Dynatrace
    From Alert to Answer in Seconds: Accelerating Incident Response in Dynatrace
    Taming Your Dynatrace Bill: How to Cut Observability Costs, Not Visibility
    Architecting for Value: A Playbook for Sustainable Observability
    How to Cut Observability Costs with Synthetic Monitoring and Responsive Pipelines
    Unlock Deeper Insights: Introducing GitLab Event Integration with Mezmo
    Introducing the New Mezmo Product Homepage
    The Inconvenient Truth About AI Ethics in Observability
    Observability's Moneyball Moment: How AI Is Changing the Game (Not Ending It)
    Do you Grok It?
    Top Five Reasons Telemetry Pipelines Should Be on Every Engineer’s Radar
    Is It a Cup or a Pot? Helping You Pinpoint the Problem—and Sleep Through the Night
    Smarter Telemetry Pipelines: The Key to Cutting Datadog Costs and Observability Chaos
    Why Datadog Falls Short for Log Management and What to Do Instead
    Telemetry for Modern Apps: Reducing MTTR with Smarter Signals
    Transforming Observability: Simpler, Smarter, and More Affordable Data Control
    Datadog: The Good, The Bad, The Costly
    Mezmo Recognized with 25 G2 Awards for Spring 2025
    Reducing Telemetry Toil with Rapid Pipelining
    Cut Costs, Not Insights:   A Practical Guide to Telemetry Data Optimization
    Webinar Recap: Telemetry Pipeline 101
    Petabyte Scale, Gigabyte Costs: Mezmo’s Evolution from ElasticSearch to Quickwit
    2024 Recap - Highlights of Mezmo’s product enhancements
    My Favorite Observability and DevOps Articles of 2024
    AWS re:Invent ‘24: Generative AI Observability, Platform Engineering, and 99.9995% Availability
    From Gartner IOCS 2024 Conference: AI, Observability Data, and Telemetry Pipelines
    Our team’s learnings from Kubecon: Use Exemplars, Configuring OTel, and OTTL cookbook
    How Mezmo Uses a Telemetry Pipeline to Handle Metrics, Part II
    Webinar Recap: 2024 DORA Report: Accelerate State of DevOps
    Kubecon ‘24 recap: Patent Trolls, OTel Lessons at Scale, and Principle Platform Abstractions
    Announcing Mezmo Flow: Build a Telemetry Pipeline in 15 minutes
    Key Takeaways from the 2024 DORA Report
    Webinar Recap | Telemetry Data Management: Tales from the Trenches
    What are SLOs/SLIs/SLAs?
    Webinar Recap | Next Gen Log Management: Maximize Log Value with Telemetry Pipelines
    Creating In-Stream Alerts for Telemetry Data
    Creating Re-Usable Components for Telemetry Pipelines
    Optimizing Data for Service Management Objective Monitoring
    More Value From Your Logs: Next Generation Log Management from Mezmo
    A Day in the Life of a Mezmo SRE
    Webinar Recap: Applying a Data Engineering Approach to Telemetry Data
    Dogfooding at Mezmo: How we used telemetry pipeline to reduce data volume
    Unlocking Business Insights with Telemetry Pipelines
    Why Your Telemetry (Observability) Pipelines Need to be Responsive
    How Data Profiling Can Reduce Burnout
    Data Optimization Technique: Route Data to Specialized Processing Chains
    Data Privacy Takeaways from Gartner Security & Risk Summit
    Mastering Telemetry Pipelines: Driving Compliance and Data Optimization
    A Recap of Gartner Security and Risk Summit: GenAI, Augmented Cybersecurity, Burnout
    Why Telemetry Pipelines Should Be A Part Of Your Compliance Strategy
    Pipeline Module: Event to Metric
    Telemetry Data Compliance Module
    OpenTelemetry: The Key To Unified Telemetry Data
    Data optimization technique: convert events to metrics
    What’s New With Mezmo: In-stream Alerting
    How Mezmo Used Telemetry Pipeline to Handle Metrics
    Webinar Recap: Mastering Telemetry Pipelines - A DevOps Lifecycle Approach to Data Management
    Open-source Telemetry Pipelines: An Overview
    SRECon Recap: Product Reliability, Burn Out, and more
    Webinar Recap: How to Manage Telemetry Data with Confidence
    Webinar Recap: Myths and Realities in Telemetry Data Handling
    Using Vector to Build a Telemetry Pipeline Solution
    Managing Telemetry Data Overflow in Kubernetes with Resource Quotas and Limits
    How To Optimize Telemetry Pipelines For Better Observability and Security
    Gartner IOCS Conference Recap: Monitoring and Observing Environments with Telemetry Pipelines
    AWS re:Invent 2023 highlights: Observability at Stripe, Capital One, and McDonald’s
    Webinar Recap: Best Practices for Observability Pipelines
    Introducing Responsive Pipelines from Mezmo
    My First KubeCon - Tales of the K8’s community, DE&I, sustainability, and OTel
    Modernize Telemetry Pipeline Management with Mezmo Pipeline as Code
    How To Profile and Optimize Telemetry Data: A Deep Dive
    Kubernetes Telemetry Data Optimization in Five Steps with Mezmo
    Introducing Mezmo Edge: A Secure Approach To Telemetry Data
    Understand Kubernetes Telemetry Data Immediately With Mezmo’s Welcome Pipeline
    Unearthing Gold: Deriving Metrics from Logs with Mezmo Telemetry Pipeline
    Webinar Recap: The Single Pane of Glass Myth
    Empower Observability Engineers: Enhance Engineering With Mezmo
    Webinar Recap: How to Get More Out of Your Log Data
    Unraveling the Log Data Explosion: New Market Research Shows Trends and Challenges
    Webinar Recap: Unlocking the Full Value of Telemetry Data
    Data-Driven Decision Making: Leveraging Metrics and Logs-to-Metrics Processors
    How To Configure The Mezmo Telemetry Pipeline
    Supercharge Elasticsearch Observability With Telemetry Pipelines
    Enhancing Grafana Observability With Telemetry Pipelines
    Optimizing Your Splunk Experience with Telemetry Pipelines
    Webinar Recap: Unlocking Business Performance with Telemetry Data
    Enhancing Datadog Observability with Telemetry Pipelines
    Transforming Your Data With Telemetry Pipelines