This guide outlines our shared approach to organizing and prioritizing issues, enabling us to reduce friction, avoid overload, and stay focused on what matters most.
Triage by Urgency and Impact
We use four levels of priority to triage issues:
Urgent
Critical blockers or regressions that must be addressed immediately.
→ Example: App crashes on launch, production login broken.
High
Important issues that significantly impact the user or team. Should be picked up in the current or next cycle.
→ Example: Friction in onboarding flow, major UI bugs, broken nav on mobile.
Medium
Valuable but not time-sensitive. Should be scheduled as part of roadmap planning.
→ Example: Adding a setting, performance optimization.
Low
Nice-to-haves, polish, or speculative ideas. Should be reviewed occasionally.
→ Example: Animating transitions, microcopy tweaks, internal tooling.
Categorize by Type
Every issue should be labeled by type to improve clarity, ownership, and focus. Main types:
Bug – Something is broken or not working as expected.
Improvement – UX, performance, or design polish to existing parts.
Feature – A new functionality to implement.
Technical Debt – Refactoring or cleanup that improves long-term maintainability.
The easiest way to describe, identify and implement Issues is by linking to the latest design. We will be creating a Design Library.