How Do You Run a Development Conversation When You Can't See the Plan?
You ask about support, obstacles and the next step, not the content of the goal itself. The employee decides what to share. The conversation works best when it is short, regular, and tied to the plan's own check-in cycle rather than to a separate performance calendar.
This is a common sticking point once an organisation sponsors development plans but keeps reflections and personal goals private, as described in How Do Organisations Protect Privacy in Sponsored IDPs?. Managers are used to reviewing content. Here, they review conditions instead.
What is a manager actually trying to find out?
Three things, and nothing more:
- Is the person stuck on something I can remove? A budget approval, an introduction, a blocked calendar.
- Is the time allocation still realistic? Plans are sized to a stated weekly hours budget; if work has crept past that, the plan will stall regardless of intent.
- Does the person need a different kind of support than last quarter? Early on this might be access to a mentor; later it might be protected time for the practice-heavy 70% of a 70/20/10 plan.
None of these require seeing the goal's wording, its measure, or the check-in notes behind it. Locke and Latham's review of goal-setting research found that feedback on progress improves performance mainly when it is specific and tied to a standard the person has accepted (Locke & Latham, 2002). A manager can provide that kind of feedback on conditions — time, access, obstacles — without needing the underlying data.
A structure that respects the boundary
| Minute | Question | What you are listening for |
|---|---|---|
| 0–2 | "How has the time been going against what you planned?" | Whether the hours budget is being protected or eroded |
| 2–5 | "What's got in the way, if anything?" | A specific, removable obstacle, not a vague complaint |
| 5–8 | "What would help most in the next few weeks?" | A concrete ask: access, time, a conversation with someone else |
| 8–10 | "Anything you want me to know for your performance review, separate from this?" | A deliberate line between development support and evaluation |
Ten minutes is usually enough. This is not a substitute for the three-minute check-in the person does themselves inside the plan; it is a separate, shorter conversation about the environment around the plan, held perhaps once a quarter.
Why the separation holds up
Self-determination theory distinguishes autonomy-supportive environments, where a person retains ownership of their goals, from controlling ones, where someone else directs the content (selfdeterminationtheory.org). A manager who asks "what do you need" rather than "what are you working on" is operating in the first mode. This matters practically: a plan that belongs to the person, and survives a change of employer or manager, only stays honest if the person believes their reflections will not be read, scored or repeated in a performance review.
Consider a touring musician on a sponsored plan of this kind. Their manager at the agency cannot see that the goal is about breath control for a demanding passage, or that a recent check-in notes anxiety before a particular venue. What the manager can see, and usefully act on, is that the musician needs three uninterrupted hours before a show and has said so. That is the whole conversation. The same logic applies to an athlete and a performance director, as explored in A Development Plan for Professional Athletes — the coach manages conditions, the athlete manages content.
What this means for programme design
Organisations sometimes try to solve the "manager can't see it" problem by building a dashboard summary instead. This usually drifts back into content, because summaries invite questions about the summary. A cleaner design keeps the manager conversation entirely separate from the system that holds the plan, with its own short agenda and its own quarterly rhythm, aligned loosely to the plan's 90-day cycle but never pulling data from it.
It also means training managers on one distinction they may not have needed before: distinguishing a performance conversation (which they own) from a development support conversation (which they facilitate). What Should a Manager See in a Sponsored Development Plan? covers the visibility question in detail; this one is about what to do once you've decided they see nothing but the request for help.
In Jobulary, sponsored plans are built on exactly this boundary: the plan belongs to the person, check-in notes and reflections stay private, and sponsors never see them. Managers who want to support development well are better served by a short, scheduled conversation about hours, obstacles and access than by access to the plan itself. See how it works for how the sponsor and individual sides are kept separate.
Frequently asked questions
What should a manager actually ask in these conversations?
Ask what support is needed, what is getting in the way, and what the next step looks like. Avoid asking for the goal's wording, the measure, or check-in notes, since these belong to the employee under most sponsored IDP arrangements.
How often should managers hold development conversations?
Roughly every 90 days works well, matching the shorter end of a typical 90/180/365-day plan cycle, so the conversation has something fresh to discuss without becoming another status meeting.
Does privacy make the conversation less useful?
Not if the manager focuses on support rather than content. Self-determination theory suggests autonomy-supportive conversations, where the person retains ownership of the goal, tend to sustain motivation better than directive ones (selfdeterminationtheory.org).
Sources
Topics: Individual Development Plan · Learning and development