Speed up delivery by seeing where work stalls

A report with time in status fields in Aha! Roadmaps

October 22, 2024

Speed up delivery by seeing where work stalls

by Claire George

Bottlenecks. Roadblocks. Delays. No one likes these words in product development — they signal trouble. But even the sharpest teams hit snags. What sets you apart is your ability to quickly spot inefficiencies and make smart adjustments to keep progress moving. With today’s launch, identifying and addressing obstacles just got a whole lot easier.

New reporting fields make it possible to track where work is stalling and take action quickly.

To keep work on track, you need to understand exactly where and why things slow down. The new fields make this possible by providing a detailed look at time spent in your workflows. They include:

  • Time in status: Tracks the total time spent across workflow statuses

  • Time in status category: Tracks the total time spent in a status category

  • Time in current status: Tracks the time spent in the record's current status

This level of granularity helps you pinpoint potential bottlenecks and identify the root cause of delays. For example, if features spend too long in development, it might indicate resource gaps or unclear requirements. And if work lingers in status categories like In progress or Not started, you can see where the team's efforts are concentrated. Tracking current status allows for real-time adjustments before small delays grow into larger issues.

The new fields are available for any report, including lists, pivots, or charts. You can apply filters to focus on specific time ranges, like ideas that have been in Needs review for more than X days. Time in status is tracked until the work is completed, excluding Shipped and Will not do statuses.

The fields are available for your reports in Aha! Roadmaps, Aha! Ideas, and Aha! Develop, as well as any record that has a workflow associated with it (this could be goals, initiatives, ideas, releases, epics, features, and requirements).

Let's take a look at a few examples:

Review stalled ideas

Responding to customer ideas quickly is always a priority. Use the Time in current status field to sort a list of ideas that have been in Needs review the longest. This way, you can get back to customers who have not heard from you yet.

Another helpful tip: If you need to meet an SLA, set up an automation to send reminders before the response deadline.

The Time in current status counter will reset each time the status changes.

The Time in current status counter will reset each time the status changes.

Identify launch risks

Find out where features get stuck in your workflow. The example report below shows the time spent in each status. Although we expect features to spend significant time in development, we are surprised to see the length of time they spend in PM review. We can use these insights to discuss improvements with the team and adjust the process to keep features moving toward delivery.

Time in status reflects the cumulative time a record has spent in each status, even if it moves between statuses multiple times.

Time in status reflects the cumulative time a record has spent in each status, even if it moves between statuses multiple times.

Every process refinement frees your team up to move faster — so you can deliver more value to customers.

So, what's next? Save the reports for easy access and regular review within your knowledge base or product dashboard. Continue to discuss improvements and ensure everyone is aligned on how to keep work moving efficiently. Even better, document how you work together in the Frameworks section of Aha! Roadmaps. And let us know how we can support you.

Start a free trial

Reporting on time in status is available to Aha! Roadmaps, Aha! Ideas, and Aha! Develop customers. Our suite of tools includes Aha! Roadmaps, Aha! Ideas, Aha! Whiteboards, Aha! Knowledge, and Aha! Develop. Use each product individually or combined to help teams deliver even greater value. Sign up for a free 30-day trial or join a live demo to see why more than 1 million product builders trust our software to build lovable products and be happy doing it.

Claire George

Claire George

Claire is passionate about helping product development teams learn how to bring their strategy to life. She is the director of product marketing at Aha! — the world’s #1 product development software. Claire has 20 years of marketing and software experience. Previously, she led product marketing at an agile-based work management platform.

Follow Aha!

Follow Claire

Related articles

Strategic roadmaps: Vision vs. strategy vs. roadmap
January 14, 2020
Strategic roadmaps: Vision vs. strategy vs. roadmap

Roadmaps are beautiful. But a roadmap is still just a visualization. Learn why you need to have a vision and strategy behind the plan.

Your Roadmap Is a Promise (Do You Keep It?)
March 22, 2021
Your Roadmap Is a Promise (Do You Keep It?)

Your roadmap is a promise. Discover how treating your roadmap like a promise creates value for your company, team, and customers.

Roadmaps make strategy work
February 24, 2020
Roadmaps make strategy work

Putting strategy into action can be difficult. That is because too many teams jump straight to the “how” before they agree on the “why” and the “what.” Typically this…

Business Roadmaps vs. Product Roadmaps
June 11, 2020
Business Roadmaps vs. Product Roadmaps

Aha! CEO Brian de Haaff breaks down the differences between business roadmaps and product roadmaps — including where the two harmonize.