Work Output: Coaching
Objective. Read coaching as the loop that connects an output or quality finding to an owned action, and treat coaching logged as an input - not proof that behaviour or output changed.
Coaching answers 'what are we doing with the people signal, and is it helping?' It closes the loop from a quality or output finding to a conversation with an owner, and it is where improvement in people terms either happens or stalls.
See it in the demo
What this screen answers
CSMs use coaching to turn a finding into an owned action and to check follow-through; Sales uses it to show the platform drives behaviour change, not just reporting. The customer question is 'did the signal lead to a coaching action, and did anything change after?' The honest framing is that logging coaching is the start, not the result.
The task
Start from a validated finding - a quality dip or output shortfall you have already checked - and read the coaching linked to it: who owns it, what was agreed, and whether there is a measured follow-up. Scope to the period around the coaching so any before-and-after is fair. For a CSM, the task is to ensure coaching is tied to evidence and has a follow-up checkpoint, so the loop actually closes rather than filling a log.
How to read it
Coaching logged is an input, not an outcome - the classic misread is counting coaching sessions as improvement. A change in output after coaching is correlational: mix, complexity, tenure and concurrent changes can all move the number, so attributing an uptick to the coaching alone overstates the effect. Read coaching as part of the improvement loop, measured against a baseline, and keep 'coaching delivered' strictly separate from 'behaviour changed' and 'output improved'.
Honest limits
This screen does not prove coaching caused an output change or that a change persisted. It depends on findings being validated first and on an honest baseline, both seeded here. Confirm with product how coaching links to findings and outcomes, and present coaching impact only as a measured, baseline-anchored before-and-after, never as a session count.
Interpretation check
Coaching logged is an input to the improvement loop, not proof of changed behaviour or output; an output change after coaching is correlational, so keep 'coaching delivered', 'behaviour changed' and 'output improved' strictly apart.
Practical task
Take one validated finding, read its linked coaching, and write a one-line finding stating whether the loop is closed with a measured follow-up or is still just a logged session.
Self-check
A manager reports 30 coaching sessions as this quarter's improvement. What is the error?
Sessions are an input, not an outcome. Improvement is a measured before-and-after against a baseline, with other causes ruled out - a session count proves activity, not change.
Output rose after coaching. Did the coaching cause it?
Correlational only - mix, complexity, tenure and concurrent changes could have moved it. You need a baseline and to rule those out before attributing the gain to coaching.
What must a coaching action be tied to, to be meaningful?
A validated finding and a follow-up checkpoint - so the loop closes with evidence rather than just filling a log.
Verified vs demo. Screen is live in the demo at https://work-output.demo.timechamp.io/#/coaching; exact controls, labels and on-screen figures are SME-validation-pending.