BETA: Report Efficiency


This feature is currently available for invited participants in our Public beta. Sign up here!

This executive report allows you to understand how quickly your product teams are at turning ideas into customer value from start to finish.

In this article:

What questions does the report help you to answer?

  • How quickly teams can deliver customer value from start to finish? Are we speeding up or slowing down?
  • How do I know where we have the biggest bottlenecks in our process?
  • Which initiatives are taking a long time to push through the process? Is something slipping?
  • Which teams are better at delivering customer value faster?
  • Which individuals/teams have a lot of things in the pipeline?



Time to complete a feature

The Time to complete a feature widget, allows you to benchmark how quick you are in delivering customer value from start to finish. It shows the median time it takes to complete a feature from start to finish and also shows the number of completed features that are used for this calculation - the more features are completed, the closer to reality is the median number of days, so you might want to expand the time range and/or adjust your filters.


Median calculation - for every feature that was completed within the selected timeframe we calculate start-to-finish duration time, this includes times spent in all the statuses selected in the Settings. Next, we calculate the median for all such features. If some feature statuses (e.g. Discovery) were worked on outside of the selected timeframe these are still included.

Chart visualization - every point on the line chart is calculated the same way as the median time above, except it is a rolling window looking back in time, based on the timeframe selected. Let’s say you select the last 30 days in the timeframe selector. In this case, every point on the chart represents a 30-day median time, looking back from that point.

You can drill down to details and see a list of all features that contributed to such calculation after clicking on the median number.


The time completed features spent in the status


Median calculation - for every feature that was completed within a selected timeframe and spent some time in a given status (e.g. Discovery) we calculate the median time of all such features spent in the status.

Features count - tells you how many of the completed features went through such a state. Let’s say 107 features went through the Discovery out of 198 completed features, which is roughly 50%. It would allow you to judge if this is expected depending on your process. However, if you have a strict process to follow, this is a good place to spot features that did not follow your process.

By clicking on the status name you can drill down to details to see a list of features that contributed to such calculation.


Features that are currently in status for more than X days

This widget allows you to identify slow-moving features that are currently in your pipeline, but not yet completed. It shows you the number of features in each selected status that are more than X number of days in such a status based on the timeframe selected.


By clicking on the individual bars you can drill down to individual statuses to get more information about such features. This is also a good location to understand if some individuals or teams have a lot of work in progress or if things simply need some cleanup because they are no longer being worked on. You can identify features that have not been updated based on the “last activity” column.



You can filter the data based on Hierarchy, Owner, and Team.

Note: To display relevant data using the Team filter, your Feature needs to be assigned to an Objective that is associated with a Team.


Timeframe selector

You can select the last 7 days, 30 days, 90 days, 12 months, and custom time range.



How do you control what is included in the start-to-finish calculation?

In the Settings of the report, you can:

  1. Include which feature statuses are considered.

    Note: By default, the first feature status is disabled. This is typically “idea” type of stage that you might not want to include in the calculation because you are just collecting the ideas.
  2. what is the final, completed, feature status (e.g. General Availability) - time feature spent in the completed status is not included in the calculation.

    Note: If you enable multiple completed statuses, most likely more features will be taken into consideration. If you disable all completed statuses, it would be exactly as if you select all of them.


How is the report calculated?

The report is calculated by how much time a feature spent in given status based on feature status changes. Therefore, updating feature statuses regularly will get you closer to reality.

What if a user changes a feature status by accident?

Feature status duration that is under 5 minutes are ignored - such short durations are most likely some user mistakes.

Was this article helpful?
1 out of 1 found this helpful



Article is closed for comments.

Articles in this section

Our Support hours:
Monday to Friday from 9:00 am - 2:00 am CET. Monday to Friday from 0:00 am - 5:00 pm PST.
Productboard Academy
Become a Productboard expert with self-paced courses, quick tip videos, webinars and more.
Product Makers Community
Connect and learn Product Excellence with a global community