A Product Pivot

What It Covers

37signals pivoted their HEY email feature mid-development from keyboard navigation to Power Through New, a stacked view that lets users process multiple emails sequentially within the original appetite timeline.

Key Questions Answered

• •Problem over solution: When technical limitations revealed inconsistent keyboard navigation behavior across different email contexts, stepping back to ask "what are we actually trying to do" opened the solution space to better alternatives beyond the initial implementation.
• •Implementation difficulty as signal: Encountering hard technical problems during development indicates the design needs deeper examination. When a feature works inconsistently across contexts, that complexity smell suggests the conceptual model itself requires rethinking rather than explaining away edge cases.
• •Executive engagement timing: Product owners reviewing work at week four of a cycle can authorize pivots with remaining time buffer. Too early misses implementation insights; too late eliminates pivot opportunity. The two-week inter-cycle buffer provides additional flexibility for last-minute refinements.
• •Building on existing patterns: The team completed the pivot within appetite by adapting HEY's existing read-together feature rather than inventing from scratch. Leveraging prior art with modified buttons and layout enabled rapid prototyping and shipping within approximately ten days post-decision.