A policy briefing attracts attention. Another receives very little. The dashboard makes the difference visible, but it does not explain it. Before deciding which content works, ask what the figures actually measure and what you would need to know to interpret them.
Use statistics to identify a question, combine them with context and member feedback, then test a practical improvement.
Start with a question your team can act on
A dashboard is easier to use when you approach it with a specific question. Are members finding a new briefing? Which resources deserve clearer promotion? Have some representatives never accessed the platform?
For a small secretariat, these questions can lead to manageable actions: improve a document title, include a resource in the next newsletter or check whether a new member needs help getting started.
Avoid beginning with a target that has no clear connection to member needs. More page views might reflect useful interest, repeated attempts to find an answer or confusion about which document is current. The figure tells you where to look, not what conclusion to reach.
Understand the unit behind each number
Before comparing figures, check the scope of the measure. A view is not necessarily a unique reader; an all-time download count is not the same as downloads during the last month. Account activity also differs from a record of individual reading behaviour.
- What action is counted: a view, a download or account activity?
- Does the figure cover a defined period or the lifetime of the content?
- Does it count events, unique people or an account status?
- Can the measure identify a person, or is it an aggregate?
- Are the two items you are comparing measured in the same way?
Members Cloud’s current Statistics & Insights includes document viewing trends, cumulative downloads and newsletter article views, plus account activity status. These measures have different scopes. They should not be presented as a complete history of what each member has read.
Read the figures in the context of the audience
A specialist briefing may serve a small working group extremely well. Comparing its readership with a general update sent to the whole membership can obscure that value.
Consider the intended audience, the document’s age, its visibility and the timing of the policy file. A briefing published just before a key meeting has a different context from a background resource intended for occasional reference.
Likewise, an account with no recorded visit is a reason to investigate, not a verdict on the member’s commitment. The representative may need help accessing the platform, may have changed roles or may receive information through a colleague. A short conversation can reveal what the dashboard cannot.
Turn one observation into one improvement
Suppose an important document receives little attention. Check whether its title communicates relevance, whether the intended members have access and whether your update explained why they should read it. Choose one change rather than redesigning the entire communication process.
Review the result using a comparable measure and ask a few members whether the information was easier to find or use. Changes in activity can inform the discussion, but they do not by themselves establish why behaviour changed.
Bring a short learning note to the team: what you noticed, what you changed and what remains uncertain. Over time, this creates a useful record of communication decisions. Statistics become a tool for improving service, rather than a collection of numbers assembled for a board presentation.
ONE PRACTICAL STEP
Start here this week.
Choose one resource your association considers important. Review an available activity measure, check its scope and audience, then ask two intended readers whether they found the resource useful. Identify one improvement.
PUTTING IT INTO PRACTICE
Members Cloud’s Statistics & Insights brings content performance and member activity into view. A demo can explore the available measures and the practical questions they can help your secretariat answer.