> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/portfolio/prioritization.md).

# Portfolio prioritization

Prioritization is where you act on your portfolio items. From the Portfolio summary, drill into the prioritization view of your choice. All three views share the same filters; pick whichever matches the kind of decision you're making.

Watch how to turn pain points and opportunities into prioritized, trackable work across the chart, table, and kanban views.

{% embed url="<https://www.youtube.com/watch?v=k1Qt2a24OE4>" %}

#### Why use the prioritization views

* Compare items side by side and decide what to tackle first, instead of scanning a flat list
* Switch between chart, table, and kanban without losing your filters or context

#### In this section

* [**Chart**](/portfolio/prioritization/how-to-use-the-portfolio-chart.md) - Map items on configurable axes for comparative prioritization (impact vs effort, value vs risk, etc.).
* [**Table**](/portfolio/prioritization/how-to-use-the-portfolio-table.md) - Tabular view with filtering and sorting for detailed item-by-item review.
* [**Kanban**](/portfolio/prioritization/how-to-use-the-portfolio-kanban.md) - Status-based columns for managing item workflow (Planned).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdesk.smaply.app/portfolio/prioritization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.