> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dacard.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Roadmap

> A function-level view of your team's active work, pulled from connected project management tools.

<Note>
  Roadmap reads your Linear workspace through the operations lens. Issues are classified into the same six functions we score: Strategy, Design, Development, Operations, GTM, Intelligence. Connect Linear once; we pull on the daily sync.
</Note>

# Roadmap

The Roadmap page pulls issues from your connected Linear workspace and groups them by function. It gives you a function-level view of what your team is actively building, mapped to the same six functions we score: Strategy, Design, Development, Operations, GTM, and Intelligence.

Hit **Roadmap** in the main nav.

## What it shows

Roadmap isn't a separate planning tool. It reads your existing Linear data and surfaces it through the operations lens. Each issue is classified into a function based on labels, project names, and title patterns.

| Column           | What it includes                                                           |
| ---------------- | -------------------------------------------------------------------------- |
| **Strategy**     | Positioning work, competitive analysis, roadmap decisions, market research |
| **Design**       | UX design, research, prototyping, design system work                       |
| **Development**  | Engineering, architecture, infrastructure, and shipping work               |
| **Operations**   | Analytics, customer signals, data pipelines, feedback processes            |
| **GTM**          | Launch planning, messaging, growth experiments, pricing work               |
| **Intelligence** | Capability experiments, model work, eval frameworks, cost optimization     |

## Connecting Linear

The roadmap requires a connected Linear workspace. If you have not connected Linear yet:

<Steps>
  <Step title="Go to Sources">
    Navigate to **Sources** from the main navigation.
  </Step>

  <Step title="Connect Linear">
    Click **Connect** next to Linear and authorize via OAuth.
  </Step>

  <Step title="Select workspace">
    Choose which Linear team to sync. Issues are pulled on the next sync cycle (or immediately via **Sync now**).
  </Step>
</Steps>

<Note>
  The roadmap view currently pulls from Linear. Dacard supports 54 integration providers for scoring signals, but the roadmap's function-level issue classification is built on Linear's label and project system. Connect Linear from the [Sources page](/knowledge-base/integrations) to populate your roadmap.
</Note>

## Issue classification

Issues are classified into functions automatically using a combination of:

* **Linear labels** labels matching function names (e.g., "design", "gtm", "infrastructure") are mapped directly
* **Project names** Linear projects named after functions are classified accordingly
* **Title patterns** common patterns like "research:", "launch:", "fix:" are used as signals

Issues that cannot be classified appear in an **Unclassified** column.

<Tip>
  To improve classification accuracy, add Linear labels that match the six function names. Dacard reads these automatically on every sync.
</Tip>

## Using the roadmap alongside scores

The roadmap is most useful when read alongside your scoring report. If your **Design** function scores low, check the Design column for active work, are there enough research and UX issues in progress? If the **Intelligence** column is empty, that signals a gap in capability investment.

<CardGroup cols={2}>
  <Card title="Connect Linear" icon="plug" href="/knowledge-base/integrations">
    Set up the Linear integration to populate roadmap data.
  </Card>

  <Card title="Understanding your report" icon="chart-bar" href="/knowledge-base/ic-understand-report">
    How to read function scores and match them to your roadmap.
  </Card>
</CardGroup>