Pathway Mapping Initiative

Learning activity was occurring in multiple places across the organization, owned by different functions, with no shared view of who was responsible for what.

Overlaps produced duplicated effort and contradictory guidance. Gaps went unnoticed because no one held a view of the whole. Employees could not determine which pathway applied to them.

This was a governance and visibility problem, not a content problem. No individual team was failing; the system had no map, no ownership boundaries, and no forum for resolving overlap.

• Designed the mapping methodology
• Conducted the analysis across functions and resources
• Documented workflows, overlaps, gaps, and ownership
• Presented findings and governance recommendations to stakeholders

I inventoried actual practice rather than documented intent, then represented the system visually so stakeholders could see their own position in it. Most of the resolution happened in the room once people could see the overlap they had been arguing about abstractly.

• Systems inventoryCataloging real activity, ownership, and resources as they exist.
• Overlap and gap analysisIdentifying duplication and unowned territory.
• Governance modelingProposing decision rights and maintenance responsibility.

Mapping is an intervention, not preparation for one. The act of making the system visible changed behavior before a single recommendation was implemented — which is why I now treat the map itself as a deliverable with its own value.