top of page

Splunk Observability Suite Onboarding

Senior User Researcher

Challenge:

Splunk's unified UI team sought to streamline the onboarding process and consolidate the experiences of recently acquired products into a cohesive suite-wide experience. The goal was to accelerate time-to-value (TTV) during onboarding, especially for users leveraging the free trial, and determine the optimal adoption path for maximizing value from the Observability Cloud Suite.

Research Questions:

  • What is the quickest path to value during onboarding (excluding data ingestion)?

  • What are the primary pain points during onboarding?

  • What is the ideal product installation order?

  • Are there quick wins that demonstrate value and drive adoption?

Methodology:

The research employed a mixed-methods approach, including:

  • Stakeholder and sales team workshops

  • In-depth semi-structured interviews

  • Remote observation of users during onboarding tasks (incorporating documentation review)

Key Insights:

  • APM Paradox: While application performance monitoring (APM) is central to observability, the onboarding process almost always begins with basic server monitoring (IMM). Setting up APM to truly get the most value out of it requires an expert developer to integrate OpenTelemetry (OTel) into your environment, which isn’t very common.

  • Docs as a Proxy: Clarity in documentation is viewed as a proxy for the ease of use of the product. We need to provide proper, concise documentation within the product as it is needed.

  • F1 Kit Car Analogy: Splunk's Observability potential is vast, but the complexity of setup and configuration demands a skilled team and strategic implementation, whereas competitors like Datadog offer a more user-friendly experience.

Outcomes:

  • Affinity Journey Maps: Detailed user journeys that highlight pain points and opportunities for improvement. There was a consistent trend of rising initial excitement when learning about the potential power of the tools in the suite, leading to a quick dip of disappointment when faced with the complex realities of customized implementation.

  • Product-Market Misalignment: Identified discrepancies between product capabilities and market needs, emphasizing the need for a more accessible onboarding experience. Marketing a direct trial with immature self-service infrastructure was a mistake. 

  • Documentation Integration: Incorporated documentation review and observation into future user research studies, revealing low-hanging usability issues.

Impact:

​This research project played a pivotal role in understanding and addressing the challenges of onboarding users to Splunk's Observability Cloud Suite. By identifying pain points, clarifying the product-market fit, and driving strategic changes, the research significantly contributed to improving the user experience.

  • Strategic Shift: The research led to the de-prioritization of self-service trials, reducing churn and improving customer satisfaction.

  • Targeted Go-To-Market: The focus shifted towards existing Splunk Cloud customers, leveraging our existing technical sales teams to guide customers during their Observability Suite trials.

  • Further Research: The study initiated further investigation into refining the onboarding process and aligning the product with customer needs.

For a more detailed case study please contact me at Wolff.RyanM@gmail.com

bottom of page