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

2026

  1. How I started building softwares with AI agents being non technical

2025

  1. Legible and illegible tasks in organisations
  2. L2 Fat marker sketches
  3. Writing as moats for humans
  4. Beauty of second degree probes
  5. Read raw transcripts
  6. Boundary objects as the new prototypes
  7. One way door decisions
  8. Finished softwares should exist
  9. Essay Quality Ranker
  10. Export LLM conversations as snippets
  11. Flipping questions on its head
  12. Vibe writing maxims
  13. How I blog with Obsidian, Cloudflare, AstroJS, Github
  14. How I build greenfield apps with AI-assisted coding
  15. We have been scammed by the Gaussian distribution club
  16. Classify incentive problems into stag hunts, and prisoners dilemmas
  17. I was wrong about optimal stopping
  18. Thinking like a ship
  19. Hyperpersonalised N=1 learning
  20. New mediums for humans to complement superintelligence
  21. Maxims for AI assisted coding
  22. Personal Website Starter Kit
  23. Virtual bookshelves
  24. It's computational everything
  25. Public gardens, secret routes
  26. Git way of learning to code
  27. Kaomoji generator
  28. Style Transfer in AI writing
  29. Copy, Paste and Cite
  30. Understanding codebases without using code
  31. Vibe coding with Cursor
  32. Virtuoso Guide for Personal Memory Systems
  33. Writing in Future Past
  34. Publish Originally, Syndicate Elsewhere
  35. Poetic License of Design
  36. Idea in the shower, testing before breakfast
  37. Technology and regulation have a dance of ice and fire
  38. How I ship "stuff"
  39. Weekly TODO List on CLI
  40. Writing is thinking
  41. Song of Shapes, Words and Paths
  42. How do we absorb ideas better?

2024

  1. Read writers who operate
  2. Brew your ideas lazily
  3. Vibes
  4. Trees, Branches, Twigs and Leaves — Mental Models for Writing
  5. Compound Interest of Private Notes
  6. Conceptual Compression for LLMs
  7. Meta-analysis for contradictory research findings
  8. Beauty of Zettels
  9. Proof of work
  10. Gauging previous work of new joinees to the team
  11. Task management for product managers
  12. Stitching React and Rails together
  13. Exploring "smart connections" for note taking
  14. Deploying Home Cooked Apps with Rails
  15. Self Marketing
  16. Repetitive Copyprompting
  17. Questions to ask every decade
  18. Balancing work, time and focus
  19. Hyperlinks are like cashew nuts
  20. Brand treatments, Design Systems, Vibes
  21. How to spot human writing on the internet?
  22. Can a thought be an algorithm?
  23. Opportunity Harvesting
  24. How does AI affect UI?
  25. Everything is a prioritisation problem
  26. Now
  27. How I do product roasts
  28. The Modern Startup Stack
  29. In-person vision transmission
  30. How might we help children invent for social good?
  31. The meeting before the meeting
  32. Design that's so bad it's actually good
  33. Breaking the fourth wall of an interview
  34. Obsessing over personal websites
  35. Convert v0.dev React to Rails ViewComponents
  36. English is the hot new programming language
  37. Better way to think about conflicts
  38. The role of taste in building products
  39. World's most ancient public health problem
  40. Dear enterprises, we're tired of your subscriptions
  41. Products need not be user centered
  42. Pluginisation of Modern Software
  43. Let's make every work 'strategic'
  44. Making Nielsen's heuristics more digestible
  45. Startups are a fertile ground for risk taking
  46. Insights are not just a salad of facts
  47. Minimum Lovable Product

2023

  1. Methods are lifejackets not straight jackets
  2. How to arrive at on-brand colours?
  3. Minto principle for writing memos
  4. Importance of Why
  5. Quality Ideas Trump Execution
  6. How to hire a personal doctor
  7. Why I prefer indie softwares
  8. Use code only if no code fails
  9. Personal Observation Techniques
  10. Design is a confusing word
  11. A Primer to Service Design Blueprints
  12. Rapid Journey Prototyping
  13. Directory Structure Visualizer
  14. AI git commits
  15. Do's and Don'ts of User Research
  16. Design Manifesto
  17. Complex project management for product

2022

  1. How might we enable patients and caregivers to overcome preventable health conditions?
  2. Pedagogy of the Uncharted — What for, and Where to?

2020

  1. Future of Ageing with Mehdi Yacoubi
  2. Future of Equity with Ludovick Peters
  3. Future of Tacit knowledge with Celeste Volpi
  4. Future of Mental Health with Kavya Rao
  5. Future of Rural Innovation with Thabiso Blak Mashaba
  6. Future of unschooling with Che Vanni
  7. Future of work with Laetitia Vitaud
  8. How might we prevent acquired infections in hospitals?

2019

  1. The soul searching years
  2. Design education amidst social tribulations
  3. How might we assist deafblind runners to navigate?