type
status
date
slug
summary
category
tags
icon
password
Inbox by Gmail was eye-opening. What's even more remarkable is that it was introduced decades after the invention of email, at a time when many believed email innovation had reached its limits.
While browsing through its help documentation, I was struck by the significant differences between Gmail and Inbox.
notion image
Here's a concise summary of the product design insights that Inbox offers to product managers:
  1. Prioritize "Actions" as a crucial analytical category for product logic
  1. Identify needs from unexpected user behaviors and offer streamlined solutions (e.g., snoozing emails, creating reminders)
  1. Continually explore ways to align expression, product interaction, and copy with users' "original intentions" or subconscious desires (e.g., the evolution from deleting emails in traditional clients, to archiving in Gmail, to marking as done in Inbox)
  1. View products as sponges—even in the most mature markets, dedication and creativity can yield innovative, attention-grabbing solutions
Product Planning Workflow and Tools: A Comprehensive GuideKey Principles for Writing Effective Product Requirements Documents (PRDs)
Loading...
Zhenye Dong
Zhenye Dong
Product Manager | New Dad | New Blogger
Latest posts
Fixing Terminal Exit Code 1 in Cursor IDE on Windows
2025-3-19
Cross-Platform Line Ending Issues When Syncing Git Repositories with OneDrive
2025-3-10
The Crying Test: A Guide for Setting Rules
2025-2-6
Parenting Note: Learning to Say Goodbye
2025-2-6
Parenting Note: Why laughter Can’t neutralize Tears?
2025-2-6
How to display [[roam/js]] results inline in Roam Research?
2025-1-5