Product
Dashboards, onboarding, research rituals and the features we deleted. Notes from the product room.
Invite flows: the social onboarding of team products
The invite flow is where one user bets their reputation on your product. Role choice at invite time, shareable links vs email, and viral-loop honesty.
Product search UX: from query box to answers
In-app search is a product decision wearing an engineering costume: scoping, suggestions, typo tolerance, filters vs facets, and no-results states that navigate.
Cancellation flows that leave the door open
Offboarding is a trust surface: retention offers without traps, exit surveys that yield signal, data-export dignity, and win-back timing that works.
Command palettes: the 200-millisecond product tour
A command palette done well is a 200-millisecond product tour. Ranking heuristics, forgiving fuzzy match, keyboard ergonomics, and when a palette is a crutch.
Keyboard shortcuts nobody finds
Most shipped shortcuts are discovered by accident or never. Legends, cheat sheets, teaching in context, remapping, and designing for the power user you'll have.
Prioritisation frameworks after RICE stops working
RICE works until the spreadsheet becomes the decision. What comes next: strategy filters, evidence maps, learning-first sequencing, meetings that decide.
Upgrade prompts that don't feel like ransom notes
In-product upsell timing and tone: moments of demonstrated value, honest limit nudges, the dismissed-state contract, and measurement that doesn't lie to you.
Workspaces and orgs: the UX of switching context
Where the workspace switcher lives, URL strategy per tenant, cross-space notifications, and preventing wrong-org mistakes without nannying confirm dialogs.
Undo beats confirm: designing reversible software
Confirmation dialogs train users to click through danger. Undo-first design: timing, reversible architecture, soft deletes, and the trust dividend of forgiving software.
Dates and times: pickers, zones and the lies of relative time
Calendar grids vs typing, timezone display rules for teams, relative timestamps that decay to absolute, and the DST edge cases that bite months later.
A research repository that gets read after the study ends
Most research dies in a read-once PDF. Build a repository people actually use: atomic notes, a lasting taxonomy, insight half-lives, traceable decisions.
Help at the point of need
The user manual nobody opens, the tooltip that shouldn't exist, and how to design help that arrives where the question does — and gets out of the way.