Master the fundamentals of product management, from user research and analytics to strategy, prioritization, communication, and execution.

Learn product management basics through practical lessons in user research, analytics, prioritization, strategy, and execution. Start on web, iOS, or Android.

Product Management Basics

Learn how to leverage AI in product management. Master AI fundamentals, prompt engineering, and practical applications for PMs.

Learn AI for product managers with practical lessons in AI fundamentals, prompt engineering, and everyday PM workflows. Start on web, iOS, or Android.

AI for Product Managers

Learn how to do competitive analysis. Master the fundamentals of competitive analysis and how to use it to make better product decisions.

Learn competitive analysis for product managers with practical lessons in market research and smarter product decisions. Start on web, iOS, or Android.

Competitive Analysis for Product Managers

## Executives Usually Want Three Things Quickly

In most PM conversations with leadership, they want to know:
- what decision you recommend
- why it matters now
- what risk or trade-off comes with it

```productme-visual
{"asset":"resource:assets/content/b726bbe4-8a0c-4649-b9ec-489294e35076/pm-executive-recommendation.visual.json"}
```

Lead with the answer, not with the whole history of the project.

<h2>Executives Usually Want Three Things Quickly</h2>
<p>In most PM conversations with leadership, they want to know:</p>
<ul>
<li>what decision you recommend</li>
<li>why it matters now</li>
<li>what risk or trade-off comes with it</li>
</ul>
<pre><code class="language-productme-visual">{"asset":"/content/b726bbe4-8a0c-4649-b9ec-489294e35076/pm-executive-recommendation.visual.json"}
</code></pre>
<p>Lead with the answer, not with the whole history of the project.</p>


<p>Which executive summary is strongest?</p>


Executive communication should usually start with detailed backlog history before stating a recommendation.

<p>Executive communication should usually start with detailed backlog history before stating a recommendation.</p>


An executive needs to decide whether to fund a bet. Lead the summary with your {{gap}}, then justify it with relevant {{gap}}.

<p>An executive needs to decide whether to fund a bet. Lead the summary with your {{gap}}, then justify it with relevant {{gap}}.</p>


## A Strong Recommendation Has Structure

A simple PM decision narrative often looks like:
- context
- recommendation
- evidence
- trade-offs
- what support or decision is needed

```mermaid
flowchart TB
  N0["Context and recommendation"]
  N1["Evidence and trade-offs"]
  N0 --> N1
  N2["Decision or support needed"]
  N1 --> N2
```

This helps leadership evaluate the call quickly.

<h2>A Strong Recommendation Has Structure</h2>
<p>A simple PM decision narrative often looks like:</p>
<ul>
<li>context</li>
<li>recommendation</li>
<li>evidence</li>
<li>trade-offs</li>
<li>what support or decision is needed</li>
</ul>
<pre><code class="language-mermaid">flowchart TB
  N0["Context and recommendation"]
  N1["Evidence and trade-offs"]
  N0 --> N1
  N2["Decision or support needed"]
  N1 --> N2
</code></pre>
<p>This helps leadership evaluate the call quickly.</p>


Which recommendation structure is strongest?

<p>Which recommendation structure is strongest?</p>


A PM is usually better off taking a position with evidence than presenting options without a recommendation.

<p>A PM is usually better off taking a position with evidence than presenting options without a recommendation.</p>


## The Best Executive Communication Is Specific and Brief

Strong executive communication:
- uses concrete business and user impact
- avoids jargon when simpler language works
- names uncertainty instead of hiding it
- keeps the ask clear

```mermaid
block-beta
  columns 2
  N0["Concrete impact"]
  N1["Clear ask"]
  N2["Named uncertainty"]
  N3["Plain language"]
```

Brevity is valuable when it preserves meaning.

<h2>The Best Executive Communication Is Specific and Brief</h2>
<p>Strong executive communication:</p>
<ul>
<li>uses concrete business and user impact</li>
<li>avoids jargon when simpler language works</li>
<li>names uncertainty instead of hiding it</li>
<li>keeps the ask clear</li>
</ul>
<pre><code class="language-mermaid">block-beta
  columns 2
  N0["Concrete impact"]
  N1["Clear ask"]
  N2["Named uncertainty"]
  N3["Plain language"]
</code></pre>
<p>Brevity is valuable when it preserves meaning.</p>


Which evidence is most persuasive in an executive conversation about prioritization?

<p>Which evidence is most persuasive in an executive conversation about prioritization?</p>


Clear, concise, and decisive communication is one of the most important PM leadership habits.

<p>Clear, concise, and decisive communication is one of the most important PM leadership habits.</p>
