Is a step line right for counts?
Decision: Pending
ClassLink · Frost · Data viz sketches
Line & trend charts
Three ways to show a count over time, from the plain line to a line with its causes.
- Category
- Line & trend charts · 3 in the audit
- Representative
- CMC Security Reports
- Sketches
- 10
- Data
- Mock, from screenshots
- Status
- Draft · For feedback
- Updated
- 2026-10-20
00 · Representative
CMC Security Reports
- What shipsA line of tenant admins over seven months, then two reset tables.
- What worksThe headline chart is a true line, simple and honest.
- What to improveAxis runs to 20 for a count of 8, so the one change is a faint kink; the tables and the line do not talk to each other.
Sketch A · Direct labels
A step, not a slope
Number of Tenant AdminsSep 2024 – Mar 2025
Why
An admin count changes in whole steps, so it is drawn as steps with the change named.
Spec
- Step line 2.5px, brand blue
- Axis 0 to 10, so the step is visible
- Labels on the change and the end value
- Draws in once, when fully in view
Principle
Label the data, not a legend
Sketch B · Layering
The line and its causes
Tenant admins and the changes behind themSep 2024 – Mar 2025
Why
The reset tables explain the trend, so they share its time axis.
Spec
- Two lanes of events under the line
- Circle = password, square = MFA; shape, not color
- One axis for line and events
- Hover names each event
Principle
Layering and separation
Sketch C · Sparklines
A trend in a stat card
Tenant Admins
8
Up 1 since November
Latest changesLast 30 days
Password resetlforgerOct 29
MFA resethhendersonOct 29
Password resetssherwoodOct 29
MFA resetffranklinOct 29
Why
On a dashboard the trend must fit inside a card, beside the number it explains.
Spec
- Value 54/600 Barlow with change note
- Sparkline marks start and end
- Latest changes as a quiet table
- Fits a 360px tile
Principle
Word-sized graphics
Sketch D · Explore · Layering
A ribbon with flags
Tenant admins and the changes behind themSep 2024 – Mar 2025
Key = password resetShield = MFA reset
Why
The flags put the reset events right on the ribbon, so cause and effect are one picture.
Spec
- Ribbon gradient, 3px line
- Key = password, shield = MFA
- Flags drop in after the line
- End value labeled
Principle
Layering and separation
Sketch E · Explore · Unit chart
People stepping in
Tenant Admins
8
Up 1 since November
Tenant Admins by MonthSep 2024 – Mar 2025
Green person = a new tenant admin that month · 1 person = 1 admin
Why
Admins are people, so each month is a stack of them and the new one is green.
Spec
- 1 person = 1 admin
- Green = joined that month, named in the key
- KPI row above
- Bounce in, new admin drops
Principle
Show the count
Sketch F · Explore · Small multiples
Month tiles
Tenant Admins
8
Up 1 since November
Tenant Admins by MonthSep 2024 – Mar 2025
Sep
7
Oct
7
Nov
7
Dec
8
Jan
8
Feb
8
Mar
8
Key = password reset · Shield = MFA reset · Green person = joined that month · ring = month an admin was added
Why
Each month is a small card with its people and its resets, so cause and count sit side by side.
Spec
- One tile per month, equal size
- 1 person = 1 admin, green = new
- Icons = resets that month
- Ring marks the month an admin was added
Principle
Small multiples
Sketch G · Explore · Layering
Route map
Tenant admins and the changes behind themSep 2024 – Mar 2025
Key = password reset · Shield = MFA reset · stations = months · the line darkens when the admin count steps up
Why
A route has stations: months are stops, the line darkens when the count steps up, and resets hang below.
Spec
- Stations = months, count above
- Line darkens at +1
- Stops below = resets
- Draws once, stops drop in
Principle
Layering and separation
Sketch H · Explore · Direct labels
Staircase
Tenant Admins
8
Up 1 since November
Tenant Admins by MonthSep 2024 – Mar 2025
Why
Admins are people, and the count only changes in whole steps, so it is drawn as a staircase with the new admin standing on it.
Spec
- Hero 54/600 above
- Steps on a 0 to 10 scale
- New admin figure in green, now in blue
- Drops in once
Principle
Label the data, not a legend
Sketch I · Explore · Layering
Vertical timeline
Tenant admins and the changes behind themSep 2024 – Mar 2025
Feb 20Password reset
Jan 22MFA reset
Jan 14Password reset
Dec 9MFA reset
DecTenant admins 7 → 8 Up 1
Nov 12Password reset
Oct 29MFA reset
Oct 29Password reset
Newest first · Key = password reset · Shield = MFA reset
Why
A short feed reads fastest on a phone: what changed, when, newest first.
Spec
- Rail with a node per event
- Key = password, shield = MFA
- Milestone = admins 7 to 8, success badge
- Slide in once
Principle
Integrate words and graphics
Sketch J · Explore · Small multiples
Event calendars
Tenant admins and the changes behind themSep 2024 – Mar 2025
Oct7 admins
Nov7 admins
Dec8 admins
Jan8 admins
Feb8 admins
Key = password reset · Shield = MFA reset · small green dot = two resets that day · ring = month an admin was added
Why
Real dates on real calendars show exactly which days had resets, month by month.
Spec
- One calendar per month with resets
- Admins count in each header
- Ring on the month an admin was added
- Bounce in once
Principle
Small multiples
Rules in every sketch
One system
- Color
- Role hue · blue for quantity · status inks
- Status
- Icon + label badge, no dots, from the Frost status spec
- Type
- Frost v.03 roles: Inter, Barlow numerals 34+
- Form
- No donuts, pies or rings
- Motion
- Once, when fully in view
- KPI cards
- One horizontal, centered row
Feedback
Which one, and why?
Should events share the line's axis?
Decision: Pending