Executive summary
Every engineering organization wants to move faster, improve collaboration, and deliver with confidence. Yet most leaders do not start with perfect visibility; they start with questions: Where are we losing time? Why is delivery inconsistent? Where should we focus our improvements?
The Executive Summary report is designed to answer these questions by providing actionable insights into your team’s development, collaboration, and delivery patterns. By combining git, PR, and ticket data into a single, cohesive view, this report eliminates the need to hunt through disparate metrics, allowing leaders to see exactly where their teams stand at a glance.
This report also serves as a guide through the typical stages of Flow’s metrics journey—a proven progression seen across hundreds of successful organizations. By using these insights to tell a story of what’s working and what isn’t, you can evolve your engineering system step by step: first establishing clarity and healthy activity, then improving collaboration; then strengthening planning and delivery, and finally optimizing portfolio-wide outcomes at scale.
The Executive summary report is most useful if you start with longer date ranges—more than a month—and larger teams. This helps you identify wider patterns in your organization before narrowing down to view more specific teams.
Take a look at the featuring percentile benchmarks across 13 core Flow metrics. They serve as the analytical foundation for the Executive Summary report, providing the objective criteria used to calculate your scores.
By comparing your team’s data against peer organizations using Flow, these benchmarks allow you to move beyond raw numbers to see where you truly stand. They function as a strategic diagnostic tool, helping you pinpoint critical friction points, validate your team's unique strengths, and prioritize growth opportunities with the greatest impact on your delivery.
Permissions
You must have the Executive dashboard Report permission to view the Executive summary.
Assessment
The Assessment section measures your maturity across Activity, Collaboration, and Delivery.
Work does not happen in a vacuum; it follows a logical progression. By grouping metrics into these three stages, the report helps you identify exactly where the pipes are clogged:
Activity: Focuses on the engine of development—how consistently and effectively code is being authored.
Collaboration: Measures development connective tissue—how well the team works together through code reviews and PR cycles to ensure quality.
Delivery: Tracks the output—how efficiently work moves through the final stages of the pipeline to reach the customer.
Activity
The Activity stage measures consistent engineering output through coding frequency, commit patterns, and code.
Dive deeper: Team health insights.
Collaboration
The Collaboration stage evaluates how well the team collaborates through code review responsiveness and thoroughness.
Dive deeper: Review collaboration and PR resolution.
Delivery
The Delivery stage tracks delivery health with cycle time and sprint completion as primary scores, and backflow and queue time as contextual diagnostics. This stage helps identify bottlenecks and improve delivery predictability.
Sprint completion
Dive deeper: Retrospective.
Activity
The Activity stage marks the official start of your Flow metrics journey and establishes the heartbeat of development. By tracking the four core coding metrics—Coding Days, Commits per Day, Impact, and Efficiency—you gain objective, leading indicators that reveal whether consistent, focused work is happening.
These signals are vital because they tell you exactly what is occurring on the ground; a sudden dip in activity acts as an early warning system, allowing you to react to blockers well before they impact delivery.
The goal is to build a stable, healthy baseline:
>3 coding days per week
Rising or stable commits
Maintained efficiency
A steady, usable Impact trend
To help you understand these values at a glance, Flow provides Percentile benchmark indicators. These color-coded banners (Green for the 75th percentile, Gray for the 50th percentile, and Orange for the 25th percentile) show how your team compares to other high-performing organizations. While every team is unique, higher percentiles generally correlate with higher performance.
For deeper analysis, click View details to see these metrics broken down by nested teams, helping you understand how individual development patterns affect your aggregate scores.
Trends only display if the selected date range contains four or more full Monday to Sunday weeks. Shorter time frames do not include trend data.
To help you dive deeper into these signals, this stage includes a direct link to the Team health insights, where you can further evaluate the underlying patterns of your team's output.
By maintaining a view of these original commit metrics, you ensure that even as your organization matures, you can identify when something goes awry—long before it becomes a critical issue.
Collaboration
The Collaboration stage focuses on enhancing how teams work together to ensure that high activity translates into high-quality output. By tracking Time to First Comment, Time to Merge, Thoroughly reviewed PRs, and Iterated PRs, leaders can uncover knowledge silos and review bottlenecks that stall work before it’s even seen. The primary goal is to expand the "knowledge web" of your organization, spreading expertise and building a deeper bench of talent through healthy feedback loops.
This stage typically evolves through two focus areas:
Increasing collaboration activity: The first priority is reducing unreviewed PRs as close to zero as possible. Often, a high Time to Merge is not caused by technical complexity but by long wait times for the first comment.
Improving collaboration quality: Once engagement is high, metrics like Thoroughly reviewed PRs and Iterated PRs ensure work undergoes the necessary rigor to maintain long-term product stability.
These metrics are powerful tools for transformation because the teams own the data. By setting clear working agreements—such as targets for response times—teams can organically improve their daily workflows.
To help you dive deeper, each metric includes percentile indicators to benchmark your performance against other organizations. You can also click View details to see a breakdown by nested teams. Strengthening these collaborative habits ensures your team isn't just moving fast, but is building with shared ownership and resilience.
This section focuses on Unreviewed PRs and Iterated PRs—these two metrics are excellent indicators of how well your teams give and respond to feedback to improve your code. These metrics are also displayed with their corresponding overall values, trends (where applicable), and percentile indicators.
Click View details to view these metrics broken down per the immediate nested team of the parent team selection.
Use the direct link to the Review collaboration and PR resolution reports to see exactly how people are working together across the organization.
These metrics reveal whether work is stalling before it is even seen or if it is undergoing the necessary rigor of multiple feedback loops. Understanding these patterns helps ensure that your team is not just moving fast, but is maintaining the collaborative standards required for long-term product stability.
Delivery
With consistent Activity and healthy Collaboration in place, the focus shifts to the flow of work itself. The Delivery stage focuses on how efficiently your processes are set up to move work from inception to the customer. By tracking Cycle Time and Sprint Completion, along with contextual signals like Backflow Rate and Queue Time, you can pinpoint exactly where friction occurs in your development pipeline.
This stage is critical for bridging the gap between engineering and the business through several key focus areas:
Balancing creation and completion: Using the Tickets and PRs pie charts, you can visualize the ratio of completed (blue) to uncompleted (yellow) work. If uncompleted work dominates, it often signals high context switching or processes that prevent teams from finishing what they start.
Predictability and trust: The goal is to consistently achieve a sprint completion rate of> 80% while keeping scope creep (added work) below 20%. This consistency builds trust with customer-facing teams, transforming engineering metrics into a reliable business forecasting tool.
Spotlighting friction: Metrics like Backflow help surface challenges beyond just coding—such as issues with requirements, testing, or releases. This allows for productive conversations with stakeholders on the periphery of development.
For teams using Agile methodologies, these trends are compared against sprint commitments. For Kanban or hybrid teams, the Flow Retrospective report—linked directly from this stage—provides the necessary throughput and velocity metrics to analyze delivery patterns.
By making these metrics transparent, you shift from a purely technical transformation to a business-wide optimization. Improving Cycle Time—the total time from active work to completion—reduces the risk of delayed releases and ensures that customers benefit from your work as quickly as possible.
Portfolio status
Once individual teams are performing at a high level, the conversation shifts from tactical output to organizational strategy. The Portfolio optimization & scale stage is where Flow becomes a permanent part of your operating rhythm—transforming from a set of metrics into a strategic decision-making system.
This phase leverages high-level insights to answer the critical question: Where is our time and investment actually going?
Strategic investment and allocation
At this scale, leaders use specialized tools to ensure engineering efforts align with business priorities:
Work type allocation: This identifies the balance between Feature, Defect, and Unassigned work. It ensures that teams aren't trapped in maintenance mode and provides the confidence needed to meet delivery commitments.
Total work breakdown: This categorizes coding efforts into four buckets—New work, Legacy refactor, Rework, and Help others. By monitoring these, you can detect if a spike in Rework is cannibalizing your capacity for New work or if you are successfully paying down technical debt through Refactoring.
Measuring maturity and health
To ensure your transformation is sustainable and delivers value, the Portfolio optimization stage incorporates broader signals:
Executive summary and DORA Metrics: Think of this as your organization’s dashboard. It alerts you when a check engine light comes on for specific teams and uses DORA metrics to confirm that leading indicators are resulting in improved speed and quality.
Developer sentiment: Quantitative data is paired with qualitative feedback to assess the sustainability of your team's success. High performance is only a win if the team isn't burning out to achieve it.
Proficiency: This tracks the success of long-term investments, such as replacing legacy systems or modernizing systems.
Scaling success with Scenario builder
One of the most powerful tools in this phase is the Scenario builder. While it is excellent for A/B testing changes in earlier stages, at the portfolio level, it lets you model different investment strategies and compare results across the organization.
Do not fall into the trap of skipping to this final stage before stabilizing the leading indicators in the first three phases. Once the foundation is solid, this stage lets you to stop managing metrics and start managing outcomes—confidently deciding where to scale, where to invest, and how to deliver maximum business value.