Topic
Design
Read Time
10 mins
Nobody Designed the Goodbye.
April 03, 2026
I was wrapping up an interview with a founder last week. Good conversation, real energy, the kind of call where you leave feeling like something might actually come of it. We said our goodbyes. There was a moment, warm, genuine, and then I spent the next three seconds frantically scanning my screen for the end call button while maintaining eye contact with him through the camera. He saw all of it. It was a small thing. But small things in design are never really small, they're just failures at a scale most people have learned to forgive.
The Problem Nobody Is Solving
Video call interfaces are obsessed with the join experience. The lobby screen, the camera preview, the "you're about to enter the meeting" gate. Every platform has thought carefully about how you arrive. Nobody has thought carefully about how you leave. On Google Meet, the end call button sits in the bottom center toolbar, the same toolbar that houses mute, camera, screen share, reactions, and more. It's a red button, which helps, but it's competing for attention with six other controls in the exact moment when your eyes aren't on the screen. They're on the person you're saying goodbye to. Zoom does the same thing. Microsoft Teams buries it even further, a "Leave" option tucked inside a dropdown. The pattern is consistent across every major platform: the exit is an afterthought. And yet ending a call is one of the most socially loaded moments in the entire interaction. You're navigating the goodbye, the last impression, the eye contact and simultaneously hunting for a button. These two things are in direct conflict, and design is the reason why.
Why This Happens
Engagement-driven design optimises for time spent. Every dark pattern, every sticky interface, every "are you sure you want to leave?" prompt exists to keep you in. The exit is deprioritised by design, sometimes literally. But in a professional context, a clean goodbye matters. The last three seconds of an interview, a client call, a pitch, that's what lingers. Fumbling for an exit button right in that window is the digital equivalent of knocking over your chair on the way out. The fix doesn't require a redesign from scratch. It requires a shift in thinking about when the end call button needs to be most accessible.
What a Better Solution Looks Like
A few directions worth exploring: ◆ Keyboard shortcut, prominently communicated. Power users already know CMD+W or platform-specific shortcuts exist. But they're buried in documentation. A subtle tooltip during the first few calls — "End call: ⌘ + E" — builds muscle memory fast. ◆ Proximity-aware UI. When your cursor moves toward the camera feed — which is where your eyes go during a goodbye — the end call button could surface automatically. The interface reading intent isn't new technology. It's just not being applied here. A grace window. After clicking end, a 2-second undo prompt ("Ending call...") removes the anxiety of mis-tapping entirely. Slack does this brilliantly with sent messages. The same logic applies.
The Bigger Point
Exits deserve as much design thought as entrances. How an experience ends shapes how it's remembered, in psychology this is called the peak-end rule, and it's well documented. We remember the peak of an experience and the end of it. Video call platforms are actively sabotaging the end. The goodbye is part of the product. It's time someone designed it properly.
Comments