“Deliver First” — When Questions Look Like Lack of Ownership

Project meeting. Olek questions the proposed way of doing the task and suggests a simpler approach. Zofia mainly wants to see the result delivered.

— Why are we doing it this way? We can make it simpler.
— Deliver first. Improve it later.

Olek hears that his initiative is not wanted. Zofia starts reading his questions as avoidance of responsibility.

What really happened

Zofia sees a lot of questions and debate from Olek, so she starts concluding that he lacks ownership. Olek hears her response as: she does not want ideas, she wants compliance. He therefore starts proposing less and asking fewer questions. Zofia sees the drop in initiative and gets what looks like proof of her original judgment: “I knew I had to keep an eye on him.” Olek gets proof of his own judgment: “I knew my input wasn’t wanted.” Each side’s initial assumption helps create the other person’s later behavior.

What the research says

Expectations about people can influence how we treat them, and that treatment can in turn affect their later behavior and performance. In workplaces, this has been studied as self-fulfilling managerial expectations, including Pygmalion effects and their negative counterparts (Eden, 1992; Kierein & Gold, 2000; McNatt, 2000). This scene is not a textbook Pygmalion experiment, but it captures the same feedback-loop logic: an expectation changes how someone is treated, then the person’s changed behavior appears to confirm the expectation.

How to handle it

Break the loop at the level of behavior, not labels. Zofia can define the phases explicitly: “During planning, I want your questions. Once we decide, I need execution by the agreed deadline.” Olek then knows when challenging the approach is a contribution and when it starts blocking delivery. Judge concrete evidence too: were tasks delivered, which suggestions were useful, where did discussion help or hurt? The general rule is: before deciding that someone’s behavior proves your judgment, check whether the way you have been treating them helped create that behavior.

How Empatyzer and Em can help

Empatyzer can interrupt this loop before “difficult employee” and “controlling manager” harden into labels for both sides. The assessment can show that Olek naturally brings questions, change, and initiative, while Zofia places more weight on pace, outcomes, and execution once a decision has been made. Profile comparison allows Em to define a clear boundary between when debate is expected and when delivery takes over. Zofia does not have to suppress initiative to get execution, and Olek does not have to stop contributing ideas in order to demonstrate responsibility. Team-level insights can reveal whether similar loops appear elsewhere. Micro-lessons help managers notice the moment when their own reaction begins producing the behavior they later treat as a fixed trait in the employee.