I jumped straight into features and had to backtrack when they asked who the app was actually for.
Start by clarifying the goal of the companion app—whether it's to enhance visitor experience, drive engagement, or generate revenue—and identify the primary user segment. Then, prioritize features based on user needs and business impact, and outline a phased roadmap with success metrics.
Pro tip: Anchor your design in a clear user journey (pre-visit, during visit, post-visit) and tie features to measurable outcomes like increased dwell time or repeat visits. Show awareness of Google's strengths (e.g., Maps, Lens, AI) to leverage existing ecosystems.
Ask clarifying questions to define the app's primary objective (e.g., enhance experience, education, revenue) and target users (e.g., families, tourists, members).
Map the visitor journey (pre-visit, during visit, post-visit) and brainstorm pain points (e.g., navigation, wait times, lack of info) and opportunities (e.g., personalization, gamification).
Use a prioritization framework (e.g., RICE, impact/effort) to select high-impact features that align with goals and user needs, considering technical feasibility.
Outline a phased roadmap: MVP with core features (e.g., map, schedules), then enhancements (e.g., AR, personalization) based on user feedback and metrics.
Specify KPIs (e.g., daily active users, session length, repeat visits, NPS) to measure success and inform iterations.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.