How might Swiftly enhance its passenger information system to better serve riders with accessibility needs?

Introduction

Enhancing Swiftly's passenger information system to better serve riders with accessibility needs is a critical initiative that aligns with our commitment to inclusive design and user-centric product development. This improvement not only addresses the needs of a significant user segment but also has the potential to elevate the overall user experience for all riders. I'll approach this challenge by first clarifying our understanding of the current system and user needs, then segmenting our users, analyzing pain points, generating solutions, and finally prioritizing our approach with clear metrics for success.

Step 1

Clarifying Questions

• Looking at Swiftly's position in the market, I'm curious about the current adoption rate among users with accessibility needs. Could you share any data on the percentage of our user base that identifies as having accessibility requirements?

Why it matters: This information will help us understand the scale of the impact and prioritize our efforts. Expected answer: Approximately 15-20% of our users have identified accessibility needs. Impact on approach: A higher percentage would justify more significant resource allocation to this initiative.

• Considering the diverse nature of accessibility needs, I'm wondering about the specific types of disabilities or challenges we're currently addressing. What are the primary categories of accessibility needs we've identified among our users?

Why it matters: Different accessibility needs require different solutions, and understanding the distribution will help us prioritize our efforts. Expected answer: The main categories include visual impairments, hearing impairments, mobility issues, and cognitive disabilities. Impact on approach: This would help us tailor our solutions to the most prevalent needs and ensure we're not overlooking any significant user groups.

• Thinking about our product lifecycle, I'm curious about where we are in terms of our accessibility features. Are we starting from scratch, or do we have existing features that we're looking to improve upon?

Why it matters: This will help us determine whether we need to focus on building new features or optimizing existing ones. Expected answer: We have basic accessibility features in place, but they're not comprehensive or fully integrated. Impact on approach: If we have existing features, we might focus on enhancement and integration rather than building entirely new systems.

• Considering the competitive landscape, I'm interested in understanding how our accessibility features compare to those of our main competitors. Are there any industry benchmarks or best practices we should be aware of?

Why it matters: This will help us set appropriate goals and ensure we're not just meeting but exceeding industry standards. Expected answer: Some competitors have more advanced features, particularly in real-time updates and personalized notifications for accessibility needs. Impact on approach: This would guide us in setting ambitious yet achievable goals for our improvements.