Relationship Skills Action Plan

Your client has difficulty declining requests without producing a lengthy justification that often ends in partial compliance anyway. When a peer asks for their time, they say no in the first sentence and yes by the fourth. They know this about themselves. They can articulate why the over-explanation happens - discomfort with perceived rejection, concern about the relationship. But knowing the pattern has not changed the behavior. They need actual language to use, not more insight into why they do it.

Frame this as building the words first, the skill second. 'Insight about why you over-explain hasn't changed the behavior because in the moment, you don't have anything ready to replace it with. The worksheet gives us specific language for three scenarios you've named, so the words exist before the pressure arrives.' The resistance pattern: clients who over-explain often believe that the right answer is to learn to be comfortable with directness, rather than to prepare direct language in advance. Name that pre-scripted language is not a crutch - it is how skilled communicators prepare for recurring difficult moments.

Watch the 'Specific language I'll use' field for each scenario. If the draft language includes qualifiers ('I think,' 'maybe,' 'if it's okay'), the over-explaining habit is showing up on paper. Work through shortening and straightening the language together. Also watch whether 'How I'll know it worked' focuses on the other person's reaction - 'They didn't seem offended' - versus the client's own behavior - 'I said no in one sentence and didn't add a reason.' The former makes success dependent on the other person; the latter is within the client's control.

Read the Scenario 1 language aloud with your client and then ask them to say it without looking at the paper. The gap between what they wrote and what they say aloud is the rehearsal data. Then ask: 'What did you want to add that you didn't?' That addition is almost always the over-explanation pattern. The closing question: 'Which of these three scenarios is most likely to come up this week?' That identifies the first real-world test case for what they have prepared.

Your client gives encouragement when they mean to give feedback. They say 'you're doing great, just keep working on X' when they mean 'X is not working and needs to change.' Direct reports leave one-on-ones feeling good about the relationship but unclear about whether they are meeting expectations. Your client is aware of the pattern but has not built a replacement. When pressed for a specific example of a direct critical statement, they struggle to produce one. The gap is not courage - they want to be direct. The gap is language.

Frame this as building one direct sentence per recurring scenario. 'We're going to work on three specific situations where you currently deflect - and for each one, write the direct version of what you mean. Not the kind version, not the full conversation, just the sentence that actually communicates the performance concern.' The resistance pattern: managers who deflect to encouragement often believe that preparing direct language feels cold or scripted and will not sound like them. Name that it will feel scripted in practice sessions and natural in the actual conversation - that is the sequence, not the problem.

Watch whether the 'What I want to do instead' field for each scenario names a different behavior or just a better version of the same deflection. 'I want to be more direct while still being supportive' is a modified version of the same pattern. 'I want to name the specific performance gap before acknowledging what is working' is a different behavior. Also watch whether 'Specific language I'll use' contains a hedge that undermines the direction - 'I want to give you a heads up that...' softens what follows before it is said.

Ask your client to read each 'Specific language' entry aloud and then ask: 'If you received that, would you know that your performance needs to change?' If the answer is uncertain, the language is not direct enough yet. That is not a judgment - it is the calibration the worksheet is designed to do. Then ask: 'Which of these three scenarios has been avoided the longest?' That is the first real-world deployment case for what they have built.

Your client has a recurring conflict with a peer in another department - the peer is aggressive in meetings, takes credit for collaborative work, and shuts down your client's ideas in front of others. Your client has responded to this by withdrawing from collaborative meetings and working around the peer where possible. They know the withdrawal is not sustainable and is affecting their reputation. They have not yet had a direct conversation with the peer. They want to address it but have no idea what to say.

Frame this as preparing for three specific moments, not one big confrontation. 'The peer dynamic has several components - being shut down in meetings, credit allocation, and the ongoing relationship. We don't need to address all of it in one conversation. The worksheet helps you build specific language for each recurring moment separately.' The resistance pattern: clients who have been avoiding a peer conflict often frame the worksheet as preparation for a confrontation they are not ready for. Name that the three scenarios can be small and specific - 'what to say when my idea gets dismissed in a meeting' is different from 'how to confront everything that has happened.'

Watch whether the 'Typical reaction' field for each scenario is honest. Clients who are uncomfortable with conflict sometimes write what they wish they did rather than what they actually do. If the typical reaction is 'I try to respond professionally,' ask directly: 'What does that look like specifically - do you say something, go quiet, redirect?' Also watch the 'How I'll know it worked' field - clients with conflict avoidance often write outcomes that are entirely dependent on the peer's response. Help them reframe success as their own behavior: 'I said what I intended to say in the moment' is a controllable metric; 'they treated me better' is not.

After all three scenarios are scripted, ask: 'Which of these feels most manageable to try first?' Starting small increases the chance of a real-world deployment before the next session. Then look at the Development Focus section: 'What is the relationship skill you are actually building across all three of these scenarios?' The answer to that question names the larger work and gives the specific scenarios meaning beyond each individual exchange. Close with: 'When in the next two weeks is one of these moments most likely to come up?'