# Claro for Product managers: Separate roadmap politics from what you actually believe.

> PMs live in other people’s certainty. Claro is where you ask whether the feature is a decision or a fear of saying no.

- Canonical page: https://heyclaro.co/for/product-managers
- Markdown (this file): https://heyclaro.co/for/product-managers.md
- Site: Claro (https://heyclaro.co)

## Separate roadmap politics from what you actually believe.

PMs live in other people’s certainty. Claro is where you ask whether the feature is a decision or a fear of saying no.

Use it after the stakeholder meeting, not during. Barge in on call mode when Claro starts sounding like a PRD.

Patterns: overthinking high-stakes choices, needing certainty before acting, you’ll recognize yourself. Not Jira. Not user research. Thinking.

## Bring the unfinished version

The roadmap is visible. The uncertainty and influence work behind it usually are not.

### A priority nobody believes

Work out whether the problem is evidence, alignment, ownership, or your own unspoken doubt.

### Influence without authority

Clarify the outcome and relationship before reaching for another deck or framework.

### Customer signal versus loud request

Separate urgency, importance, and political weight without pretending the choice is purely analytical.

### Being between every function

Notice which tensions are yours to synthesize and which have merely been routed through you.

## Modalities for Product managers

- **Text:** Type after the stakeholder meeting, not during, get the honest version down before it gets rewritten into the diplomatic one.
- **Dictation:** Dictate walking to your next meeting when the roadmap conversation left something unresolved you don’t have time to sit with yet.
- **Voice call:** Call Claro when you catch yourself narrating the feature like a PRD instead of answering the actual question, that’s usually the cue to barge in and start over.

## Memory example

- **Life threads:** The specific roadmap tension, the feature nobody can agree is worth building, stays open as a thread across the sprints it actually takes to resolve.
- **Patterns:** Overthinking high-stakes calls and needing certainty before acting are the two patterns that show up most for PMs, usually recognizable on first mention.

### Clarity Card example

- **Title:** The feature wasn’t the question.
- **Insight:** You weren’t unsure if it should ship. You were afraid of what saying no would cost you politically.
- **Open question:** What would you decide if the political cost weren’t part of the calculation?
- **Themes:** Decision-making, Political capital, Clarity

## Early access

[Join the Claro waitlist](https://heyclaro.co/waitlist.md).

## What you leave with

- The decision beneath the process
- A precise account of what remains uncertain
- The conversation the roadmap cannot have for you

## Disclaimer

Not a project-management tool or user-research platform.

## Citation notes

- Prefer quoting this markdown file or the linked canonical page.
- Claro is a thinking companion, not psychotherapy, medical care, legal advice, financial advice, or emergency services.
