Metric Definition
Engagement per board
Track from
Board activity analysis
Board activity analysis is the practice of measuring how actively people create, edit, comment on, and view a shared board over a defined period. It turns a collaboration surface into a tracked metric so you can see which boards are alive, which are stalling, and who is driving the work. It is most useful when the board represents a real workflow, such as a project, a sprint, or a planning cycle.
7 min read
What is board activity analysis?
Board activity analysis is the practice of measuring how actively people create, edit, comment on, and view a shared board over a defined period, normalised so different boards can be compared. A board with 200 actions across 4 people behaves very differently from a board with 200 actions across 40 people, so the raw count alone hides the truth. Normalising by active members gives you a per-person intensity you can track week over week.
The metric matters because a board is a proxy for real work. When activity falls, it usually means the underlying project has stalled, the owner has moved on, or the board has been replaced by a side channel such as chat. Tracking activity early lets you intervene before the board quietly dies and the work loses its single source of truth.
Definition note
Count only meaningful actions. Passive page loads, bot refreshes, and automated syncs inflate the number and make a dead board look busy. A clean measure weights created cards, edits, comments, and status moves above raw views.
How to calculate board activity analysis
Start by deciding the period, usually a week or a month, then sum every tracked action on the board within it. Divide by the number of distinct members who took at least one action. If a board logged 180 actions across 12 active members in a week, the board activity score is 15 actions per active member.
For a portfolio of boards, calculate the score for each one and rank them. The boards at the bottom are the ones to investigate, and the boards at the top tell you where collaboration is concentrated.
- 1
Define the period
Choose a consistent window, such as the last 7 or 30 days, and apply it to every board you compare.
- 2
Count tracked actions
Sum created cards, edits, comments, status moves, and weighted views within the period.
- 3
Count active members
Count distinct people who took at least one action, not everyone with access.
- 4
Divide and rank
Divide actions by active members to get the per-person score, then rank boards to find the stalled ones.
Board activity analysis in a metric tree
A single activity score tells you a board is quiet, but not why. A metric tree decomposes the score into the behaviours that drive it, so a drop points you at a specific cause rather than a vague concern. The first level splits activity into who is showing up, what they are doing, and how fresh the content is.
KPI Tree models this decomposition and connects each branch to the people who influence it. With RACI ownership on every node, a fall in comment activity is pushed to the person accountable for that board, not lost in a dashboard nobody reads. That is the gap between seeing a number move and someone acting on it.
Metric tree insight
When activity drops, the tree shows whether fewer people are showing up or the same people are doing less. Those two causes need opposite responses: one is an access or interest problem, the other is a workload or relevance problem.
Board activity analysis benchmarks
There is no universal benchmark because activity depends on what the board is for. A live sprint board should be busy every day, while a quarterly planning board peaks and then goes quiet by design. Use these ranges as a starting reference, then calibrate against your own healthy boards.
| Board state | Actions per active member per week | What it usually signals |
|---|---|---|
| Thriving | 12 or more | Active project, multiple contributors, board is the source of truth |
| Healthy | 5 to 12 | Steady work, owner engaged, no intervention needed |
| At risk | 2 to 5 | Slowing down, work may be drifting to chat or email |
| Stalled | under 2 | Likely abandoned, owner disengaged, candidate for archive or revival |
How to improve board activity analysis
Improving activity is not about forcing more clicks. It is about making the board the place where real work happens, then removing the friction that pushes people to side channels. Focus on ownership, relevance, and rhythm.
Assign a clear owner
Boards with one accountable owner stay tidy and current. Shared ownership with nobody accountable is the most common cause of drift.
Prune stale cards
Archive or close cards untouched for two weeks. A board cluttered with dead items discourages people from engaging with the live ones.
Create a rhythm
Tie the board to a recurring ritual such as a weekly standup so people have a reason to open it on a predictable cadence.
Find the side channels
If activity is low but the work is clearly happening, the conversation has moved to chat. Pull those decisions back onto the board.
Common mistakes when tracking board activity analysis
- 1
Counting views as engagement
A view is passive. Weight created cards, comments, and moves above raw page loads or the number flatters dead boards.
- 2
Ignoring board purpose
Comparing a daily sprint board against a quarterly planning board produces a false alarm. Group like with like before ranking.
- 3
Forgetting to normalise
Raw action counts reward big teams and punish small ones. Always divide by active members to compare fairly.
- 4
Chasing the number, not the work
Driving activity up with busywork hides the real signal. The goal is genuine collaboration, not a higher score.
Related metrics
Feature adoption rate
Product Metrics
Metric Definition
Feature Adoption Rate = (Users Who Used the Feature / Total Active Users) × 100
Feature adoption rate measures the percentage of users who use a specific feature within a given period. It tells product teams whether new features are resonating with users and which existing features are underutilised, guiding investment decisions and roadmap priorities.
Daily active users
DAU
Product Metrics
Metric Definition
DAU = Unique Users Who Performed a Qualifying Action in a Single Day
Daily active users measures the number of unique users who engage with your product on a given day. It is the primary engagement metric for consumer and SaaS products, indicating whether your product has become a daily habit for its users.
Retention rate
Product MetricsMetric Definition
Retention Rate = (Users Active at End of Period / Users Active at Start of Period) × 100
Retention rate measures the percentage of users or customers who continue to use your product over a given period. It is the most important growth metric because sustainable growth is impossible when users leave faster than they arrive.
Sprint velocity
Agile planning metric
Operations Metrics
Metric Definition
Sprint Velocity = Sum of Story Points Completed in a Sprint
Sprint velocity measures the amount of work a team completes during a sprint, typically expressed in story points, ideal days, or another unit of estimation. It is a planning tool that helps agile teams forecast how much work they can commit to in future sprints based on their historical completion rate. Velocity is one of the most widely used and most frequently misunderstood metrics in agile software development.
Metric trees for operations teams
Metric Definition
Board activity analysis is an operations signal, and this guide shows how operations teams structure engagement metrics like it inside a metric tree.
Vanity metrics vs actionable metrics
Metric Definition
Engagement per board can drift into a vanity number, so this guide helps you turn board activity analysis into a metric the team can actually act on.
Build board activity analysis as a metric tree
Decompose your board activity score into active members, actions, and freshness, then put a named owner on every branch. When a board starts to stall, KPI Tree pushes the change to the person accountable so it gets revived before the work loses its single source of truth.
