Close a Development Conversation With an Observable Commitment

A development conversation becomes useful when it ends with a behavior that can be seen in ordinary work. General intentions such as “communicate better” leave the employee and manager with different pictures of progress. Ask what the employee will do, where they will do it, and what record will make the attempt visible. Keep the commitment small enough to begin before the next meeting.

Rachel tells her manager, Paul, that she wants to grow her influence across the product group. Paul asks for an example of a meeting where she wanted more influence. Rachel describes a planning session in which she had data but waited until the agenda was almost over. Paul says, “What could you do in the next planning session that people would notice?” Rachel answers, “I will send the usage chart the day before and ask for five minutes near the start to explain one recommendation.” Paul follows with, “What will tell us whether you made the case clearly?” She chooses to ask two peers whether they understood the decision she wanted.

An observable commitment does not promise a career result. It creates a practice opportunity and a way to learn from it. The manager can offer access, feedback, or a chance to rehearse, while the employee retains ownership of the action. If the person needs technical instruction or a formal program, identify that support separately.

Rachel will send her chart by Tuesday and place her recommendation in the meeting agenda. After the session, she will note the question she received and the decision made. Paul will spend ten minutes with her that week reviewing those facts and asking whether the preparation helped her enter the discussion earlier.