Skip to content
Interface language: English
Imperium / Signal

A dispute between departments: two reasonable goals can block one service

How to identify conflicting departmental goals, distinguish facts from missing resources and frame a shared service problem for a decision.

Article language: English

A hand adjusts a gold-colored mechanism beside a clear teardrop-shaped object, a pale sphere and a dark bowl.
In this article

Customer service replies on the same day. The studio does not start without approved material. Both rules sound reasonable. Trouble starts when “we'll take care of it” is taken as confirmation that work has begun, while the studio sees three unanswered questions in the order. The client waits, customer service chases, and the studio sends the request back. Everyone is attending to their own duty, but the service is stalled.

Imagine a company that prepares exhibition graphics. Account managers want to accept new work quickly so the organiser can plan the opening. The typesetting team needs to know which texts are final and who approves corrections. A disagreement starts over a particular panel, but the conversation soon turns to “they always promise” and “they never help”. Examples of fault replace the question of what the panel actually needs.

Start by reconstructing the tension between tasks before judging people's attitudes. Not every conflict can be solved this way. This article concerns conflicting goals and working conditions; it is no substitute for mediation or a response to inappropriate treatment of employees.

What each side is trying to protect

Ask both sides what outcome they are trying to prevent. An account manager might say: “If we don't acknowledge the request, the organiser will think there is nobody to discuss the opening with.” The studio might say: “If we start with a text that isn't final, a correction will change the layout of the whole panel.” These answers reveal more than saying that one side values speed and the other quality. They identify specific risks in the same case.

Then check what each side regards as finishing its own task. For customer service it may be passing the order to the studio. For the studio, work starts only when a complete set of materials is accepted. Between those points lies an area that can look both completed and not started in reports. The form need not be broken for a company to create this paradox.

A service map covering customer contact and back-office work can help. Here, however, the key question is what the handoff means. Does sending a file request an assessment, reserve capacity, or authorise work to begin? If the sides attach different meanings to the event, a more detailed process diagram will not settle the dispute by itself. See the guide to mapping a service and its backstage work (in Polish) for a related perspective.

In our example the studio could help before final materials arrive by assessing what remains unknown. That is a different task from typesetting the finished panel. Customer service could answer quickly, acknowledge contact and identify missing information. That answer need not promise delivery yet. The company has more options than starting immediately or remaining silent.

Facts, resources and the measure of success

A factual dispute sounds like: “That file was approved.” Find the message and check what the approval covered. Perhaps the client approved the text but not the layout, or the account manager sent an earlier version. There is no need to create a new collaboration policy at once. First establish what actually happened in this case.

A resource dispute is different: “We have nobody today who can assess an unusual format.” Even perfect material cannot create missing expertise or time. Urging the team to “communicate better” misses the cause. Someone must decide the order of work, a narrower scope or another way to handle the order. Each choice has consequences the client should know.

A dispute over the measure of success is harder to see. Customer service might be assessed on handoff speed and the studio on the number of jobs completed without later corrections. Both then have a reason to move uncertainty beyond their own part. Passing on an incomplete case improves one result; refusing it improves the other. The client's waiting time may appear in neither.

Research cautions against easy recipes. A 2012 meta-analysis by de Wit, Greer and Jehn distinguishes relationship conflict, conflict over work organisation and conflict over task content. The relationship between the last and performance depended on conditions. There is no basis for treating every heated exchange as a useful clash of ideas.

The practical question is what, precisely, the sides disagree about. A wrong file version, a missing person to assess it and contradictory measures of success call for different responses. Calling all of them “communication problems” makes them easy to name and harder to address.

One panel, not two indictments

Choose a case both sides can reconstruct. There is no need to start with the most dramatic story of the past few years. For the studio, a panel for which the client sent materials twice is enough. Check what was known at first contact, when the gap emerged and what was promised after it did. Label your interpretation as interpretation rather than adding it to the sequence of events.

A shared problem statement might be: “The client receives confirmation that we will deal with the request before we establish whether the studio can accept it for execution. When an additional assessment is needed, it is unclear who arranges it with the client.” This includes both departments' difficulty. It does not decide that customer service should stop replying or that the studio should accept every submission.

Aeneia conceptual photography

Now compare possible responses. One calls for a preliminary assessment of unusual orders before giving a date. Another separates acknowledgement of contact from acceptance for execution. A third permits a narrower initial scope, such as laying out an agreed excerpt. These are not three names for the same change. Each distributes work, waiting and the risk of repeating layout differently.

Not everything belongs in a compromise. If the studio has agreed that a particular element needs confirmed copy, “half an approval” helps nobody. You can, however, check whether the constraint applies to the whole order or only part of the work. The boundary remains clear without blocking work that can actually begin.

A 2001 longitudinal study by Jehn and Mannix concerned MBA student teams working on a project; many participants also had jobs. It found associations between conflict over time and performance, but the authors noted limits on causal inference and transfer to other tasks. It is not a timetable for disputes in a studio.

Test your proposal on its own task. Once the two confirmations are separated, can the account manager reply without inventing a delivery date? Does the studio see what assessment is requested? Does the organiser understand what they are waiting for? The answers help judge whether the new intake process addresses the disagreement.

Distinguish two stories that might look identical in a final report. In the first, the requested text was missing from the initial submission. In the second, the client supplied the agreed set and later changed some content. Both involve additional contact and repeated work. Only the first concerns acceptance of an incomplete order; the second is a change to an accepted case. A single count of corrections obscures the difference.

Suppose the account manager also knows a particular circumstance: the organiser is waiting for an author's approval of a caption. That may help plan partial work, but it should not remain only in a phone conversation with the studio. The handoff must state which fragment is pending and what the existing approval does not cover. Otherwise an exception can become a false precedent: a later order may cite the previous job as proof that the company started without complete material.

After comparing the cases, the company can keep its ordinary acceptance condition and allow a named, limited piece of work before the full set arrives. This responds to the difference between situations. It does not require declaring one department right in every earlier dispute or giving every account manager freedom to create exceptions independently.

Who can decide the cost of a concession?

A shared problem statement does not remove the difference in interests. A preliminary assessment takes studio time even if the order is not accepted. A later date confirmation may be harder for customer service. Someone must decide which cost the company accepts and in which cases. Without that authority, teams renegotiate the same rule for every order.

This calls for a process owner with defined responsibilities. A job title alone does not tell us whether the person can change intake criteria, reschedule work or correct a promise to the client. The person guiding the decision needs to know which consequences they may accept and which must be referred onward. For related guidance, see the guide to a process owner’s mandate (in Polish).

An expert becoming a leader faces a particular challenge. They may understand their former studio's reasons perfectly, but must now see the cost to customer service and the client as well. If they act only as their old team's strongest defender in every case, the new role remains unfulfilled. Expertise is needed to assess constraints; the decision concerns the wider service outcome. The article on an expert becoming a leader (in Polish) explores this question.

Also check whether the right recipient has disappeared from the conversation. The user, buyer and payer may expect different things. The organiser pays, the curator approves text, and an exhibition worker uses the finished panel. Quick acceptance by one person need not settle a question belonging to another. That is another reason not to treat every delay as departmental resistance. See the article on users, buyers and payers (in Polish) for a related perspective.

When conflicting rules reach AI

Suppose this fictional company uses AI to draft client messages. Customer service wants a quick, helpful response; the studio wants the system to flag missing material. If the tool is told to “confirm that the order will be fulfilled”, it may elegantly phrase a promise the team never agreed to. Correct language does not establish that it was authorised to send that meaning.

A sensible starting point is to trace one flow of information: where order data comes from, who assesses completeness, what the tool can propose and what a person checks. You can discuss your needs and the possible scope of an AI-use review with Aeneia Audit. The company can establish AI's role, verification and responsibility for using the result with reference to both teams' real work.

End the conversation with a choice that can be reproduced for the next panel. Who acknowledges contact? Who assesses whether the work can be done? How does the client recognise the difference? Where does a case go if it cannot be accepted through the usual route? If several people must decide, prepare a meeting for a specific decision with the consequences of each available answer visible. For related guidance, see the guide to a decision meeting (in Polish).

A returning dispute does not necessarily mean people ignored the agreement. It may reveal an order type the rule did not cover, or a cost the company had not noticed. Then the particular operating condition can be corrected. Assigning permanent character traits to departments is faster, but the panel still awaits its text and the client an answer they can trust.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear