The LavaCon Content Strategy Conference | 5–8 October 2025 | Atlanta, GA
Hedley Simons

Heds Simons is a Senior Principal Field Engineer, and an SME for several Grafana Labs products, most notably for tracing and profiling telemetry. He specializes in architecture and observability pipeline discussions with both customers and community users, public workshop creation and maintenance, acting as a product power-user for Grafana’s engineering teams. Heds is the maintainer of several repositories, including Intro-to-MLTP, a fully Grafana OSS-based Observability pipeline environment that is freely available to the public

D(ocs)&D(evelopment): Finding the Perfect Party for Your Documentation Campaign

Co-presented with: Kim Nylander

It’s product release time. The code is stable. You’ve got everything EXCEPT the docs.
How do you create meaningful, prioritized content quickly?
Your writer needs to collaborate with a Subject Matter Expert (SME) who understands the technical and user contexts.
At Grafana, this synergy often happens between Field Engineers (FE) and Technical Writers (TW). FEs are a three-in-one SME with the understanding of a developer, sales engineer, and technical support.

How does this collaboration benefit both writers and SMEs?

  • TW has a single SME for user needs and cross-product technical expertise.
  • FEs get accurate, up-to-date content that help them and Grafana’s customers learn products.
  • Product users get accurate, up-to-date docs.

We’ll share how this collaboration started through a love of RPGs, the traps we encountered and lessons learnt, and how a bi-weekly session between two colleagues became the foundation for a model now used across Grafana’s telemetry products.

In this session, attendees will learn:

  • How to Identify and recruit collaborators best suited to work on documentation
  • How to guide documentation contributors on what level of documentation is useful for their software, product, feature, etc.
  • Tips for establishing a collaborative workflow with regular cadence
  • How to prioritize work that best addresses the user’s needs
  • Why you need relentless curiosity, to be willing to ask questions no one else does