> ## 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.

# Strategist Quickstart

> Build your first planning tree in minutes.

This mirrors the in-app onboarding. If you've already completed the wizard, you've done most of this.

## 1. Start with what's on your mind

After signing up, the wizard asks: **"What are you working on?"**

You don't need to think in goals or frameworks. Describe what you're building, a problem you're facing, or an idea you're exploring. The AI maps your input into the right level of the tree.

**Examples of good starting points:**

* "I'm building a claims management tool for insurance adjusters"
* "I need to figure out how to reduce churn in my SaaS"
* "I want to automate my email workflow with AI"

## 2. Review the AI's draft

The AI generates a structured branch. A goal, needs underneath it, and approaches for each need. Review what it suggests:

* **Does the goal capture your business outcome?** Edit it if not.
* **Do the needs cover what must be true?** Add or remove as needed.
* **Are the approaches reasonable bets?** You don't have to keep all of them.

Click **Commit** when you're happy. The nodes appear on your Planning Tree.

## 3. Describe your project

Open the project panel and tell the AI about your project. This isn't just a description. It shapes how the AI talks to you going forward. It'll ask about:

* What you're building
* What tools you use
* How you verify that things work

## 4. Create an iteration

An iteration is a bundle of work you plan to ship together, like a release, a sprint, or a milestone. Click the iteration panel and create your first one. Call it whatever makes sense: "MVP", "Phase 1", "June release".

## 5. Generate jobs

Select an approach and click **Propose jobs**. The AI generates verifiable acceptance criteria. Proof that the approach is working. Review, edit, and commit.

## 6. Assign jobs to your iteration

Select jobs and assign them to your iteration. This is how you decide what ships when.

## 7. View the Delivery Map

Switch to the Delivery Map view. Your approaches are columns, your iteration is a row, and the jobs show what proof you need for each bet. This is your execution view.

## Next Steps

<CardGroup cols={2}>
  <Card title="The Framework" icon="sitemap" href="/framework/overview">
    Understand the model in depth. What each level means and how they connect.
  </Card>

  <Card title="Iterations" icon="layer-group" href="/framework/iterations">
    How to think about bundling work into releases.
  </Card>
</CardGroup>
