impact-sizing

Quantify feature value using driver trees and a 4-step framework.

Updated Aug 23, 2026

Search Tags:#product management #prioritization #business case #impact sizing #feature value #driver tree

Ready to run

npx skills add https://github.com/TimothyNguyen04/pmos --skill impact-sizing-timothynguyen04

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: impact-sizing
Source: https://github.com/TimothyNguyen04/pmos/tree/main/PM-OS/.claude/skills/impact-sizing
Command: npx skills add https://github.com/TimothyNguyen04/pmos --skill impact-sizing-timothynguyen04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product managers systematically estimate the potential business value and impact of new features, enabling better prioritization and resource allocation.

Core Features & Use Cases

Driver Tree Analysis: Visually map feature impact to key business metrics.
4-Step Sizing Framework: Guides users through usage, impact, assumptions, and takeaways.
Assumption De-risking: Identifies and plans mitigation for key uncertainties.
Use Case: A PM needs to justify allocating engineering resources to a new feature. They use this Skill to quantify the expected revenue increase and user adoption, presenting a data-backed business case.

Quick Start

Use the impact-sizing skill to quantify the value of the new user onboarding flow.

Frequently Asked Questions about impact-sizing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I quantify feature value for a product management business case?▼

Quantify feature value using driver trees to map impact to key business metrics, analyzing user impact, problem severity, addressable users, and revenue drivers to build a data-backed business case.

What is a driver tree for analyzing feature impact and revenue drivers?▼

A driver tree visually maps feature impact to key business metrics by breaking down revenue impact drivers, historical adoption rates, and pain severity to systematically estimate potential business value.

How do I prioritize features using impact sizing and a 4-step framework?▼

Prioritize features by applying a 4-step sizing framework that guides you through usage, impact, assumptions, and takeaways to estimate value and allocate engineering resources effectively.

Can I use impact sizing to identify and mitigate assumptions in a PRD?▼

Impact sizing identifies key uncertainties within your PRD and plans mitigations for them, de-risking assumptions by integrating confidence levels and historical adoption rates into your metric definitions.

Does impact sizing work without historical adoption rate data for new features?▼

Impact sizing integrates historical adoption rates to estimate business value, so lacking this data requires setting lower confidence levels and explicitly de-risking assumptions during the sizing process.

What is the best way to estimate addressable users and pain severity for prioritization?▼

Estimate addressable users and pain severity by analyzing user impact and problem severity through the 4-step framework, integrating these findings with confidence levels to justify resource allocation.