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