Vishal Gupta (@visualbit) profile picture

Founding Team, Head of Design | AI × UX Strategist | Scaling Product Design with Systems Thinking | ex-Dunzo, ex-Instamojo | CUA™

Bengaluru, India
Joined November 2009
I was trying to watch a movie called “The Invite” however there is no movie on Z5. Just the trailer. 😢 Perhaps someone is doing chain smoking or someone’s cat 🐈‍⬛ sat on keyboard and deleted the whole movie. 😅 @ZEE5India @PicturesPVR
50
Haha #claude 🤦🤭😀
13
Replying to @AmazonHelp
finally it loaded and this is what is happening. how can you ask for a physical invoice for an Amazon Now order. It never comes with the order. Never.
1
16
Replying to @AmazonHelp
Also, that link is not loading. It just keep doing this.
1
16
Replying to @captureone
@captureone I am not able to activate, I am seeing this. Could you please help.
7
Someone stopped a conversation mid-sentence and asked: "What is the box?" We had just said "think outside the box." And nobody could answer. We had been using that phrase for years without ever interrogating what it actually asked of people. A few days later I tried something smaller with my team. Two words instead. "What if." The room changed. Wrote about why it works, where it breaks, and what it does to people over time. Here is the full read: medium.com/@visualbyte/what-… #ProductDesign #DesignThinking #UXDesign #thethinkinglayer #tangibleux
11
Which one is right? @perplexity_ai @Google I see Perplexity is showing a big peak around November end. Very unreliable 👀
16
Don't know what to say...
8
Candour = Design for Humans Two decades in product rooms has taught me this: Teams rarely fail because of lack of talent. They fail because of lack of candour. I’ve seen it across companies: → Teams almost ship redesigns that everyone knows are clunky—until someone finally speaks up. → Engineers stay quiet on scale issues until late in the cycle—by then, weeks are already lost. → PMs push features no one truly believes in—because saying “let’s not build this” feels unsafe. When candour is absent, teams perform theatre. Polished decks. Polite nods. “Alignment.” But under the surface, fractures grow. When candour is present, the game changes. Tough truths surface early. The real debates happen in the room, not after launch. Velocity compounds—not because teams move faster, but because they move clearer. Candour feels risky in the moment. But the absence of candour is far more expensive: → Bad UX slips through. → Months of effort vanish. → Teams burn out solving problems they saw coming. Candour is not confrontation—it’s care. It says: I value the work enough to challenge it. I respect you enough to be direct. Empathy makes products lovable. Candour makes them buildable. Both are design for humans. #ProductDesign #DesignLeadership #ProductManagement #TeamCulture #Leadership #TeamCulture
15
When a menu doesn’t open where you click, you pay a tax—every single time. TL;DR Windows 11’s centered Start menu improves visibility on ultra-wide screens and keeps parity across inputs, but it breaks two workhorse principles—Fitts’s Law and muscle memory—for mouse users. Anchor matters more than aesthetics. What the change gets right ✓ Center-field visibility: On big monitors, middle-of-screen UI is easier to notice than a far-corner target. ✓ Input consistency: A single, centered panel feels uniform across mouse, touch, pen, and Win-key habits. Where it regresses ⨉ Trigger → Outcome gap: The menu opens away from the button you pressed, adding refocus + pointer travel. ⨉ Lost “infinite” target: Corners let you slam the cursor without precision; a floating icon removes that advantage. ⨉ Moving targets kill skill: Centered taskbars shift with app count, so Start’s position—and your motor memory—drifts. Design principles to steal for your product → Anchor to invocation. Menus should appear adjacent to their trigger (or where the pointer is) to minimize travel. → Prefer fixed coordinates for primary controls. Stability breeds speed. → Input-adaptive placement. • Mouse: edge-anchored menus (+ bumper effect). • Touch: near-thumb zones; edges aren’t faster for fingers. • Keyboard: center overlay is fine—focus the search field immediately. → Context-adaptive rules. If invoked by pointer → open near pointer; by keyboard → center; by touch → thumb zone. → Offer a “classic” option. Power users will choose predictability; don’t make them install third-party fixes. How I’d measure it → Time-to-first-selection → Pointer travel distance (px) → Mis-click rate / corrections → Repeat-use speedup (does motor memory form?) Bottom line Modern is good. Predictable is better. If you’re shipping a redesign, keep the novelty—but don’t upend the anchors users rely on daily. #UXDesign #ProductDesign #InteractionDesign #HCI #Usability #DesignSystems #Windows11 #FittsLaw #DesignCritique @tangibleux
25
🌀 The Jalebi Loop of Design In ancient Egyptian and Greek mythology, there’s a symbol called the Ouroboros — a serpent eating its own tail. It represents cycles without end: creation and destruction, life and death, infinite repetition. Design has its own Ouroboros. Only, for me, it doesn’t look like a snake. It looks like a Jalebi. 🍭 Attractive on the outside. Sweet in effort. But once you’re inside, it’s sticky, tangled, and never-ending. That’s what happens when we get stuck in iteration loops: → One option leads back to another. →Tiny tweaks masquerade as progress. Weeks go by, but decisions don’t get made. → A Jalebi has no clear beginning or end — and neither do these cycles. How to escape the Jalebi loop: → Anchor to the problem. Write down what you’re solving before you open Figma. → Time-box iteration. Creativity needs boundaries; endless exploration isn’t progress. → Look for real signals. User feedback breaks loops faster than another internal debate. → Close the loop. Document decisions clearly so the team doesn’t spiral back. Iteration is vital in design. But iteration without direction is just self-consuming. It’s Jalebi — the desi Ouroboros. 👉 Closing thought: Good design isn’t about circling forever. It’s about knowing when to close the loop and move forward. #UXDesign #ProductDesign #DesignLeadership #DesignProcess #Iteration #DesignMetaphors #StorytellingInDesign #DesignMetaphors #DesignThinking
27
🍬Melody khao, khud jaan jao — The Only UX Rule That Always Works In UX, we often say “be in the user’s shoes.” But too often, we try those shoes on while sitting at our desks. Parle’s old Melody campaign nails it better: “Melody khao, khud jaan jao” — experience it yourself. For me, as a product design leader, it means: Walk the exact path your user walks Use the same devices, constraints, and frustrations Don’t just imagine their journey — live it The MELODY Playbook A quick way to make this mindset part of your work: M — Map the full journey, including the messy bits E — Embed with real users, watch without steering L — Log every friction point, even the small ones O — Observe the real context — environment, mood, tools D — Dry-run the journey under real-world constraints Y — Yield insights into quick, testable fixes A real example: Designers love building discovery-rich menus. But when you’re hungry, between meetings, or wrangling kids — most people don’t explore. They hit “reorder.” Industry research shows nearly half of users order from the same restaurant weekly — yet many still struggle to find the reorder option easily. ⚡ Lesson: In real life, convenience beats discovery. Design for shortcuts — especially the ones users are already primed to take. Figma is where you shape; the real world is where you learn. Taste the journey — Melody khao, khud jaan jao. #UX #ProductDesign #UserResearch #DesignLeadership #EmpathyInDesign #ServiceDesign
16