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

# For Strategists

> Map out your product thinking with AI that helps you explore, not just execute.

You're the person deciding **what** to build and **why**. You need to see the full landscape of bets, tradeoffs, and priorities, not a flat backlog.

## Where ProductBrain fits

ProductBrain is the strategic layer above your delivery tools. It doesn't replace your tracker. It answers the question your tracker can't: **why does any of this work exist?**

If you already use a roadmap or backlog tool, ProductBrain sits on top. The strategic reasoning lives here. Goals, needs, and the bets you're making. Your existing tools handle execution. Integrations connect the two, decisions flow down, delivery status flows up.

The boundary is a pair of definitions your team already uses. Your tracker drives a ticket to **Definition of Done**. ProductBrain plans *down to* **Definition of Ready**. Each job is a *proof* (its acceptance criteria), so "ready" means what success looks like is already defined. ProductBrain owns everything above that line: the *why*, and what counts as done. Your tracker owns everything below it: the *how*, and the doing. One clean seam, nothing to duplicate, nothing to argue over. And once the work is Done, ProductBrain asks the question the tracker can't: did the bet actually pay off? *Done* means built. Whether it *worked* is where ProductBrain picks back up.

If you're migrating from another tool (Aha!, Productboard, or similar), we'll import your data for you, free, hands-on. Export what you have, send it to us, and we'll restructure it into a clean Goal → Need → Approach → Job hierarchy. You start with your existing strategy, not a blank canvas. Email [import@productbrain.com](mailto:import@productbrain.com).

If you're starting fresh, paste your brief, pitch deck, or project notes into the onboarding wizard. The AI extracts goals, needs, and approaches from whatever you give it, structured plan in under a minute.

If you don't have a dedicated tool yet, ProductBrain covers both. The Planning Tree for strategy and the Delivery Map for execution.

## What ProductBrain does for you

### Think in structure, not lists

Traditional tools give you a backlog, an ever-growing list where everything feels equally urgent. ProductBrain gives you a tree: every piece of work traces back through needs to business goals. You can see at a glance which goals are well-served and which are neglected.

### AI that thinks with you

You don't need to arrive with a perfectly formed strategy. Start with what's on your mind, a problem, a half-formed idea, even just a frustration, and the AI maps it into the framework. It suggests approaches you might not have considered, asks clarifying questions that sharpen your thinking, and structures messy input into something you can act on.

Describe something loosely. Get back a structured goal, need, and approach set. Tighten it, adjust it, move on. You go from vague idea to clear strategy in minutes, not days.

### Jobs are proof, not tasks

When you break an approach into jobs, you're not writing a task list for a developer. You're defining **what success looks like**. Observable proof that this bet is paying off. "Customer can compare prices from the scan result" not "Add API call to price service."

### From ideas to decisions

Everyone knows how to brainstorm. The hard part is what comes after, turning a wall of ideas into a clear plan. ProductBrain picks up where brainstorming leaves off. The hierarchy forces you to connect every implementation idea to a need and every need to a goal. If an approach doesn't serve a need, you see it immediately. Nothing hides.

### Share your strategy, not a slide deck

Generate a shareable link for any goal in your tree. Stakeholders get an interactive read-only view, both the Planning Tree and the Delivery Map, scoped to exactly what you want them to see. No account required, no login, no "let me pull up the deck." You choose which goals are visible. They explore the reasoning at their own pace.

This is how strategy leaves your head without you being in the room. The shared view is the artifact, always current, always traceable, always interactive.

### See delivery without managing it

The Delivery Map shows your approaches as columns and iterations as rows. You can see what's bundled into each release and how your bets mature across time, without managing sprints, velocity, or story points.

### Keep pace as delivery speeds up

AI made building faster, and it keeps getting faster. The bottleneck moved. The hard part is no longer shipping, it's keeping the *why* coherent while the team ships at speed. As delivery accelerates, the cost of building the wrong thing faster goes up, not down. ProductBrain is where the thinking keeps up with the building: every job still traces to a need and a goal, however fast the work moves. You stay the person who can always answer "why this?", instantly, without a prep deck, no matter how quickly the floor moves underneath you. It runs alongside the delivery tools your team already lives in. It isn't another tracker to keep in sync.

## How it fits your workflow

1. **Map your thinking**. Use the Planning Tree to capture goals, needs, and approaches
2. **Let AI challenge you**. The AI suggests structure, fills gaps, and asks questions you haven't considered
3. **Define proof**, Break approaches into jobs that describe what "working" looks like
4. **Bundle into iterations**, Group jobs into releases that deliver balanced value
5. **Hand off to builders**. The Delivery Map and API give builders exactly what they need to execute

## Get Started

<CardGroup cols={2}>
  <Card title="Strategist Quickstart" icon="rocket" href="/guides/strategist-quickstart">
    Build your first planning tree in minutes. The AI guides you through it.
  </Card>

  <Card title="The Framework" icon="sitemap" href="/framework/overview">
    Understand the Goal → Need → Approach → Job model in depth.
  </Card>
</CardGroup>
