The playbook
Sales Performance Coaching: Worked Examples
The following sales performance coaching examples illustrate how to move from an observed problem to a practical decision. They are hypothetical operating scenarios, not customer results or performance benchmarks. The central question is whether the work helps improve improvement in coached behaviors without losing the context needed to judge it.
Put the task in context
Choose a specific observable behavior, such as confirming the buyer's success criteria before a demo. Review examples, practice the behavior, then inspect later conversations. Account quality and territory conditions matter when comparing sales outcomes.
Example 1: establish a usable starting point
A team begins working on sales performance coaching but cannot consistently describe seller and observed behavior for the same item. The immediate task is review representative conversations and opportunity records. The team records the current state, identifies the source of each value, and resolves conflicting information before making a broader change.
The useful output is a customer or opportunity record that another person can interpret. This example does not require assuming an uplift. Success at this stage means the next decision can be made using a shared set of facts, with missing information explicitly identified.
Example 2: correct a specific failure
In a second situation, the team observes judging sellers only by activity counts without context. It proposes the correction: combine activity with quality evidence and opportunity conditions. Before applying that correction everywhere, the owner checks whether the same cause is present in other affected items. A common symptom alone does not prove that all items need the same repair.
| Decision | Illustrative reasoning |
|---|---|
| Observation | Judging sellers only by activity counts without context |
| Likely correction | Combine activity with quality evidence and opportunity conditions |
| Verification task | Choose one specific behavior to practice |
| Result to inspect | Check whether the behavior improves later conversations |
After the change, the owner repeats the relevant task and records what happened. If the condition remains, the team returns to the evidence rather than declaring the process complete. The example illustrates a repair cycle; it does not claim a particular commercial result.
Example 3: extend a process after it works
A third team already has reliable records for a small scope and wants to expand. It compares the next group with the first: are seller, observed behavior, practice defined in the same way, and does the intended outcome remain improvement in coached behaviors? Differences are written down before the earlier process is reused.
Expansion is appropriate when the assumptions still hold and an owner can review exceptions. Where the new group has different needs, the team adapts the process and tests again. Reusing the structure is useful; reusing a conclusion without checking its conditions is much less reliable.
Apply the examples to your own work
- Write the current problem in observable terms using seller.
- Choose which of the three examples matches the stage of the work.
- Complete this action first: review representative conversations and opportunity records.
- Keep the resulting evidence and review improvement in coached behaviors on a consistent basis.
Use observable customer milestones when assessing progress. A seller sending a message is an activity; a buyer agreeing to a next meeting is a different event. Recording both helps the team locate the actual constraint.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now