> 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

Chart, table, and kanban views of your portfolio for prioritization work. Toggle between them and filter to focus on the items that matter.

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**](https://helpdesk.smaply.app/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**](https://helpdesk.smaply.app/portfolio/prioritization/how-to-use-the-portfolio-table.md) - Tabular view with filtering and sorting for detailed item-by-item review.
* [**Kanban**](https://helpdesk.smaply.app/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
