Grew API Adoption 2X by Influencing Improvements to Developer Onboarding and Simplifying API Implementation at Walmart.

Executive Summary

Grew API adoption 2X by leading generative research with developers that influenced improvements to developer onboarding and simplifying API implementation. Drove $3MM in new revenue, allowing low-maturity suppliers to adopt APIs via pre-built dashboards for the company’s $250MM data analytics business.

The Challenge

Walmart’s API adoption stalled, limiting supplier integration and reducing visibility into real-time inventory and sales. Existing tools fell short, leaving critical data underused.

Methodologies Used

  • Structured Interviews

  • Quantitative Survey

  • Kano Analysis

  • Concept Testing

  • Journey Mapping

Collaborated With

  • Product Director

  • Product Manager

  • Director of Technology

  • Sr. Director of Technology

  • UX Manager

Timing

  • 4 weeks

My Approach

I led generative research with developers and internal teams. Mapped critical breakdowns in on-boarding and implementation workflows, uncovering inefficiencies in communication and process improvements to close critical gaps to API access and drive adoption.

Research Questions

  • What barriers do suppliers face trying to onboard and implement the API?

  • How do low-maturity suppliers interact with Walmart’s data tools, what prevents them from adopting the API?

  • What internal process and communication gaps impact API integration and support?

Research Objectives

  • Understand the limitations, knowledge gaps, and tooling needs developers face during onboarding and API integration.

  • Uncover breakdowns across internal teams that prevent effective API support, and identify opportunities to align and streamline cross-functional efforts.

  • Identify pain points and friction in the current onboarding and implementation workflows to inform improvements that make API adoption faster and easier.

Key Themes

  • API Knowledge Gap Impacts Adoption: Internal teams lack fundamental resources, impacting their ability to promote the API and drive use. This creates difficulty for teams communicating with potential suppliers.

  • Disconnected Workflow Impacts Access: The onboarding workflow creates a disconnect between internal systems and API access. The gap requires manual intervention to retrieve data, leading to inefficiencies and limiting access for suppliers who would benefit.

  • High Set-Up Costs Slows API Adoption: The high cost of using the API limits adoption. Implementation it requires significant investment of time and resources, many suppliers lack the expertise to effectively integrate it.

Impact

  • 2X API Adoption: Based on the research, launch of the updates doubled API adoption.

  • +$3MM in New Revenue: This work resulted in pre-built dashboards that accelerated API adoption and generated $3MM in new revenue from suppliers lacking resources to integrate API functionality.

  • Design Team Engaged to Support Growth: Based on my recommendation, design was engaged to migrate platforms, ensuring a unified experience and streamlined functionality.