Bottleneck Analysis Template for Product Managers

Use your project tracker (Linear, Jira, Shortcut) to pull transition timestamps. Most tools log when an issue moves between statuses. Export the last 20-30 features and calculate the time between each status change. If you do not have this data, start with a 2-week manual tracking exercise where each team member logs stage transitions.

Fix them sequentially, not simultaneously. Pick the one with the highest wait-to-active time ratio first. That ratio indicates the most wasted time. After fixing it, re-measure and tackle the next one. Attempting to fix multiple bottlenecks at once makes it impossible to measure which intervention worked.

Bottleneck analysis is a quantitative complement to retrospectives. Retros surface qualitative pain points ("code review feels slow"). Bottleneck analysis provides the data to confirm or disprove those perceptions and prioritize fixes based on measured impact rather than sentiment.

Yes. Dependencies on external teams (platform, infrastructure, data) are some of the most common bottlenecks. Include them as explicit stages with their own duration measurements. If a dependency consistently adds wait time, that needs its own intervention plan. ---