Progression
Progression compares stored maturity snapshots with the active company's current maturity state. It shows movement across sessions and can also surface in-progress changes made after the latest completed snapshot.
When the page becomes available
With no assessed live state and no snapshots, Progression shows an empty state and a link to start a session.
Once an active conversation assesses dimensions, the page can show a current position even before the first completed-session snapshot. Finishing sessions builds the historical timeline.
Readiness over time
When at least two usable points exist, the line chart plots the average level across assessed dimensions for each snapshot.
If the live company state is newer than the final loaded snapshot, Navaid adds Now.
The velocity badge reports average-level change over the trailing 30 days:
- positive values indicate an increase;
- negative values indicate a decrease; and
- no badge appears when the available series cannot support the calculation.
Changing assessed coverage can also affect the average. Use the per-dimension view to understand the cause.
Current profile
The radar chart shows the latest current profile across 15 dimensions. Greater distance from the centre means a higher level; a balanced shape is not necessarily the correct strategic objective for every company.
Summary measures
The cards compare the first loaded snapshot with the latest state:
- Advanced — assessed dimensions whose latest level is higher;
- Unchanged — assessed dimensions at the same level; and
- Sessions — number of loaded snapshots.
They do not count every transcript message or active session.
Biggest movers
This list orders dimensions with upward movement by the size of their first-to-latest change and shows transitions such as L1 → L3.
No list appears if nothing advanced in the loaded comparison window.
Stuck at low levels
This identifies assessed dimensions that:
- remained unchanged from the first loaded snapshot; and
- are currently L1 or L2.
“Stuck” is a prioritisation aid, not proof that the team made no useful progress. Evidence may be accumulating without crossing a level.
Level changes table
Rows are the 15 dimensions. Columns are:
S1,S2, and so on for loaded snapshots; and- Now, when the live state is more recent.
Cells show L1–L5 or an em dash for unassessed. Date labels identify each snapshot.
The page currently loads at most 20 stored snapshots. If the company has more history, not every snapshot is represented in this view; the current company state is still used for the latest profile.
Sessions timeline
The timeline lists each loaded snapshot with:
- date and time;
- trigger, such as session complete, task complete, or admin edit;
- changed dimensions, when stored; and
- View session summary when the snapshot has a session reference.
A snapshot without a session link can still be valid if another supported trigger created it.
Compare with Session Summary
Progression and Session Summary answer different questions:
- Session Summary compares the start and end of one session.
- Progression compares maturity states across the loaded historical window and current live state.
An older summary remains a historical record even after Progression moves on.
Interpretation cautions
- Averages include assessed dimensions only.
- Newly assessing a low-level dimension can reduce the average while improving coverage.
- Reassessment can move a level downward.
- Completed task count is not the same as a maturity-level change.
- A mid-session Now point may change again before completion.
Troubleshooting
The chart is missing
At least two average-level points are needed for a trend line. The radar and grid can still be available.
Sessions count differs from the Sessions page
Progression counts loaded maturity snapshots, not every active, abandoned, legacy, or group-session record.
A recently completed session has no link
Refresh after summary generation completes. If the snapshot lacks a session reference, the timeline cannot construct a summary link.
A task completion did not create visible movement
Task status alone does not advance maturity. The page can record supported snapshot triggers, but maturity still requires evidence-backed state change.