Key person risk shows up first as a Tuesday morning resignation. Your best logistics coordinator handed in her notice on a Tuesday. By Thursday, you were quietly rearranging the duty roster. By the following Monday, the commercial director had stopped by your desk to ask, more carefully than he would have liked, whether the programme would still run properly during the four-week handover period. The question was not framed as a threat. It did not need to be. You and he both knew the answer was mostly, with some gaps, and please do not ask me to be more specific.
The coordinator who resigned was not the only person in the operation. There are twelve others. But she was the one who knew, in her head, how three of the most demanding customers liked to be communicated with. She was the one who maintained the rail-consist forecasting logic in the master workbook. She was the one who had built the informal relationship with the port scheduler over five years, and who could get a berth swap agreed with a phone call, where anyone else would need three emails and a day. Her departure was not just a staffing gap. It was a capability gap that the organisation had not named and could not easily close. That is what key person risk looks like when it finally arrives.
In most bulk commodity operations, key person risk is understood as an HR issue: a problem to be managed through succession planning, cross-training, and salary retention. This post argues that in a workbook-and-expertise-run logistics operation, key person risk is not an HR issue. It is an operational risk, a customer relationship risk, an audit risk, and an enterprise value risk at the board level. And the fix is not more cross-training. It is a structural change in how the operation’s institutional knowledge is held.
The phrase key person risk conjures an image of a single indispensable individual. In a bulk logistics operation, the reality is more diffuse and harder to see. The risk is distributed across three or four people: the logistics manager, one or two senior coordinators, a quality lead, and sometimes a chartering specialist, all of whom collectively hold the operational competence of the business. Remove any one of them without warning, and the programme continues running, but at a meaningfully reduced level of quality, for a meaningfully long period, in ways the rest of the business will not fully understand until something goes wrong.
The symptoms of key person risk show up in predictable patterns. Meetings run longer because the shared context those individuals provided has to be rebuilt each time. Decisions take longer because the tacit judgment those individuals provided now has to be constructed from explicit inputs. Quality claims tick up slightly because the pattern recognition those individuals applied to data now has to be done by people who have not yet seen enough cycles. Customer relationships cool because the relational continuity those individuals provided is replaced by a more transactional mode of interaction.
None of this looks like a crisis. All of it looks like normal operational drift. That is exactly what makes key person risk expensive: the impact is real, the causation is diffuse, and the accounting will never line up cleanly with any single departure.
HR frames the issue in the language of succession planning. A good HR function will identify key people, run a cross-training programme, implement retention arrangements, and develop a pipeline of successors. Everything in that response is sensible. It is also insufficient because the problem it addresses is the departure of the key person, not the concentration of institutional knowledge that made that departure high stakes in the first place.
The board-level framing is different. Key person risk, from a governance perspective, is a species of operational resilience risk: the same family as cybersecurity exposure, single-supplier exposure, or regulatory compliance exposure. It needs to be named, measured, and reduced, with board-level visibility on the mitigation plan. A well-run board audit committee will ask about it directly. In increasing numbers of sectors, they are starting to.
There are four specific board-level concerns that key-person risk poses in a bulk logistics operation.
The single most important metric in any commodity business is do we deliver what we promised, when we promised it. Bulk customers, steel mills, utilities, and trading houses build their downstream planning around the reliability of your delivery. A logistics operation that depends on the continuous presence of two or three individuals is an operation whose reliability is hostage to their individual circumstances. A sickness absence, a family emergency, a resignation, a competitor’s recruitment offer: any one of these can produce a week or a month of reduced operational capacity, during which customer promises may or may not be kept. This is the most direct expression of key person risk on the P&L.
As customer procurement teams and regulatory regimes increasingly require system-backed evidence of operational controls, a logistics operation whose controls are held in individual minds is exposed. An audit team that asks who makes this decision if the logistics manager is unavailable and receives the answer the deputy, usually, with some difficulty is an audit team that will flag the finding. Over time, those findings accumulate into reduced supplier rankings and lost volume, and key-person risk shifts from a workforce concern to a commercial one.
When a bulk commodity business is sold, acquired, or partially divested, the due diligence process will probe the operational resilience of the logistics function. A function whose competence depends on specific individuals creates a discount to valuation, either because the acquirer must build retention arrangements into the deal or because the risk of post-close disruption is priced in. I have seen this discount run into tens of millions of dollars on substantial transactions. It is a line item that the selling board did not know was there until the diligence quantified it. Key person risk, expressed as transaction-value impairment, is one of the cleanest financial framings available.
A logistics function whose knowledge is held in a workbook and in a handful of heads does not produce leaders. It produces operators. The best of those operators can run the current operation well, but they cannot easily be promoted because promoting them would remove the person who holds the operation together. The organisation’s leadership development is throttled by the very concentration of expertise that makes the operation work today, another second-order cost of unaddressed key person risk.
These four concerns, taken together, make key person risk a standing agenda item for the board’s audit and risk committee in many of the better-run businesses. It stops being a discussion about talent and starts being a discussion about enterprise value.
The most vivid illustration of key person risk that most operations have is a holiday. A senior member of the logistics team takes two or three weeks of annual leave, and during that window, a series of small things happen that would, under normal circumstances, have been handled without anyone noticing. The vessel’s ETA, which shifts by 18 hours, needs a customer courtesy call. The addition to the stockpile that changed the blend profile required a nomination adjustment. The rail operator that sent a service-disruption notice in the middle of a weekend needed a coordination cascade. Each of these would be unremarkable on a normal week. Stacked together during a holiday, with the deputy who is competent but has never handled all three simultaneously, the response is slower and less clean. A quality claim emerges. A demurrage dispute drags. A customer sends a gentler-than-expected but still concerning note about responsiveness.
When the key person returns, they triage the fallout, smooth the customer relationship, and close the open items. The operation settles. Nobody talks about it in a way that would feel pointed. But the pattern has been demonstrated. The organisation has learned that the operation is brittle in the face of a predictable, foreseeable event such as a holiday.
This is the dress rehearsal for key person risk. The resignation, the medical absence, or the recruitment by a competitor is the full performance. If the dress rehearsal incurred a six-figure cost due to rework, claims, customer softness, and internal time, the full performance will incur a seven-figure cost. The board should want to know that number and the plan to reduce it.
The instinctive response to key person risk is more documentation. Write everything down. Build a runbook. Create process maps. Record the key person as they run through their calculations. Hand the documents to the deputy and to HR.
This rarely works for a simple reason. The knowledge the key person holds is not the kind that can be written down. It is pattern recognition built from hundreds of cycles of the specific operation. It is relational knowledge of specific stakeholders. It is a tacit judgement about which of several plausible answers is the right one for this customer, at this moment, given a context that is not available in any single document.
Documentation is an artefact; expertise is a practice. Attempting to convert one to the other loses most of the value. Operations that have invested heavily in documentation for key person risk mitigation typically find, at the moment they need it, that the runbook tells them how, but not why, and the why is exactly what they need to make a good decision.
The other instinctive response is cross-training. Have multiple people able to do each critical task. This is genuinely better than documentation, as it captures more tacit knowledge, but it runs into a different problem. The cross-trained deputy still has to build pattern recognition through repetition, and the operation does not have enough cycles to spread across enough people for that pattern recognition to develop in parallel. There is only one monthly fixture cycle per customer. The senior person lives through twelve monthly cycles per year. Their cross-trained deputy can at best live through the same twelve, and the operation is unwilling to hand the primary responsibility to the deputy for enough of them to build deep competence. So the cross-training produces deputies who can cope in an emergency but have not actually reached the same level of capability.
Neither fix is wrong. Both are insufficient on their own to materially reduce key person risk.
The durable fix for key person risk in a logistics operation is to shift the institutional knowledge from individual minds into the system the operation runs on. This is not a rhetorical move; it is a specific engineering discipline with specific outputs.
The blend calculation is not a formula in a cell known only to the logistics manager. It is a documented piece of business logic, reviewable by the team, with a change log showing when it was last updated and by whom, and a test case showing what inputs produce what outputs. Any competent successor can inspect, understand, and make informed changes to it.
The customer communication protocol is not a set of habits the senior coordinator has developed over five years. It is a structured record in the system: this customer prefers their update at this time of day, in this format, via this channel, with these particular data points surfaced. A new coordinator joining the team can see the protocol on the first day and execute it without needing to rediscover it through trial and error.
The rail operator relationship is not a mobile number that the logistics manager alone has. It is a stakeholder record with escalation contacts, historical performance data, service-level expectations, and a running log of the most recent conversations. The next person who needs to pick up the phone knows who to call, what to say, and what the last three interactions established.
The port scheduler’s informal accommodation of your berth preferences is not a tacit understanding between two individuals. It is a documented working arrangement, reviewed periodically, owned by a role rather than a person. When the scheduler moves to a different port or your senior coordinator is on leave, the arrangement persists because it is held by the system.
None of this removes the value of expert individuals. It amplifies it. The senior coordinator still holds unique relational capital and pattern-recognition skills. The system ensures that when they are not available, for a week, for a month, permanently, the operation does not lose everything they knew, only what was genuinely irreducibly theirs. That is the difference between a function exposed to key-person risk and one that has structurally addressed it.
This is a cultural shift as much as a technical one, and it should be framed as such. The senior people whose knowledge is being captured are not being replaced. They are being given the leverage to scale their expertise across a larger, more resilient operation, and to step away from it without the operation breaking. Most senior logistics professionals, when the framing is correct, are relieved rather than threatened by it.
If key person risk is to be a board-level conversation, it needs to be measurable. Three tractable metrics work in most operations.
The first is the bus-factor, a slightly morbid but useful question: how many people would need to be simultaneously unavailable for the operation to seriously degrade? If the answer is three or fewer, the operation has a concentration problem. A well-structured logistics function in a business of this scale should be able to absorb the simultaneous unavailability of five or six people without a material drop in capability.
The second is the time to proficiency for a new senior coordinator joining the team. In workbook-run operations, this is typically 9 to 18 months. In platform-run operations with well-encoded institutional knowledge, it is three to six months. The gap is the measurable value of the encoding and the most direct counter-metric to key person risk.
The third is the handover fidelity during a planned absence. When a key person takes a two-week holiday, what percentage of the decisions that would have been made under their presence were made in the same way during their absence, and with the same quality of outcome? A well-designed handover produces numbers in the 85–95 per cent range. A workbook-run operation typically produces numbers in the 50–70 per cent range. The board should see this number annually.
None of these metrics is exotic. They are collectively a practical proxy for operational resilience, and any reasonable audit committee would recognise them as the operating dashboard for key-person risk.
If this framing is new to the business, the sensible starting point is not a mitigation programme. It is a map.
Map the key individuals whose unavailability would materially affect the operation. For each, map the specific knowledge they hold: the calculations they own, the stakeholders they relate to, the decisions they uniquely make, the systems they uniquely maintain. For each element of that knowledge, note whether it exists anywhere outside their head. Note, specifically, whether a competent successor could pick it up in one day, one week, one month, or longer.
The resulting map is the key person risk exposure picture. Most operations, running this exercise for the first time, find that the exposure is larger than they thought, more distributed than they thought, and more reducible than they thought. Reducible is the important word. The exposure is not a fixed feature of the operation; it is a feature of how the operation’s knowledge has been held, and it can be changed.
From the map, prioritise. The elements in which the key person could leave tomorrow and the business would be in immediate difficulty come first. The elements where the key person could leave with six months’ notice and the business would manage a transition are second. The third tier can wait.
For each priority element, decide whether the mitigation is a system change, a process change, or a personnel change. Most will be system changes, moving knowledge from a workbook to a platform, from an individual’s email to a shared record, from a habit to a protocol. Some will be process changes, rebalancing decision authority, redistributing stakeholder ownership, and formalising handover patterns. A few will be personnel changes, adding a second senior person, building a true deputy role, creating a genuine succession path.
This is a 12- to 18-month programme of work in most operations. It is not cheap. It is also not expensive relative to the cost of a single material key person risk event, and it produces benefits — scalability, audit readiness, leadership pipeline — well beyond the narrow question of who answers the phone when the senior coordinator is on leave.
If you are the logistics manager reading this and wondering whether you personally are a key person risk concentration, a short self-assessment is useful.
Answer each of the following honestly. Would the business’s next Capesize load be on schedule if I were unreachable for the next two weeks? Could my deputy produce next week’s blend plan without consulting me? Could my commercial counterpart run next month’s customer quarterly review with the data and narrative that currently sits in my head? Would the rail operator’s performance conversation at the next contract renewal go as well without my personal relationship? Could a competent successor, given my laptop and access to the systems, run the programme at 80 per cent of my current output within one month?
The honest answers are, for most senior logistics managers in workbook-run operations, some variation of: mostly, probably not, definitely not, noticeably worse, and not within one month. That pattern is not a criticism of the manager. It is the predictable outcome of how the function has been structured. The useful response is not guilt; it is to name the pattern as key person risk, take it to the commercial director or the COO, and begin the conversation about what a more durable structure looks like.
Key person risk connects to several of the other pieces in this series. For the workbook dimension, the concentration of institutional knowledge in a single Excel file, see your billion-dollar supply chain is running on a spreadsheet. For the customer-facing consequences, see why bulk commodity customers really leave. For the scaling conversation, see double your logistics throughput without doubling the team. External board-level perspective on operational resilience in commodity businesses is well covered by the ICMM’s work on operational risk and the long-running OECD work on supply chain due diligence.
The senior people in your logistics function are, almost certainly, among the most valuable contributors in the business. They have earned their place. The conversation this post argues for is not about reducing their importance. It is about making sure the organisation is not held hostage by its individual circumstances, that individuals can take a holiday, receive a well-deserved promotion, or pursue an outside opportunity, and that the business continues to run because the institution has learned to hold what the individual used to carry. That is what good operational design looks like. It is also, as the audit committee will increasingly remind the board, what good governance requires, and the only durable answer to key-person risk.
Nick Ogle has over 30 years of experience in Enterprise IT, spanning engineering, sales, and marketing roles across Australia, the USA, and APJ for various IT vendors.
Nick is passionate about entrepreneurship and Software innovation that drives positive change. Currently, he is the Sales & Marketing Manager at SCIAR Systems, a Newcastle-based SAAS startup, where he is helping commercialise their groundbreaking Bulk Commodity Logistics solutions.
For more information on Nick and to find articles that have been written on the IT sector in the past, feel free to look at his LinkedIn profile or browse some of the additional articles Nick has written for SCIAR.