One coached meeting tells you about one meeting. The trends view plots the same measurements over time, which is where they start meaning something.
Three scopes
Mine. Your own meetings. Always available to everybody.
My team. Your reports and peers, derived from the reporting structure rather than from a list somebody has to maintain.
Organisation. Everybody, where your position allows it.
Which scopes you can see follows your role rather than a setting you can switch on, and that is deliberate.
What is tracked
Three skills, chosen because they are behavioural rather than circumstantial.
Talk share. How much of the conversation you carried.
Interruptions. How often you started while somebody else was mid-thought.
Listening. How often you acknowledged before responding.
Alongside those sit the issues that recur across coaching passes, with an indication of whether each is getting better or worse.
Reading a trend properly
A single point is noise. One meeting where you talked eighty per cent of the time might have been a demo you were asked to give.
A month is a signal. Consistently high talk share across every kind of meeting is a habit rather than a circumstance.
Direction beats level. Somebody moving from poor to acceptable is doing better work than somebody sitting comfortably at good and not moving. The first is learning; the second is coasting.
Compare like with like. Demos and discovery calls have genuinely different healthy ranges, and a mixed average across both means less than either one on its own.
For a manager
The team view is a coaching aid, and its failure mode is obvious enough to name plainly: it is not a performance metric.
The reasons are not subtle. Talk share is contextual. Interruption counts are heuristics computed over text with imperfect punctuation. The person with the best numbers may simply be running easier meetings with more agreeable people.
Used well it does one thing very reliably: it tells you where to look. Somebody whose listening has dropped steadily for six weeks is worth a conversation. What that conversation turns out to be about is not something a chart can tell you, and it is frequently nothing to do with meetings.
Used badly it teaches people to perform for the measurement, at which point the measurement stops describing anything real and you have lost the instrument as well as the trust.
If you are going to show somebody their own trend, show it to them as a question rather than a finding.
For yourself
The honest use is picking one thing and watching it.
Acknowledgement rate is the best first target. It is the most measurable of the three, the most directly under your control, and the one that changes how a conversation feels to the other person most immediately.
Watch it for two months. If it moves and stays moved, that is a habit rather than a good fortnight.
What the issue list adds
Alongside the three skill lines sits a list of the issues coaching keeps raising, with an indication of whether each is getting better or worse.
It is the more actionable half of the surface and the half people skip, because a chart is easier to look at than a list of things you keep doing.
Two readings are worth taking. An issue that recurs and is not improving is the one to work on, and it is usually the one you have privately decided is not really a problem. An issue that has disappeared is worth noticing, because behaviour change is invisible from the inside and this is the only place it is recorded.
Setting a baseline
The first month of trends is not a trend, it is a baseline, and treating it as either good or bad news is a mistake.
Generate coaching on four or five meetings across a few weeks before drawing any conclusion. Anything less and you are reading the meetings you happened to pick rather than the way you work.
Once there is a baseline, the useful question stops being "is this good" and becomes "is this moving", which is the only question the data can actually answer.
Building a habit around it
The trends view rewards a rhythm and punishes browsing.
Monthly, not weekly. Coaching is generated a few times a month, so a weekly check is looking at one or two new points and drawing conclusions from noise.
Look at one skill. All three at once produces a general sense of doing badly rather than anything actionable.
Write down what you changed. The chart records the behaviour; it does not record the intervention. Six weeks later the useful question is which of the things you tried actually moved it, and that is not in the data unless you put it there.
Where the numbers mislead
Four situations where a trend is real and the interpretation is wrong.
A role change. Somebody moving from delivery to sales will see every measure shift, because the meetings changed rather than the person.
A difficult account. One demanding customer across a quarter drags every average, and it says more about the account than the individual.
Fewer coached meetings. A line that flattens because there are only two points is not stability.
A deliberate strategy. Talking eighty per cent of the time is correct in a training session and looks identical in the data to talking over a customer.
The rule that covers all four: the chart shows what happened, never why. The why is always a conversation, and treating the chart as the answer is how a useful tool becomes a resented one.
What it will not show
It will not show outcomes. These are conduct measurements. Whether the meetings converted is a pipeline question and it lives in Sales HQ, where it belongs.
It will not explain a change. A drop in talk share might be better listening or a bad month with a difficult account. The chart shows the change; the reason is always a conversation.
It only covers coached meetings. Coaching is generated on request, so a sparse chart almost always means few coaching passes rather than few meetings. Before drawing conclusions from a thin line, check how many points are actually on it.
Did this answer your question?
No, ask a person