That's the interesting problem behind @zomato's “Think it, Search it” experience.
User has a need → Expresses intent → Product interprets it → Options → Decision
Is “Think it, Search it” really Search? Or is it actually Discovery / Decision Support disguised as Search?
I am exploring Zomato’s “Think it, Search it” as a shift from classic keyword search to an intent‑driven discovery and decision‑support experience.
- Traditional flow: User knows → Keyword → Search → Results
I decided to treat “Think it, Search it” as a discovery/decision‑support feature rather than pure search because the product must help users figure out what fits their situation.
- 📊 Search‑to‑result engagement
I will run A/B tests comparing this intent flow against the baseline keyword search to decide which metrics improve.
- 📊 Recommendation → order conversion
- 📊 Time to decision
- 📊 Search refinement rate
- 📊 Repeat usage
- 📊 Customer satisfaction
- Intent‑based flow: User has a need → Expresses intent → Product interprets it → Options → Decision