When an employee is treated like a tool

‘I need two people by tomorrow’

In urgent workforce planning, a sentence like this may simply be shorthand. The problem arises when the shorthand becomes a whole way of thinking. An employee says the task cannot be completed without the data and hears, 'Your job is to deliver, not argue.' They try to explain the constraint, but their knowledge and experience carry no weight. In this example, the issue is no longer merely a tight deadline. The question is whether the person remains an active participant in the work or is merely expected to produce a result on someone else's orders. Objectification at work means treating a person in a way that reduces them to a function or tool. It can involve ignoring autonomy, needs, and subjective experience. It's not a synonym for every division of labor or efficiency requirement. Organizations need to plan staffing and evaluate the results. The real dividing line is whether, beyond their usefulness, employees retain a voice, the opportunity to explain the situation, and some influence over the conditions in which they perform their duties. Objectification does not result from the mere use of metrics, plans, or divided responsibilities. Each organization must coordinate its work and evaluate its results. What is important is whether there is room in this process for the perspective of the person performing the task. Can they explain constraints, flag risks, and influence how the work is carried out? Are their needs treated as part of the situation or merely as an obstacle to achieving the result? An employee does not have to make all the decisions to be treated as a person with agency. They do, however, need recognition that they have knowledge, boundaries, and goals of their own. Management becomes problematic when these elements systematically disappear from the conversation, and a person is judged only by their immediate usefulness to others.

Why a job title alone does not explain the problem

The studies of Andrighetto, Baldissarri and Volpato analyze objectification in the context of job characteristics. Belmi and Schroeder look at the instrumental perception of people in organizations. The literature allows us to separate the concept from the general dissatisfaction with the company. A person may be dissatisfied with a difficult task and yet feel respected as an autonomous person. They may also be well paid yet find that their perspective is ignored whenever it complicates a convenient plan. Andrighetto et al., 2017 Belmi and Schroeder, 2021. It is worth avoiding hasty conclusions based on language. The term 'human resources' does not in itself prove that a company objectifies its employees. On the other hand, a warm declaration that we're family doesn't guarantee respect. The decision-making process is more revealing: Is it possible to challenge an unworkable instruction, explain the error, and point out the support you need? Is the person still heard when their answer is inconvenient? These behaviors reveal how much weight the organization gives to that person's experience.

A metric helps until it replaces the whole job

Let's imagine a consultant being judged solely by the time of the conversation. If a longer interaction automatically counts as a worse result, there may be no room for a complex client problem. The consultant understands the circumstances, but the system gives them no way to explain them. This example does not prove that time measurement is wrong. It shows the risk of treating one metric as the whole truth while giving employees no way to contribute the knowledge needed to interpret it properly. Human agency can still be preserved in an environment requiring strict procedures. What is needed is clarity about where the rule is binding, where there is room for decision, and how to report an unusual situation. In high-security work, autonomy does not have to mean freedom. It may mean having the right to stop a process when a risk emerges and knowing that the report will be taken seriously. The employee remains accountable for the task but is not forced to act as though they have no knowledge or judgment. In everyday contact, small differences in wording can matter. The question 'How much more can you take on?' leads to a different conversation from 'What needs to change to make this work?' The first question is not necessarily harmful, but repeated without any interest in working conditions can reduce a person to their available capacity. Similarly, praise focused solely on availability can obscure an employee's judgment, responsibility, and knowledge. It is worth considering what the organization really appreciates. If the person reporting a boundary or risk is treated as less valuable, the message is clear. What is valued then is the person's availability for use, not their full contribution to sound execution and better collaboration.

What people notice when they are treated only as a resource

The signal can be the repeated experience that only availability matters and limits are treated as flaws. A request for clarification is labeled 'resistance', the need for rest becomes a lack of commitment, and suggestions for changing the process are not discussed. Not every single situation creates such a pattern. However, it is worth considering how often it happens and whether there is a way to correct it. If an employee repeatedly provides relevant information and is told each time that their job is simply to execute, the problem is with the management approach, not just the tone of the message. In a conversation, it is helpful to name a specific area of influence: I am accountable for the deadline, but I need to be able to agree on the sequence of tasks or I want the missing data I reported to be taken into account when evaluating the outcome. It does not guarantee change, but it clarifies the issue in dispute. If the manager cannot change the entire process, they can at least explain the constraints and escalate the problem. Pretending that an employee has a choice when they do not is no substitute for setting honest boundaries.

How to examine a process from the perspective of human agency

The organization may ask whether the employee understands the purpose of the task, has access to the necessary information and knows how to report an obstacle. It is worth checking whether an inaccurate assessment can be corrected and whether the people who do the work have a meaningful voice in designing procedures. These practices do not eliminate accountability or lower expectations. They help to use people's knowledge and avoid reducing employees to mere executors of someone else's plan. Respect then becomes a feature of the process, rather than an add-on to a message about results. Practical change can begin with matching responsibility to authority. An employee should not be liable for an outcome when they have no influence over the conditions that materially affect it without being able to report that discrepancy. Organizations also need to discuss about burdens and priorities, not just individual resilience. If another assignment is added, it is important to determine what can be postponed and who makes the decision. Treating employees as people with agency does not mean granting every request. It means that a refusal or requirement is supported by a clear rationale and the employee's perspective is actually considered. A person may not receive the preferred solution and yet be respected if they can present their arguments and understand the reasons for the decision.

Goals, procedures, or metrics do not automatically amount to objectification. Objectification occurs when utility overshadows human agency and experience. Good work organization combines clear requirements with the ability to clarify the situation, influence how the work is carried out and report constraints.

How Empatyzer supports conversations about influence and boundaries

Empatyzer can help you prepare a message about the conditions in which an employee performs their duties. In Talk to Em about yourself, the user can name a situation in which their perspective is overlooked and identify the change needed. It is helpful to move from a general sense of being treated as a resource to a specific issue, such as a lack of decision-making authority, with full responsibility for the outcome. Talk to Em about a specific person can then support the preparation of a request to agree on priorities, the scope of decision-making authority or the way to report overload. The available profile helps tailor the communication, but it is not an assessment of the manager's intentions. Empatyzer does not audit employment conditions or determine organizational liability. It helps prepare a conversation about what needs to change. Its effectiveness depends on the other party's genuine willingness to listen to arguments and take appropriate action in the organization of work.