How to View Bottleneck Analysis
Kofi has 28 completed beats through his "Beat Production" process. His Advanced Analytics screen shows that "Sound Selection" averages 3.1 days — more than 3x longer than any other stage — so he knows exactly where to focus his process improvement efforts.
Prerequisites
- You need at least 3 completed items (songs/albums that have reached the final stage) to see timing insights. Until then, the Dashboard shows a "not enough data yet" message.
- Advanced analytics (bottleneck charts, velocity metrics) require a Plus or Pro subscription.
Steps
-
Go to the Dashboard tab.
-
Find the timing card for your process — it appears once you have 3+ completed items. It shows:
- Average time per stage across completed items
- Total average time per item
-
Look for the bottleneck indicator — the stage with the highest average duration is highlighted with a visual marker. This is your current bottleneck.
-
For Plus/Pro subscribers: Tap "Advanced Analytics" to open the full view:
- A bar chart showing average time per stage for the selected process
- Velocity metrics (items completed per month, with trend direction)
- Time comparison across completed items to show whether you're getting faster
-
Interpret the data:
- A stage that averages 3x or more longer than others is a significant bottleneck
- High variance in a stage (some items fast, some very slow) suggests inconsistent practices at that stage
- Upward velocity trend means your throughput is improving
Expected Outcome
- Timing card shows average time per stage and total average per item
- Bottleneck stage is visually highlighted
- Plus/Pro subscribers see the full bar chart and velocity trend
Acting on Bottleneck Data
Once you identify a bottleneck:
- Consider splitting that stage into two smaller stages to make the work more manageable
- Add done-criteria to the bottleneck stage to clarify what completion means
- Modify the process (Processes tab → edit) — modifying a process based on data is one of the criteria for reaching "Mastering" level
Tips
- Kofi's example: his "Sound Selection" stage was his bottleneck at 3.1 days. He considered splitting it into "Sample Sourcing" and "Sound Design" to give each sub-task its own stage and timing visibility.
- Timing data only exists for items tracked through the app — songs you completed before installing the app won't contribute to calculations.
- Data from 3 items is the minimum; 10+ items gives you more reliable averages.
Was this article helpful?