Product · Development plans
Development plans that survive contact with the quarter
A plan is goals, activities and evidence — not a document that gets written in January and opened again in December. Progress is what was actually submitted and reviewed, so the plan reflects the work rather than the intention.
Dashboard
Profile
Team
PDPs
Reviews
Quests
Skills
Career MapPDPs
+ Create my PDP
PDPsMy active PDPs
1
Created by me
4
In your line
36
Goals with something under them
Each goal carries activities, and each activity carries evidence somebody submits. A goal with nothing under it reads as empty, because it is.
Managers review, they do not chase
Submissions arrive in one queue with the context attached. Approving, returning and commenting all happen in the same place, and every decision is recorded.
Every step on the record
Published, reviewed month by month, signed off: the plan keeps its own history, and every goal change goes to the audit log.
A plan is goals, activities and evidence
A development plan that is only goals is a wish list. Each goal here carries activities, and each activity carries evidence somebody actually submits. A goal with nothing underneath it reads as empty, because it is.
Progress is what was submitted and reviewed, not what was intended in January. That is the single structural difference between a plan that reflects the work and a document that gets opened twice a year.
← Back to PDPs
Ani’s growth plan · Apr 2026
Active16 Apr 2026 – 17 Oct 2026 · Reviewed monthly by Mher G.
Regulatory awareness
Track licensing requirements across our markets.
Managers review, they do not chase
Submissions arrive in one queue with their context attached. Approving, returning and commenting all happen in the same place, and every decision is recorded against the activity it relates to.
The failure mode this is built against is familiar: the plan exists, the work happened, and nobody wrote down that it happened, so at review time both people are reconstructing the year from memory.
Tied to skills that were verified
A plan aimed at reaching Advanced in a skill is measured against an assessment, not against an opinion. The target is a rung on a ladder that everyone in the organisation is measured against the same way.
That connection is what stops development planning drifting into a separate universe from capability data. The plan says where someone is going; the verified level says whether they arrived.
Every step on the record
Whoever manages a plan changes it directly when priorities move, adding, rewriting or removing a goal, and every change is written to your company's audit log with who made the change and when. The person the plan belongs to rates each goal out of five, and the rating stays on the plan where their manager sees it.
The plan also keeps a history both people can read: when it was published, each monthly review, when it went for final review and when it was signed off. Goal changes are not in that history; they are in the audit log, which is where an administrator looks when the question is who changed what.
Monthly goals (6)
Regulatory awareness
Plan history · Mher G. reviewed month 3 on 2 Sep.
Templates, and why they are only a start
There are starting shapes for the plans people actually need: moving up a level, growing into a lead role, closing one specific capability gap. They exist because a blank plan is the reason most planning stalls.
They are not a substitute for the conversation. A template that is filled in without either person thinking produces a plan that is complete and useless, which is harder to spot than one that is obviously empty.
New PDP
Employee
Duration
Transcript
Generate draftWhat good looks like after two quarters
The honest measure is not how many plans exist. It is how many have evidence attached to their activities, and how many goals closed because someone verified a level rather than because the quarter ended.
Both of those are visible without asking anybody. That is the point of putting evidence and verification in the same system as the plan: the reporting is a by-product of the work rather than a separate exercise in chasing people for updates.
Frequently asked questions
Does PDP Quest create personal development plans?
Yes, and each plan is goals, activities and submitted evidence rather than a document. Managers review submissions in one queue, whoever manages a plan edits its goals, with every change written to the audit log, and plans target levels that are verified by assessment rather than agreed in a meeting.
How does a plan get written?
From a conversation. A manager interviews the person — typed, or spoken and transcribed — and Piko drafts a plan of topics from it, which the manager edits before it is published. In Starter, managers write the plan themselves; the structure is the same.
Can employees push back on their plan?
Partly. Employees rate each goal out of five, and the rating stays on the plan where their manager sees it. They do not edit the plan themselves: whoever manages it makes the change, and every change they make is written to your company's audit log. The plan also keeps a history both people can read — when it was published, each monthly review, and when it was signed off.
What are quests and exercises?
Exercises are the practice work generated for a topic on a daily, weekly or monthly rhythm — quizzes, flashcards and scenarios. Daily and weekly ones are checked automatically; monthly scenarios go to the manager. Quests are goal-driven challenges an admin sets on top, with XP for completing them.
