How Old is Two in Startup Years?

4 MIN READ
MIN READ

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

There is no ice breaker in the world better than karaoke with 40 strangers that have your professional future in their hands. 

It was Summer 2019 and I had just joined LogDNA as a marketing communications manager when we went to San Diego for our company offsite. There was something special about this group, and I knew it right away when we were in that karaoke bar. They had classic taste in music (to anyone that grew up in the 90’s), they cheered each other on (even the bad singers), and they jumped in to help someone with the chorus when they fumbled or got shy. Through the fumbles and shy moments over the last two plus years, these are the same things that have kept me at LogDNA. We celebrate together, we learn together, and we encourage each other to take on the BHAGs that come with scaling a startup. 

A team without a leader

The week we all “worked from home for two weeks until COVID passed” was the week that our CMO and our sole product marketer both left the company. As an interim manager, we reported to Tucker, who had just taken the reins as the CEO and was also the acting CRO (that’s three C-level jobs at once, in case you lost count). This could have been bad, and admittedly the marketing team wasn’t sure what to expect. Tucker could have forced us to sacrifice all brand efforts and focus solely on sales pipeline. He could have micromanaged us. He could have frozen our budget or paused all strategy until we hired a new marketing leader. But, he didn’t do any of those things. Instead, he listened. He had discussions with us about what we were working on and what we thought could be better. And, he gave us a lot of autonomy to manage our respective programs. During this time I got to try on a product marketing hat, I managed a PR team for the first time ever, I learned about the magic of Gartner, and I got to throw a lot of spaghetti at the wall to see what stuck. 

Since the marketing and sales teams were both reporting to Tucker, we were forced to get closer (I say forced in an endearing way). We realized that we hadn’t been aligned before and started working on the inevitable tension that exists between teams in a go-to-market organization. Although I think some of that will always exist in a healthy org, this period helped us better understand one another and align around common goals—a practice we’ve maintained to this day. Above all, my favorite part of this period was how close the marketing team got. Many of us were in uncharted territory and early in our careers (this was my second tech company after having started my career in the fashion and beauty industry—not exactly cloud-native if you know what I mean). In the absence of a CMO or VP to guide us, we collaborated on nearly every marketing function. We each owned a part of demand generation, content creation, advertising, and events, and when one component was completed the next person would jump in to do their part. We got really good at working a-sync on projects, providing feedback, and knowledge sharing—three things that are essential as a startup and only possible if you start from a foundation of trust. Trust was the number one thing that we had, built, and grew during this period and that we still nurture every day. 

A team with a leader

Six months later, the marketing team had a lot to be proud of, but we had also blurred the lines between who owned what functions. Then, at the perfect moment, Tucker sent us a gift named Dave. 

Dave is the VP of Marketing and the best boss I’ve ever had. He’s had the career every tech marketer in the valley dreams of: eBay in the early days, Twitter, Facebook, Cloudflare. He joined LogDNA and inherited a high-functioning group with a friendly, albeit kind of cult-like, energy. He created the structure that we needed, hired the folks that we really needed, and gave us the stability and structure to take risks. Note that there’s a difference between the feeling that I described earlier as, “throwing spaghetti at the wall to see what stuck” and having a stable foundation from which you can experiment. One of his first hires was a head of demand generation, who is brilliantly data driven, and has helped us implement a culture of testing. This is essential for understanding our audience, how they consume information, and how they ultimately make decisions about the technology that they’re going to adopt. 

Thinking big and thinking small

I joined LogDNA when we were 40 people. In the last two years we’ve more than tripled our full-time staff and have dozens more teammates that we partner with from supporting agencies. A few months ago, Tucker introduced this concept of thinking big and thinking small. It means that we must acknowledge that there are times when we must think and operate like a big company—for example our infrastructure team must think BIG because they are supporting thousands of customers that send us petabytes of data every month. And, there are times when we must think and act like a small startup—like launching a new website in two months, field testing concepts with analysts and design partners, and evolving our product roadmap depending on what the industry is telling us they need. We move fast, we iterate constantly, we push each other to do more than we think we can. 

I am so grateful for this team and all of the amazing things that they’ve thrown at me over the last couple of years. I can’t wait to write another post in 2024 talking about how long the next two years felt. Maybe there will be another karaoke story by then. 

P.S. We're hiring.

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