← Back to the problem

The builder's path

Five steps from a problem to its solution.

For: People in Karnataka facing a medical emergency can't tell which ambulance will reach them fastest while the 108 service runs at half strength.

“The unexamined life is not worth living.”

ὁ δὲ ἀνεξέταστος βίος οὐ βιωτὸς ἀνθρώπῳ

Socrates · Plato, Apology 38a

Routes to a solution

Six ways to take this forward

Each route is a different kind of journey, with real people and organisations to contact at each step, starting with those in Karnataka.

  1. Step 1

    Join an impact incubator

    Shape a model that pays for itself without excluding the people who need it.

    • Villgro ↗

      Incubator for social enterprises in health, agriculture and livelihoods.

    • Social Alpha ↗

      Lab-to-market platform for science and technology aimed at social problems.

    • Acumen ↗

      Patient capital and fellowships for enterprises serving low-income communities.

    • Startup India ↗

      The national startup programme: recognition, schemes and a directory of incubators.

  2. Step 2

    Raise patient capital

    Impact funds and fellowships for enterprises serving low-income communities.

    • Villgro ↗

      Incubator for social enterprises in health, agriculture and livelihoods.

    • Social Alpha ↗

      Lab-to-market platform for science and technology aimed at social problems.

    • CIIE.CO (IIM Ahmedabad)

      Incubator and investor at IIM Ahmedabad, with impact programmes.

    • Acumen ↗

      Patient capital and fellowships for enterprises serving low-income communities.

What this problem needs

Ideas, sources and tools for this problem, from first interviews to funding.

  • Open data
  • Maps
  • Voice and phone
  • Mobile

Ideas to explore

  • Idea 1Nearest ambulance by talukA directory of government hospital and registered private ambulances by taluk, each with a direct number and a 'last confirmed working' date, searchable by village name or location.
  • Idea 2Missed-call fallbackA number that, on a missed call, sends back an SMS with the three nearest ambulance numbers for the caller's registered taluk, in Kannada.

Specific to this problem

  • OpenStreetMap ↗

    Open map data that includes many hospital locations, useful to seed a taluk-level directory.

Talk to first

  • Department of Health and Family Welfare, Karnataka

    Runs the taluk hospitals whose ambulances the Minister pointed people to, and is restructuring the 108 service.

  • GVK EMRI

    The agency that operates the 108 service in Karnataka and employs its staff.

  • 108 Ambulance Workers' Union

    Knows where the fleet is short and which districts wait longest.

Starter prompt

Built from this problem's brief. Paste it into Claude or any AI assistant.

Help me design and build a first working prototype for this problem in Bengaluru, Karnataka, India.

Problem: People in Karnataka facing a medical emergency can't tell which ambulance will reach them fastest while the 108 service runs at half strength.
Who it hurts: Families across Karnataka, especially in taluks far from a district hospital, who have always relied on dialling 108 in an emergency.
The moment it hurts: A heart attack, accident or difficult delivery at home, when 108 is slow to answer or the nearest vehicle is an hour away.
What people do today: The State has told people not to depend solely on 108 for two months and to use ambulances at taluk-level government hospitals, but there is no single list of those ambulances or how to call them.
Why it is still unsolved: Taluk hospital ambulances, private ambulances and the 108 fleet are run by different bodies, numbers change hands, and nobody publishes which vehicles are working on a given day.
What solved looks like: A free, Kannada-first lookup by phone and web: enter a village or taluk and get the direct numbers of the nearest working government hospital ambulances and registered private ambulances, with a note of when each was last confirmed, plus a one-tap fallback to 108.
Where: Bengaluru, Karnataka, India

First, list what you would need to learn from the people affected before building, as interview questions.
Then propose the simplest version that would help, the screens or messages it needs, and the data it would use.
Keep it cheap to run, accessible, and respectful of people's privacy. Flag anything you are unsure about instead of guessing.
  1. Understand it

    Talk to the people who live it before you build.

    “The true creator is necessity, which is the mother of our invention.”
    Plato · Republic II, 369c (tr. B. Jowett)
  2. Prototype with AI

    Get a working version in front of people fast.

    Using AI is not cheating. Every tool carries the work of the people who made it, and using it well is how knowledge has always moved forward. The thinking, the care for the people who live the problem, and the judgement are still yours.

    “The Analytical Engine weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves.”
    Ada Lovelace · Notes on Menabrea's Sketch of the Analytical Engine, Note A (1843)
  3. Find the data

    Open data that fits this problem.

    “In the fields of observation chance favours only the prepared mind.”

    Dans les champs de l'observation le hasard ne favorise que les esprits préparés.

    Louis Pasteur · lecture at the University of Lille, 7 December 1854
  4. Build it

    Tools matched to what this problem needs.

    “We are like dwarfs sitting on the shoulders of giants; we see more, and things more distant, not by our own sharp sight but because we are lifted up by their greatness.”
    Bernard of Chartres · as reported by John of Salisbury, Metalogicon III.4 (1159)
  5. Launch and get support

    Ship it responsibly, and find help and funding.

    “While we teach, we learn.”

    Homines dum docent discunt.

    Seneca · Letters to Lucilius 7.8

Kit written for this problem from its brief; every link was checked. Links go to each provider's own site. Zetema is not paid for any listing.