Coaching: Manager Dashboard

By Summit53 Team

Overview

The Coaching dashboard (/coaching) is the managerโ€™s starting point each week. Its job is to answer one question โ€” where should I spend my coaching time? โ€” by running a diagnostic across every rep on your team and surfacing the ones most likely to be blocked. The page is headed โ€œCoaching dashboard โ€” where to spend this weekโ€.

Two actions sit in the header: Re-run diagnostic regenerates the team analysis from the latest CRM and activity data, and Plan this weekโ€™s 1:1s jumps straight to the agenda builder for the top-priority rep.

The diagnostic model

The engine classifies each rep into the layer most likely blocking their performance, evaluated top-down: Results โ†’ Effort โ†’ Knowledge โ†’ Skills. The first failing layer is where coaching should focus โ€” the principle being that skills work wonโ€™t land while effort is the real blocker. A rep who is hitting their numbers is labelled On Target; reps the engine canโ€™t yet place are shown as Unclassified.

KPI strip

Across the top, five tiles summarise the team at a glance:

  • Reps in scope โ€” how many reps were diagnosed.
  • Below target โ€” reps not currently On Target, shown as a fraction of the team.
  • Avg quota attain. โ€” the teamโ€™s average quota attainment.
  • Sessions this week โ€” the coaching sessions scheduled for the week.
  • Flagged meetings โ€” meetings carrying coaching signals, out of total analysed meetings. This tile appears only when meeting analytics are available.

Diagnosed layer distribution

The Diagnosed layer card breaks the team down by their first failing layer โ€” On Target, Effort, Knowledge, Skills, and Unclassified โ€” with a count and percentage bar for each. Use it to read the shape of the team: a team that is mostly โ€œEffortโ€ needs a different response from one that is mostly โ€œSkillsโ€.

Priority queue

The Priority queue is the heart of the page: a ranked table of every rep with their diagnosed Layer, quota Attainment, the Focus metric (current value vs benchmark), the Gap to benchmark, and a Meetings count with a warning marker when a rep has flagged conversation signals. Click any row to open that repโ€™s deep-dive.

A Sort control lets you reorder the queue by Severity (the default, worst-blocked first), Name, Attainment, or Gap %. The queue shows the first twelve reps; if the team is larger, a view all control expands the rest.

Framework components โ€” team rollup

This heatmap scores every rep against the MEDDPICC and SPICED framework components (Authority, Budget, Champion, Critical Event, Decision Criteria, Discovery, Economic Buyer, Metrics, Pain, Timeline, and so on), each scored 0โ€“1 and shown 0โ€“100 in the cell. The benchmark is the P75 (0.75) line. Colours run from red (needs work) through to green (strong), and each row ends with the repโ€™s AVG. Click a rep to open their deep-dive. Use this to spot which framework skills are weak across the whole team versus isolated to one rep.

Cadence mix

The Cadence mix card lays out the quarterโ€™s 13-week coaching plan and the type of each week: Strategic (business plan, pipeline, executive roll-up), Skills (skills development, call review, focus-metric coaching), Career (career growth, development goals), Execution (pipeline execution, deal-level coaching), and Close (quarter close, deal acceleration). The current week is marked This week so you know which kind of 1:1 the agenda builder will assemble.

Meeting quality โ€” team rollup

When reps have recorded meetings with conversation analytics, a second heatmap rolls up meeting quality across the team. Columns cover Talk ratio, Questions/min, Interactivity, Monologue (longest stretch), Interrupts, and Fillers/min, each coloured against an ideal range from โ€œNeeds workโ€ to โ€œStrongโ€. Reps are sorted worst-first so the conversations most in need of review float to the top. This section is hidden until at least one rep has analysed meetings.

Before diagnostics exist

If the team has not been analysed yet, the page shows โ€œNo team diagnostics available yetโ€ with a prompt to click Re-run diagnostic. Re-running can take a few seconds while the engine recomputes, after which the dashboard populates.