03 · Whimsicals and Mind Maps (your original wording)

info · Transcribed from your three whimsical images (Madam_otp__2x.png, Screenshot_2026-09-10_at_8_35_20_PM.png, Screenshot_2026-09-21_at_6_06_39_PM.png). Every node is kept exactly as you wrote it, including spellings. The Mermaid blocks are only a way to render the same tree in Obsidian.

Map A · "OTP" (first mind map, upper half)

Tree (verbatim nodes)

OTP (root)
first principles
- metric for finished delivery to the right person
- prevents against fraud
OTP
- Touch points1
- when the order is out for delivery the otp is shared on WA
  - multiple orders → a stack of delivery OTPs and not neccesarily in the numerical order of the deliveries
  - single order → 1 otp is shared
- touchpoint 2
- when you reciever collects the parcel from the delivery agent
buyer is not the receiver
- insight → "Over many calls, we realize that the buyer is not the one who receives the order. It's usually his friends who are available at that time, or his mom and dad, who are not that well-versed in technology, or anyone else who accepts the order but does not really have the OTP necessary for collecting the order."
- "Usually, the buyer is pretty busy during this time."
location issue
- insight
- delivery parter are usually local people of the area and they know many places by memory
- there are 15% of the time when they don't know the location of the buyer( link to gmap to the delivery adress)
- 30% of addresses are properly structured. the other are no so accurate.
refund issue
- insight
- people have money problems, if their refund is due then their cashflow is stuck and hence it becomes hard for them to issue a new order
- multiple chat bot interaction and if your complaint is not inn synch with the actual product complaint/ return policy then there is a mismatch.
lots of these conversation happen over wa. those who don't have WA face a lot of problem

mindmap
  root((OTP))
    first principles
      metric for finished delivery to the right person
      prevents against fraud
    OTP
      Touch points1
        when the order is out for delivery the otp is shared on WA
          multiple orders
            a stack of delivery OTPs and not neccesarily in the numerical order of the deliveries
          single order
            1 otp is shared
      touchpoint 2
        when you reciever collects the parcel from the delivery agent
    buyer is not the receiver
      insight
        buyer is not the one who receives the order - friends, mom and dad, anyone else without the OTP
        Usually the buyer is pretty busy during this time
    location issue
      insight
        delivery parter are usually local people of the area and they know many places by memory
        15% of the time they don't know the location of the buyer
        30% of addresses are properly structured. the other are no so accurate
    refund issue
      insight
        refund due means cashflow stuck, hard to issue a new order
        multiple chat bot interaction, complaint not in synch with return policy = mismatch
    lots of these conversation happen over wa. those who don't have WA face a lot of problem

Map B · "questions" (first mind map, lower half)

questions (root)
Who is this team, and why is this opening yours?
The one customer insight you discovered.
how ur agent works in 6steps → What triggers it / What it already knows. / What it does. / Who it deals with, person or institution. / What it asks its human, and when. / How it knows it's done
how your solution touches each rails
which rail will you innovate on
which customer asset will you ask for
which use case do you subsume next
which of the sixteen openings would you never hand to an assistant?
Which Indian company should have built this already?
Which track are you entering?

Map C · "The one customer insight you discovered." (insight mind map)

The one customer insight you discovered.
delivery riders are frustrated
- location not accurate
- otp issue - delivery people waste time and their OKRs are not empathetic to that but the penality is just 5 ruppes for every missed order
delivery people are local to a certain area so that mostly no a good amount of places via their memory
10-15% of the time location is not shown - 2 out of 3 delivery agents told so

mindmap
  root((The one customer insight you discovered.))
    delivery riders are frustrated
      location not accurate
      otp issue - delivery people waste time and their OKRs are not empathetic to that but the penality is just 5 ruppes for every missed order
    delivery people are local to a certain area so that mostly no a good amount of places via their memory
    10-15% of the time location is not shown - 2 out of 3 delivery agents told so

Map D · "madam otp" (second mind map: delivery agent, refunds and pickup, otp)

Branch 1 · delivery agent

use case
buyer is extremely busy and (less tech savy)parents/ maid is picking up the order
a security guy is picking up the order
india has a system of sharing many accounts among each other so a friend is ordering on a different account
multiple orders and OTP becomes a search task
leave at the door/ gate/ security - call the person
- either buyer is super busy
- or buyer picks up the call
return pickups
- another person is giving the return order
- the return is kept outside the house
delivery location of the house is not clear - tech and location issue
buyer is not the reciever and also unreachable
buyer has not exact data points about the delivery
exact ETA
for multiple orders juggling between multiple otp is also irritating
fear of fraud if the item is stolen on prepaid delivery
on COD orders how to then receive up the order if the buyer is both unreachable and not the receiver
delivery agent has incentives to max the amount of orders per day and the penalty fees is just rupees 5 for each other unsuccessful order
DA sometimes don't come and delivery the order
- delivery address is not known
- has some personal important task
- would prefer already known places > unkown places

Branch 2 · refunds and pickup

in india people find it intimidating to search and raise refunds and talk to chat bots etc
if the refund ticket is of the wrong type then the entire process is delayed even further
lets say a grey color blanket was ordered which was supposed to be black and also the material was uncomfortable. the user raise a refund on the material part but the delivery agent refused to take the order since the color of the actual product and the color of the blanket from the user were different
cash flow problems if the return is delayed
return seems like a info and data mismatch and too many chatbot interaction problem
return policy of the product
how to raise the correct ticket
what are the steps to be taken for the return

Branch 3 · otp

OTP is shared during the time of delivery - DA schedules it instantly
OTP is shared 4-5hrs before the agent reaches

mindmap
  root((madam otp))
    delivery agent
      use case
        buyer is extremely busy and less tech savy parents or maid is picking up the order
        a security guy is picking up the order
        india has a system of sharing many accounts among each other so a friend is ordering on a different account
        multiple orders and OTP becomes a search task
        leave at the door or gate or security - call the person
          either buyer is super busy
          or buyer picks up the call
        return pickups
          another person is giving the return order
          the return is kept outside the house
        delivery location of the house is not clear - tech and location issue
      buyer is not the reciever and also unreachable
      buyer has not exact data points about the delivery
        exact ETA
        for multiple orders juggling between multiple otp is also irritating
      fear of fraud if the item is stolen on prepaid delivery
      on COD orders how to then receive up the order if the buyer is both unreachable and not the receiver
      delivery agent has incentives to max the amount of orders per day and the penalty fees is just rupees 5 for each other unsuccessful order
        DA sometimes don't come and delivery the order
          delivery address is not known
          has some personal important task
          would prefer already known places > unkown places
    refunds and pickup
      in india people find it intimidating to search and raise refunds and talk to chat bots etc
      if the refund ticket is of the wrong type then the entire process is delayed even further
        grey blanket ordered instead of black, refund raised on material, delivery agent refused the pickup because the colours differed
      cash flow problems if the return is delayed
      return seems like a info and data mismatch and too many chatbot interaction problem
        return policy of the product
        how to raise the correct ticket
        what are the steps to be taken for the return
    otp
      OTP is shared during the time of delivery - DA schedules it instantly
      OTP is shared 4-5hrs before the agent reaches

Back to 00 README Index