Team trendsRoadmap
Behaviors across the team, at a glance.
A heatmap of behaviors by rep shows whether a habit belongs to one person or to the whole team. Planned after the first release.
AnswersIs this a rep problem or a team problem?
Roadmap. Planned, not in the first release. The screen below is an illustrative layout built from the same sample data as the rest of the site.
How it would work
- 01
Every rep, every behavior
Rows are behaviors, columns are reps, cells come from the same profiles managers already use.
- 02
Colored by tag, not rank
Strength, Watch or Leak against the team median. No scores, no order of merit.
- 03
Open a cell
A cell would open the behavior detail and the calls behind it.
What you see
Read off the screen above. Every number is sample data from the app’s own prototypes, arranged in an illustrative layout.
- A row of red
- When a leak runs across the row, it is a team habit. Coach the team, or look at the playbook.
- A column of red
- When it runs down one rep, it is one person’s focus for the next ten days.
- Trend arrows
- Direction over the last four weeks, so a cell that is improving reads differently from one that is stuck.
Who it’s for
Decide between a team session and a one-on-one in a glance.
Reps would not see the team grid. They see their own profile.
Where it fits
Bylda is one loop. Team trends is the patterns step.
- EventsWhat happened on the call
- BehaviorsHow the rep acted
- PatternsWhat repeats, for whom
- OutcomesWhat it travels with
- ChangeOne focus, then measured
What it won’t claim
- Roadmap. Not in the first release. Only Jordan’s column is read off the app; the rest is illustrative.
- Managers only. Reps never see peer comparisons.
Also in Measure
The whole product
What happened on the call, named as behavior.
Whether the behavior changed, with the confidence stated.
Where the system goes after V1. Not in the product yet.
