The Invisible Wiring: Mapping the Dependencies Your Org Chart Misses
Photo: Foreign, Commonwealth & Development Office, CC BY 2.0, via Wikimedia Commons
Most UK SMEs can draw their organisation chart in minutes. The boxes are familiar, the reporting lines are clear and the leadership team knows who owns which function. Yet the chart rarely shows the connections that determine whether the business bends or breaks: the supplier who quietly holds a critical certification, the finance analyst who is the only person able to reconcile a legacy system, or the informal handoff between sales and delivery that keeps a key account happy. These are the hidden dependencies — the ampersands between formal boxes — and they deserve the same scrutiny as any strategic plan.
Why the formal picture is incomplete
An organisation chart is a map of accountability. It answers the question of who reports to whom, but it does not answer the more operationally useful question of who or what depends on whom to keep work moving. In growing UK businesses, the gap between the two becomes wider as teams add tools, suppliers and specialist roles. Each addition is sensible in isolation. Together they create a web of connections that nobody owns and few people understand.
The consequence is not usually dramatic until something goes wrong. A key contact leaves, a supplier changes its terms, a software integration fails, or a team adopts a workaround that becomes permanent. At that point, the business discovers that a process described as straightforward in the operating manual is actually held together by one person, one contract or one spreadsheet. Mapping dependencies is therefore not an administrative exercise. It is a resilience exercise.
A one-page dependency-mapping exercise
The aim is to produce a single page that a leadership team can read together. It should be simple enough to complete in a focused session and useful enough to review quarterly.
-
Set the scope. Choose one customer journey, service line or operational process. Trying to map the whole business at once produces a diagram that nobody uses.
-
List the nodes. Include teams, key suppliers, systems, external partners and — where relevant — named roles rather than individuals. Keep the list to no more than fifteen or twenty nodes.
-
Draw the flows. Show how information, approvals, cash, materials or data move between the nodes. Use a solid line for a primary flow and a dotted line for an informal or secondary one.
-
Mark the ampersands. Place an '&' on each link that represents a dependency rather than a simple sequence. Ask: if this link failed, what would stop? Mark each as critical, important or convenient.
-
Annotate fragility. Note where a dependency relies on one person, one supplier, one custom integration, one undocumented process or one informal relationship. This is the information that turns a diagram into a risk register.
-
Agree the next action. For every critical link, assign an owner and a specific next step. The map should leave the room with decisions attached, not just observations.
The exercise works best with four to six people who see different parts of the process. A operations lead, a finance representative, a delivery manager and a customer-facing colleague will usually surface more than a single functional team. The discussion itself is valuable: it exposes assumptions that have never been tested.
Three red flags to watch
The map will reveal many dependencies. Three patterns deserve particular attention because they signal dangerous single points of failure.
The single-person bridge. This is a role that connects two teams, systems or supplier relationships and has no meaningful cover. The warning signs are familiar: holiday cover is improvised, the person is copied into every escalation and colleagues describe the process as 'quicker if we ask them'. The risk is not only absence. It is also concentration of knowledge and the difficulty of scaling a business that depends on one individual's memory.
The supplier or platform concentration. A business may rely on one supplier for a critical input, one platform for a core workflow or one integration that nobody fully understands. The red flag is not simply spend concentration. It is the absence of a tested exit route, a second source or a clear contractual position on service levels, data and continuity. In 2026, with technology and supply chains still shifting, convenience should not be mistaken for resilience.
The silent cross-team handoff. Some of the most fragile dependencies sit between teams rather than inside them. Sales hands a promise to delivery; operations hands a report to finance; a partner hands work to a subcontractor. If the handoff relies on email, a shared spreadsheet or an informal understanding, it is a candidate for failure. The warning signs are rework, repeated clarification and a lack of agreed service levels.
Turning the map into a 2026 action list
A dependency map is only useful if it changes priorities. The simplest way to convert it into action is to score each critical link on two dimensions: likelihood of failure and impact on customers or revenue. That produces a short list rather than an overwhelming programme.
Actions can then be grouped into a small number of categories. Document the process where knowledge is concentrated. Cross-train or introduce cover where a single-person bridge exists. Qualify a second source or negotiate stronger continuity terms where supplier concentration is high. Formalise service levels and escalation routes where handoffs are silent. Automate or simplify where a workaround has become permanent.
Each action should have an owner, a date and a measure of success. Review the map at the next quarterly planning cycle and update it whenever a significant supplier, system or team changes. The point is not to eliminate every dependency; that would be neither possible nor desirable. The point is to know which ones matter, which ones are fragile and which ones the business is prepared to carry into its next stage of growth.
That is the practical value of the '&' map. It makes the invisible visible, and it gives UK leaders a clearer basis for deciding where to invest attention before a quiet dependency becomes an operational surprise.
