Impact-First Product Management

Your team must be able to answer “If I were the CEO, would I fully fund this team?”

Most PMs assume their team’s existence is a righteous fact; instead, treat headcount as an investment that must show ROI.

Why: Headcount is now expensive; companies will cut teams that cannot articulate their contribution to revenue or strategic goals.

"if you were the CEO of this company, would you fully fund your own team? Frankly, most of the people I asked that question to don't know the answer right away"

Set team goals no more than one step away from company-level goals.

Avoid cascading OKRs into oblivion; every team goal should orbit the company goal like moons around a planet.

Why: Intermediate layers accumulate assumptions and risk; direct linkage keeps accountability and clarity.

"setting team goals, no more than one step away from company goals. Don't let it get cascaded into oblivion"

Impact is measured by the business model, not by best-practice checklists.

Understand whether the company needs growth, profitability, retention, or regulatory compliance and translate that into team metrics.

Why: Best practices are context-free; business models are context-rich. Success is judged by the latter.

"the best product managers and teams I've worked with are really curious to understand what success means to their particular business"

Low-impact work begets more low-impact work until the next layoffs.

Teams add cosmetic features to avoid risk, increasing complexity and coordination overhead, making high-impact work harder.

Why: Each small feature adds dependencies; the ‘hood of the car’ becomes too heavy to open and fix the engine.

"the Low Impact PM Death Spiral... adding little features here and there... until the next round of layoffs"

Take ownership even when executives hand you low-impact projects.

Pushing back with data and alternative high-impact proposals is safer than silently executing doomed initiatives.

Why: Executives value teams that surface reality early; silent compliance leads to shared failure.

"even if you are told to build a thing that the execs are really excited about, you're still going to get fired eventually"

The PM’s job is to make the whole team think like a CEO, not to be the sole mini-CEO.

Engineers, designers, and researchers often spot impact opportunities first; the PM facilitates that shared commercial lens.

Why: Collaborative ownership scales better and surfaces insights from diverse perspectives.

"the product manager is responsible for the whole team thinking like a CEO"

Product management is facilitating a value exchange between business and customers.

Map what value the business extracts (revenue, data, retention) against what value customers receive (utility, delight, cost savings).

Why: Clarity on both sides of the exchange guides prioritization and ethical decision-making.

"product management as facilitating a value exchange between a business and its customers"

Regulation, B2B sales cycles, and quarterly targets are design constraints, not excuses.

Competitors face the same constraints; mastering them becomes a competitive advantage.

Why: Trying to ignore constraints wastes energy; embracing them shapes focused, feasible solutions.

"those constraints are how you do product management... work with, not against the commercial realities of our business"