The two dashboards: rep view and leadership view

A founder asks for "the outbound dashboard" and gets one screen trying to do two different jobs. The rep checks it in the morning and finds quarterly trend lines they cannot act on by five o'clock. The founder checks it at night and drowns in dial-level noise that means nothing without context. One artifact, two audiences, neither served. The fix is not a better dashboard. It is admitting there are two.

The rep view: today

A rep's dashboard answers one question, which is what to do next. This morning's call list, ranked, with the reason each account is on it. Follow-ups that come due today. Dials and conversations so far this week, set against the activity standard the rep owns. Meetings on the calendar that still need confirming. Every element on it should be changeable by end of day, because that is the entire point: a rep view is a work surface, not a scoreboard.

What does not belong there: conversion trends, unit economics, quarter-over-quarter anything. A rep staring at a quarterly conversion rate has been handed a number they cannot move today, and a number you cannot move today is decoration at best and anxiety at worst.

The leadership view: trend and cost

Leadership needs the opposite altitude. Four-week trend lines across the funnel stages, so this week means something relative to the last four. Conversion between stages, so a drop in output can be traced to the stage that caused it instead of blamed on the whole system. Cost per outcome, so the program can be compared to its alternatives on level ground. Segment splits, because the average always hides which third of the list is doing the work.

None of it should be daily. Daily numbers at leadership altitude are noise: a Tuesday with three conversations is not information, and a leader who treats it as information teaches reps to manage the dashboard instead of the phone. The leadership view also only works on top of honest inputs, which is why the five enforced CRM fields matter more than any visualization built on them, and why a baseline has to exist before any trend line means anything at all.

The seam between them

The two views meet once a week, in a written report that translates activity into trend and trend into one paragraph of narrative: what the conversations taught us, what we are changing next. Weekly is the right seam because it is fast enough to steer with and slow enough to smooth the noise. The rep sees where their inputs went. Leadership sees whether the system is converging. Same facts, two altitudes, one honest meeting point.

This is how CommandVA runs it. Our reps work their day from a ranked list and a live activity view; our clients get the weekly trend picture with the narrative attached, and neither audience has to squint at the other's screen. If your current dashboard is one screen doing both jobs badly, book a strategy call and we will show you what each view looks like against an ICP like yours.