How might we assist deafblind runners to navigate?

Shreyas Prakash headshot

Shreyas Prakash

Equarun is used to help deafblind people (especially those suffering from Usher Syndrome, a progressive disorder affecting more than 400,000 people worldwide) and their guides engage in safe and comfortable long-distance running.

This device is capable of transmitting complex instructions on road conditions, striking a good balance between freedom and safety.

Equarun being used across running tracks, crowded public spaces and even outdoor tracks within forests.

Roles and responsibilities

As a design engineer and project manager, I was responsible for two main roles:

  1. To conduct design tests in the form of weekly agile sprints to unravel insights from a very sensitive user group—  deaf-blind runners
  2. Translate research insights into product requirements and eventually, embodiment design improvements. I was also responsible for designing the embedded system including the haptic system (PCB)
  3. Managing tight timelines to go from concept-to-launch within 6 months from product discovery to pilots with end users. Led 12+ Design Tests to resolve usability issues and designed the electronics architecture
  4. Paper publication at the International Conference on Engineering and Product Design Education, Denmark

Usher Syndrome affects nearly 10,000 people worldwide in the form of acquired deaf-blindness. Imagine losing your senses gradually.

How would that feel? For some of the Ushers, their vision gets clouded similar to the gradient I have overlayed on top of this image.

​Running is often suggested as a form of therapy to allow the Ushers to cope with the anxiety and stress of losing their senses.

But how do they run across forests, race tracks or even marathons with ease?

A robust, intuitive device to support deaf-blind runners with safe, long distance running

Equarun consists of a haptic actuator system that allows communicating the terrain information allowing the runners to run across race tracks, forests and crowded spaces.

The embodiment is designed in such a way it doesn’t affect the running gait (posture) of both the runners.

With the principle of ‘As less design as possible’, we didn’t overpopulated the interface with too many buttons.

All the essential instructions for navigation was easy to follow with the physical structure and some advanced commands were communicated by means of haptics.

If you notice up close, the ‘Empathise’ stage in the standard design cycle didn’t come upfront. That was because empathizing was not just a stage in the process but was cultivated throughout the process of iteration and product development.

Over six months, we followed the methodology of action research to get weekly insights from the runners through a series of design sprints. These knowledge loops were lead by empathy.

User personas were detailed. How does a day in the life of a buddy or the Usher look like? Currently the buddies use a cotton strap to provide commands to the ushers.

Ideation

After analysing the pain points, a variety of concepts for assisted running were explored.

After selecting one of the concepts based on the program of criteria, certain micro, macro and meta experiences were charted out to help define the product experience better.

In this way, the form and the function went hand in hand in the final selection of the concepts.

Running gait analysis was conducted among 15 participants to influence the impact of the device on the foot landing, the knee window and the arm flexion. Concepts were shortlisted based on findings.

Primarily as a sports device, the material and the structure had to be robust. FEA analysis was conducted to ensure that the product withstands push/pull.

The instructions had to be intuitive for the deafblind runners to understand and navigate. Ergonomic analysis of the position of buttons and usability tests were conducted to shortlist haptics

While running long distances, comfort is key and an ergonomic evaluation using (System Usability Scale) was performed to select the size, material and thickness of the handle.

Action research and testing

In order to understand if there has been any improvement in the accuracy rate and reaction time of participants while using the device, a comparative test was carried out with various structures.

30 deaf and blind runners along with their guides participated in these design tests. To get qualitative insights from the deafblind runners, a translator helped us understand how they experienced using the device. Along with this, the quantitative results proved the effectiveness of the final device.

Designing a haptic language for running

A validation study was done with 3 blind runners as participants. This was used to finalize the waveforms for the commands that indicate ‘Surface change’ and the ‘Counting down’ option.

A general questionnaire was made to gather general data about the intuitiveness of the haptics on keywords such as ‘stop, pause, follow etc’.

This was then used to shortlist waveforms to be tested by the deafblind participants.

Improvement through iteration

The following iteration map showcases the evolution of the product and its transition from a cotton strap.

a, b, c and d were different structural configurations tested.

e, f, g and h were various embodiment improvements made. i, j and k ere various adjustments to include more comfort to the runners.

The electronics architecture designed evolved from a simple Arduino nano prototype to a neatly fitting PCB snug-fitting into the housing of the handle. Apart from this, several iterations were made to minimise inter-wiring operations reducing the error rate.

For the first batch of 40 units, as per the client requirements, an assembly instruction diagram was created. The design was optimised according to standard parcel dimensions for shipping to bring the cost down to 210 euros.

Apart from the product development, I also spread awareness on improving the safety of running to a group of 150 Ushers from the Netherlands.

I also participated in marathons and became more closer to this community through the design process.

On reflection, I realised that advocacy was as important as the design itself to launch a product into the market.

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct-management
  2. How I started building softwares with AI agents being non technicalagentic-engineering
  3. Legible and illegible tasks in organisationsproduct
  4. L2 Fat marker sketchesdesign
  5. Writing as moats for humanswriting
  6. Beauty of second degree probesdecision-making
  7. Read raw transcriptsknowledge
  8. Boundary objects as the new prototypesprototyping
  9. One way door decisionsproduct
  10. Finished softwares should existproduct
  11. Essay Quality Rankerobsidian
  12. Export LLM conversations as snippetsbrowser-extension
  13. Flipping questions on its headinterviewing
  14. Vibe writing maximswriting
  15. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  16. How I build greenfield apps with AI-assisted codingai-coding
  17. We have been scammed by the Gaussian distribution clubmathematics
  18. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  19. I was wrong about optimal stoppingmathematics
  20. Thinking like a ship
  21. Hyperpersonalised N=1 learningeducation
  22. New mediums for humans to complement superintelligenceai-coding
  23. Maxims for AI assisted codingai-coding
  24. Personal Website Starter Kitai-coding
  25. Virtual bookshelvesaesthetics
  26. It's computational and AI everythingai-coding
  27. Public gardens, secret routesdigital-garden
  28. Git way of learning to codeai-coding
  29. Kaomoji generatorsoftware
  30. Copy, Paste and Citecuriosities
  31. Style Transfer in AI writingai-coding
  32. Understanding codebases without using codeai-coding
  33. Vibe coding with Cursorai-coding
  34. Virtuoso Guide for Personal Memory Systemsmemory
  35. Writing in Future Pastwriting
  36. Publish Originally, Syndicate Elsewhereblogging
  37. Poetic License of Designdesign
  38. Idea in the shower, testing before breakfastsoftware
  39. Technology and regulation have a dance of ice and firetechnology
  40. How I ship "stuff"software
  41. Weekly TODO List on CLIcli
  42. Writing is thinkingwriting
  43. Song of Shapes, Words and Pathscreativity
  44. How do we absorb ideas better?knowledge
  45. Read writers who operatewriting
  46. Brew your ideas lazilyideas
  47. Vibescreativity
  48. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  49. Compound Interest of Private Notesknowledge
  50. Conceptual Compression for LLMsai-coding
  51. Meta-analysis for contradictory research findingsdigital-health
  52. Beauty of Zettelswriting
  53. Proof of workproduct
  54. Gauging previous work of new joinees to the teamleadership
  55. Task management for product managersproduct
  56. Stitching React and Rails togetherai-coding
  57. Exploring "smart connections" for note takingknowledge
  58. Deploying Home Cooked Apps with Railssoftware
  59. Self Marketing
  60. Repetitive Copypromptingwriting
  61. Questions to ask every decadejournalling
  62. Balancing work, time and focusproductivity
  63. Hyperlinks are like cashew nutswriting
  64. Brand treatments, Design Systems, Vibesdesign
  65. How to spot human writing on the internet?writing
  66. Can a thought be an algorithm?product
  67. Opportunity Harvestingcareers
  68. How does AI affect UI?design
  69. Everything is a prioritisation problemproduct-management
  70. Nowlifestyle
  71. How I do product roastsproduct
  72. The Modern Startup Stacksoftware
  73. In-person vision transmissionproduct
  74. How might we help children invent for social good?social-design
  75. The meeting before the meetingmeetings
  76. Design that's so bad it's actually gooddesign
  77. Breaking the fourth wall of an interviewinterviewing
  78. Obsessing over personal websitessoftware
  79. Convert v0.dev React to Rails ViewComponentsrails
  80. English is the hot new programming languagesoftware
  81. Better way to think about conflictsconflict-management
  82. The role of taste in building productsdesign
  83. World's most ancient public health problemsoftware
  84. Dear enterprises, we're tired of your subscriptionssoftware
  85. Products need not be user centereddesign
  86. Pluginisation of Modern Softwaredesign
  87. Let's make every work 'strategic'consulting
  88. Making Nielsen's heuristics more digestibledesign
  89. Startups are a fertile ground for risk takingentrepreneurship
  90. Insights are not just a salad of factsdesign
  91. Minimum Lovable Productproduct
  92. Methods are lifejackets not straight jacketsmethodology
  93. How to arrive at on-brand colours?design
  94. Minto principle for writing memoswriting
  95. Importance of Whytask-management
  96. Quality Ideas Trump Executionsoftware
  97. How to hire a personal doctor
  98. Why I prefer indie softwareslifestyle
  99. Use code only if no code failscode
  100. Personal Observation Techniquesdesign
  101. Design is a confusing worddesign
  102. A Primer to Service Design Blueprintsdesign
  103. Rapid Journey Prototypingdesign
  104. Directory Structure Visualizercli
  105. AI git commitscli
  106. Do's and Don'ts of User Researchdesign
  107. Design Manifestodesign
  108. Complex project management for productproducts
  109. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  110. Pedagogy of the Uncharted — What for, and Where to?education
  111. Future of Ageing with Mehdi Yacoubiinterviewing
  112. Future of Equity with Ludovick Petersinterviewing
  113. Future of Mental Health with Kavya Raointerviewing
  114. Future of Tacit knowledge with Celeste Volpiinterviewing
  115. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  116. Future of unschooling with Che Vanniinterviewing
  117. Future of work with Laetitia Vitaudinterviewing
  118. How might we prevent acquired infections in hospitals?digital-health
  119. The soul searching yearsentrepreneurship
  120. Design education amidst social tribulationsdesign
  121. How might we assist deafblind runners to navigate?social-design