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.

Issues Status

Backlog

Every new Issue goes to Backlog. Every week we should move around 7 to 10 issues from Backlog to Todo.

Todo

Todo Issues is our appetite for the week. We expect to finish all the Todo Issues by HyperTuesday Meeting.

In Progress

When we start working on an Issue we move it to In Progress.

In Review

If the definition of done is uncertain change status to In Review and re-assign the Issue to another coworker.

Done

GET THINGS DONE :).

Canceled

When the Issue is not relevant anymore change the status to Canceled.

Duplicate

When there is a Duplicate Issue change the status to Duplicate and add a link to the remaining Issue.

Triage

Every issue must have an owner. Anybody can add an owner. If it is uncertain ask Gabo.

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.

Enhancement – UX, performance, or design polish to existing parts coming from an Enhancement Note in Seed.

Feature – A new functionality to implement coming from a Project Task in Seed.

Technical Debt – Refactoring or cleanup that improves long-term maintainability.

Labels

Task Type:

Project Task.

Enhancement Task.

Bug.

Knowledge Task.

Design Task

Scope:

Desktop.

Editor.

Email.

Web.

Gateway.

Discussion.

Feed.

Blocked by:

Needs Decision.

Needs Repro.

Browser:

Chrome.

Safari.

Platfrom:

Mobile

Windows

The easiest way to describe, identify and implement Issues is by linking to the latest design. We will be creating a Design Library.