What “top down” usually means for a PM

#product

Your manager is likely saying you start (or stay) too close to details, features, or execution, and not enough from:

Business outcome — What problem are we solving, and why does it matter now?
Strategic context — How does this connect to company goals, OKRs, or product vision?
Tradeoffs at the right altitude — What are we choosing not to do, and why?
Narrative for leadership — Can you explain the work in 30 seconds without mentioning tickets or UI?

Top down: “We need to reduce churn in enterprise accounts because renewal risk is up 12%. The highest-leverage bet is improving onboarding for admins in the first 14 days.”

Bottom up (what they may be hearing): “We should add a dashboard widget, fix these 5 bugs, and ship the export feature users asked for.”

Both can be true — the issue is often where you begin and how you justify the work.

How to practice top-down thinking

1. Use a simple framing template

Before any recommendation, force this structure:

Context: What’s happening in the business/market?
Problem: What’s broken or missing (one sentence)?
Impact: What happens if we don’t solve it?
Proposal: What’s the smallest bet that moves the needle?
Success: How will we know it worked?

2. Lead with the “so what”

In docs, Slack, and meetings, put the headline first:

“Recommendation: Deprioritize Feature X this quarter to protect enterprise retention.

Reason: 3 of our top 10 accounts flagged onboarding friction as a renewal risk.”

Then add details — not the other way around.

3. Tie everything to a north star

For each initiative, be able to answer:

Which goal/OKR does this serve?
What metric moves?
What’s the counterfactual (what we give up)?

If you can’t answer those, you’re still thinking bottom-up.

4. Zoom out before zooming in

When you get a request (from users, sales, eng), ask:

Is this a symptom of a bigger problem?
How many users/accounts does this affect?
Is this urgent, important, or just loud?

5. Practice the “executive version”

Take your current roadmap item and rewrite it as:

1 slide title
3 bullets (problem, approach, outcome)
1 risk

If that’s hard, the thinking isn’t top-down yet.

A useful mental model

Strategy (why / where to play)
    ↓
Outcomes (what success looks like)
    ↓
Bets (which problems to solve)
    ↓
Solutions (features, specs, tickets)

If you live mostly at the bottom two layers, you’ll get this feedback — even if you’re doing good PM work day to day.

Bottom line

“Think top down” usually means: start from outcomes and strategy, then derive work — and lead conversations that way.

Your next step isn’t to think less about details; it’s to anchor details to a clear higher-level story every time you propose, prioritize, or update.