Outsourced CompanyPowered by StealthAgents

Philippines staffing research · Published · Updated

How dual managers fragment an outsourced role's priorities

Two managers can each give clear instructions and still leave the role without a priority. The conflict appears in small delays, repeated work, and a queue that follows the loudest voice.

Two managers discussing priorities with a coordinator in a meeting room

Research findings

A delegated role often reports to two people because the work crosses two functions. One manager owns the customer relationship and the other owns the process. Each has a legitimate view of what matters, and each can give a clear instruction. The problem is not that either manager is unclear. The problem is that the role receives two clear instructions that cannot both be first.

The first symptom is a queue that follows the loudest voice. The coordinator completes the task from the manager who asked most recently or most forcefully. The other task waits, even when it has a closer deadline. The coordinator is not being careless. They are making a reasonable choice in the absence of a rule. The queue records the choice as a delay, not as a conflict.

The second symptom is repeated work. One manager asks for a report in one format, and the other asks for the same data in a different format. The coordinator produces both because neither manager knows about the other request. The duplication looks like inefficiency, but the cause is a missing agreement about the output. The role absorbs the cost of the disagreement.

The third symptom is a slow decision. A customer issue needs an answer that touches both the commercial relationship and the process standard. Each manager waits for the other to decide, and the coordinator waits for both. The case ages while the managers assume someone else is handling it. The queue shows a delay, but the real issue is an unclear decision right.

The fourth symptom is a change in the role itself. The coordinator learns which manager to ask for which exception, and the informal map becomes the real process. A new person cannot see the map, so they escalate to the wrong manager or ask both. The role becomes harder to hand over, and the dependency on specific people grows.

Dual management is not automatically wrong. It can work when the split is explicit and the role has one place to resolve a conflict. The design needs three elements: a primary manager for priorities, a defined scope for the second manager, and a tie-break rule for the cases that overlap. Without those elements, the role carries a conflict it cannot resolve.

Discussion

Choose one primary manager for day-to-day priorities. That person sets the order of work when two requests compete, and the coordinator can point to that authority. The second manager can still set standards within their scope, but not the overall queue order. The distinction should be written so both managers can explain it the same way.

Define the second manager scope in terms of decisions rather than topics. A topic such as quality can be broad enough to cover the whole role. A decision scope such as approving a refund or changing a template is easier to apply. Write examples of decisions that belong to each manager and decisions that need both.

Write a tie-break rule for the overlap. The rule can say that customer commitments take priority over internal reporting, or that a regulatory deadline takes priority over a scheduled review. The rule should be specific enough to apply without a meeting. When the rule does not cover the case, name the person who decides and the time limit for the decision.

Give the coordinator a way to record a conflict without choosing a side. A short note with the two requests, the deadlines, and the manager who needs to decide is enough. The note should go to both managers, not just the one who asked first. Visibility reduces the chance that the same conflict is resolved twice in different ways.

Implications and limits

Review the conflicts monthly and group them by cause. A repeated conflict about report format is a template problem. A repeated conflict about customer commitments is a priority rule problem. A repeated conflict about exceptions is a decision-rights problem. Each cause has a different fix, and the pattern is more useful than the individual disagreement.

Measure the effect of the split on the queue. Look at the number of cases that wait for a decision, the number of duplicated outputs, and the time between a request and a clear owner. Compare those measures with a role that has one manager. The difference is the cost of the dual structure, and it should be weighed against the value of the second perspective.

The best dual-management design is boring. The coordinator knows who sets the order, what the second manager can change, and how a conflict is resolved. The managers know the same rules and use them consistently. The role still has two stakeholders, but it no longer has two competing priorities disguised as clear instructions. That predictability is the point, because the role needs a stable rule more than a clever one.

How priority conflicts appear

Conflicts appear as delays, duplicates, and workarounds rather than as open disagreements. A delayed report and a repeated data pull can both be symptoms of the same priority gap. Look for cases that were completed twice or that waited for a decision that never had an owner. The pattern is easier to see in the case history than in a conversation with either manager.

Ask the coordinator to describe the last three times they had to choose between requests. The examples reveal the informal rule they are already using. That rule is the starting point for a written version. Ignoring it produces a policy that nobody follows because it does not match the real work. Write the examples down and compare them with the managers' account of the same weeks.

Choosing one accountable manager

Pick the manager who owns the outcome the role primarily serves. If the role exists to support customers, the customer manager should set the queue order. If the role exists to protect a process, the process manager should set it. The choice should follow the purpose of the role, not the seniority of the manager.

Publish the choice to both managers and to the coordinator. State what the primary manager decides and what the second manager decides. A private agreement between managers will not survive a busy week. The coordinator needs to be able to name the authority without apologizing for it. A public choice also makes it easier to notice when an old arrangement returns.

Writing a tie-break rule

Write the rule with two or three real cases and the decision for each. Keep the rule short enough to remember and specific enough to apply. A rule that says use judgment is not a tie-break because it returns the conflict to the coordinator. The rule should produce the same answer from either manager.

Review the rule when the business changes. A new customer commitment or a new regulatory deadline can change the order. Update the examples at the same time so the rule stays usable. A tie-break rule that is never reviewed becomes another source of ambiguity. Put the review date beside the rule so it does not depend on someone remembering.

Costs of consolidating

Consolidating to one manager reduces conflict but may remove a useful check. The second manager often sees a risk that the primary manager misses. Keep that perspective as a review rather than a second priority. The role can receive input from both without receiving two queues. Keep that check as a scheduled review with a clear question, not as a second queue.

Consolidation also changes the relationship with the second manager. They may feel excluded from decisions they used to influence. Define the review points and the decisions they still own. A clear scope is more respectful than an informal arrangement that keeps everyone guessing. Explain the change in writing and confirm which decisions still sit with them.

A monthly conflict review

Hold a short monthly review with both managers and the coordinator. Read the recorded conflicts, the decisions that were delayed, and the work that was duplicated. Ask which rule would have resolved each case without a meeting. The review should produce one rule change, not a general discussion about communication. Keep the meeting to thirty minutes and end with one owner for each change.

Track the number of conflicts that needed escalation and the time they waited. A falling count is evidence that the decision rights are working. A count that stays flat may mean the rule is unclear or the managers are still using the old path. Publish the trend so both managers can see the effect of the change.

Questions

Can a role report to two managers?

Yes, if one manager sets the queue order and the second has a written decision scope. The role needs one place to resolve a conflict.

What is the first sign of a problem?

A queue that follows the most recent or most forceful request. The coordinator is usually making a reasonable choice without a rule.

Who should own the tie-break rule?

The primary manager, with input from the second. The rule should be published and tested on real cases.

Does dual management always slow work?

No. It can add a useful perspective when the scope and the decision rights are clear. The cost appears when the role receives two competing priorities.

Philippines staffing intake

Define the position before hiring begins.

Share the tasks, tools, schedule, and approval limits for your Filipino team member. The intake turns those details into a practical staffing brief.

Contact Us