Should Intersection prioritize expanding its Link network coverage or enhancing features on existing kiosks to improve user engagement?

Introduction

The trade-off question at hand is whether Intersection should prioritize expanding its Link network coverage or enhancing features on existing kiosks to improve user engagement. This scenario involves balancing growth with user experience improvement for Intersection's public Wi-Fi and information kiosk network. I'll analyze this trade-off by examining the product context, potential impacts, key metrics, and experimental approaches to inform a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Based on the current market landscape, I'm thinking network coverage might be a key differentiator. Could you provide more context on our current coverage compared to competitors?

Why it matters: Helps assess the urgency of expansion vs. feature enhancement Expected answer: We're behind in certain key markets Impact on approach: Would prioritize expansion if we're significantly behind

• Considering our business model, I assume advertising is a major revenue stream. How does kiosk engagement currently impact our ad revenue?

Why it matters: Connects user engagement directly to business outcomes Expected answer: Strong correlation between engagement and ad revenue Impact on approach: Would emphasize feature enhancements if engagement significantly drives revenue

• Looking at user behavior, I'm curious about the primary use cases for our kiosks. What are the top 3 features users engage with most frequently?

Why it matters: Identifies areas for potential feature enhancement Expected answer: Wi-Fi connectivity, local information, and wayfinding Impact on approach: Would focus on enhancing these key features if they're underperforming

• From a technical standpoint, I'm wondering about the scalability of our current kiosk infrastructure. How easily can we roll out new features across the network?

Why it matters: Assesses feasibility of feature enhancements Expected answer: Moderate difficulty due to legacy systems Impact on approach: Might lean towards expansion if feature updates are technically challenging

• Regarding resources, I'm curious about our current team structure. Do we have separate teams for network expansion and feature development, or is it a shared resource pool?

Why it matters: Helps understand resource allocation implications Expected answer: Shared resource pool with some specialization Impact on approach: Would consider team restructuring or hiring needs based on chosen priority