What Should a Manager See in a Sponsored Development Plan?

What Should a Manager See in a Sponsored Development Plan?

A manager should see the structured parts of a goal: why it exists, where it sits (current role, profession, or next role), how it is measured, the hours committed, the first step, and whether progress has grown or held steady. A manager should not see reflections, check-in notes, or goals the person has chosen to keep private. That line is what makes sponsorship trustworthy enough for people to use honestly.

This matters more than it sounds. If sponsorship means a manager can read everything, people write safe goals and keep the real ones elsewhere, on paper or not at all. Self-determination theory points to autonomy as one of the conditions people need to stay genuinely motivated, rather than merely compliant (Self-Determination Theory, selfdeterminationtheory.org). A development plan that feels supervised rather than supported tends to produce the first kind of effort, not the second.

Why organisations sponsor plans at all

Sponsoring a development plan is usually about three things: making sure time and budget go toward something specific, giving managers a shared language for development conversations, and being able to say, honestly, that the organisation invests in people rather than only in output. None of those three requires reading someone's private reflections. They require visibility into the goal's shape and its measured progress.

Goal-setting research is clear that specific, measurable goals outperform vague ones (Locke & Latham, 2002), which is the real argument for structure. It is not an argument for surveillance.

What a sponsor can reasonably see — and what stays private

This is roughly the split used on Individual Development Plan platforms built for organisational sponsorship: the structure is shared, the inner working is not.

A worked example: a national sports federation and an athlete

Consider a federation that sponsors development plans for its athletes alongside training. An athlete might put a live goal under "current role" — tightening a technical weakness before the next qualifying cycle — with a measure the coach agrees on and a fixed number of weekly hours drawn from an already full training schedule. The federation can see that goal and its measured progress each cycle. What it should not see is the athlete's private notes on confidence, rivalry, or a parallel goal about life after competition. The structure supports the federation's interest in performance; the reflections remain the athlete's own, which is also roughly how this is handled for performing artists sponsored by a company or ensemble, where the stakes of being watched too closely are just as real.

The same split holds for a founder whose seed investor wants evidence of capability-building, or a first-time manager whose employer is paying for a leadership programme. The sponsor's legitimate interest is in the goal's structure and its trajectory, not in the person's unfiltered thinking.

What should a manager ask instead of "show me your plan"?

A development conversation works better when it is built around a small number of specific questions rather than a request to see everything:

1. Which goal is live right now, and why that one over the others?
2. What does progress look like, concretely, by the end of this cycle?
3. What's getting in the way of the hours you'd planned to give it?
4. Has anything genuinely changed since the last check-in, or has it held steady?
5. Is there a trade-off I should know about, if a second priority has come up?

These questions respect the private-public line while still giving the manager enough to help. They also tend to produce more useful conversations than "how's your development going," which invites a vague, reassuring answer.

How programme design should handle the line

Three design choices do most of the work:

• Cap visible goals. A default of up to three live goals, with a ceiling of five, keeps conversations focused rather than exhaustive.
• Separate the check-in from the review. A short, roughly three-minute check-in belongs to the person; a periodic review with a sponsor can draw on the same measured data without requiring raw notes.
• Report change honestly. If a measure hasn't moved beyond what could be ordinary noise, say "held steady" rather than inventing a story of growth, in the same spirit covered in measuring professional growth honestly.

Programme designers sometimes worry that privacy will make sponsorship feel thin. In practice the opposite tends to be true: people are more willing to set an ambitious, specific goal, as recommended by the goal-setting literature, when they know the private reasoning behind it is theirs to keep.

Where Jobulary fits

Jobulary is an Individual Development Plan platform from Bodhih Training built around this exact split: organisations sponsor plans, but reflections, check-in notes and personal goals are never visible to the sponsor. Goals go live with a reason, a measure, weekly hours from a stated budget, and a first step within seven days, following a practice-first 70/20/10 path sized to those hours.

Because the plan belongs to the person rather than the employer, it survives a change of job — which is worth knowing if you're designing a sponsorship programme meant to build real capability, not just retain someone for a quarter. For managers building their own skills in this area, it's worth reading alongside how to write a development plan for a first-time manager and how many professional goals should run at once, both of which sit well beside the privacy question covered here.