DBASC INSIGHTS — MANAGEMENT ACCOUNTABILITY
How to establish clear accountability across departments
Sales has passed it on. Operations is waiting for clarification. Finance cannot invoice. Everyone can explain their own position, but who is responsible for getting the whole job completed?
By David Bowman — Founder of DBasc and co-founder of Zebsoft
Accountability becomes difficult when work crosses boundaries that the management structure treats separately. Each department has its own priorities, information and measures. The process depends on those parts working together, including the decisions made between them.
Clear accountability establishes who owns the outcome, who performs each activity and who can resolve a conflict or authorise a change. It also gives those people the information, authority and resources needed to act.
Start with the outcome that crosses the departments.
Choose a process with a recognisable beginning and end. For example, an accepted customer order becomes a delivered product, an approved service record and an accurate invoice. Agree what successful completion means before assigning ownership.
Then identify the departments, decisions and handovers involved. This reveals where a team can finish its local activity while leaving the wider outcome incomplete.
Ask where the work stops.
Who notices that progress has stopped?
Who is expected to resolve the cause?
Can that person make the necessary decision?
What happens if the departments disagree?
1. Give the overall process an accountable owner.
Identify a role responsible for reviewing the performance of the complete process and coordinating improvement across its boundaries. This person needs a clear remit, access to relevant information and a route to management when an issue exceeds their authority.
Department managers continue to manage their teams and activities. The process owner looks at how those activities connect, including delays, recurring disputes and failures that are difficult to see from a single department.
Make the arrangement achievable. If the owner cannot obtain information, convene the relevant people or escalate an unresolved conflict, the title alone will have little practical effect.
2. Define responsibility at the point of handover.
A handover needs an agreed condition for acceptance. Specify what information or work must be complete, where it is recorded and which role accepts it. Establish whether receipt is automatic or requires an explicit check.
Also define what happens to an incomplete submission. Who identifies the missing information? Who obtains it? Who keeps the customer or next team informed? Those decisions prevent an item being returned repeatedly without anyone resolving the cause.
Avoid leaving work unowned while acceptance is pending. The process should make clear who retains responsibility during that interval and when an unresolved handover must be escalated.
3. Match responsibility with decision authority.
People can be assigned an action without being able to complete it. A coordinator may be expected to recover a late job but have no authority to change the schedule, obtain extra resources or agree a revised commitment.
Identify the decisions the work depends on. Agree who can prioritise, approve, reject, release or authorise a departure from the normal process. Define any limits and the route for decisions beyond them.
Include cover for absence and a realistic decision timescale. A clear approval rule still creates a bottleneck if the authorised person is unavailable when the decision is needed.
4. Make competing priorities visible.
Departments may be encouraged to achieve outcomes that conflict. Sales pursues an early delivery commitment, operations aims to maintain a stable schedule and finance requires approved commercial information before release.
Each priority has a purpose. Management needs to establish how conflicts are resolved and which information is required before a commitment becomes binding within the process.
Review measures across the complete process. Alongside departmental activity, examine outcomes such as usable handovers, avoidable rework, time spent awaiting decisions and completion against agreed commitments.
5. Record actions so another person can understand them.
An action such as “operations to review” leaves the intended result, ownership and timing uncertain. Specify the required output, assign a named owner, agree a due date and identify dependencies that could prevent completion.
For example, “the operations manager will confirm production capacity for the revised order and provide an achievable delivery date by Thursday” makes the next decision clear. The relevant names and dates belong in the live action record.
Completion should be supported by the agreed output. Where an action is intended to prevent recurrence, include a later check that it has achieved that purpose.
ILLUSTRATIVE EXAMPLE
The customer changed the order. Who owns the consequences?
A customer asks sales to change a specification after the job has been scheduled. Sales emails the request to operations. Production continues using the original information, while finance holds the original price. Each team has a different view of the current agreement.
Where accountability is missing
The request has been communicated, but nobody has accepted responsibility for coordinating its impact. The process does not identify who approves the revised specification, checks cost and capacity, or confirms the change to the customer.
An email trail shows that people were informed. It does not establish that the change was assessed and authorised before work continued.
What a workable arrangement includes
Assign an owner to coordinate the request. Identify the technical, delivery and commercial approvals required. Define who decides whether affected work should pause and who releases the revised information.
Record the agreed change against the job and confirm that the affected teams are working to the same approved position. Review subsequent changes to check that the arrangement is being used.
This is an illustrative scenario, not a reported client result.
Will a responsibility matrix solve the problem?
A responsibility matrix can help make roles visible. Its usefulness depends on whether the people named understand and accept the arrangement, and whether it describes the decisions that matter in practice.
Test it against a real exception. If information is missing, an approver is absent or two departments disagree, can the team identify who acts next? If the answer remains unclear, add the decision rule or escalation route that is missing.
Keep the level of detail proportionate. Concentrate on important outcomes, decision points and handovers, then review the arrangement when the process or organisational structure changes.
Create a useful route for raising problems.
People need to be able to raise a capacity problem, conflicting instruction or unclear handover while there is still time to act. Establish where concerns go, what information is needed and who responds.
Management should examine the circumstances alongside individual decisions. Ask whether the requirements were clear, whether the necessary authority existed and whether the assigned work was achievable. That provides a sound basis for deciding what needs to change.
APPLY DEFINE, COMMUNICATE, ASSURE
Make accountability part of how the work runs.
Define
Agree the outcome, process owner, handover conditions and decision authority. Check that assigned responsibilities are achievable with the available people, time, skills and resources.
Communicate
Walk through the arrangement with the departments involved. Use examples to check that people understand when ownership transfers, what they can decide and how to escalate a problem.
Assure
Review actual handovers, delayed decisions and unresolved actions. Check whether ownership remains clear under pressure and whether the complete process achieves its intended result.
Start with one difficult handover.
Bring together the people sending and receiving the work. Review a recent example and agree what each side needs, when responsibility transfers and who resolves an incomplete submission.
Write the arrangement in language both teams recognise. Test it on subsequent work and review any exceptions with the process owner. Expand the approach once the first handover works consistently.
A shared system can support visibility of owners, decisions and outstanding actions. Define those arrangements before configuring the technology so the system reflects an agreed way of working.