“My Schedule, Your Problem” — Autonomy Versus Shared Priorities

Morning at the task board. Olek moves one of his tasks to tomorrow so he can deal with an urgent client issue today. A moment later, Jonas discovers that the change prevents him from starting his own work.

— Who changed the order?
— I did. It made more sense.
— You can’t move things that my work depends on.

Olek believes he sensibly managed his own schedule. Jonas sees someone changing his schedule without telling him.

What really happened

Olek changes the order of his own tasks because he sees a more urgent issue and wants to help the client quickly. From his point of view, this is normal autonomy: the goal has not changed; he has simply found a better route to it. Jonas sees something Olek did not take into account at the moment of decision: Jonas’s work depends on Olek’s task. A change that looks like “my schedule” to one person becomes a blocker for someone else. The conflict is therefore not about whether Olek is allowed to decide for himself. It is about whether the decision is still solely his once it changes another person’s working conditions. Their profiles make the difference plausible: Olek naturally values freedom and quick replanning, while Jonas pays closer attention to sequence and dependencies.

What the research says

In team work, autonomy is rarely absolute because tasks are interconnected. The more one person’s output becomes another person’s input, the more a “private” decision becomes a team decision — task interdependence. A large meta-analysis of team research shows that the way these dependencies are structured affects coordination and team outcomes (Courtright et al., 2015). Research also suggests that autonomy and interdependence do not have to conflict, but they need to be designed together: people can have substantial freedom in how they work while still having clear points where changes must be communicated to others (de Jong, 2014). The issue is not “more control.” It is visibility of consequences.

How to handle it

The best rule is not “ask permission for every change,” because that destroys autonomy. Nor is it “do whatever you want,” because other people then absorb the cost of invisible decisions. A useful distinction is simple: if a change affects only your own work, decide for yourself; if it changes someone else’s timing, sequence, or ability to act, give them a quick signal. Often one chat message is enough: “I’m moving X to tomorrow, so your Y won’t start until the morning. Let me know if that breaks your plan.” The general rule is: autonomy should include the right to make decisions, but not the right to hide their consequences from people whose work depends on them.

How Empatyzer and Em can help

Empatyzer can help Olek and Jonas see that their argument about the schedule is really about the boundary of autonomy inside a network of dependencies. Olek naturally optimizes his plan around what seems most important at the moment; Jonas watches sequence more closely because his work depends on earlier steps by other people. With profile and task context, Em can prompt Olek before a similar change: “Does this affect only you, or does it block someone downstream?” If it affects others, the answer is not necessarily to seek approval for everything — it may simply require a quick heads-up and alignment. Team data can also reveal where different planning styles repeatedly collide with process dependencies. Micro-lessons reinforce a practical rule: autonomy is broad where the consequences are yours; when the consequences change someone else’s work, coordination begins.