TL;DR
- An edge case is an unusual but realistic condition that changes normal product behavior.
- Edge cases can come from data, timing, permissions, concurrency, limits, interruptions, and external systems.
- An edge case is not automatically a bug.
- Teams should prioritize edge cases by probability and impact, not try to design every theoretical possibility.
- Important edge cases should be considered before engineering handoff.
What does an edge case look like?
A file upload seems simple until the user uploads a duplicate name, loses network midway, exceeds storage quota, lacks folder permission, or uploads five files where four succeed and one fails.
Each condition is plausible, but it lies outside the simplest happy path.
Where do edge cases come from?
- unusual data values
- permission changes
- timeouts and network loss
- partial completion
- concurrent actions
- account or subscription limits
- external API failures
- unexpected sequence of actions
Edge case vs. error
An edge case is a condition. An error state is one possible product response when a condition prevents success.
Some edge cases should not produce errors at all. They may require a different branch, warning, or constrained state.
How do teams find edge cases?
- Map the happy path.
- List assumptions required for each step to succeed.
- Challenge each assumption: what if it is false?
- Check permissions, limits, timing, and data boundaries.
- Review support tickets and production bugs.
- Ask engineering and QA where similar flows usually break.
- Prioritize by impact and likelihood.
Common mistakes
Treating all edge cases equally
A rare cosmetic issue should not outrank a low-frequency state that risks money or data loss.
Discovering them during implementation
Late discovery turns product ambiguity into rework.
Designing for impossible completeness
Focus on meaningful conditions, not every theoretical permutation.
The bottom line
An edge case asks: what plausible condition could make the normal flow behave differently, and what should the product do?
Related terms
Happy path · Product state · Error state · User flow
Relevant Figr resource
Read 10 Edge Cases Every PM Misses.
