I love this idea. Since most organizations track this annually, it makes sense to create a project for each user that sets up milestones on a quarterly basis and actually adds the specific development activity to a user's workload. Too often at review time a PDP is made, only to be forgotten until the review cycle is over, at which point both the user and their leader are reminded that they put together a great plan that neither followed up on. This introduces more accountability on both sides. Projects and reports/dashboards lend themselves easily to this concept, but I'm curious to know what kinds of request queues you have in mind for this? My first thought would be to contain all user's PDP project in a Development Portfolio for easier reporting and to separate T&D activities from project activities. You could also leverage project templates, such as onboarding new employees. If all users must have a core set of skills, those are added to the user's PDP project by attaching a "First 90 days" template, where each skill is listed as a task. As the user is verified for each skill, the task is marked done. We have a form of this already for onboarding/offboarding employees to ensure no procedural steps are overlooked. (Did you get Fred's laptop before he left? / No, I thought you did!) Please share your final design and I'd love to steal some ideas from that :) William English
If you like my content, please take a moment to view and vote on my Idea Requests: https://tinyurl.com/4rbpr7hf