How managers see Journey progress for their direct reports — one report at a time, across every Journey they're on.
The manager view is scoped to direct reports and pivoted by person, not by Journey. Where an admin opens a single Journey to see everyone on it, a manager opens a single person to see every Journey they're on. That difference matters when the conversation is "how is this person doing" rather than "how is this program going."
The same blind spot from the admin side applies here: Journey progress doesn't surface on the standard assignment report. Managers who only check that report will think their direct reports aren't being tracked on Journey work at all.
For the strategic frame on Journeys overall, see Journeys In Continu.
How to Open a Direct Report's Journeys
1. Open the Manager tab. From the left-hand navigation, click Manager.
2. Select the direct report. Search for and click the name of the direct report whose Journey progress you want to see.
3. Open the Journeys tab. On the direct report's page, click the Journeys tab. You'll see every Journey this learner is currently assigned, with progress for each.
What to Look For
Progress on each Journey. the main column — how far the learner has gotten in each Journey they're assigned. Stalled progress on a high-priority Journey is the cue for a 1:1 conversation.
Multiple Journeys at once. If a direct report is on three or four Journeys simultaneously, look for the pattern across them. Stalled on all of them suggests workload or motivation; stalled on one suggests something specific about that program.
Completed Journeys. Use these as conversation starters in 1:1s and growth check-ins — completing a Journey is a milestone, not a row in a report.
Configuration Pitfalls
Using This as a Compliance Audit Tool. The manager view is built for coaching conversations, not org-wide compliance reporting. For audit and stakeholder reports, send the request to the program admin — they have the per-Journey view and the CSV export.
Treating Stalled Progress as a Performance Issue Without Context. A learner stalled on a Journey may be blocked by something the manager can fix (workload, priority signal, missing prerequisite). Open the conversation with curiosity, not consequences.
Only Checking When Asked. A monthly glance at direct reports' Journey progress catches stalled programs before they become overdue. Build it into the 1:1 cadence rather than waiting for a stakeholder ping.
Forgetting You Only See Direct Reports. A manager who oversees a broader function (e.g., skip-level direct reports) doesn't see those learners' Journeys in this view. Skip-level progress requires admin access or going through the intermediate manager.
Where This Fits
You're here because a direct report is on one or more Journeys and you want visibility into their progress. The admin-side counterpart — per-Journey rather than per-learner — lives in Tracking Journeys For Admins.
See Also
- Journeys In Continu — the strategic anchor.
- Tracking Journeys For Admins — the admin's per-Journey view across all learners.
- Assign a Journey — how Journeys get to learners in the first place.
- Creating Journeys — building the Journey, including the time delays that show up in this view.
Per-learner, scoped to direct reports. Use it for coaching conversations, not compliance audits.