-
Risk Management Is a Decision Structure, Not a Register
Risk management in a mid-market company is a decision structure rather than a document. Most programs produce a register that lists exposures, assigns owners, and gets reviewed on a cycle. That artifact creates the appearance of control while scoring the wrong arithmetic entirely.
The register runs an average that no single company experiences
A standard register scores each exposure on likelihood and impact, then multiplies the two. That product is an expected value, and expected value is the correct instrument for a party facing the same situation repeatedly. An insurer occupies that position across thousands of policies.
A mid-market company does not occupy that position at all. The distinction is operational rather than academic, and it changes the ranking. Expected value averages across branches that one business only ever travels once, so an exposure carrying a small chance of ending the company scores low. That score is arithmetically correct and useless for the decision at hand.
Survivability is the threshold that governs everything else
The load bearing question is not what an exposure costs on average. It is whether the business is still operating in the branch where the exposure actually lands. Those two questions produce different priority orders and different spending decisions.
Sort exposures into two classes before scoring any of them. The first class threatens continuity, meaning normal operation does not resume afterward. The second class produces cost, disruption, and discomfort without ending anything.
Rigor here means refusing to blend the two classes into one ranked list. A single list invites trading a continuity exposure against several expensive ones, and that trade is never sound. Continuity exposures get handled first and separately, whatever the product of two estimates happens to say.
Inherent exposure, residual exposure, and the gap nobody tests
Registers almost always record residual exposure, meaning what remains once controls operate. Inherent exposure is what exists before any control at all. The distance between those two figures is a claim about how well the controls work.
That claim is rarely tested after it is first made. The residual figure gets entered when the control is designed, then carried forward unexamined through every subsequent review cycle. Nobody returns to ask whether the control still operates, so the register quietly becomes a record of intentions.
Design effectiveness and operating effectiveness are separate claims
Audit practice separates these two, and the separation is worth borrowing wholesale. Design effectiveness asks whether the control would prevent the exposure if it ran exactly as specified. Operating effectiveness asks whether it actually ran.
Most controls in a growing company pass the first test and fail the second. The control depends on somebody remembering it during a week when attention is fully consumed by a live problem. That is precisely the week the exposure tends to arrive.
The inexpensive version of this test takes an afternoon. Pick one control, find the recent instances where it should have fired, and confirm in the record that it did. What the register says about that exposure is now evidence rather than assertion.
Correlation is what turns a list into an event
A register presents exposures as independent rows. Real failures rarely arrive as one row. They arrive as several rows moving at once because a single underlying driver moved all of them together.
A downturn compresses a large customer's payment behavior, tightens the credit facility, and stresses a thin supplier simultaneously. Each row was scored separately and each score was defensible in isolation. The combined position was never scored, because no line on the register represents it.
Ask which rows share a driver before scoring any of them individually. Group the rows that move together and score the group as one exposure. Coherence between those groupings and the real operating dependencies is what separates a risk model from an inventory.
Concentration is the shared driver nobody logs
The most common shared driver in a mid-market business is concentration. One customer producing most of the revenue, one supplier holding a critical input, one person carrying knowledge that exists nowhere in writing.
Concentration rarely appears as a register row because it is not an event. It is a standing condition, and registers are built to hold events. That condition nonetheless determines how severe every event on the list becomes when it arrives.
Measure it directly rather than waiting for it to express itself. Revenue share by account, single-source inputs, and functions where one departure stops the work are all countable in a morning. Each is a continuity exposure regardless of what happens this quarter.
Four treatments exist and most registers use one
An exposure can be avoided, reduced, transferred, or deliberately retained. Registers overwhelmingly record reduction, because reduction is the treatment that produces a visible control and a satisfying entry in the document.
The other three are decisions rather than absences. Avoidance means declining the work that carries the exposure. Transfer means insurance or a contractual term moving the consequence to a party better positioned to absorb it. Retention means the organization has examined the exposure and chosen to carry it.
Retention is the treatment most often applied without ever being decided. An exposure sitting through successive cycles without movement has been retained by default, and default retention has no analysis standing behind it.
Bow-tie analysis puts barriers on both sides of the event
Bow-tie analysis is one of the few risk methodologies that survives contact with an operating business. The top event sits in the middle of the diagram. Threats that could cause it run in from the left, and consequences that follow it run out to the right.
Preventive barriers sit on the threat side, mitigative barriers on the consequence side. Most programs construct only the left half of that diagram. The organization has then invested entirely in the event never occurring and not at all in surviving it.
Drawing one requires a whiteboard and an hour. The value sits in the right half, because that is the half nobody has considered and the half deciding whether a bad quarter becomes a terminal one.
Layered barriers fail through aligned gaps
James Reason described accident causation as a series of defensive layers, each carrying holes. Failure occurs when the holes in successive layers line up and a threat passes cleanly through all of them.
The organizational reading of that model is specific and uncomfortable. Barriers sharing a dependency carry their holes in the same position. Three controls that all require the same person to notice something are one control described three times.
Check barriers for shared dependencies rather than counting how many exist. Independence is the property making layered defense work at all, and it is the property most commonly missing in a small operation where a few people hold everything.
Indicators that move before the event rather than after it
Most risk reporting counts activity because activity is easy to count. Items logged, reviews held, controls documented, attendance recorded at the quarterly session. None of those describe whether exposure is rising or falling.
A risk indicator differs from a performance indicator in direction rather than in format. A performance indicator reports what already happened. A risk indicator moves ahead of the event, and that property is the only reason to watch it.
Useful ones are usually dull and already sitting in the systems. Days of cash coverage, revenue share held by the largest account, elapsed time from signal to decision. Consistency in tracking a few of these beats sophistication in tracking many.
Where the standard says this work actually belongs
ISO 31000 makes an argument that most implementations quietly ignore. Risk management is described as part of decision making rather than as a parallel process reporting on decisions taken elsewhere.
That placement is effectively the whole content of the standard. A separate function reviewing decisions after the fact produces documentation. Risk criteria applied inside the decision itself produces different decisions, which was the intended outcome.
The practical translation is small and cheap to build. Every recurring decision class carries a stated threshold above which the decision changes route. Below that threshold the owner proceeds without consultation and without apology.
Conditional rules for a mid-market register
Where an exposure could end the business, lift it out of the ranked list and handle it on its own. Ranked lists invite trades that are unsound the moment one side is terminal.
Where a control has never been tested against a real instance, record the inherent exposure rather than the residual one. An untested control is a plan, and plans do not reduce exposure.
Where several rows share an underlying driver, score the group instead of the rows. The business is exposed to the driver, not to the individual lines describing it.
Where an exposure has survived successive reviews without treatment, mark it retained and name the person retaining it. Default retention becomes an actual decision the moment somebody signs for it.
Strategic fit decides which exposures are worth carrying
Not every exposure should be reduced. Some are the direct cost of the strategy, and removing them removes the position that made the business worth building in the first place.
A concentrated customer base is an exposure and frequently also the reason margins hold. Operational excellence in this work is knowing which exposures are load bearing and which are merely tolerated because nobody examined them.
Strategic fit is the test separating the two. An exposure the strategy requires earns structural attention and a survival plan. An exposure the strategy does not require gets removed, and stakeholder value improves in either direction.
Structure is what protects the people carrying the exposure
The argument for building this is not documentation quality. Ambiguous risk ownership is absorbed by staff as personal exposure, and human capital erodes under that condition faster than under heavy workload.
Someone who cannot tell whether an exposure belongs to them will escalate it, wait on it, or work around it quietly. Each response costs them standing, and none of the three appears on any report. Servant leadership expressed operationally means naming the owner so the ambiguity stops being theirs to absorb.
Composure follows from that clarity more reliably than from any control. Teams who know who holds what will raise problems earlier, and early problems cost less than late ones by a margin no documentation can match.
Watch the full explainer
Related
Further material on management consulting and operational structure from World Consulting Group: [www.worldconsultinggroup.com](https://www.worldconsultinggroup.com)
-
Strategic Planning Fails at the Handoff to Execution
Strategic plans in mid-market companies rarely fail because the thinking was wrong. They fail at the point where an intention has to become a commitment somebody can be held to. That handoff is a distinct piece of engineering, and almost nobody builds it.
An objective and a commitment are different objects
An objective describes a desired end state. A commitment names a person, a date, and a quantity of capacity that person will spend. Planning sessions produce the first in volume and the second almost never.
The gap is easy to miss because both fit on the same slide and use similar grammar. Growing into a new segment reads like a plan. Two named people spending a third of their week on that segment through the third quarter is a plan.
Anything that cannot be written in the second form has not been planned yet. It has been wished for, which is a legitimate first step and a poor final one.
The plan assumes capacity that is already spent
Most annual plans are built as though the organization starts the year empty. In practice every person is already fully consumed by the work that keeps revenue arriving this month.
New initiatives therefore arrive as an addition to a full load rather than as a reallocation from something else. The team accepts them because refusing looks like a lack of ambition. Then the initiative loses every scheduling conflict against the work that produces this quarter's invoices.
Run the arithmetic before the plan is approved rather than after. List what each contributing person currently spends their week on, then subtract what the plan requires. Where the subtraction produces a negative number, the plan is not a plan yet.
Naming what stops is the actual planning decision
The hard half of strategy is subtraction, and subtraction is what gets skipped. Adding an initiative is a pleasant meeting. Naming the activity that ends so the new one can exist is an unpleasant one.
Organizations avoid the unpleasant meeting by declaring both the old and the new important. The result is an initiative stack deeper than the capacity available to it, which converts a prioritization problem into a queueing problem nobody manages.
Work in progress limits solve this more reliably than better prioritization does. Cap the number of live strategic initiatives at a figure the organization can actually staff. Anything beyond the cap waits in a visible queue rather than proceeding at a quarter of the necessary intensity.
Cascading is not the same as allocating
The standard model pushes a corporate objective down through each layer until every team holds a version of it. That motion distributes language rather than resources, and language is not the scarce input.
Hoshin Kanri describes the corrective as catchball, meaning the objective travels down and the constraints travel back up before anything is fixed. The team receiving an objective states what it would need and what it would have to stop. Leadership then adjusts the objective, the resourcing, or both.
Skipping the return leg produces plans that were never agreed to by anyone required to deliver them. Coherence between the stated objective and the resourcing is what makes the cascade mean anything at all.
Plans get estimated from the inside and should not be
Teams estimate a new initiative by imagining how it will go. That method systematically produces optimistic numbers, because imagining a project surfaces the steps and not the interruptions.
The alternative is to look outward at comparable efforts already completed. What did the last three initiatives of similar scope actually take, measured from approval to operating? That figure is nearly always longer than the inside estimate and considerably more accurate.
Rigor here is cheap and unpopular. Keeping a simple record of how long past initiatives ran gives every future plan a reference point that does not depend on anyone's mood in the planning room.
Strategy is a portfolio of bets, so write the kill criteria
Some initiatives will not work, and the plan should say so in advance. A portfolio framing accepts that outcome rather than treating each failure as a discrete embarrassment requiring explanation.
Write the abandonment condition at approval, while the initiative is still unattached to anyone's reputation. What observable result by what date would mean this bet is not paying. Deciding that in advance costs nothing and later saves an argument nobody can win.
Without stated kill criteria, initiatives end by quiet starvation rather than by decision. Starvation is slower, consumes capacity the whole way down, and teaches the organization nothing usable.
The annual cycle is the wrong clock for most of the work
A twelve month planning horizon made sense when the operating environment moved slowly enough that a January estimate stayed useful in September. That condition has largely stopped holding for mid-market companies.
The practical repair is not continuous replanning, which produces churn and no direction. It is separating the parts of the plan that hold from the parts that need refreshing. Direction and resource envelopes hold for a year, while specific initiative sequencing holds for a quarter.
Consistency in that split is what allows a company to change tactics without relitigating strategy every time something moves. Continuity of direction and flexibility of sequencing are compatible once the two are separated on purpose.
Naming the frameworks that carry the handoff
Three named models do useful work here, and each fails in a specific way when applied without the others.
The OKR framework is built to make objectives measurable, and its common failure is producing measurable objectives nobody resourced. A key result without a capacity allocation behind it is a scoreboard rather than a plan, which is why teams report red for two quarters and change nothing.
Hoshin Kanri contributes the return leg described above, and its value is entirely in the negotiation rather than in the paperwork. Organizations that adopt the templates without the shared negotiation get a longer document and the same unresourced plan.
The Theory of Constraints supplies the sequencing rule that the other two lack. Where several initiatives depend on one constrained person, total completion time is set by that person and by nothing else. Running the initiatives in parallel simply delays all of them together.
Where the handoff actually breaks
Three failure points account for most of the distance between a good plan and a poor year, and all three are observable within a week of approval.
The first is an unnamed owner. An initiative assigned to a department rather than to a person has no one whose week changes on Monday, and a week that does not change produces no progress.
The second is an absent first action. Where the plan states an outcome without stating what specifically happens next, the initiative waits for someone to design that step and nobody has been asked to.
The third is a missing forum. Where progress has no scheduled place to be examined, review happens only when something has already gone visibly wrong. By then the useful decisions have expired.
Conditional rules for the planning cycle
Where an initiative has no named owner whose weekly schedule changes, remove it from the plan and hold it in the queue. An unowned initiative consumes attention in reviews while producing nothing.
Where two initiatives require the same scarce person, sequence them explicitly rather than running both. Parallel execution against a single constrained resource finishes later than deliberate sequencing does, and it finishes with worse quality.
Where an initiative has produced no observable movement across two consecutive review cycles, treat that as data about resourcing rather than about effort. The team is almost certainly working, and the work is almost certainly going somewhere else.
Governance of the plan is a rhythm, not a document
A plan is a set of live commitments and needs a cadence that keeps them live. The mechanism is small and most organizations already own the parts.
A standing forum meets on a fixed schedule. A visible list carries each initiative, its owner, its next observable step, and its kill criteria. Anything that misses two cycles gets an explicit decision to continue, resource differently, or stop.
Process architecture at this level is unglamorous and does most of the work. The systems that keep a plan alive are considerably duller than the ones that produce it.
Strategic fit is what makes the subtraction survivable
Cutting activity is only defensible when there is a clear account of what the organization is choosing to be. Without that account, every subtraction reads as arbitrary and gets quietly reversed by whoever was cut.
Strategic fit supplies the account. An activity that the chosen position requires stays even when it is expensive. An activity that made sense under a previous position leaves, and stakeholder value improves because the capacity moves to something the strategy actually needs.
Operational excellence in planning is mostly the discipline to state the position clearly enough that the subtractions follow from it rather than from a budget target.
Plans that respect capacity protect the people executing them
Capacity arithmetic is not an administrative nicety. A plan exceeding available capacity does not fail on paper first. It fails on people, who absorb the shortfall as longer weeks and a persistent sense of falling behind.
Human capital erodes quickly under a plan that was never achievable, and it erodes fastest among the people who tried hardest to deliver it. Servant leadership expressed here means doing the capacity arithmetic before asking anyone to commit.
Teams extend real effort to plans they believe are possible. Establishing that belief is a design task rather than a motivational one, and it starts with a plan that subtracts as honestly as it adds.
Watch the full explainer
Related
Further material on management consulting and operational structure from World Consulting Group: [www.worldconsultinggroup.com](https://www.worldconsultinggroup.com)
-
Performance Improvement Beyond Cost Cutting
Performance improvement gets treated as a synonym for spending less, which limits the exercise to one of at least four available levers. The other three are usually larger, slower to see, and unavailable to anyone whose only instrument is the expense line. Knowing which lever a situation actually calls for is most of the work.
Cost accounting reports where money went, not where margin comes from
Standard cost accounting allocates overhead across units of output. That allocation is necessary for reporting and actively misleading as a guide to improvement, because it distributes fixed cost onto things that did not cause it.
A product absorbing a large share of allocated overhead looks unprofitable and often is not. Removing it drops the revenue and leaves the overhead behind, so the remaining products absorb more and the next candidate for removal appears. Companies have shrunk themselves several steps down that path before noticing the mechanism.
Activity-based costing exists to correct this by tracing cost to the activity that drives it. The exercise is worth running once, in enough detail to learn which products and customers genuinely consume disproportionate effort.
Throughput has no ceiling and cost has a floor
Three levers move operating profit. Throughput can rise, operating expense can fall, and working capital can be released. Only the first is unbounded.
Cost reduction terminates at zero and reaches a practical limit long before that, usually at the point where further cuts remove the capability that generates revenue. Every organization eventually meets that limit, and many meet it without recognizing it.
Throughput carries no equivalent floor, which is why an improvement program that only ever examines the expense line is working the smallest of the three. The discipline is checking all three before choosing, rather than reaching for the one that produces a fast and visible number.
Local efficiency and system profit are separate measurements
Making one part of an operation faster feels like improvement and frequently is not. Where the accelerated step feeds a slower one downstream, the additional output accumulates as work sitting between stations.
That accumulation is a cost rather than a gain. It occupies cash, space, and attention, and it lengthens the time between starting a job and being paid for it. The local metric improves while the system metric moves the wrong way.
Apply effort at the constraint and nowhere else. Improvement anywhere upstream of the binding step produces inventory, and improvement downstream produces idle capacity waiting on the same step it was already waiting on.
Utilization above a threshold buys queue rather than output
Running people and equipment near full occupancy looks efficient and behaves badly. Queueing behavior is not linear, so waiting time climbs sharply as occupancy approaches capacity.
The practical consequence is that a department run at very high utilization delivers longer lead times than the same department run with deliberate slack. Nothing about the people changed. The arrival pattern is variable, and a fully occupied system has no room to absorb variability.
Deliberate slack is therefore a design choice rather than waste, and it is the choice most often eliminated during a cost exercise. Removing it improves a utilization figure and lengthens every delivery the organization makes.
Price realization is the most neglected lever
The price a company charges and the price it collects are different figures, and the distance between them is rarely examined. Discounts, freight allowances, payment terms, rebates, and unbilled scope each remove a slice.
Nobody manages the total because each slice is granted by a different person under a different justification. The cumulative effect only appears when someone reconstructs the realized price for individual transactions and compares the spread across similar customers.
That spread is almost always wider than leadership expects. Closing part of it requires no cost reduction, no new customers, and no operational change, which makes it the cheapest available improvement in most mid-market businesses.
The cost of poor quality sits mostly outside the accounts
Quality cost divides into four categories. Prevention and appraisal are spent deliberately. Internal failure covers rework caught before delivery, and external failure covers what the customer finds.
Most companies measure only the fourth, because returns and warranty claims arrive with invoices attached. Internal failure is absorbed inside normal operating hours and never appears as a line, which makes the largest category the least visible.
Counting rework for a single month changes the conversation. The figure is usually large enough that prevention spending stops looking like an expense and starts looking like the highest return available.
Mix is a decision rather than an outcome
Which customers and products an operation serves is treated as given, when it is the most powerful lever the business holds. Demand is not uniform, and neither is the cost of serving it.
Some customers consume disproportionate coordination for ordinary margin. Some products require setups that displace better work. Serving both because they arrived is a decision made by default rather than by analysis.
Reshaping the mix is slow and produces effects the expense line cannot. It changes what the operation is being asked to do, which is a different order of improvement than doing the same thing more cheaply.
Naming the models that keep the levers separate
Throughput accounting supplies the framing that cost accounting cannot. It treats operating expense as largely fixed in the short term and directs attention to the rate at which the system converts work into collected revenue.
The Theory of Constraints contributes the ordering rule that the accounting models leave out. Improvement at the binding step raises system output, while improvement anywhere else raises a local number and nothing more.
Lean contributes an observation methodology rather than a set of tools. Watching one job travel end to end, and recording every wait, reveals a distribution of delay that no report describes accurately.
A value stream map is the written form of that walk, and its value is the honesty it forces rather than the diagram it produces. Waiting time typically dominates working time by a wide margin, which reframes the improvement question from how fast people work to why the work sits still.
Diagnosis has to precede the choice of lever
Improvement programs usually begin with a target rather than with an analysis, and the target then determines which evidence gets collected. That order guarantees the organization finds support for the lever it had already chosen.
The disciplined order runs the other way. Establish where margin is actually lost by tracing a representative sample of jobs, orders, or accounts from acceptance through to collected cash. The distribution of loss is rarely where the leadership team predicts, and the prediction is usually shaped by whichever number is easiest to see on a monthly report.
Rigor at this stage costs a few days and prevents a full quarter spent improving something that was never the problem. Composure matters as much as speed, because the pressure to announce a program tends to arrive before the diagnosis is finished.
The levers cross functions and need a shared definition
Three of the four levers cannot be pulled by one department. Realized price is set by sales behavior and finance policy together. Mix is set by sales and operations together. Quality cost sits between operations and whoever owns the customer relationship.
Where those functions hold different definitions of the same term, the improvement stalls without anyone opposing it. Sales counts a discount as a competitive necessity, finance counts it as margin, and neither view is wrong inside its own frame.
Building a shared definition first is unglamorous and load bearing. Coherence between how the functions describe a number is what makes collaborative improvement possible, and its absence is why cross-functional programs produce meetings rather than movement. Consistency in that vocabulary outlasts any individual initiative.
Conditional rules for choosing the improvement
Where margin is falling while volume holds, examine realized price before examining cost. Price leakage produces exactly this pattern and responds to attention within a quarter.
Where lead times are lengthening while utilization looks strong, the problem is queueing rather than capacity. Adding capacity will help, and adding slack at the right station will help more for less money.
Where a product looks unprofitable under allocated overhead, trace its actual consumption before removing it. Products carrying allocation they do not cause are the most common source of avoidable shrinkage.
Where rework is invisible in the accounts but visible on the floor, measure it for one month before designing anything. The measurement usually settles the argument about where to spend.
The position determines which lever is legitimate
Not every improvement suits every strategy. A business competing on responsiveness cannot buy margin by removing the slack that produces its responsiveness, even though the arithmetic works on paper.
Strategic fit is the filter. An improvement that strengthens the thing customers actually buy is compounding, and one that quietly erodes it borrows from next year to pay for this quarter. Both look identical in the month they are executed.
Operational excellence here means being able to name the capability the company is protecting before choosing where to cut. Stakeholder value follows from the protection of that capability rather than from the size of the reduction.
Improvement that does not consume the people delivering it
A program run entirely on the expense line asks people to produce the same output with less of everything. That request is answerable once and unanswerable as a pattern, and the second request begins eroding human capital.
Throughput, price realization, and mix work differently, because each changes what the system does rather than how hard people push against it. Teams participate willingly in improvements that make the work more sensible and resist improvements that only make it denser.
Servant leadership expressed operationally means finding the lever that does not land on people first. Trust accumulates when improvement removes friction, and it drains when improvement removes the room people needed to do the job properly.
Watch the full explainer
Related
Further material on management consulting and operational structure from World Consulting Group: [www.worldconsultinggroup.com](https://www.worldconsultinggroup.com)
-
Supply Chain Management Is a Governance Problem
Supply chain failures present as supplier failures and are usually something else. Most of the variability a mid-market company experiences upstream was manufactured by its own ordering behavior. Fixing that requires changing internal decisions rather than changing vendors.
Variability grows as it travels upstream
Customer demand for a given item is generally steadier than the orders a company places for it. Each step back through the chain amplifies the swing, so a modest change at the point of sale arrives at the supplier as a severe one.
That amplification is well documented and consistently underestimated. The supplier experiences erratic demand, protects itself with longer quoted lead times and higher minimums, and the buyer experiences those protections as poor service.
Both parties then describe the other as unreliable. Neither description is accurate, because the pattern is generated by the structure connecting them rather than by either organization's competence.
The causes of amplification are internal decisions
Four behaviors produce most of the swing, and each is a choice somebody made for a defensible local reason.
Order batching comes first. Placing a large order every several weeks instead of a smaller order every week converts steady consumption into a spiky signal, and the spikes are what the supplier plans against.
Forecasting from orders rather than from consumption comes second. A supplier reading its customer's order pattern is reading an already distorted signal and amplifying the distortion again for its own suppliers.
Promotional buying is third, since a discount pulls future demand forward and leaves a trough behind it. Shortage gaming is fourth, where buyers inflate orders during scarcity to secure allocation and cancel once supply recovers.
Reliability matters more than speed
Buyers negotiate hard on quoted lead time and rarely on the variance around it. That priority is inverted for almost every operation.
A supplier who reliably delivers in six weeks can be planned around with a modest buffer. A supplier who averages three weeks but ranges from one to seven cannot, and the buffer required to absorb that range costs more than the four weeks saved.
Measure the spread rather than the average before renegotiating anything. Consistency in delivery is the property that reduces the working capital an operation must hold, and it is almost never what the negotiation is about.
Suppliers are not one category and should not share one playbook
Applying the same commercial approach to every vendor wastes attention on items that do not matter and underserves the few that do. Segmentation solves this cheaply.
The Kraljic model sorts purchases on two axes, being financial impact and supply risk. Items low on both are administrative and should be automated out of anyone's calendar. Items high on financial impact and low on risk are where competitive tendering earns its keep.
The quadrant that matters is high risk with meaningful impact. Those relationships need collaborative planning, shared forecasts, and named contacts on both sides, because the alternative to partnership there is exposure the purchase price never reflected.
Supplier power is a structural position, not a negotiating mood
Porter described supplier power as a force shaped by structure rather than by conduct. Concentration in the supply base, absence of substitutes, and switching costs each raise it independently of how either party behaves.
Recognizing the position changes what a negotiation can achieve. Where structural power sits with the supplier, pressing for price produces short term movement and a degraded relationship, and it does nothing about the underlying condition.
The durable responses are structural in turn. Qualify an alternative source, redesign the specification toward a more available input, or accept the position deliberately and manage it. Each is slower than a negotiation and each actually changes something.
Total landed cost is the number the purchase order does not show
Purchase price is the visible figure and rarely the relevant one. Freight, duty, inspection, expediting, rework caused by variable quality, and the working capital tied up by long or unreliable lead times all attach to the same decision.
A cheaper unit price frequently arrives with a longer lead time and a wider delivery spread. The buyer books a saving and the operation absorbs the difference somewhere it will never be attributed back.
Reconstruct the full cost for the handful of items that matter most. The exercise takes days rather than weeks and regularly reverses a sourcing decision that looked settled.
The decoupling point is a governance decision
Every operation holds inventory somewhere between raw input and finished output. Where it holds that stock determines both responsiveness and capital consumption, and the position is usually inherited rather than chosen.
Holding generic material and configuring late gives flexibility across many end items with less total stock. Holding finished goods gives immediate availability at the cost of guessing the mix in advance.
Naming the decoupling point explicitly turns an accident into a decision. It also makes the tradeoff legible to finance and operations at the same time, which is generally the first time both have discussed it in the same terms.
The service measure most companies report is the wrong one
Line fill rate counts how many order lines shipped complete. On time in full counts how many complete orders arrived when promised. Those two figures can differ dramatically for the same operation.
Customers experience the second and internal reporting usually tracks the first, which is why service can appear strong while accounts describe the opposite. The measurement gap sustains the disagreement indefinitely.
Report the number the customer feels. Where that number is uncomfortable, the discomfort is information rather than an argument for a different metric.
Visibility ends at the first tier and the exposure does not
Most companies know their direct suppliers and almost nothing about who supplies them. A disruption two tiers back arrives with no warning and no obvious cause.
Mapping the second tier for critical items is a finite piece of work. Ask the direct supplier where the input originates and whether an alternative exists, then record the answers where somebody will look at them again.
Discipline here is simply doing it before it matters. The mapping is inexpensive when nothing is wrong and impossible to complete during a shortage.
Repair the signal before replacing the supplier
The cheapest available improvement is usually to stop distorting the demand signal, and it requires no supplier conversation at all. Three changes do most of the work.
Order on a shorter and more regular cadence, even where the quantity per order falls. Smaller regular orders cost slightly more in administration and remove a large share of the amplification the supplier is planning against.
Share actual consumption rather than only orders. A supplier who can see what is being used, rather than inferring it from a batched purchase pattern, plans against reality. The padding for a variability that was never real then comes out of the quoted lead time.
Then build the ordering rules into the systems rather than leaving them to judgement. Rules that live in someone's head get abandoned during the exact weeks that generate the worst distortion. Those are the weeks when a buyer is busy and reaches for one large convenient order.
Naming the models that make this legible
Two frameworks and one accounting habit carry most of the analysis, and each answers a different question.
The segmentation model answers where to spend attention. The supplier power analysis answers what a negotiation can realistically achieve. Total landed cost answers whether a sourcing decision was actually a saving.
Sales and operations planning is the methodology that connects them to the rest of the business. Its value is a single monthly forum where demand, supply, and finance agree one set of numbers, which is a modest ambition that most mid-market companies have not yet met.
Conditional rules for supplier decisions
Where a supplier is described as unreliable, examine the ordering pattern sent to them before changing vendors. Switching reproduces the amplification against a new party.
Where an item is high risk and low spend, treat it as high priority regardless of its value. Spend is a poor proxy for exposure, and the cheapest input can stop the line.
Where a price concession has been won without any structural change, expect it to reverse. Negotiated movement against a strong structural position is a loan rather than a saving.
Where lead time variance exceeds the buffer currently held, raise the buffer or fix the variance. Continuing with neither means the operation is absorbing the difference through expediting and overtime.
What the chosen position requires
Supply chain design follows from what the business competes on rather than from a generic efficiency target. An operation selling on availability needs stock and dual sources. One selling on price needs the opposite and should say so plainly.
Strategic fit resolves arguments that otherwise run indefinitely between functions. The question is not whether inventory is good or bad, but whether this business has promised something that inventory is required to deliver.
Operational excellence in sourcing is the alignment between that promise and the structure built to keep it. Stakeholder value erodes quietly wherever the two have drifted apart and nobody has reconciled them.
Governance protects the people absorbing the disruption
The argument for building this is not procurement tidiness. Where the structure generates instability, a small group of people spend their weeks expediting, apologizing, and rebuilding schedules that were never achievable.
That work is invisible in any report and expensive in human capital, because it consists almost entirely of absorbing consequences somebody else's decision created. Servant leadership expressed operationally means removing the generator rather than praising the people coping with it.
Trust between functions recovers once the ordering behavior stabilizes. Coherence between planning, purchasing, and operations is what makes that stability possible, and it is a design output rather than a matter of goodwill.
Watch the full explainer
Related
Further material on management consulting and operational structure from World Consulting Group: [www.worldconsultinggroup.com](https://www.worldconsultinggroup.com)
-
Inventory Management Is Purchasing Governance
Inventory problems get treated as warehouse problems and are almost always buying problems. The stock sitting on a shelf is the visible residue of decisions taken weeks earlier by people who never saw the shelf. Governing those decisions is what changes the balance.
The commitment is made at the specification
A purchase order is the moment the money becomes visible and not the moment it was committed. The real commitment happened when somebody chose a part, wrote a specification, or approved a design that only one supplier can satisfy.
Everything downstream of that choice is administration. The buyer negotiating the order has almost no room to move. Cost, lead time, and availability were all determined by an engineer or a product manager who was not thinking about any of the three.
Move the review upstream if the intent is to change outcomes. A specification review that asks whether a common part would serve does more for inventory than any amount of attention applied at the order stage.
Approval authority is per transaction and exposure accumulates
Approval limits are almost always written against a single order. Anyone below a threshold can commit, and each individual commitment is defensible on its own terms.
Nobody holds the total. The organization can therefore accumulate a large open commitment through a series of small approved decisions, and no control anywhere in the process was violated. The exposure is real and the process report is clean.
Report open commitment rather than spend. Spend describes what has already been invoiced, while open commitment describes what the business has promised to pay and cannot easily withdraw from. The second number is the one that constrains next quarter.
Carrying cost is understated wherever nobody calculates it
The cost of holding stock is routinely estimated at whatever figure the finance team last mentioned. The real components are specific and they add up faster than the estimate suggests.
Capital tied up is the obvious one. Storage, handling, insurance, and shrinkage follow. Obsolescence sits underneath all of them and is usually the largest. It is the only component able to consume the entire value of an item rather than a percentage of it.
Calculate the figure once for the business rather than borrowing a rule of thumb. Every stocking decision downstream depends on it, and a wrong input produces confidently wrong answers at scale.
Obsolescence is a deferred decision rather than an incurred cost
Dead stock sits on the balance sheet at cost until somebody books the write-off. Nobody wants to book it, because the write-off makes visible a decision that was already wrong and identifies the period rather than the person.
So the stock stays. It occupies space, absorbs counting effort, and misrepresents the asset position to everyone reading the accounts, including the people making the next stocking decision.
Set an aging rule and apply it without argument. Anything past a stated threshold gets a decision to sell, use, or dispose, and the decision is scheduled rather than triggered by discomfort. Composure at that moment is worth more than optimism about a future order.
Two axes matter and most companies use one
Classifying items by annual value is standard practice and only half the picture. Value tells you how much money an error costs. It says nothing about how predictable the item is.
Adding a second axis for demand variability changes the policy substantially. A high value item with steady predictable demand needs tight ordering and very little buffer. A low value item with erratic demand needs a generous buffer and almost no attention.
Managing both on value alone produces the opposite of both. The expensive predictable item accumulates buffer it never needed, and the cheap erratic one runs out and stops the work.
Safety stock is arithmetic rather than temperament
Buffers get set by whoever was most recently embarrassed by a stockout. That method produces buffers correlated with memory rather than with variability.
Safety stock is a function of two things. How much demand varies during the replenishment window, and how much the replenishment window itself varies. Where lead time is unreliable, the second term dominates and no amount of demand forecasting compensates for it.
The arithmetic is not difficult and the inputs are already in the systems. Applying it consistently across a few hundred items releases capital and improves availability at the same time, which is the combination that convinces a sceptical finance team.
Record accuracy is the precondition for every rule above
None of this works on records that do not match the shelf. Where the system shows stock that is not there, the reorder logic fires late and the operation runs short while reporting healthy coverage.
Annual counting does not fix this. It corrects the ledger once a year and leaves eleven months during which every automated decision runs on drifting data.
Cycle counting fixes it as an operating property rather than an event. A small number of items counted every week, weighted toward the ones that matter, keeps accuracy high continuously and surfaces the process defect causing the drift.
Order quantity models optimize a variable that stopped mattering
The classic order quantity model balances the cost of placing an order against the cost of holding what it delivers. It assumes steady demand and a fixed ordering cost, and it was built when placing an order carried real administrative expense.
Ordering is now nearly free in most businesses, which collapses one side of the balance. The model consequently recommends quantities larger than the situation warrants and pushes the operation back toward the batching that generates its own problems.
Treat it as a teaching device rather than a policy. The useful residue is the idea that order size is a tradeoff, and the tradeoff should be re-derived with current numbers rather than inherited.
Naming the models and what each one assumes
Three models carry most of the analysis, and each is safe only where its assumption holds. Applying any framework outside the conditions it was built for is the most common way a sound methodology produces an unsound policy.
Classification models assume the population is heterogeneous enough that differentiated policy pays, which is nearly always true above a few hundred items. Reorder point models assume lead time is known within a range, which is where a supplier with wide variance breaks them.
Activity-based costing supplies the discipline for the specification review, by attributing the handling, counting, and expediting effort a proliferating part number actually consumes. Without that evidence, adding a variant looks free at the moment it is proposed.
Where the stock is held changes who pays to hold it
Ownership of inventory is negotiable and rarely negotiated. Consignment leaves title with the supplier until the item is consumed, which moves the capital cost without moving the availability.
Vendor managed replenishment goes further by handing the supplier responsibility for maintaining agreed levels against shared consumption data. Both arrangements suit items where the supplier has better visibility of the pattern than the buyer does.
Neither is free. The supplier prices the carrying cost into the unit, so the question is whether they can carry it more cheaply than the business can. That depends on whether they pool the same item across several customers, and where they do the transfer is genuinely cheaper for both parties.
Coverage is a better instrument than value
Total inventory value is the number that reaches the board and the least useful one available. It moves with price, with mix, and with the calendar, so a change in the total explains nothing about whether the position improved.
Days of coverage by item class is the instrument that answers the question. It expresses stock in the only unit that matters operationally, which is how long the business can continue serving demand from what it currently holds.
Tracking coverage also exposes the two failure states separately. A rising total with falling coverage means the money moved into items nobody wants, and that combination is invisible in any valuation report.
Conditional rules for the buy decision
Where a part exists in several near-identical variants, the inventory problem is a specification problem. Consolidating variants releases more capital than tightening any ordering rule.
Where availability is poor while total stock is high, the mix is wrong rather than the quantity. Buying more will worsen both conditions simultaneously.
Where an item has not moved in a defined period, stop reordering it automatically and force a decision. Automatic replenishment against dead demand is the most reliable way to convert a small write-off into a large one.
Where a supplier's lead time varies widely, raise the buffer for that item specifically rather than across the category. Uniform buffers spread capital evenly across an uneven problem.
What the chosen position requires
Inventory policy follows from what the business promises rather than from an efficiency target. A distributor competing on next day availability must hold stock and should stop apologizing for the working capital that produces its advantage.
A make to order operation carries the opposite obligation and should resist the drift toward stocking finished goods that begins the first time a customer complains about a lead time. Strategic fit is what settles that argument before it becomes a habit.
Operational excellence here is the alignment between the promise and the stocking rules built to keep it. Stakeholder value erodes where the two drift apart, and the drift is gradual enough that nobody notices until the write-off arrives.
Structure protects the people holding the stock
The argument for governing this is not a tidier warehouse. Where policy is absent, the people closest to the stock absorb the consequences of decisions made elsewhere. That absorption arrives as expediting, apologies, and blame for shortages they did not cause.
That pattern erodes human capital quickly, because the work consists of managing the results of choices the person had no part in. Servant leadership expressed operationally means fixing the specification and approval structure rather than asking the warehouse to compensate for it.
Trust between functions recovers once the rules are explicit and shared. Coherence between what purchasing commits to and what operations can actually hold is a design output, and it is the thing that stops the same argument recurring every quarter.
Watch the full explainer
Related
Further material on management consulting and operational structure from World Consulting Group: [www.worldconsultinggroup.com](https://www.worldconsultinggroup.com)
-
Due Diligence: What an Operational Assessment Finds
Financial diligence establishes whether the reported numbers are real. It does not establish whether those numbers will repeat once the current owner leaves the building. Those are different questions, and only the second one determines what the buyer actually receives.
Clean financials and repeatable earnings are separate findings
A quality of earnings review normalizes the profit and loss statement. It strips out items that will not recur, adds back costs a new owner would not carry, and produces a defensible figure for what the business earned.
That figure describes the past accurately. Its usefulness for the future depends entirely on whether the mechanism producing it survives the transaction, and no accounting procedure examines the mechanism.
Operational assessment examines exactly that. It asks which people, decisions, and undocumented habits the earnings depend on, and what happens to each of them at close.
Key person dependency is a decision map rather than an org chart
Every seller says the business does not depend on them, and most believe it. The claim is testable and the test is specific.
List the decisions made in the business over a recent quarter that were consequential and non-routine. Pricing exceptions, hiring, supplier selection, scope disputes, credit decisions. Then record who actually made each one rather than who is formally authorized to.
The concentration in that list is the dependency, and it is usually severe in businesses whose owner insists otherwise. An owner who signs nothing and decides everything shows clean on paper and transfers badly.
The second tier is the thing worth examining
Whether a management layer exists below the owner is easy to verify and largely uninformative. Whether that layer has ever decided anything is the finding that matters.
Managers who execute well under close direction have not demonstrated the capability the business will need after the direction stops. That is not a criticism of them. They were never given the opportunity, and the absence of the opportunity is the defect.
Ask the second tier what they would do differently if they held the authority. Fluent, specific answers indicate latent capability. Vague answers indicate a layer that has been carrying out instructions and will require replacement or development, both of which cost time the deal model rarely includes.
Relationships held by individuals leave with individuals
Customer relationships sit somewhere on a spectrum between the person and the company. At one end the customer buys because of a specific individual. At the other they buy because of price, availability, or contractual lock.
The position on that spectrum determines what transfers. A book of business held personally by a departing owner is not an asset the buyer is acquiring, whatever the purchase agreement says about it.
Test it by asking who the customer calls when something goes wrong. Where the answer is a name rather than a function, the relationship is personal and the retention plan needs to be built around that fact rather than around an assumption.
Deferred spending flatters the earnings it postpones
Maintenance not performed, systems not replaced, and roles not filled all improve current period profit. None of them are savings. Each is a liability that has been moved off the accounts and into the operation.
Sellers preparing for a transaction have a rational incentive to defer, and the deferral is invisible in any financial statement. It appears instead as equipment near the end of its life, software that no longer receives updates, and functions running with one person where two are needed.
Walk the operation and count what has been postponed. That figure belongs in the model as a day one capital requirement, because it will be spent whether or not it was negotiated.
Working capital can be borrowed from the future
A stretched payables position and a thin inventory position both look like operating efficiency. They are frequently a loan taken from the period after close.
Suppliers extended beyond agreed terms will tighten once ownership changes, because the informal accommodation was extended to a person rather than to an entity. Inventory run deliberately low will need rebuilding before service levels are defended.
Both effects land in the first quarter of ownership and neither appears in the historical statements. Normalizing working capital is standard practice financially, and the operational version asks what it will cost to restore the position rather than what the average was.
Undocumented process is the transition liability
Businesses run on knowledge that exists nowhere in writing. Which customer accepts a substitution, which supplier will expedite for a phone call, which step in the process everybody skips because it stopped being necessary years ago.
That knowledge is an asset while the people holding it stay and a liability the moment they leave. Diligence should inventory it rather than attempt to document it, because documenting it during a transaction is neither possible nor the buyer's job yet.
The inventory is a list of processes with a name attached and a note on whether anyone else can run them. Where a critical process has one name and no alternate, that is a finding with a cost attached to it.
Integration capacity sits on the buyer's side of the table
Most diligence examines the target exclusively. The most common cause of a disappointing acquisition is not a defect in the target but an absence of capacity in the acquirer.
Integration consumes senior attention for a sustained period, and that attention is already fully allocated to running the existing business. Where no one has been freed to hold the integration, it proceeds by part time supervision and produces the predictable result.
Assess the buyer with the same rigor applied to the seller. Naming who will own the integration, and what they will stop doing in order to own it, is a diligence output rather than a post close detail.
Naming what the assessment actually produces
The deliverable is not a report describing the business. The seller already knows the business, and the buyer will not read three hundred pages during a live process.
The useful output is a short list of conditions that must be true on the first day of ownership, each with a cost, an owner, and a date. Deferred capital, retention arrangements, process coverage, and the integration owner all appear on that list.
No single framework generates that list, which is why operational diligence resists productization. The methodology is a sequence of questions rather than a template, and the sequence changes with what the previous answer revealed.
A VRIO analysis is worth running alongside it for the handful of things the seller describes as competitive advantage. Whether each is valuable, rare, difficult to imitate, and actually supported by the organization determines whether the buyer is purchasing a durable position or a temporary one.
The first hundred days are designed during diligence, not after it
Buyers routinely defer transition planning until the deal closes, on the reasonable grounds that it might not. The deferral is expensive because the access required to plan properly disappears at exactly the moment planning becomes urgent.
During diligence the seller is cooperative, the operating team is accessible, and questions carry no threat. After close the same questions arrive from a new owner and get answered defensively, which slows everything by weeks.
Draft the transition plan while the access exists. It should name who the buyer's team will work with and which decisions continue unchanged for a defined period. It should also mark every process where the two organizations need a shared definition before either can rely on it.
Continuity of the operating rhythm matters more than speed of change
New owners frequently begin by changing things, on the theory that early movement establishes authority. The operation reads that differently, especially where the changes touch routines the team relies on to get work out of the door.
Hold the operating rhythm steady through the first cycle and change the things that clearly do not work. That restraint is not timidity. It preserves the output the acquisition was purchased for while the buyer learns which parts of the structure are load bearing.
Alignment between the two leadership groups is the real precondition for any of it. Where the seller's managers and the buyer's team hold different accounts of how the business works, every subsequent decision inherits that disagreement.
Conditional rules for the assessment
Where the owner cannot take an uninterrupted two week absence, the dependency is structural regardless of what the organizational chart shows. Price and structure the deal around that finding rather than around the seller's reassurance.
Where earnings improved sharply in the period immediately before sale, examine what stopped being spent. Improvement arriving on schedule for a transaction deserves a specific explanation.
Where the second tier has no equity, no retention arrangement, and no relationship with the buyer, assume departure risk is high. The people most capable of running the operation are also the most employable elsewhere.
Where a process has one name against it and no alternate, treat it as a day one cost. Cross training after close is slower and more expensive than budgeting for it before.
Strategic fit decides what counts as a defect
An operational finding is not automatically a problem. A business dependent on its owner is a poor acquisition for a financial buyer and a reasonable one for an operator intending to run it personally.
Strategic fit is what converts a list of findings into a decision. The same dependency that destroys value in one deal structure is manageable in another, and the assessment should state which structure each finding assumes.
Operational excellence in diligence is the discipline to describe findings without grading them. Grading belongs to the buyer's strategy, and stakeholder value suffers when an adviser conflates the two.
Diligence done properly protects the people being acquired
The people inside a target are usually the last to learn what is happening and the first to absorb the consequences. Uncertainty of that duration erodes human capital before the transaction even completes.
A thorough operational assessment reduces that damage rather than adding to it. Findings that name a capability gap create a development plan, while findings that go unexamined create a surprise redundancy in month four.
Servant leadership expressed here means running the assessment to understand what people need in order to succeed after close. Trust built during that period is what allows the integration to proceed at all, and it is far cheaper to build than to repair. Coherence between what the acquired team is told and what subsequently happens does more for retention than any bonus structure.
Watch the full explainer
Related
Further material on management consulting and operational structure from World Consulting Group: [www.worldconsultinggroup.com](https://www.worldconsultinggroup.com)
-
What Management Consulting Actually Delivers
Disappointing consulting engagements are usually misspecified purchases rather than poor work. The client bought one thing and needed a different one, and both parties discovered the mismatch after the invoice. Getting the specification right is the client's job and almost nobody is taught how to do it.
Five different things are sold under one word
Information is the first, meaning facts the client does not have and could obtain with enough time. Market sizing, competitor pricing, and regulatory requirements all sit here.
Analysis is the second. The client has the data and lacks the structure to interpret it, so the engagement converts existing material into a conclusion.
Design is the third, producing a target state that does not yet exist. Installation is the fourth, meaning the target state actually operating in daily behavior. Capacity is the fifth, where the client knows exactly what to do and has nobody available to do it.
Each of the five carries a different duration, a different price, and a different test of success. Confusing any two of them produces an engagement that satisfies its own terms and disappoints anyway.
The common mismatch is analysis bought where capacity was needed
Mid-market leadership teams usually know what is wrong. They have discussed it for months and can describe it in detail without any external help.
What they lack is somebody with the time and standing to hold a change in place while it stabilizes. That is a capacity purchase, and it looks nothing like an analysis purchase in duration, staffing, or price.
Buying analysis in that situation produces a document confirming what everyone already believed. The client concludes that consulting does not work, when the accurate conclusion is that the wrong item was ordered.
The industry defaults to selling analysis for structural reasons
Analysis is easy to scope, easy to schedule, and easy to complete. It has a defined end, it can be staffed with junior people under supervision, and its delivery does not depend on the client changing any behavior.
Installation has none of those properties. It runs long, it depends entirely on client cooperation, and it fails visibly when the client will not do the difficult part. A firm optimizing for predictable delivery will drift toward the first and away from the second.
Understanding that incentive lets the client correct for it. Where the proposal converges on a document regardless of the problem described, the shape was chosen by the seller rather than by the situation.
A deliverable is the wrong unit of purchase
Engagements are almost always specified as artifacts. A report, a model, a set of recommendations, a roadmap with phases. Acceptance then means the artifact was produced to a professional standard, which it invariably was.
Nothing in that arrangement connects payment to whether the business operates differently afterward. Both parties can perform perfectly and leave the underlying condition untouched.
Specify the state change instead. What will be observably true at the end that is not true now, and how will both parties recognize it without argument. That sentence is harder to write than a deliverable list and it is the whole of the contract that matters.
Write the scope as an observable condition
A well written operational scope reads like a test rather than a promise. Orders route to a named owner within a stated window. The monthly close completes without the controller working weekends. New hires reach independent production inside a defined period.
Each of those can be checked by somebody who was not involved. None of them are satisfied by a document, and none of them can be delivered without the client changing something.
Rigor in writing that sentence protects both sides. The consultant gains a defensible definition of done, and the client gains a purchase connected to the reason they went looking in the first place.
Knowledge transfer requires a receiver with time
Every proposal contains a knowledge transfer clause and most of them fail quietly. Transfer is not a document handover. It requires a named person inside the business with capacity reserved to receive it.
That capacity is never reserved, because the person capable of receiving the knowledge is the person already fully occupied. The clause therefore resolves into a folder of files nobody opens.
Name the receiver during scoping and reduce their other commitments in writing. Where neither is possible, the engagement is a capacity purchase rather than a transfer, and pricing it as a transfer misleads everybody.
The value of an outsider decays with tenure
An external adviser is useful partly because they lack internal history. They can ask why a process exists without the question carrying an accusation, and they can describe an uncomfortable finding without a stake in who caused it.
That property erodes with time on site. After a sustained period the adviser has relationships to protect, past recommendations to defend, and a position in the informal structure. The independence that made the early observations valuable has quietly gone.
Neither party usually notices, because the relationship is comfortable by then. Building a review point into long engagements is the cheap correction, and it is a discipline the client has to impose because the adviser has no incentive to raise it.
Benchmarks describe other companies' constraints
Comparative figures are persuasive and frequently misleading below enterprise scale. A benchmark reports what a set of other organizations achieved under their own conditions, staffing, and product mix.
The mid-market variance around any such figure is enormous, so the comparison rarely identifies whether this business is performing poorly or simply differently configured. Acting on the gap treats an artifact of the sample as a defect in the operation.
Internal trend beats external comparison at this scale. Measuring the same process against itself over several periods answers the useful question, which is whether the thing is improving under the actions being taken.
Any benchmarking methodology worth using states its sample and its adjustments plainly. Where a proposal presents a comparative figure without either, the framework behind it is decoration rather than evidence.
Naming the engagement shapes and what each suits
Three engagement models cover almost everything a mid-market business needs, and the failure is nearly always selecting the wrong one rather than executing it badly.
Project work suits information, analysis, and design, because all three have natural endpoints. The engagement finishes when the answer exists, and the client owns what happens next.
Retained advisory suits a client with capable people who need periodic external judgement. Its failure mode is comfortable drift, where the sessions continue past the point of producing decisions.
Embedded or interim work suits installation and capacity. Somebody carries operational authority for a defined period and leaves behind an operating structure rather than a recommendation. Its cost is higher per month and lower per unit of change, which is the arithmetic clients most often get backwards.
What an installation engagement leaves behind
The output of installation work is not a document and not a trained individual. It is a set of operating systems that continue producing the behavior after the external party stops attending.
Concretely that means written procedures the team actually follows, a decision rhythm on the calendar, and a small number of measures somebody reviews on a schedule. None of it is sophisticated. All of it is the difference between a change that holds and one that reverts within two quarters.
Process architecture of that kind compounds. Each installed structure makes the next one cheaper, because the organization has already built the habit of running to a defined pattern rather than to individual memory.
The client side of the engagement decides the outcome
External capability is roughly half of what determines whether an engagement works. The other half is whether the client organization has arranged itself to absorb what arrives.
That arrangement is specific and checkable. One executive sponsor who will decide rather than convene. A shared account across the leadership team of what problem is being solved. Named participants whose other commitments have been reduced rather than merely acknowledged.
Where those three are absent, the engagement will produce good work that lands on an organization unable to receive it. Alignment before the start is worth more than any amount of methodology applied afterward, and it costs a single honest conversation to establish.
Conditional rules for buying
Where the leadership team can already describe the problem accurately, do not buy analysis. Buy the capacity to execute what they have already concluded.
Where the proposal is priced against deliverables rather than against an observable condition, rewrite the scope before signing. A seller unwilling to accept an operational test is telling you something useful.
Where no internal person has reserved time to receive the work, treat knowledge transfer language as decorative. Either free the person or accept that the capability leaves with the adviser.
Where an engagement has run long enough that the adviser is defending previous recommendations, the independence has expired. Close it cleanly rather than letting it decay.
Strategic fit determines what should be external at all
Not every capability gap should be filled by an outsider. Work that sits close to what the business competes on belongs inside, even where an external party could do it faster this quarter.
Work that is necessary, demanding, and permanently non-differentiating is the natural candidate for external help. The distinction is not about difficulty or cost. It is about whether owning the capability changes what the company can win.
Operational excellence in buying advice is the discipline to make that call before evaluating any provider. Stakeholder value depends more on that judgement than on which firm is eventually selected.
Good engagements protect the team rather than grade it
An engagement that arrives as an assessment of people produces defensiveness, and defensiveness produces the careful, incomplete answers that make the findings wrong. The framing decides the data quality before any interview happens.
Engagements framed around the structure get different treatment. People describe what actually happens when the question is about the process rather than about their competence, and that candour is the entire input to a useful diagnosis.
Servant leadership expressed in this context means using external help to remove obstacles rather than to justify decisions already taken. Human capital survives the first framing and erodes under the second, and teams can tell which one is in the room within a week. Coherence between the stated purpose of an engagement and how it actually behaves is what determines whether people cooperate with the next one.
Watch the full explainer
Related
Further material on management consulting and operational structure from World Consulting Group: [www.worldconsultinggroup.com](https://www.worldconsultinggroup.com)
-
Digital Transformation Without an Operating Model
An operating model has six moving parts and a transformation programme typically moves one of them. Technology changes while structure, process, data, people, and governance hold their previous shape. The result is a business that looks modernized in procurement records and behaves exactly as it did before.
Six components move together or the change does not hold
Structure determines who reports where and which functions own which outcomes. Process determines the sequence in which work travels. Technology determines what the available tools permit anyone to do.
Data determines what anybody can actually see. People determines which skills exist in the building. Governance determines how decisions get made and how quickly they arrive.
Each of the six constrains the others. A tool permitting a faster sequence delivers nothing where the governance still requires the old approvals. A redesigned process delivers nothing where the data to run it does not exist in usable form.
Programmes fail on this arithmetic rather than on execution quality. Moving one component against five that hold means the five win, because five constraints beat one capability every time.
The system will encode the organization that built it
Conway observed that systems come to mirror the communication structure of the organizations designing them. Teams that do not talk to each other produce components that do not talk to each other.
The observation is uncomfortably reliable in enterprise software. Where finance, operations, and sales each configure their own area with limited contact, the resulting system has three areas that hand off badly. The handoff problem was organizational before it was technical, and the configuration made it permanent.
Fix the communication structure before configuration begins, or accept that the structure is about to be cast into software. Buying a tool does not escape an organizational shape. It records it.
Digitizing a form does not redesign the work
Replacing paper with a screen removes filing and retains everything else. The same fields get completed by the same person, routed to the same approver, for the same reasons nobody has examined.
That substitution is worth doing and should not be described as transformation. It is a media change, and its benefits are real but bounded by the design of the underlying activity.
Redesign asks a different question. Which of these fields does anybody use, which approvals change any outcome, and what would this activity look like if it were designed now rather than inherited. Very few programmes ask it, because asking it reopens decisions people would rather leave settled.
The data model is the constraint nobody budgets for
Every capability a new system promises depends on data arriving in a consistent shape. Reporting, automation, and forecasting all collapse where that shape is inconsistent, and it usually is.
The work of defining entities, agreeing definitions, and cleaning historical records is unglamorous, expensive, and consistently omitted from the business case. It is then discovered mid-programme, at which point it gets compressed rather than resourced.
Budget it explicitly at the start. A programme treating data preparation as a task rather than as a workstream will spend the difference later. It will spend it under time pressure and at a considerably worse rate.
The same customer exists several times under several spellings
Master data problems sound technical and behave commercially. One customer entered five ways produces five partial views, none of which describes the relationship accurately.
Every downstream number inherits that fragmentation. Revenue by account, service performance, and credit exposure all become approximations, and the people using them learn to distrust the reports and reconcile privately in spreadsheets.
Declare a single system of record for each entity and enforce it. That declaration is a governance decision rather than a technical one, and it is the precondition for any claim about a single source of truth being true.
Integration debt grows faster than the system count
Each additional application connected point to point adds more than one obligation. Every new connection must be built, monitored, and updated whenever either end changes.
The maintenance load therefore grows faster than the portfolio does. Organizations reach a point where a substantial share of technical capacity is consumed keeping existing connections functional, which leaves very little for anything new.
Decide the integration approach before the third system arrives rather than after the tenth. The choice is cheap early and expensive to retrofit, and almost nobody makes it at the point where it is cheap.
The seams reveal themselves in the reporting layer
A useful diagnostic requires no assessment methodology at all. Find the reports that need manual work before anyone trusts them.
Every one of those reports marks a seam in the operating model. Somebody is reconciling two systems that disagree, or filling a gap where no system holds the field, or correcting a classification that arrives wrong.
The manual step is not the problem and removing it will not help. It is a symptom describing precisely where the model has a discontinuity, which makes the reconciliation list the best available map of what actually needs fixing.
Nobody owns the flow, only the segments
Systems are owned by function and work travels across functions. Each owner is accountable for their segment and nobody is accountable for the journey a customer order actually takes.
Delay accumulates at the boundaries as a consequence. Each handoff waits for the receiving function's own priorities, and no individual owner has visibility of the total elapsed time or authority to compress it.
Name an owner for the end to end flow with authority across the segments. That role is uncomfortable to create because it cuts across the existing structure, which is exactly the property that makes it effective.
Change saturation limits what can land at once
Organizations have a finite capacity to absorb concurrent change, and it is lower than programme plans assume. Beyond that limit additional initiatives do not proceed more slowly. They stop while continuing to consume attention.
Count what is already in flight before scheduling anything. Most mid-market businesses discover several simultaneous changes competing for the same operational managers, none of which appeared on the same list before somebody assembled it.
Sequencing against that capacity is what allows a programme to finish. Continuity of delivery matters more than the ambition of the plan, because a half installed system is worse than either the old one or the new one.
Naming the models that make this legible
The operating model framework itself does most of the work, by forcing a programme to state what happens to all six components rather than to technology alone.
A capability map contributes the honest inventory. Listing what the business must be able to do, then marking which capabilities are supported, partially supported, or performed heroically by individuals, produces a picture no system diagram contains.
Conway's observation supplies the constraint that the other two miss. Any target design that requires two groups to collaborate closely will produce a system reflecting how closely those groups actually collaborate today.
Adoption is a measurement problem before it is a training problem
Programmes report adoption as logins, completed training modules, and records created. Each of those can be high while the intended change has not occurred anywhere.
The measure worth building is behavioural rather than technical. Whether the decision the system was bought to accelerate is actually arriving faster, and whether the reconciliation somebody used to perform has stopped being necessary.
Consistency in tracking those two questions across the programme reveals problems while they are still cheap. Composure at the point where the numbers disappoint is what separates a correction from a relaunch, and relaunches are how programmes consume two budgets to deliver one outcome.
Conditional rules for the programme
Where the target design depends on data that does not currently exist in consistent form, treat data as the first phase rather than as preparation. Everything downstream inherits its quality.
Where a process is being moved onto a new system without examination, expect the same performance at a higher licence cost. The system is not the variable in that arrangement.
Where several functions are configuring their own areas independently, insert a shared design review before build. The seams created at this stage are the ones that persist for a decade.
Where the organization already has more change in flight than it can absorb, sequencing beats scoping. Adding this programme to a saturated portfolio delays everything including this programme.
Strategic fit decides what should change first
Transformation budgets get allocated to the areas with the loudest complaints, which correlates poorly with where capability actually matters. A distribution business and a professional services business need entirely different things from the same software category.
Strategic fit is the allocation rule. Capabilities close to what the business competes on deserve designed solutions and internal ownership. Capabilities that are necessary and undifferentiated deserve the standard configuration and no further attention.
Operational excellence here is the discipline to underinvest deliberately in the second category. Stakeholder value suffers most where scarce design capacity is spent perfecting something no customer will ever notice.
Structure is what makes the change survivable for people
Every component of the operating model except technology is experienced by staff as their working conditions. Moving technology alone means asking people to deliver a new outcome using the same structure, the same approvals, and the same unreliable data.
That request is answerable through extra effort for a short period, which is why early programme reports look encouraging. The effort is not sustainable, and human capital erodes through exactly the group that carried the programme furthest.
Servant leadership expressed here means moving the other five components so the effort is not required. Trust in the next change depends entirely on whether this one arrived with the structure it needed, and teams keep an accurate record of that.
Watch the full explainer
Related
Further material on management consulting and operational structure from World Consulting Group: [www.worldconsultinggroup.com](https://www.worldconsultinggroup.com)
-
Three COOs in four years. That’s not bad luck.
Three COOs in four years. That’s not bad luck.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
You copied a leadership model built for someone else’s company.
You copied a leadership model built for someone else’s company.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
You set annual goals in January. By March nobody remembers them.
You set annual goals in January. By March nobody remembers them.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
You set the goals. Nobody’s measuring if they’re hit.
You set the goals. Nobody’s measuring if they’re hit.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
You’re marketing harder, not smarter, along a leaking value chain.
You’re marketing harder, not smarter, along a leaking value chain.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
You can’t scale past the people problems holding you back.
You can’t scale past the people problems holding you back.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
Your team isn’t slow. Your decisions are stuck waiting.
Your team isn’t slow. Your decisions are stuck waiting.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
You’ve outgrown founder-led marketing. A $300K CMO isn’t the answer.
You’ve outgrown founder-led marketing. A $300K CMO isn’t the answer.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
You can’t afford a full-time COO. Bottlenecks cost more.
You can’t afford a full-time COO. Bottlenecks cost more.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
You paid for a strategy deck. You needed it deployed.
You paid for a strategy deck. You needed it deployed.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
You paid for a 150-page deck. It’s still on the shelf.
You paid for a 150-page deck. It’s still on the shelf.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
Consultants aren’t too expensive. You bought the wrong engagement.
Consultants aren’t too expensive. You bought the wrong engagement.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
You have the plan. You can’t stop being the chokepoint.
You have the plan. You can’t stop being the chokepoint.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
You’re quoted six figures for the brand, not the coach.
You’re quoted six figures for the brand, not the coach.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
Consultants hand you a report and leave. Then nothing changes.
Consultants hand you a report and leave. Then nothing changes.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
You bought expertise. What you needed was an execution system.
You bought expertise. What you needed was an execution system.
Kamyar Shah, Fractional Executive, World Consulting Group.
-
Your systems aren’t breaking. You’re hiring the wrong title.
Your systems aren’t breaking. You’re hiring the wrong title.
Kamyar Shah, Fractional Executive, World Consulting Group.
subscribe via RSS