Creating a Skill Map is just the beginning. Updating and using it regularly as you operate is what sets planned talent development in motion. This article introduces typical operational patterns with Dive.
For an overview of Skill Map, see What is Skill Map? / How to read Skill Marks.
Basic operational cycle
- Identify skills that need improvement: It's effective to prioritize skills where gaps are visible in your Skill Map
- Link related SOPs: If there are SOPs related to your target skill, link them from the skill definition. If not, capture a video and create a new SOP
- Update skill levels regularly: Evaluate and update each user's skills on a regular basis—for example, quarterly
Data helpful when evaluating levels
The following data is available for each user and can be referenced when updating levels.
- Linked SOP viewing completion history: You can also see question-answer results
- Manually entered training history: Entering information about work done on the job becomes material for evaluation. Both the user and administrators can enter this
Results against your plan (manual training records, level changes) are visualized per user.
Operational tips
- Make gap visualization your starting point: Planning development around "missing skills" makes priorities clear
- Strengthen your SOP library: The more SOPs you link, the more self-directed learning on skill development progresses. Also try bulk linking SOPs with AI
- Take quarterly snapshots: Regularly take snapshots of your Skill Map—for example, quarterly—to make review of changes and audit compliance easier
- Leverage Team-common skills: When multiple groups use the same skill, defining it commonly in the Skill Catalog simplifies cross-functional management