“A Suggestion or an Order?” — When Hierarchy Fills in the Gaps

Office, final checks before a launch. Samuel points Jonas to part of the solution that he believes should be changed.

— Jonas, maybe we should rethink this part?
— Sure.

Samuel walks away believing he has asked for a revision. Jonas reviews the issue and leaves the solution unchanged because he never heard a decision.

What really happened

Samuel phrases the message softly: “maybe we should rethink this part.” In his mind, his position and the situation give the sentence more weight — he expects a change. Jonas takes the wording literally: he has been asked to consider it, not required to change it. This is subtly different from article 03. There, a casual thought accidentally becomes a decision. Here, the speaker really does have an expectation but does not state it because he assumes his position will supply the missing force. Jonas refuses to make that inference.

What the research says

In a hierarchy, people often assign more weight to words spoken by someone senior than to the same words spoken by a peer, but they differ in how much they rely on that cue. Research on employee voice shows that status affects how people speak, what they raise, and how they respond to people above them (the hierarchy of voice; Pfrombeck et al., 2022). Research in high-risk teams also describes situations where differences in rank make it harder to challenge a message directly (authority gradient). The concept is useful here, but it does not mean every workplace behaves like an aircraft cockpit or a medical team.

How to handle it

Samuel should say what he expects without turning his style into something harsh: “Please change this part before launch. If you see a reason not to, come back to me.” Jonas can ask: “Is that a suggestion you want me to consider, or a decision you want me to carry out?” A team can also agree on a simple shared vocabulary: “idea,” “recommendation,” “expectation,” and “decision.” The general rule is: job title should not function as a hidden imperative; if you expect something, name the expectation.

How Empatyzer and Em can help

Empatyzer can catch the exact moment when Samuel’s polite style meets Jonas’s literal style and hierarchy makes the gap more consequential. The assessment alone may show a difference in directness, but comparing the two people and their roles lets Em see why “maybe we should rethink this” is especially risky: Samuel genuinely expects a change, while Jonas can reasonably hear an option. Before the conversation, Em can suggest wording that still sounds like Samuel but is operationally clear: “Please change this part; if you disagree, come back to me.” Jonas can get a prompt to ask, “Is that a suggestion or a decision?” If the same ambiguity appears across the team, Empatyzer can help build a shared language for levels of decision, while micro-lessons reinforce the habit until people stop guessing the weight of a message from tone and job title.