Sachin Patalasingh

Juggling Brain and MRI @BrainSightAI.
Neuroimaging, Python and Everything in between.

[Sachin Patalasingh @fMRI_boy]

@khaileidoscope_ Sobrang pagod

[Sachin Patalasingh @fMRI_boy]

@wordisbonz Ummm I am not even close 🤣🤣

https://t.co/8VnDDD8npv

[Sachin Patalasingh @fMRI_boy]

@5harath @_nightsweekends Here you go

[Sachin Patalasingh @fMRI_boy]

Me during the next 6 weeks of Nights and Weekends! Excited af 😎😎

@_buildspace @_nightsweekends

[Sachin Patalasingh @fMRI_boy]

@codingmickey @_nightsweekends Congratulations @codingmickey. See you in s5.

[Sachin Patalasingh @fMRI_boy]

@_aamnakhan @MotwaniSuhas Thanks a lot Secret Santa! I have to give credit to you for your awesome taste in murder mysteries. Have started reading it already.
PS. If you sent this, please do send me a DM. I have to take book recommendations from you 😅 #BookSecretSanta

[Sachin Patalasingh @fMRI_boy]

A classic example of what PMF research looks like. The amount of work and research that goes into being a customer obsessed team is insane.

[Elizabeth Laraki @elizlaraki]

In 2008, Google Maps launched in India.

But we quickly ran into a problem:

Nobody used street names.

And street names were the foundation of Google Maps.

The team had to make some big adaptations.

15 years later, the changes have stood the test of time.

Here's how the team came up with creative solutions to adapt Google Maps to work in India:

–––

When Google Maps launched in India, turn by turn directions were unusable.

Because there were no road names, directions looked like this:

This was before real time, accurate GPS in phones had become mainstream.

In short, directions were pretty much useless in India.

–––

We could have left the product as it was.

We could have assumed it was good enough, would get better over time, or that eventually people would adapt.

But India was a massive potential market and we wanted the product to thrive.

The solution wasn’t just a case of acquiring and cataloging street names.

Many streets either didn’t have names, had multiple names, or weren’t known by their official names.

So we had to find an alternative.

We already knew that many communities around the world relied on landmarks (rather than street names) for navigating.

e.g. “Turn left at the park, head towards the water”

We knew this was also true in India.

But we had to confirm landmark based navigation would work.

And if it did, how we could make it work.

–––

So we dove in.

We started to explore how Google Maps could work if it oriented around landmarks.

But we needed to understand 2 key questions:

1. How did people use landmarks to navigate in India?

2. What types of landmarks were good for navigating?

This is where user research came in.

At the time, Google had robust support for user research.

There were research labs on campus with eye tracking technology and one-way mirrors.

There was a team dedicated to recruiting research participants.

But in this case, my friend and researcher extraordinaire, Olga (@okhroust) simply focused on how she could best answer these key questions.

She put together a creative and scrappy research plan.

And then she and Janet, the designer, hopped on a plane to India.

–––

What followed was nimble, on the ground field research to understand, first-hand, the answers to these questions.

They creatively explored various approaches including:

• Calling businesses and asking them for directions to their stores

• Asking people to draw diagrams of routes to familiar places

• Following people around as they navigated unfamiliar places

• Recruiting people to keep track of directions they gave or received + later interviewing them on their experiences

• Sharing early designs of landmark based directions and asking for feedback

Rather than relying on sophisticated technologies or being bounded by formal research methods, they creatively tried several different tactics to understand how locals navigated their way through India.

Olga and Janet found that people used landmarks to navigate in a few key ways:

• Orientation: “Head towards the water”

• Description of a turn: “Turn just past the Big Bazaar”

• Confirmation of the right path: “You'll see a petrol station on the right”

• Error correction: “If you get to the roundabout, you've gone too far”

Landmarks that were used for navigating included parks, monuments, shopping centers, notable buildings, stores, petrol stations, roundabouts, etc — basically anything that anyone would notice while on the road.

And so the team reworked turn-by-turn street directions to include navigational landmarks to help orient people, signal turns, confirm direction, and error correct.

The team worked through several iterations before landing on a final solution that emphasized landmarks, but also subtly included road names (when available):

–––

The research drove the product changes that helped transform Google Maps into the dominant navigational product for India.

A lot has changed in the last 15 years with the pervasiveness of location-enabled mobile phones, cheap mobile data, and generally how locals navigate in India.

But the use of landmarks to help people navigate through India has stood the test of time.

–––

What I love about this story and my 2 biggest takeaways are:

1. Research is a critical tool for ensuring you’re building a good product

2. Research can be as simple as just talking to people to answer your questions

tl;dr: If you are looking for answers, go talk to people.

For more on design + tips for early stage founders, follow @elizlaraki

[Sachin Patalasingh @fMRI_boy]

Normallly, Not Normal.

[Rob @thegallowboob]

Just found out they give live fish CT scans by placing them on a wet sponge and I can’t stop thinking about it

[Gašper Beguš @begusgasper]

IIT stands for Indian Institute of Technology btw

[Sachin Patalasingh @fMRI_boy]

I choose violence, everytime. Each and every time. And I dont look back. 😈

[GitHub Projects Community @GithubProjects]

There are only two types of dev, which one are you? 😅

[Sachin Patalasingh @fMRI_boy]

The OG promptmaster and ChatGPT.
#beyblade #ChatGPT

[🧬Kylee J. Veazey, Ph.D.🧬 @DrKVeazey]

My husband told me I talk about epigenetics too much…

I told him I didn’t like histone

[ETtech @ETtech]

@udaykotak @skirani @deepigoyal @_Kalyan_K @harshilmathur @satyan @arjunsethi @fyers1 @BoultAudio @KlentyHQ @GameberryHQ @leddzy @PraveenAnanthu @_afsaar ET Startup Awards 2023: Nominees for Top Innovator

■ @StringBio
■ Zero Cow Factory
■ @GalaxEye
■ @BrainSightAI
■ @newtracetech

Read more at:
https://t.co/TeXbxhJbvr

#ETStartupAwards2023

[Chelsea Parlett @ChelseaParlett]

taking the derivative of f(x,y) with disrespect to x

[Rebecca Saxe @rebecca_saxe]

We are sharing an open dataset of >300 children, 3–12-years-old, including 64 (neurotypical) children assessed longitudinally and 68 autistic children, each answering >40 ToM questions ranging in difficulty.

10 years of @hil_richardson's and Saxelab's data! Please re-use.