The critical distinction between making requests and setting standards
Managers tell me all the time that someone on their team does not respect their boundaries. When I ask what the boundary was, they describe a request. They asked for something. It did not happen. Now they feel disrespected.
The difference comes down to who owns the action. A request is something you want another person to do; whether it happens is entirely up to them. A boundary is something you will do yourself, no matter what the other person chooses. The action is yours, and you do not need their cooperation to follow through.
Firm language is where this gets confusing. A VP I worked with was exhausted by a team that drifted into meetings ten minutes late. She had told them many times, “Everyone needs to be on time. It is in your contract.” It sounded non-negotiable, but it was still a request because she was asking others to act.
We rewrote it together to prioritize both clarity and dignity: “I have noticed many of us are not arriving on time for the 9:00 a.m. meeting, but it is part of your employment requirements. From now on, I am starting at 9:00 sharp. If you are late, come in quietly, please. I will not recap, but the notes will be available. If you are late five times, I will have to write you up. Please let me know if you have any concerns.” Now the action was entirely hers. She owned the start time, the information flow, and the disciplinary consequence, but she kept the door open for honest communication. It worked whether one person was late or five were.
This shows up in our sales and negotiation cycles, too. A salesperson saying, “I need you to decide by Friday,” is making a request. The client feels pressured but not compelled. A boundary in this context sounds like: “This quote is valid until Friday. If I have not heard back by then, I will call to close the file so I can release this capacity to other projects.” One leaves you chasing a lead; the other keeps you in control of your calendar and your margin.
In a city the size of Halifax, where your client is also your neighbour and your kid’s soccer coach, the cost of fuzzy language compounds. People remember how you made them feel three years ago. When a leader makes their internal state dependent on other people’s compliance, they lose their ability to lead with clarity. That inconsistency shows up eventually in turnover, in reputation, and in the deals that quietly go to someone else.
To be clear, requests are highly valuable and a fundamental part of a healthy workplace culture. A team that can operate effectively on requests is a team with high trust. The problem is not the request; the problem is utilizing one when a boundary is actually required. We have to know the difference.
This is a skill. It gets sharper with practice. Pick one situation where you have been asking for the same thing for months without much changing. Run it through the Two-Question Check:
1. Am I describing what I will do?
2. Am I the only person who needs to act for this to be true?
If the answer to either is no, you have a request. Own it as one, or rewrite it until both answers are yes. When you stop outsourcing your peace of mind to other people’s compliance, you build a culture of high-dignity accountability that protects your reputation and your bottom line.
Learn more about Cyr Method at:
