A customer-service manager is asked to improve response times and reduce repeat contact. They can schedule the team and change some working procedures, but pricing, product defects, and staffing budgets sit elsewhere. Whether the role is workable depends on more than attaching those outcomes to the manager’s objectives.
The manager does not need unrestricted control over the business. They do need a clear account of what they can decide, which contributions other teams have committed to provide, and how unresolved trade-offs will be settled. Their performance should be reviewed against that arrangement and the evidence about what happened.
Authority and responsibility describe different parts of this design. Confusing them can lead to an unrealistic role, but treating every dependency as a defect is equally unhelpful. Most substantial work involves decisions and contributions distributed across several people.
Distinguish Authority, Responsibility, and Accountability
For this article, authority means recognised permission to make decisions or act within a defined scope. It can include approving expenditure, assigning work, changing priorities, or accepting an exception under an established policy. The permission has boundaries.
Responsibility concerns the duties and work assigned to a role. The service manager might be responsible for staffing the queue, maintaining guidance, reporting significant problems, and delivering a service plan. Some duties can be performed directly; others require coordinating contributions.
Accountability concerns being answerable for decisions, conduct, and results within the relevant arrangement. It includes explaining what happened, providing evidence, accepting appropriate review, and ensuring corrections are pursued. It should not be reduced to blame or a guarantee that every desired outcome will occur.
Organisations and frameworks use these terms somewhat differently. State the intended meaning rather than assuming everyone interprets a responsibility matrix in the same way. A shared definition helps clarify duties without settling every question about actual power or resources.
Formal Permission Is Different From Influence and Practical Capacity
An experienced adviser may strongly influence a decision without being authorised to make it. Conversely, a manager may have formal permission but lack the information, system access, funding, or available people needed to act.
Aghion and Tirole’s analysis of formal and real authority distinguishes formal decision rights from effective control influenced by information. It is a theoretical account of organisational arrangements, not evidence that every reporting structure produces a particular behaviour.
For the service manager, a title does not establish whether they can change shifts, hire staff, alter a refund rule, or prioritise a product correction. Each is a separate decision involving different resources and constraints.
Technical access also needs distinction. Being able to edit a price in software does not establish organisational permission to do so. Likewise, a delegated approval that cannot be exercised in the relevant system may exist on paper while remaining unusable in practice.
The decision-access article examines the information side of this problem. Role design needs both the formal scope and the conditions that allow it to be exercised competently.
Match Duties to Decisions Rather Than Seeking Total Control
Begin with a specific responsibility and trace the decisions it requires. For response times, those may include shift coverage, queue priority, escalation rules, and additional capacity. For repeat contact, the relevant decisions may include product corrections, guidance, and customer commitments.
An illustrative allocation might be:
| Duty | Local authority | Dependency needing agreement |
|---|---|---|
| Maintain daily queue coverage | Assign available staff within the roster | Additional staffing or changed opening hours |
| Keep service guidance current | Publish approved operational instructions | Product or policy decisions owned elsewhere |
| Resolve recurring customer issues | Investigate and recommend corrections | Delivery capacity in another team |
The dependency is not automatically a reason to remove the objective. It is a reason to establish how the other contribution is prioritised, who decides a conflict, and what happens if the commitment changes.
Some outcomes also depend on external conditions. A service manager cannot determine incoming demand or every customer response. They can be accountable for the quality of their assessment, actions, escalation, and adaptation without being treated as the sole cause of the final metric.
This approach makes accountability more precise. It preserves expectations while identifying which parts of the outcome require decisions elsewhere.
Delegate Authority With Boundaries and Continuing Oversight
Delegation should specify the decisions transferred, applicable limits, required information, and the route for exceptions. Assigning work without discussing those points can leave the recipient unsure whether they may act or merely recommend.
For example, the manager could adjust shift allocation within an agreed capacity while needing approval for additional expenditure. That gives meaningful discretion without transferring the entire staffing budget or removing necessary controls.
Delegation does not require a senior manager to stop overseeing the service. Different roles can be answerable for different aspects: the delegate for decisions within scope, and the delegating manager for the design, support, and monitoring of the arrangement.
Check capability before expanding discretion. A role may need training, access to specialist advice, usable records, and practice with exceptions before it can exercise a wider delegation competently. Giving permission without those conditions can transfer exposure without creating effective capacity. A limited initial scope with review may be appropriate while the capability develops.
The US GAO Green Book provides a public-sector internal-control framework covering organisational structures and responsibilities. It is one reference for thinking systematically about such controls, rather than a universal rulebook for every business.
Review the boundary when conditions change. A spending limit or staffing arrangement suitable for ordinary demand may become inadequate during a sustained surge. Repeated exceptions can indicate a need to redesign the delegation rather than a reason to abandon oversight altogether.
Some separation is intentional. The person requesting a purchase may appropriately be different from the person approving payment. That control does not by itself make the first role unworkable. The dependency needs a defined process, sufficient availability, and a way to resolve exceptions. Alignment means making the combination dependable, rather than removing every independent check in pursuit of complete local control.
Shared Work Needs an Explicit Method for Resolving Trade-offs
A product defect driving repeat contact may compete with another team’s roadmap. Both teams can understand the problem while lacking permission to make the resource trade-off themselves. A workable arrangement identifies the decision role or authorised forum that can settle it.
The solution need not be one person owning every aspect of the service. A joint body can make decisions if its mandate, participants, decision rule, resource commitments, and escalation route are clear. Informal agreement becomes fragile when nobody can explain how a contested decision becomes binding.
Distinguish consultation from approval. A specialist may need to provide evidence without having a general veto over unrelated priorities. Another role may hold a required approval within a defined domain. Make those differences visible so teams know what is needed to proceed.
The decision-rights article develops the design of those arrangements. The basic authority-responsibility question is whether the assigned duties have a usable route through the decisions they depend on.
Review Decisions and Conduct Alongside Results
A missed service target deserves investigation. Compare the agreed scope, resources, information available, decisions made, and changes during the period. Avoid assuming the result alone identifies either individual failure or a structural defect.
If the manager had authority to adjust coverage but ignored a known imbalance, that decision can be examined. If additional staff were declined after a documented capacity review, the review should include the decision to retain the service target and its consequences.
A constraint does not remove every duty. The manager may still need to communicate the likely effect, use available alternatives, and escalate within the agreed process. Equally, repeated escalation cannot substitute for a decision indefinitely when the issue exceeds local authority.
Keep records proportionate to the work. A useful decision note preserves the request, evidence, decision, owner, and conditions. Documentation can support learning and review; it should not become an exercise in collecting approvals solely to avoid any possibility of criticism.
Where facts are disputed, investigate them. Claims about resources, changed priorities, or earlier warnings are not inherently unfalsifiable. Budgets, task records, communications, and participants’ accounts can help establish what occurred.
Repair the Specific Mismatch
A role review should lead to a concrete change where one is needed. Options include transferring a decision, revising the objective, funding a dependency, improving information access, or providing an escalation route with the capacity to respond.
For the service manager, the most useful repair may be a commitment from the product team to assess recurring defects within a defined period, with a sponsor able to resolve priority conflicts. Giving the manager unrestricted authority over product development would solve a different problem and could create new ones.
Test the revised arrangement on real cases. Can the manager make ordinary decisions, obtain a binding answer on exceptions, and explain how the outcome will be reviewed? Can other teams identify their own commitments and limits?
Authority enables particular decisions. Responsibility identifies the work expected, and accountability establishes how decisions and results are examined and corrected. Aligning them means creating a credible arrangement for shared work, rather than promising complete control or assuming that assigning a name is enough to produce an outcome.
