A retail company wants to change its returns process. The service director sponsors the work, branch managers explain the practical problems, finance examines the proposed credit arrangements, and an operations specialist tests how the change would work in stores. The reporting chart helps identify the people and functions involved. It does not describe the complete route from a proposal to an authorised change.
That is a reason to add a decision-flow view. It is not evidence that the chart is fictional or that every influential specialist has taken authority from a manager. Advice, professional judgement, formal approval, and control over resources can all shape a choice in legitimate ways.
A useful map shows how the relevant information reaches the people who need it, which roles can commit the organisation, and what happens after the answer. Comparing that route with the formal arrangement can reveal missing responsibilities, repeated waiting, or a sensible practice that needs clearer documentation.
Ask Different Questions of the Two Maps
An organisational chart primarily represents reporting relationships and structural groupings. It may indicate where to begin looking for a decision-maker, but the actual authority can come from delegations, policies, committee mandates, or other formal arrangements. A title alone is an incomplete account.
A decision-flow map follows a particular class of choice. For the returns process, it would show who develops the proposal, supplies evidence, assesses constraints, authorises the change, allocates implementation capacity, and communicates the result. Those roles may cross reporting lines.
Neither map needs to contain everything. A chart that attempts to show every recurring consultation would become difficult to read. A detailed process map should not be expected to explain all employment or reporting relationships. Together they can answer a more useful set of questions than either can alone.
Start with a decision whose consequences people recognise. Trying to map the entire organisation at once can produce a complicated picture without identifying which practical problem needs attention. A defined process and a few completed cases provide a manageable boundary.
Reconstruct the Actual Route From More Than One Account
Choose ordinary cases as well as unusually fast or difficult ones. Ask participants when they first received the issue, what they contributed, what they waited for, and what they understood the next role to be authorised to do.
Compare those accounts with the available record. The service director may remember approving the policy while branch managers remember a later operational condition that delayed implementation. Both can be accurate descriptions of different stages. The map should distinguish those stages rather than decide prematurely which account is the real decision.
Record the relevant version of the proposal. If finance assessed one arrangement and stores implemented another, the problem may concern change control or communication. A map of job titles alone would miss it.
A simple working table can organise the evidence:
| Stage | Question to establish |
|---|---|
| Proposal | What choice was being requested, and by whom? |
| Evidence | What information was required, and who supplied it? |
| Assessment | Which judgements or conditions had to be satisfied? |
| Authorisation | Who could make the relevant commitment? |
| Delivery | Who obtained resources and implemented the answer? |
| Review | Who checked the result and handled exceptions? |
Add waiting and return loops where they actually occurred. Avoid converting every contact into an approval or treating every period without visible activity as unnecessary delay. Some time may have been needed to produce relevant evidence.
Distinguish Expertise, Influence, and the Right to Decide
The operations specialist may identify that a proposed returns rule cannot be applied using the current till system. That finding can change the available options without giving the specialist unilateral authority over the whole policy. Their contribution is evidence with material implications.
A specialist may also hold an explicit approval right within a defined domain. In that case, record its scope and the route for resolving disagreement. The distinction matters because asking for advice and seeking mandatory agreement create different obligations.
Aghion and Tirole’s Formal and Real Authority in Organizations models the distinction between formal decision rights and effective control over decisions, including the role of information. It is a theoretical account. It does not imply that every expert who influences a proposal exercises an improper veto.
Ask what happens when the specialist is unavailable or disagrees. The answer may reveal a knowledge dependency, a formal control, an informal expectation, or uncertainty about the mandate. Those are different findings and should not all lead to the same restructuring proposal.
Bain’s RAPID framework separates recommendation, input, required agreement, decision, and implementation roles. It offers one vocabulary for making those distinctions explicit. Naming the roles still requires the organisation to establish usable authority and resources behind them.
Examine the Return Path and the Commitment to Act
A decision is not operationally complete just because the final meeting ended. Branches need to know which policy applies, when it starts, which exceptions remain, and how the system and training will support it. A flow map should follow the answer far enough to establish whether people could use it.
The service director might approve a preferred approach while implementation funding remains unsettled. That is a real decision, but it is narrower than approval to launch. Make the status clear so teams do not infer a delivery commitment that nobody has made.
Map objections after authorisation as carefully as those before it. A branch may raise new evidence that justifies reconsideration. It may instead be reopening a settled preference. The process needs a way to distinguish those situations without making every disagreement an unauthorised challenge.
For a committee decision, record the mandate and how a valid decision is reached. Collective authority can be legitimate. The map should show how it operates, which participants have defined responsibilities, and who communicates the outcome. It need not invent a single informal decider to make the diagram look simpler.
Use the Findings to Change a Specific Operating Problem
Suppose the map shows that all stores wait for one specialist to translate an approved policy into local instructions. The intervention might involve clearer guidance, training another person, or involving store representatives earlier. Moving the specialist’s reporting line may leave the actual dependency unchanged.
A different finding may concern authority. If nobody can commit implementation capacity, the organisation needs a resource decision or a clearer delegation. A faster information tool cannot supply that missing right.
Some informal practices are worth preserving. Branch managers may already share useful examples directly with the operations specialist. Making that route visible can help new staff participate, while the formal approval remains where it belongs. Documentation should improve access without requiring every useful conversation to follow a rigid sequence.
The related article on authority gaps examines missing or unusable decision routes. Mapping helps establish whether such a gap exists, instead of assuming that any difference from the chart is evidence of dysfunction.
Assess the information you collect appropriately. A diagnostic map needs enough detail to understand roles and decisions, not a record of every private conversation. Sensitive personnel matters and restricted material should remain within the relevant access arrangements.
Make the Route Usable Beyond Existing Relationships
An experienced branch manager may know which specialist to call before raising a returns proposal. A new manager may follow the published route and discover that the same conversation was expected but never described. This is an access problem even if the informal discussion itself improves the decision.
Publish enough information to make the useful route available: the relevant role, what evidence it needs, and how to obtain help when the usual person is absent. A contact directory alone is insufficient if people still cannot tell whether they are seeking advice or permission.
Check access to supporting records as well. A proposal may wait because its requester cannot view the current policy or the reasoning behind an exception. Provide appropriate access or an authorised source of clarification. The objective is a process people can navigate through their role and available evidence, rather than one that requires personal familiarity with the same few colleagues. Useful relationships can remain important without being the only way to obtain a decision.
Check the Map Against the Next Live Case
Test the revised route with a routine returns exception and a material policy change. Ask people to explain where evidence goes, who can authorise the commitment, and how they will learn the result. Differences can expose a remaining uncertainty before the next difficult case.
After the process operates, compare the map with what happened. A new return loop may reveal an omitted judgement or a poorly prepared request. A step that nobody uses may be obsolete, or participants may not understand why it matters. Investigate before removing it.
Keep the map current when mandates, systems, or resources change. Assign maintenance to a role with access to the relevant participants. Otherwise it can become a second outdated description alongside the chart it was intended to complement.
The connection to decision rights is practical: people need to understand their own contribution and the route beyond it. Reporting structure identifies relationships; decision flow explains how a particular commitment is prepared, authorised, implemented, and reviewed. Using both makes the organisation easier to navigate without pretending that either captures every source of judgement or influence.





