How can Yext enhance its Knowledge Graph to better support multi-location businesses?

Introduction

To enhance Yext's Knowledge Graph for better support of multi-location businesses, we need to focus on improving data management, scalability, and integration capabilities. I'll outline a strategic approach to address this challenge, considering user needs, technical constraints, and market dynamics.

Step 1

Clarifying Questions (5 mins)

• Looking at Yext's position in the market, I'm thinking about the scale of multi-location businesses we're targeting. Could you help me understand the typical size range of businesses we're focusing on? Are we primarily looking at enterprises with hundreds of locations, or are we also considering smaller chains with 10-50 locations?

Why it matters: Determines the scalability requirements and complexity of the Knowledge Graph enhancements. Expected answer: Focusing on businesses with 50+ locations, but want to improve support for smaller chains as well. Impact on approach: Would prioritize scalability and flexibility in data structure to accommodate various business sizes.

• Considering the evolving nature of business information, I'm curious about the current update frequency for the Knowledge Graph. How often do multi-location businesses typically need to update their information, and what's our current capability to handle these updates?

Why it matters: Helps identify if we need to focus on real-time updates or batch processing improvements. Expected answer: Most businesses update weekly or monthly, but some require daily updates which our current system struggles with. Impact on approach: Would prioritize improving real-time update capabilities and possibly introducing an API for direct integrations.

• Given the complexity of multi-location businesses, I'm wondering about the types of data relationships we currently support. Can you elaborate on the current capabilities of our Knowledge Graph in terms of handling hierarchical data structures, like regional groupings or franchise relationships?

Why it matters: Determines if we need to focus on enhancing data relationship models or improving existing structures. Expected answer: Basic parent-child relationships are supported, but more complex hierarchies and lateral relationships are challenging. Impact on approach: Would focus on expanding the data model to support more complex business structures and relationships.

• Thinking about integration with other systems, I'm curious about our current API capabilities. How well does our Knowledge Graph currently integrate with other business systems like CRMs, POSs, or inventory management systems?

Why it matters: Helps determine if we need to focus on improving external integrations or internal data processing. Expected answer: Basic API exists but lacks advanced features and has performance issues with large data sets. Impact on approach: Would prioritize enhancing API capabilities and performance, possibly introducing a GraphQL interface for more flexible queries.