Home / Companies / Honeycomb / Blog / Post Details
Content Deep Dive

Autocatalytic Adoption: Harnessing Patterns to Promote Honeycomb in Your Organization

Blog post from Honeycomb

Post Details
Company
Date Published
Author
Nick Travaglini
Word Count
1,633
Company Posts That Month
6
Language
English
Hacker News Points
-
Post removed?
No
Summary

When organizations adopt Honeycomb at the Enterprise level, they receive support from a Technical Customer Success Manager (TCSM) to help implement and leverage the observability tool effectively. The TCSM assists central observability teams in developing strategies to ensure their colleagues can use Honeycomb, addressing basic needs like login access, data availability, and query training, and working collaboratively with Honeycomb's Customer Success department to solve problems. The overarching goal is to foster a customer experience (CX)-centric culture where customer experience dictates product development decisions. However, challenges arise when engineers new to operations roles or unfamiliar with tools like distributed tracing face high-pressure situations, such as late-night outages, without sufficient practice time. Observability teams must navigate organizational constraints by identifying and utilizing existing social institutions and routines, such as team onboarding, sprint tasks, and deployment watch parties, to build engineers' confidence and promote observability-driven development. By integrating Honeycomb into these familiar activities, engineers can gradually enhance their understanding of the system, leading to better incident response and system optimization. Honeycomb's Customer Success team supports this organizational shift by providing resources such as online training and documentation while collaborating with teams to tailor strategies that maximize the tool's benefits.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.