In this guide
Start with the expectation
A useful development conversation has an expectation to discuss. Identify the task or responsibility, what was understood to be expected and the evidence available about the result. Syracuse's public workshop pages describe Performance Partnership learning for staff, and its position-evaluation page links role descriptions with responsibilities. This article supplies an independent preparation method, not the university's form or rating system.
Do not infer a current deadline from an old announcement. Use the employer's current instructions for the actual process. A personal preparation note should help the conversation, not create a parallel evaluation or claim authority to change a job description.
Bring three different kinds of evidence
The first kind is completed work that illustrates an expectation. The second is a difficulty that needs clarification. The third is a development goal grounded in a real task. Keep each example specific. A collection of only successes can conceal the most useful question; a collection of only problems can obscure work that is already dependable.
In a hypothetical exercise, a person improved a public instruction, encountered uncertainty about who approves a change and wants to practice clearer handovers. The three points connect work, boundaries and learning. They do not establish a performance score or show that a promotion should follow.
Separate result and interpretation
Describe the observable result before deciding what it says about your performance. If a team achieved an outcome, identify your contribution. If another person reviewed the work, distinguish their feedback from your own interpretation. Use numbers only when their source is clear and sharing them is permitted.
A useful question might ask what evidence would demonstrate progress on a particular responsibility. It should not assume that a broad trait such as initiative has one universally measurable meaning. The appropriate supervisor and current process establish the expectations for the real role.
Leave with a checkable next step
A development goal is easier to use when it names a task, an appropriate practice opportunity and a review point. Keep the scope realistic and within authorization. Do not promise an institutional change, expenditure or outcome that neither participant has approved.
The preparation note is successful if it supports a clearer conversation about work and learning. It does not determine compensation, classification, continued employment or promotion. Those matters have their own policies and authorities. A small set of well-labeled evidence can be more useful than a long narrative that leaves the next question unclear.
Before the conversation, check that each example has a date or period and a source you may appropriately discuss. That small preparation makes it easier to distinguish a recurring pattern from a single event or an impression.
Continue reading: Build a first-term map of responsibilities, A pay band and a vacancy range are different evidence, A repair, a quote and a project are different requests.