惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

人人都是产品经理
人人都是产品经理
Apple Machine Learning Research
Apple Machine Learning Research
云风的 BLOG
云风的 BLOG
罗磊的独立博客
博客园 - 三生石上(FineUI控件)
量子位
GbyAI
GbyAI
腾讯CDC
T
Tailwind CSS Blog
博客园 - Franky
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
D
Docker
G
Google Developers Blog
aimingoo的专栏
aimingoo的专栏
The GitHub Blog
The GitHub Blog
Microsoft Security Blog
Microsoft Security Blog
Stack Overflow Blog
Stack Overflow Blog
Hugging Face - Blog
Hugging Face - Blog
小众软件
小众软件
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
N
Netflix TechBlog - Medium
Jina AI
Jina AI
IT之家
IT之家
Y
Y Combinator Blog

Linear Blog

Styling Linear for the future with StyleX Sharing Linear’s growth with the people building it Rebuilding Linear’s delta sync read path How we built Linear Agent Introducing Loops - Linear Teaching an agent to auto-fix bugs - Linear Now Linear writes the code, too - Linear Reviewing code in the agent era - Linear Code review should be fast - Linear Code Intelligence for Linear Agent - Linear How we hire at Linear - Linear Output isn’t design - Linear How we use Linear Agent at Linear Post mortem on Linear security incident on March 24th, 2026 A calmer interface for a product in motion Design is more than code - Linear How our Customer Experience team works in Linear - Linear Continuous planning in Linear - Linear Designing remote work at Linear - Linear Self-driving SaaS: When software runs itself - Linear A Linear spin on Liquid Glass - Linear Best practices for designing Linear Dashboards - Linear Why we committed to a zero-bugs policy - Linear How we built Triage Intelligence - Linear Giving our team liquidity through Linear’s first tender offer - Linear How Cursor integrated with Linear for Agents - Linear Quality Wednesdays: How we trained our team to see what doesn’t work - Linear Our approach to building the Agent Interaction SDK - Linear Inside Mercury’s six-month journey building with AI agents - Linear Building our way: Announcing our Series C - Linear
How Commure uses Dashboards to track performance and guid...
Kevin Hartnett · 2025-09-11 · via Linear Blog

As teams grow, the surface area of their work expands. This makes it harder for leaders at every level of an organization to plan on both short- and long-term timescales. It’s easy to lose track of what’s happening day to day, and just as easy to miss slow-growing trends until they’ve already caused problems.

We built Dashboards in Linear to help with that. They let you bring together multiple insights in a single place so you can see where things stand and step in early when something’s off. Dashboards are fully customizable, allowing you to filter by team, dig into specific issues, and take actions directly from the page.

Commure, a healthcare technology company that supports over 400,000 clinicians, uses Dashboards to guide both short-term action and longer-term planning. They check some dashboards daily to stay on top of triage, SLA performance, and postmortem follow-through. Others they refer to at longer intervals to understand how engineering time is being spent and whether it matches the company’s priorities. One of the biggest impacts for Commure has been tracking whether different workstreams are moving in the right direction. Burnup charts, for example, give their teams a way to see if issue volume is increasing or decreasing over time.

The dashboards below are real examples from their workspace, shared by Myles Baumann, a senior product manager at Commure.

1. High-Priority Issues Over Time

Intended user: Everyone

Purpose: Track how the backlog is doing and how it’s spread across teams

Scope: One product, many teams

Usage: This shows how the backlog has changed over time and how it’s distributed across teams. Not all teams get the same number of high-priority issues, so this helps Commure see who’s carrying more load and how that’s shifting. It’s useful for just keeping an eye on whether things are trending in the right direction.

A chart that shows how the Commure backlog is doing and how it’s spread across teams.

2. Feature SLA Tracking

Intended user: Everyone

Purpose: Track SLA performance based on severity

Scope: One product, many teams

Usage: We have SLAs depending on how critical a feature is—P0, P1, or P2—and this dashboard helps Commure see how we’re doing. It shows how often we’re hitting or missing those SLAs, what our lead times are by severity, and how that breaks down by team.

A dashboard for tracking SLA performance based on severity.

3. Project Estimate Burndown and Investment View

Intended user: Product Manager, Engineering Manager

Purpose: Understand where engineering time is going and whether project scoping matches reality

Scope: One product, several teams

Usage: The top chart shows cumulative effort across all active projects. It helps teams explain delivery timelines and surface cases where a project is taking more time than expected. The bottom chart splits out time spent outside of projects on feature requests, operational work, and more. It’s used to spot how much unplanned work is drawing attention away from roadmap commitments.

The top chart shows cumulative effort across all active projects. It helps teams explain delivery timelines and surface cases where a project is taking more time than expected. The bottom chart splits out time spent outside of projects on feature requests, operational work, and more.

4. Insights Dashboard: Cycle Time by Assignee

Intended user: Product Manager, Engineering Manager, Team Lead

Purpose: Provide context for performance-related questions

Scope: Product-wide. Multiple engineering teams

Usage: This dashboard visualizes cycle time by assignee, giving managers a way to spot patterns in how long individuals take to complete issues. It’s not used as a performance metric on its own, but it’s helpful in two ways: as a starting point to ask questions—like whether someone is getting poorly scoped tickets or not surfacing blockers—and as a way to validate anecdotal concerns. When it feels like someone isn’t keeping up, unusually long cycle times can help reinforce the case for follow-up.

This dashboard visualizes cycle time by assignee.

5. Engineering Hygiene Review

Intended user: Product Manager, Engineering Manager, Team Lead

Purpose: Support regular board cleanup and planning

Scope: Engineering team

Usage: This dashboard is used to prepare for weekly or bi-weekly reviews. It shows high-priority issues that need to be addressed in an upcoming cycle, outstanding bugs, tickets missing estimates, and tickets that haven’t been assigned. Other views highlight metadata gaps—such as missing feature labels, ticket types, or notability flags—so that teams can keep pace with labeling standards. The goal is to make sure nothing slips through the cracks and that every issue is accounted for in the current or upcoming cycle.

This dashboard is used to prepare for weekly or bi-weekly reviews. It shows high-priority issues that need to be addressed in an upcoming cycle, outstanding bugs, tickets missing estimates, and tickets that haven’t been assigned.

Dashboards are available to workspaces on our Enterprise plans. See the docs to learn more.