بازخوردهای متناقض را رأی‌گیری نکنید؛ موقعیت‌ها را مقایسه کنید

This article is prepared by an AI-based persona acting as an advisor on organizational structure and order. Its starting point is simple: conflicting feedback about a manager does not necessarily indicate careless employees or an inaccurate account. The feedback may describe real experiences that occurred in different situations.

For example, a manager may be described as “controlling” by part of a team and “absent” by another part. A common response is to ask people to agree on which label is correct. That response turns a reviewable behavior issue into a broad judgment about the manager’s personality.

Counting how many people support one label does not improve the quality of the diagnosis. If several people encountered the manager in the same type of work, communication channel, or process stage, repeated opinions are not necessarily independent evidence about all work situations.

The unit of analysis should be the situation, not the label. Instead of recording that “the manager interferes too much,” clarify which decision was involved, how urgent it was, which channel was used, which role was affected, and what outcome produced that perception.

A simple record for each piece of feedback can include five elements: decision type, urgency level, communication channel, the feedback giver’s role, and the work outcome. Where useful, add the work stage and the stated level of authority. The purpose is not to build a case against a person; it is to make experiences comparable.

Decision type is the first important variable. Decisions about daily priorities, resource allocation, output quality, and accepting an external commitment are not the same. A manager who intervenes in high-risk decisions may be largely absent from routine execution decisions.

Urgency also changes how people interpret managerial behavior. When response time is short, a manager may centralize a decision quickly or bypass normal paths. If these exceptions are not recorded and later explained, people may interpret them as a permanent pattern of control or disorder.

The communication channel is part of the issue itself, not merely a detail. Intervention in a public meeting, a short message in a collaboration tool, a comment on a document, and a direct call affect people’s experience of authority and fairness differently. The same decision may appear supportive or intrusive depending on the channel.

A person’s role also determines which part of the manager’s behavior they see. Someone responsible for execution may view a missing timely decision as absence, while someone responsible for final approval may see the same manager immersed in details. Both observations can be true at once while pointing to different parts of the process.

The work stage should be recorded separately: initiation, design, execution, quality control, delivery, or exception handling. Many managers enter the details during a crisis but fail to clarify decision criteria and authority boundaries at the start. The result is late intervention and an early sense of abandonment.

The work outcome moves feedback beyond perception alone. Ask what happened after the intervention, or after its absence: Did the decision move faster or remain stalled? Did rework increase or decline? Did accountability become clearer or diffuse across people? These questions are not for blame; they are for observing design effects.

Feedback collection should not begin with labels. A useful prompt is: “Describe the most recent situation in which you needed the manager’s involvement to make a decision or move the work forward, or found that involvement excessive.” Then record the circumstances, rather than only the person’s final impression.

After collection, rewrite statements in neutral terms. For example, “the manager controls everything” can be recorded as: “During an output review before delivery, the manager made changes directly without previously stated criteria.” This rewrite makes process review and improvement possible.

The next step is to group comparable situations. Place feedback side by side according to decision type, urgency, channel, or work stage. You may find that perceptions of control occur mainly in decisions close to delivery, while perceptions of absence appear more often in early, low-urgency decisions.

These patterns should become testable hypotheses, not final judgments about the manager. For example, one hypothesis may be that authority boundaries are unclear at the beginning of work and the manager enters only after noticing risk. Another may concern misalignment among communication channels.

If the issue is authority design, the primary solution is not a general recommendation to “delegate more.” For each decision type, clarify the decision maker, required consultees, escalation timing, authority limit, and conditions for managerial intervention. Without these elements, delegation may merely transfer ambiguity from the manager to the team.

If the issue is communication, the path for announcing decisions and decision changes should be standardized. The team should know what is announced in which channel, which changes require an explanation, and when silence does not mean approval. Communication order makes sudden interventions less personal and more predictable.

A feedback conversation should not stop at defending labels. Rather than replying, “I am not controlling,” the manager can ask: “What decision was unclear in that situation, where did I enter the work, and what effect did that have on your work?” This shift returns attention to improving the work.

After the conversation, a behavioral follow-through loop is required. Select one or two specific changes, assign an implementation owner and a review time, and examine similar situations to see whether people’s experience has changed. Feedback that is not connected to later observation often creates only superficial agreement.

As a hypothetical example, if feedback shows that a manager gives direct instructions to team members for urgent customer requests but is unresponsive during internal planning, the solution is not simply to reduce messages. Clarify which requests are truly urgent, who gives the initial response, and at which point the manager enters the decision.

The review should remain focused on observable behaviors. Instead of asking broadly, “Has the manager improved?”, examine whether authority boundaries were announced before work began, whether interventions used clear criteria, whether decision changes were explained, and whether the final accountable person was known to the team.

Conflicting feedback is often scattered data from an unaligned system. By comparing situations, managers and teams can determine whether the issue lies in individual behavior, authority design, intervention timing, or a communication channel. This method moves the conversation from voting on personality to trackable improvement of the work.