Profile picture of Kartik Jangid
Kartik Jangid
Product Designer | AI SaaS | Productivity | CRM | Automation | Founding Designer | B2B | D2C
Follow me
Generated by linktime
Stay updated
Subscribe to receive my future LinkedIn posts in your mailbox.

By clicking "Subscribe", you agree to receive emails from linktime.co.
You can unsubscribe at any time.

Airbnb's design team noticed something weird in 2019. Hosts were sending 1.5 MILLION photo messages every single week. Not random vacation photos. Not friendly chit-chat. The SAME photos. Over and over. Photos of: • Where to find the key • How to open the tricky door lock • Which buzzer to press • Parking instructions • WiFi router location Hosts were literally photographing check-in instructions and texting them to every single guest. 1.5 million times. Every week. Most companies would've seen this and thought: "Cool, users are engaged with messaging!" Airbnb's UX team saw something else: **Users were building their OWN solution because Airbnb hadn't built one.** Think about it: • If messaging worked perfectly, why are hosts taking photos? • If instructions were clear, why repeat the same info thousands of times? • If the platform supported check-in well, why this workaround? So Airbnb built a dedicated check-in tool: → Visual step-by-step instructions → Photo uploads built into the check-in flow → Standardized format guests could understand instantly → Reduced back-and-forth messaging The real UX lesson? Your users are already designing solutions. You're just not watching. Stop asking "what features do you want?" Start watching what people are ACTUALLY doing with your product. When you see the same workaround repeated thousands of times, that's not user behavior. That's a missing feature screaming at you. The best product insights don't come from surveys. They come from observing what your users build when you're not looking. #UXDesign #ProductManagement #Airbnb #UserBehavior #ProductStrategy
0 comments
November 24, 2025
Spotify had a problem. They built a new feature powered by machine learning. It would show users their current favorite songs and playlists on the Home tab. Simple concept. But nobody could agree on what to NAME it. So they did what every tech company does: A/B testing. Test 1: Failed. Inconclusive. Test 2: Failed. Inconclusive. Test 3: Still nothing. The data couldn't tell them which name users preferred. Here's where most teams give up or just pick randomly. Spotify's UX research team tried something different: → Stopped looking at numbers → Started talking to actual humans → Asked people how they FELT about different options → Noticed something: users lit up when they saw personalized greetings like "Good Morning!" They weren't responding to the NAME of the feature. They were responding to feeling SEEN by the app. Final decision? They added personalized time-based greetings throughout the interface. The lesson here is simple but brutal: Data shows you WHAT is happening. Conversations show you WHY it matters. Most designers worship A/B tests like gospel. But numbers can't capture emotion, context, or the "why" behind user behavior. You need both: • Quantitative data for patterns • Qualitative research for meaning Stop treating user research like a checkbox. Start treating it like a conversation. Because sometimes the answer isn't in your analytics dashboard. It's in the words your users choose when they talk about your product. #UXDesign #UserResearch #ProductDesign #Spotify #DataVsIntuition
0 comments
November 25, 2025
2009. Airbnb was broke. They had a website. They had listings. They had an idea. What they didn't have? Bookings. The founders were confused. The concept was solid. The tech worked. Why weren't people booking? They started looking at the listings more carefully. Then they saw it: The photos were TERRIBLE. Dark, blurry, unflattering. Taken with 2009 flip phones. Bad angles. Poor lighting. Some listings didn't even have photos. Here's the thing about booking a stranger's home: **You're not buying a room. You're buying TRUST.** And grainy photos = zero trust. Most founders would've: • Built a photo filter feature • Added an AI enhancement tool • Written better copy • Blamed the hosts Brian Chesky and Joe Gebbia did something insane: → Flew to New York → Rented a $5,000 camera → Went door-to-door photographing listings THEMSELVES Revenue in those listings DOUBLED overnight. Not 10% better. Not 20% better. DOUBLED. They realized: this isn't a tech problem. This is a TRUST problem. So they scaled it: → Hired professional photographers → Offered FREE photoshoots to hosts worldwide → Made professional photography a standard, not a luxury Results? • 2-3x increase in bookings for professionally photographed listings • Became a core part of Airbnb's trust strategy • Changed how the entire vacation rental industry thinks about photos The brutal truth about UX: **Sometimes the solution isn't in your app. It's in the real world.** You can't A/B test your way out of a fundamental trust problem. You can't "iterate" your way to trustworthy photos. Sometimes you need to get off Figma, step away from the laptop, and go meet your actual users. That's where real insights live. #UXDesign #StartupLessons #Airbnb #ProductStrategy #DesignThinking
0 comments
November 26, 2025