Back to Use Cases
Insurance

Creating end-to-end visibility for streamlining processes & coaching engineers.

Request Demo

Results Achieved

18%
Increase in PR Throughput per Contributor
42%
Decrease in Cycle Time
53%
Decrease in Time to Merge

The Challenge

  • EverQuote’s engineering leadership needed clearer visibility into how engineering teams were performing in relation to product development.
  • Attempts to use Jira for these insights were unsuccessful because the data couldn’t be easily tied back to actual engineering work.
  • They tried another software intelligence tool, but its metrics weren’t comprehensive or holistic enough for their needs.
  • Leadership lacked visibility into how much technical debt was accumulating.
  • They had no clear understanding of how fast pull requests were moving through the development lifecycle.
  • Bottlenecks in the code review process surfaced repeatedly during sprint retrospectives.
  • Despite hearing about these issues, they had no data showing where or why work was getting stuck.

    • Our Solution

  • Velocity gave EverQuote leaders precise visibility into how long each PR remained open, how long it waited for review, and when it was merged.
  • Each PR could be directly linked to its related Jira ticket, creating a unified view of work.
  • They discovered that measuring only “days spent coding” overlooked major parts of completing a Jira issue.
  • With metrics for every phase of development, they gained a complete understanding of Cycle Time and deeper insight into workflow slowdowns.
  • A high-level review of code review habits revealed that some teams approved over 50% of PRs without comments.
  • Investigation showed these comment-less PRs were mostly mundane configuration tasks that didn’t need review.
  • Leaders partnered with product managers to automate these basic configuration tasks, freeing engineers to focus on more complex, high-value work.
  • With Velocity, engineering leaders now have concrete data to present to the CTO for diagnosing root causes, informing process changes, guiding teams, and evaluating the impact of those changes.

    • Implementation Journey

    1
    2
    3
    4
    5
    6
    I love how I can mix and match a bunch of metrics together to look for correlations, make hypotheses about what’s happening with teams, and identify datasets that line up with those hypotheses to validate them.
    —Pheak Yi, Director of Engineering

    Ready to Transform Your Organization?

    Our proven methodology has delivered measurable results across industries. Let's discuss how we can help you achieve similar success.
    Schedule ConsultationView Other Cases