Priorities

Priority decides what happens next and why one item comes before another.

Where priority shows up

Each initiative and bug has a priority level. Issues synced from Jira or Linear keep the priority set in that tool.

Issue priorities

Priority	Meaning
Critical	Highest severity work that needs immediate attention.
Urgent	Time-sensitive work that should interrupt normal ordering.
High	Important work that should be handled before the default queue.
Medium	Normal priority work.
Low	Useful work that can wait behind higher-impact items.
Lowest	Low-impact work to keep visible without crowding current planning.

Decide priority with context

Before setting priority, answer:

• Goal: Which outcome does this support?
• Customer or company: Who is affected?
• Product: Which area changes?
• Owner: Who can move it forward?
• Blocker: Is another item waiting on it?

Order planned initiatives

Priority levels tie easily. When the team needs a single ordered list of planned initiatives, use stack ranking.