Organizational consulting examines how responsibilities, decisions, processes and working relationships affect an organization’s performance. It is useful when work crosses departments but ownership remains unclear. This article explains how to define the assignment, compare consultants and accept useful outputs. The aim is to fix an operating problem through evidence, rather than begin with an attractive organization chart.
Define the organizational problem
Organizational consulting is a professional assignment to assess how an organization works and recommend changes within an agreed scope. Organization design focuses on aligning organizational arrangements with strategy. Organization development places greater emphasis on the planned development of people, relationships and organizational capability. An assignment may involve both, but its boundaries should be explicit.
Describe the problem through observable events. Examples include customer requests circulating between departments, duplicated approvals or decisions repeatedly returning to the owner. “Our culture is weak” is too broad to diagnose without examples. Record the affected work, frequency, consequences and people involved.
Use a fictional distributor as an example. Sales promises delivery dates before checking warehouse capacity. The resulting delays may involve decision rights and handovers, not simply poor attitudes. Replacing the department names on a chart would not resolve that failure.
Ask for a diagnosis before a new structure
A useful review combines documents, interviews and observation of actual work. Compare the approved procedure with what staff must do to complete a transaction. Include the people receiving the output, not only department heads. Explain confidentiality and how interview findings will be reported.
The consultant should distinguish evidence, interpretation and untested assumptions. Ask how contradictory accounts will be investigated. A single senior person’s explanation is a starting point, not a complete diagnosis. Check whether the proposed change addresses the cause or merely relocates the workload.
Write a brief that limits guesswork
| Brief element | What to specify |
|---|---|
| Problem | The work failing and its consequences |
| Scope | Processes, locations and roles included or excluded |
| Evidence | Available records and access arrangements |
| Outputs | Diagnosis, options and implementation responsibilities |
| Acceptance | How each output will be reviewed and tested |
Name an internal sponsor with authority to resolve scope questions. Assign a working contact who can arrange access and consolidate comments. The consultant can facilitate choices, but management remains accountable for organizational decisions.
Compare consultants using the same problem
Provide shortlisted consultants with the same brief. Ask each to explain their diagnostic approach, relevant experience and proposed team. Request examples of the type of output they produce, with confidential details removed. A polished presentation is not evidence that the proposed method fits your problem.
Compare assumptions, exclusions, effort, fees, client responsibilities and change control. Clarify whether implementation, staff communication and follow-up are included. Ask who will perform the work after the sales meeting and how replacements would be managed.
Check declared conflicts, confidentiality arrangements and the handling of employee information. Do not request confidential material from another client as proof of experience. References should be shared with permission.
Require outputs that people can use
In the distributor example, useful outputs might include a map of order acceptance, named decision owners and a rule for confirming capacity. Role descriptions should explain responsibilities and interfaces, not merely provide new titles. Include unresolved decisions so management can address them.
Compare alternatives before choosing a structure. Centralizing approval may improve consistency but create a bottleneck. Delegating approval may shorten waiting time while requiring clearer limits and competent staff. Record the trade-offs and the reason for the chosen arrangement.
Test the new arrangement before extending it
Run a limited pilot with representative cases. In the distributor, sales and the warehouse could test the new order-confirmation process on one suitable product line. Check whether staff know who decides, what information is needed and when to escalate exceptions.
Measure actual waiting time, rework and unresolved handovers against a documented starting point. Check unintended effects, such as reduced flexibility or additional administrative work. A faster approval is not an improvement if errors increase elsewhere.
Communicate what changes, what each role must do and where concerns can be raised. Where proposed changes affect employment terms, obtain appropriate HR and legal review before implementation. Consulting recommendations do not replace the organization’s obligations.
What changes in decision ownership?
In the fictional distributor, sales previously promised a delivery date and then asked the warehouse to meet it. Under the revised process, sales confirms the quantity requested, the warehouse owner confirms availability and handling capacity, and sales communicates the confirmed date. Changes to an accepted delivery commitment require the designated internal approval and agreement with the customer through the authorised contact; merely notifying the other department is insufficient.
If an urgent request conflicts with existing commitments, both teams submit documented options to the operations manager: change the date, use an alternative supplier with the cost stated, or decline the order. The authorised owner records the decision and reason. Set an escalation response time and a named deputy within approved authority limits, so another approval does not simply become another bottleneck.
For a clear pilot measure, count late orders against all orders originally due in the same review period, including orders still undelivered. Keep the original promised date and record any agreed revision separately; moving the date must not erase the original delay. In a fictional baseline, 6 late orders out of 40 due equals 15%. If the pilot records 3 out of 40 comparable orders, the rate is 7.5%, a reduction of 7.5 percentage points. Review product mix, capacity, errors and customer complaints before attributing the change to the new arrangement. Set the target and review period before the pilot; these illustrative figures are not a benchmark or proof of sustained improvement.
Assign follow-up ownership after the assignment
Before the consultant leaves, name who receives staff questions, reviews exceptions and can amend the documents. Retain the approval decision, the reason for the selected arrangement and unresolved issues. Review a sample of transactions after implementation to check that agreed authority is being used. If staff return to the old process, investigate what prevents implementation instead of simply sending the chart or procedure again.
Make handover part of acceptance
Agree acceptance criteria for each deliverable before work begins. A diagnosis-only assignment may be accepted when the evidence, analysis and options meet the agreed criteria; it should not be judged as if implementation were included. Where the scope includes implementation and handover, test whether responsible staff can use the approved outputs. Record gaps, who will resolve them and the acceptance decision under the contract.
Assign document owners, a review date and a route for exceptions. Transfer editable files and explain how to maintain them where this is part of the agreement. An organization chart alone is insufficient when the original problem concerns decisions and workflow.
Start by mapping one repeated cross-department failure. Use business process documentation to make the work visible and job descriptions to clarify responsibilities. ATMACSS’s business and operation modelling service provides a relevant starting point for discussing an organizational assignment.