Supply Chain Management A Global Perspective

1. 1Draw the chain as flows before you draw it as companies. Per the source, SCM orchestrates materials and information flows that run from the marketplace, through your firm and its operations, to all your suppliers. Mark every point where a flow crosses from one firm to another. Those crossings are your cross-enterprise integration surface.
2. 2Check internal coordination first. The source says an organization can integrate with other chain members only if it has internal coordination, meaning marketing, operations, sourcing and logistics share information and run coordinated activities. If the four functions don't align inside your firm, fix that before you extend anything outward.
3. 3Assign each boundary crossing to the function that owns it. Sourcing links you to suppliers. Marketing links you to customers. Logistics moves and positions inventory so the right product reaches the right place at the right time. Operations turns raw materials into finished goods. Name one accountable owner per crossing.
4. 4Treat every partner as both supplier and customer (the Chapter 4 framing that every supply chain member is both). Write down what each partner needs from you and what you need from them, and use that as the basis for sharing information.
5. 5Decide what information crosses the boundary and where it enters the planning process. The source points to collaborative forecasting methods, CPFR and S&OP, as the mechanisms for shared planning. Specify the forecast and plan data each partner exchanges, how often, and which planning step consumes it.
6. 6Test the process design across firms, not only within one. The ASICS case contrasts a serial distribution network (original) with a parallel one (redesigned). For each cross-firm process, ask whether partners work one after another or at the same time, and whether any hand-off is a pure wait.
7. 7Place your chain on the stages of supply chain integration (Figure 3.5) and choose the next stage deliberately. Align your IT and network design (Figure 3.1, ERP modules) so partner data can move without re-keying.
8. 8Govern the relationships as well as the data. Relationship management is one of the three characteristics of a competitive supply chain, alongside responsiveness and reliability. Define how alliances and negotiation are handled so integration doesn't rest on goodwill alone.

The source offers two usable anchors, and it gives only their outlines. First, Starbucks: the beans come from across the globe, including Rwanda, and reach the cup through several firms. Every hand-off between those firms is a place where materials and information cross a company boundary, so the 'extended enterprise' includes the growers, the logistics providers and the store. Second, ASICS: the source's figures show its original distribution network as a serial process and its redesigned network as a parallel process, filed under the point that organizational processes cut across many functions. Applying the method: map the flows, mark each firm-to-firm crossing, and ask whether the activity on each side waits for the other. Where it does, you have a serial process, and the ASICS redesign suggests moving it to parallel. The source does not give ASICS's figures, partners or results, so any numbers have to come from your own network. The test of success is the one the source implies: the chain behaves as one enterprise serving the final customer.

• If your marketing, operations, sourcing and logistics functions do not share information or coordinate activities internally, then fix intraorganizational integration before adding partner links, because the source makes internal coordination the precondition.
• If a cross-firm process runs as a serial sequence in which each firm waits for the previous one, then redesign it toward a parallel structure, as ASICS did with its distribution network.
• If partners plan from separate forecasts, then move to a collaborative method such as CPFR or S&OP so that demand and plan information is shared rather than guessed.
• If a partner is treated only as a vendor or only as a buyer, then redefine it as both supplier and customer and design the information exchange for both roles.
• If a proposed integration step cannot be tied to responsiveness, reliability or relationship quality, then defer it, because those are the characteristics the source names for a competitive chain.

• Integrating outward while the inside is fragmented. Tell: marketing, operations, sourcing and logistics give partners different numbers or commitments.
• Treating integration as a technology purchase. Tell: ERP or IT connections exist, but no named owner, shared plan or agreed information set uses them.
• Leaving cross-firm processes serial. Tell: each firm optimizes its own step and the product still waits between firms, which is the pattern the ASICS redesign addressed.
• Seeing partners only as vendors or customers. Tell: information flows one way, upstream or downstream, and the partner is surprised by your plans.
• Optimizing locally instead of for the final customer. Tell: each firm hits its own metrics while the end customer's needs are met poorly, so the chain does not act as an extended enterprise.

• ▸Boundary crossing: name the two firms and the flow (material or information) that passes between them.
• ▸Owning function and person: name the one function (marketing, operations, sourcing or logistics) and the one individual accountable.
• ▸Internal readiness: state yes or no on whether your four functions share information and coordinate on this flow today.
• ▸Partner's dual role: list what you need from them as a supplier and what they need from you as a customer.
• ▸Information shared: list the data exchanged, its frequency and the planning step that uses it (for example CPFR or S&OP).
• ▸Process structure: mark serial or parallel and note where one firm waits on another.
• ▸Current integration stage: place the relationship on the stages of supply chain integration (Figure 3.5).
• ▸Enabling systems: record the IT, ERP or network design that supports the exchange.
• ▸Next action and test: write one change to make and how you will check that the chain performs as one enterprise for the final customer.

1. 1Separate the two halves before you measure anything. Agility is how fast and flexibly you meet changing demand: lead time, flexibility, product choice. Reliability is how consistently you perform despite uncertainty. Write one sentence for each, per product or customer segment, so you can tell which half is failing.
2. 2Inventory the uncertainty. List every source the source material names: uncertain demand, uncertain supplier ability to meet deadlines, and uncertain quality of component materials. Add any others you find. Next to each, record where you hold safety stock to guard against it, because safety stock is the visible cost of that uncertainty.
3. 3Attack reliability by redesigning the processes that drive performance, not by adding buffer. The source calls process redesign the best way to reduce uncertainty. Pick the process behind each uncertainty (supplier order handling, inbound quality checks, demand signal capture) and redesign it. Then reassess how much safety stock the uncertainty still justifies.
4. 4Raise visibility up the chain. Upstream firms typically forecast from their immediate customer's orders and cannot see downstream activity, which produces the bullwhip effect. Set up real-time sharing of demand and inventory data through IT so every entity sees the same demand signal.
5. 5Shorten the chain and shift it from forecast-driven to demand-driven. Agility comes from short chains that respond to what customers actually demand. Identify the steps between customer order and delivery that wait on a forecast, and cut or restructure them. Dell's reputation for reducing customer response time is the benchmark example.
6. 6Test where partner arrangements move decisions closer to demand. Vendor-managed inventory (as at Cisco) has suppliers manage replenishment, order fulfillment, and stock levels at the customer's distribution centers, with the vendor owning inventory until it is used. The source credits this with better communication, agility, and responsiveness. Check whether it fits your critical items.
7. 7Add resilience for the disruptions that process redesign cannot remove. Choose from the listed options: backup suppliers, built-in excess capacity, supplier screening and monitoring, required disruption plans from suppliers of critical items, and expected disruption costs included in total cost of sourcing. Lean chains have no slack to absorb even a short material-flow problem, so decide deliberately where slack goes.
8. 8Build the trust layer. The source ties robust, transparent, trust-based relationships to resilience, adaptability, and agility. Data sharing, VMI, and supplier disruption plans only work if partners will actually share and act. Assign an owner for each critical partner relationship.

The source offers a scenario, not measured data, so the example uses no figures. An influenza vaccine producer suddenly cannot receive a key ingredient from a supplier during peak flu season. Production may halt, the company's survival may be at risk, and customer welfare is jeopardized. First, classify the uncertainty: this is supplier-ability uncertainty, a reliability problem. Second, check the lean trap. If the producer has trimmed inventory and excess capacity, it has no way to make up the lost production. Third, apply the listed protections to that single critical ingredient: a qualified backup supplier, a required disruption plan from the primary supplier, ongoing screening and monitoring of that supplier's risk, and the expected cost of disruption added to the total cost of sourcing. That last step shows whether the cheaper single source is actually cheaper. Fourth, improve visibility so the supplier's constraints surface before peak season, not after. The result is a chain that stays dependable under a shock and can recover faster, which is the combination the construct names.

• If safety stock is concentrated against one uncertainty (demand, supplier deadlines, or component quality), redesign the process behind that uncertainty before adding more stock, because stock only hides the uncertainty and adds cost.
• If upstream partners plan from their immediate customer's orders, then share real-time demand data through IT. Order-to-order forecasting is the cause of the bullwhip effect.
• If customers are pressing for shorter lead times, more flexibility, or more choice, then shift the affected flow from forecast-driven to demand-driven and shorten the chain. Do not respond by lengthening the forecast horizon.
• If an item is critical and the chain is lean, then require a backup supplier or a supplier disruption plan, and include expected disruption costs in total cost of sourcing before you approve the lowest-price source.
• If a partner arrangement such as VMI is proposed, then confirm trust and information-sharing are in place first. The arrangement depends on them to deliver the agility benefit.

• Treating agility and reliability as the same thing. The tell: the team reports lead-time gains but still carries heavy safety stock and frequent missed supplier deadlines.
• Buffering instead of redesigning. The tell: safety stock keeps rising to cover uncertainty while the underlying processes stay unchanged, and costs climb.
• Running lean to the point of fragility. The tell: no spare inventory or capacity, and a short material-flow problem stops production, as lean chains experienced in the 2020 COVID-19 outbreak.
• Planning from the immediate customer's orders only. The tell: upstream demand swings are larger than end-customer demand, the classic bullwhip pattern, and partners cannot see downstream activity.
• Concentrating sourcing in one region or supplier on price alone. The tell: purchase price is the only sourcing metric, and expected disruption costs appear nowhere in total cost, so one event leaves you without supply.

• ▸Product / flow: name the product or flow being audited.
• ▸Customer demand on speed: record the lead-time, flexibility, and product-choice demands customers place on this flow.
• ▸Current response position: describe where the flow is forecast-driven and where it is demand-driven, and how many steps separate order from delivery.
• ▸Uncertainty sources: list demand, supplier-deadline, and component-quality uncertainties, plus any others, and the safety stock held against each.
• ▸Process to redesign: for the largest uncertainty, name the process that drives it and the redesign to test.
• ▸Visibility gap: state which upstream partners cannot see real-time downstream demand and what data sharing would close it.
• ▸Disruption exposure: list critical items, their single-source or single-region dependencies, and the expected cost of disruption.
• ▸Protection chosen: select from backup supplier, excess capacity, supplier screening and monitoring, supplier disruption plan, or VMI, and give the reason.
• ▸Trust and owner: name the relationship owner for each critical partner and note whether information sharing is actually happening.

1. 1Name the four dimensions you will score: cost, quality, speed of delivery, service level. Write one sentence per dimension saying what it means for your chain. The passages tie them to what customers now demand: customization, speed of delivery, and zero defects (Six Sigma performance).
2. 2Build the scorecard from both sides of the silo. Operations measures: productivity, units produced, number of defects. Marketing measures: sales, profitability, market share. Put them on one page with one owner. Two separate vocabularies are why operations and marketing managers 'were not able to communicate and had different goals'.
3. 3Assign each measure to a dimension. Productivity and carrying cost go to cost. Defects go to quality. Customer lead time goes to speed. Meeting customer requirements, flexibility and product choice go to service level. Any dimension with no measure is a blind spot, so fix it first.
4. 4Measure responsiveness as the time to meet a customer's precise requirement. Customers want shorter lead times, greater flexibility and greater product choice, so track all three. Ask whether the chain is demand driven or forecast driven. The source holds that agility comes from short, demand-driven chains.
5. 5Measure reliability by locating uncertainty. Check three sources: future demand, supplier ability to meet deadlines, and component material quality. Treat safety stock as the symptom. The source says uncertainty is the main reason companies carry it, and it raises cost.
6. 6Check visibility next. Ask whether each tier sees real-time demand or only its immediate customer's orders. Upstream tiers that forecast from the next tier's orders produce the bullwhip effect. Where visibility is missing, plan for disruption, as PPE and medical supplies showed in COVID-19.
7. 7Test cross-functional coordination with one question: does procurement learn about sales forecast changes? If not, expect excess inventory, higher carrying costs and waste. Fix the information link before changing any target.
8. 8Review the four dimensions together on a fixed cadence. Do not accept a gain on one dimension until you have checked the others. Redesign the processes that drive reliability rather than adding buffer.

The passages give a real chain-level diagnosis rather than a numeric case. Start with the silo failure they describe. Sales revises its demand forecast, but the procurement team is not told. Procurement orders too much inventory, which raises carrying costs and creates potential waste. Scored on the four dimensions, cost deteriorates because of the extra inventory, and the lack of coordination is the cause. Now take Dell as the contrasting case. Dell made its reputation as an icon of a supply chain designed and managed to reduce customer response time, which shows up as speed and service level. The source also credits that supply chain with letting Dell be limber and adapt as markets changed, including its move to IT solutions for healthcare, education and the military. The lesson is that performance sits in the links between functions. Fixing one metric inside one function does not address the cause. The passages give no figures, so you supply your own baselines.

• If safety stock is rising, then look for uncertainty in demand, supplier deadlines or component quality before blaming inventory policy, and work on reliability.
• If upstream tiers forecast only from their immediate customer's orders, then share real-time data through IT to restore visibility and reduce the bullwhip effect.
• If operations reports efficiency gains while marketing reports lost share or low variety, then the scorecard is siloed. Merge the measures and name a shared owner.
• If customers demand shorter lead times and more choice, then favor short, demand-driven structures over forecast-driven ones, since agility matters more than a long-term plan in fast-changing environments.
• If a cost reduction lowers quality or speed, then do not count it as a performance gain until all four dimensions are reviewed together.

• Scoring only operating measures (units produced, productivity, defects). The tell: marketing cannot connect the report to sales, profitability or market share.
• Buying reliability with safety stock. The tell: inventory and carrying costs climb while the sources of uncertainty stay unchanged.
• Ignoring visibility beyond the first tier. The tell: demand signals distort as they move upstream (bullwhip), and shortages arrive as surprises, as with PPE in the pandemic.
• Procurement and sales working separately. The tell: orders placed against a forecast that sales has already changed, and excess inventory follows.
• Treating relationships as arm's-length and adversarial. The tell: partners withhold data, so visibility and reliability cannot improve.

• ▸Dimension (cost / quality / speed / service level): list each of the four and add one line defining it for your chain.
• ▸Operations measure: the measure from the operations side, such as productivity, units produced or defects.
• ▸Marketing measure: the paired measure from the marketing side, such as sales, profitability or market share.
• ▸Baseline and target: enter your own current value and goal, since the source gives none.
• ▸Responsiveness check: current lead time, flexibility and product choice versus what customers ask for.
• ▸Uncertainty source (demand / supplier deadlines / component quality): name the main one driving your safety stock.
• ▸Visibility gap: which tier lacks real-time demand data, and what data-sharing fix is planned.
• ▸Cross-function link: who tells procurement when the sales forecast changes, and how.
• ▸Single owner and review date: one named person and the date for the joint four-dimension review.

1. 1Define the advantage at the level of the supply chain, not the firm. The source holds that 'it is not companies that compete. Rather, it is their supply chains that compete.' List the discrete activities from suppliers through producers, wholesalers/distributors, retailers, and customers, since the source (via Porter's value chain) says advantage comes from these activities and each contributes to total cost position.
2. 2Choose your target position on the competitive advantage matrix (Figure 2.2): a cost-productivity advantage, a value advantage (quality, innovation), or both. Write it as one sentence, then check it against your business strategy, since the source shows supply chain and business strategies must be aligned (Figure 2.1).
3. 3For a cost-productivity advantage, pick the productivity measures you will track (Figure 2.6) and set a baseline. The source treats productivity as a measure of competitiveness and ties it to Toyota Production System aims: optimize production, minimize waste, engage employees. Note that increasing sales volume is not itself a productivity advantage.
4. 4For a value advantage, start from the customer's benefit rather than the product. The source says customers 'do not buy products but rather the benefits or value provided by those products,' including intangible benefits. Translate the voice of the customer into specifications (Figure 4.5, QFD) and name which benefits (quality, innovation, time, customization) you will outdo rivals on.
5. 5Audit each supply chain stage for value. The source says stages that add no value are 'quickly bypassed or eliminated.' Mark every stage as value-adding or not, and remove or redesign the ones that are not.
6. 6Manage the three flows (products, information, funds) as the mechanism. Dell turns inventory roughly every four days and is often paid a week before it pays suppliers; map where your own cash and inventory timing give a comparable financial benefit.
7. 7Test responsiveness against rivals. Zara and H&M outperformed Forever 21 by keeping agile supply chains that adapt quickly to trends. Compare your speed of adapting to changing demand with your closest competitor's.
8. 8Monitor for failure signals: excess inventory, slow turnover, overexpansion, or cost-to-serve above a competitive level. These caused Forever 21's downfall and Webvan's failure. Review them on a fixed cadence and correct before the gap becomes structural.

Forever 21 versus Zara and H&M, as described in the source. Forever 21's downfall was 'primarily due to supply chain issues, including overexpansion, excessive inventory, and slow turnover.' Those three issues erode cost-productivity, because stock sits and capital is tied up, and they erode value, because slow turnover means products miss trends. Zara and H&M outperformed by 'maintaining agile supply chains, swiftly adapting to trends, and satisfying consumer demands.' Applying the steps: all three firms sell fashion, so the activities compared are sourcing, inventory, and distribution speed rather than the product itself. The winners show both advantage types. They hold less stale inventory (cost) and match current trends (value). The loser shows neither. The lesson is that the advantage came from supply chain capability, not from the brand or the marketing concept. The same logic appears in Webvan, which had a workable concept but could not bring grocery picking and delivery cost to a competitive level.

• If your supply chain cannot bring the cost of delivering the offer to a competitive level, then fix the cost-productivity side before investing in more marketing or concept work, as Webvan shows.
• If a supply chain stage adds no value to the customer's benefit, then bypass or eliminate it; the source says such stages are quickly removed under financial pressure.
• If inventory turns slow and stock builds while you are expanding, then pause expansion and fix turnover first, because overexpansion plus excess inventory preceded Forever 21's failure.
• If customers' demands are shifting fast, then prioritize supply chain agility and responsiveness over low-cost optimization alone, following Zara and H&M.
• If you pursue a value advantage, then define it by customer benefits (including intangibles), not by product features alone.

• Judging advantage by the firm alone rather than its supply chain. Tell: you cite brand and marketing strengths but cannot name which supply chain activities beat rivals' cost or value.
• Chasing sales volume as if it were a productivity advantage. Tell: revenue grows while productivity measures and margins stay flat or fall.
• Strong concept, weak execution of the flows. Tell: good marketing, but cost of picking and delivering exceeds what customers will bear, as with Webvan.
• Overexpansion with excessive inventory and slow turnover. Tell: warehouses fill, markdowns rise, and trend responsiveness drops, as with Forever 21.
• Defining value as the product rather than the customer's benefit. Tell: you compete on features while rivals win on intangible benefits such as speed or customization.

• ▸Target advantage type: state cost-productivity, value, or both in one sentence.
• ▸Business strategy alignment: note how the supply chain strategy supports the business strategy.
• ▸Key rival and benchmark: name the closest competitor you measure against.
• ▸Value chain activities: list each activity from supplier to customer and mark value-adding or not.
• ▸Stages to bypass or redesign: list stages with no value added and the action for each.
• ▸Productivity measures and baseline: name the measures from Figure 2.6 and the current figure for each.
• ▸Customer benefits to outdo rivals on: list quality, time, innovation, customization, or intangible benefits.
• ▸Flow check (product, information, funds): note inventory turnover and cash timing versus rivals.
• ▸Warning signs and review date: record excess inventory, slow turnover, cost-to-serve gaps, and the next review date.

1. 1Fix the definition before measuring anything: sustainable SCM lets the firm meet three tests at once: economic viability, social responsibility and environmental stewardship. Write one goal per dimension for the product or service you are assessing. A goal that serves only one dimension is a cost or marketing goal, not a triple bottom line goal.
2. 2Map the product's full chain in the order the source uses: gather component parts, combine them into a product, ship to retail, use, and dispose of the residual material. Use these as the rows of your analysis. Anything that happens after the sale (usage, disposal) stays on the map, because that is where hidden costs sit.
3. 3Build the economic baseline with total cost of ownership (TCO): the sum of procurement, manufacture, distribution, usage and disposal costs. Put a cost line against every stage. TCO captures costs that the price tag does not show.
4. 4Run the same stage-by-stage pass for environmental and social effects. Look for resource consumption such as trees for packaging and energy for freezing or baking. Look for end-of-life harm such as improper disposal of car batteries. Check people effects such as jobs created. Mark each stage's dominant risk, since the source notes that costs at each stage vary widely and carry distinct risks.
5. 5Find the single most salient risk stage. For a frozen pizza it is the cumulative consumption of packaging and energy. For a car battery it is end of life. Aim your first actions there rather than spreading effort evenly.
6. 6Choose actions that address the source's named areas: sustainable sourcing, eco-friendly product design and packaging, and sustainable manufacturing and distribution. Sequence them by maturity. Implementing lean, changing product design and optimizing distribution sit together in one implementation stage. Third-party audits that document compliance to all standards belong to a later, more formal stage.
7. 7Put disruption exposure into the economics. Include the expected cost of disruptions in the total cost of sourcing. Screen and monitor suppliers for risk, and keep backup suppliers or excess capacity where the item is critical.
8. 8Re-score after each action using the same three goals and the same stage map. Keep a record of any case where an economic gain was bought with a social or environmental loss, and treat that as an open problem, not a result.

Take the source's two contrasting products. A frozen pizza looks benign, but a TCO view shows consumption of trees for packaging, energy to freeze it and energy to bake it. A car battery's most salient risk is end of life, since improper disposal can seriously harm the environment. Run the five-stage chain (parts, assembly, shipping, use, disposal) for each. For the pizza, you target packaging and energy in the design and manufacturing stages, which fits the source's 'eco-friendly product design and packaging' and 'sustainable manufacturing and distribution'. For the battery, you target disposal, so you secure a responsible end-of-life path and count that cost in TCO, not leave it with the customer or community. In both cases the economic test is TCO, not unit price. The source applies the same logic to Tesla, whose upfront price can be higher than a conventional car's yet is judged by TCO. The social dimension has a real parallel in Apple's push to diversify its supply chain. Foxconn plans a $700 million plant in India expected to create around 100,000 jobs, which both reduces dependence on China and builds a more diverse supply chain. The source gives no cost figures for the pizza or the battery, so you supply your own numbers at each stage.

• If a product's price looks low, then compute TCO before judging it: procurement, manufacture, distribution, usage and disposal can hold costs the price tag hides.
• If the biggest risk sits at end of life, as with car batteries, then put your first effort and budget into disposal design and sourcing, not into the cheaper upstream stages.
• If a sourcing decision rests on lowest purchase price, then add the expected cost of disruptions to total sourcing cost, and require disruption plans from suppliers of critical items.
• If you are early in implementation, then start with lean, product redesign and distribution optimization. Reserve third-party audits for later, when you need documented compliance to all standards.
• If one dimension improves only by worsening another, then do not count the initiative as triple bottom line performance until the trade-off is resolved or explicitly accepted.

• Scoring economics by price, not TCO. The tell: the business case has no usage or disposal cost lines.
• Treating sustainability as a packaging or marketing exercise. The tell: actions sit only in the product-design stage while sourcing, manufacturing and distribution are untouched.
• Spreading effort evenly across every chain stage. The tell: no single stage is named as the most salient risk, so nothing gets a decisive fix.
• Equating supply chain diversification with sustainability. Moving production to reduce dependency, as in Apple's India shift, serves economic resilience and jobs. The tell: no environmental measure is reported for the move.
• Jumping to audits and compliance paperwork before the operational changes exist. The tell: certificates are in hand but lean, design and distribution changes are not.

• ▸Product/service and scope: name the item and the chain you are assessing.
• ▸Goal per dimension: write one economic, one social and one environmental goal in a sentence each.
• ▸Stage rows: list parts, assembly, shipping to retail, use and disposal, with the owner of each.
• ▸TCO cost per stage: enter the procurement, manufacture, distribution, usage and disposal cost, using your own data.
• ▸Environmental and social effect per stage: note resource consumption, end-of-life harm and people or community effects.
• ▸Most salient risk stage: name the one stage with the largest risk and why.
• ▸Disruption cost: add the expected disruption cost to total sourcing cost, and note backup suppliers and supplier plans.
• ▸Action and implementation stage: record the action (sourcing, design, packaging, manufacturing, distribution, lean) and where it sits in your rollout.
• ▸Trade-off log and re-score: record any dimension that worsened, then re-score all three goals after the action.

1. 1Write the competitive priorities in one ranked list before you touch the network. The source names the dimensions: quality, time, cost, customization, and rapid innovation. Pick the one or two you must win on, and state the others as thresholds you only need to meet.
2. 2Segment the business before designing for it. The source lists 'ways to segment supply chains' and 'market segmentation based on volume and profitability' as design inputs. Group products or customers by volume and profitability, then give each group a priority from step 1. One design for all segments is the default failure.
3. 3Set the product positioning for each segment (the source's 'product positioning strategies' and 'competitive advantage matrix'). Record the position each segment holds and the advantage it relies on. Every later design choice has to trace back to that advantage.
4. 4Design the network structure to support that strategy. Decide the number and role of nodes, and whether flow runs serial or parallel. The source's ASICS example moved a distribution network from a serial process to a parallel one. Ask for each node whether it serves the stated priority, such as speed or cost.
5. 5Derive each functional strategy from the same priority. Operations: product design, process type, layout. Sourcing: competitive bidding vs negotiation, the degree of outsourcing, and exposure to demand vs supply uncertainty. Logistics: transport mode, warehousing, cross-docking, DC location, and 3PL use. Check that no function optimizes against another.
6. 6Pick the integration level deliberately. The source describes stages of supply chain integration, with the end state a chain operating as a single entity. Information technology (IT) and ERP are the enablers, and relationship management is the precondition. Set up a cross-functional internal team that works continuously with suppliers, carriers, and distributors.
7. 7Decide how risks and rewards are shared with partners. The source warns that most firms minimize their own risk and maximize their own reward, at partners' expense. Write down which risks and gains are shared, and tie them to joint long-term goals.
8. 8Test the design against productivity measures and the disruption, security, and sustainability pressures the source names. Re-run steps 1–6 when a priority or a constraint changes.

Toyota is the source's own example of a supply chain designed around a cost advantage. Toyota brings suppliers in at the earliest stage of product design ('early supplier involvement'). It also transfers technology to suppliers, helps them source more price-competitive raw materials, trains their staff in efficient processes, and helps with their logistics so transportation costs stay low. Sourcing, operations, and logistics are therefore all set toward one aim, lower material cost. The source states the result: material costs fall sharply, which gives Toyota a great competitive advantage and a significant reduction in the cost of producing its cars. The design is deliberate because supplier development is built into the architecture, not left to purchasing negotiations. Toyota also shows the integration requirement: an internal cross-functional effort working continuously with outside partners.

• If cost is the priority, then design sourcing and logistics to lower partners' costs too (Toyota's supplier technology transfer, training, and logistics help), instead of squeezing price alone.
• If segments differ in volume and profitability, then give them different supply chain designs. Do not run one design for all.
• If a process is a serial chain of handoffs that slows the priority metric, then test a parallel redesign, as ASICS did with its distribution network.
• If a partner relationship must support strategic plans and long-term goals, then require collaboration on those plans and shared risks and rewards. Information sharing and cost focus are not enough.
• If demand or supply uncertainty is high, then choose sourcing and outsourcing structures for that uncertainty, using the source's demand vs supply uncertainty framework, and do not default to lowest-bid selection.

• Designing the network first and the strategy afterward. The tell: you cannot name which competitive priority a given facility or lane serves.
• Treating supply chain strategy as a logistics or purchasing decision. The source says SCM is commonly misunderstood this way. The tell: one function owns the design and the others only comply.
• One-size-fits-all design across segments. The tell: high-volume, high-profit products and low-volume ones use the same network and service levels.
• Adversarial or merely information-sharing partnerships. The tell: partners cut their own risk at others' expense, and there are no joint long-term goals.
• Treating IT and ERP as the design, not the enabler. The tell: integration is described by system modules and not by processes and relationships.

• ▸Segment: name the product or customer group, with its volume and profitability.
• ▸Winning priority: pick one or two of quality, time, cost, customization, rapid innovation.
• ▸Threshold priorities: list the dimensions you only need to meet, and the minimum level for each.
• ▸Network design: nodes, roles, and serial vs parallel flow, and which priority each serves.
• ▸Operations choices: product design, process type, and layout, with the reason each supports the priority.
• ▸Sourcing choices: bidding vs negotiation, outsourcing scope, and demand/supply uncertainty handling.
• ▸Logistics choices: transport mode, warehousing or cross-docking, DC location, and 3PL role.
• ▸Integration and partner terms: internal cross-functional team, external partners, and how risks and rewards are shared.
• ▸Review trigger: the change in priority, disruption, security, or sustainability that forces a redesign.

1. 1Map the three flows first. SCM is the design and management of flows of products, information, and funds. Draw your chain as suppliers, manufacturers, your own distribution centers or wholesalers, retailers, and the final customer. On each handoff, mark which of the three flows moves and who holds the data. The unmarked handoffs are your visibility gaps.
2. 2State the supply chain strategy in one sentence before choosing any system. The source frames IT as supporting strategy ('Network and IT design support supply chain strategy'). Every system you select must trace to a named strategic need: responsiveness, reliability, or relationship management.
3. 3Integrate inside the company before reaching outside. The source separates intraorganizational integration (marketing, operations, sourcing, logistics) from cross-enterprise integration. List the functions that touch an order from entry to delivery. Confirm they work from one shared record (the ERP modules view) rather than separate ones.
4. 4Test each cross-functional process for serial versus parallel structure. The ASICS example redesigned its distribution network from a serial process to a parallel one. Ask whether your systems force steps to wait on each other. If so, redesign the process and the data flow together, not the software alone.
5. 5Add sensing technology only where a gap is mapped. IoT and next-generation RFID capture real-time position and status. Place them at the handoffs you flagged in step 1, not across the whole network.
6. 6Layer analytics and AI on the shared data, not on fragmented data. The source's AI & Analytics examples are Target capturing customer preferences and UPS's navigation system. In both, the model feeds a specific operational decision. Name the decision each model feeds before building it.
7. 7Extend the data to partners through a collaborative process, not a data feed alone. The source names CPFR and S&OP as collaborative forecasting methods, and it flags the bullwhip effect as a core flow problem. Share demand information along the chain so each tier plans from the same signal.
8. 8Build security and judgment into the design. The source says threats to security force investment in systems that protect products and information at every step. It also says analytics decisions involve trade-offs beyond what the model shows. Write down who may override a system recommendation and why.

The passages give only the outline of the ASICS case: Figure 3.3 shows its original distribution network as a serial process, and Figure 3.4 shows the redesigned network as a parallel process. The details below are an illustrative reading, not facts from the source. Under a serial design, each stage acts only after the previous one finishes and passes information along. You would first mark each handoff and ask what information moves and when. Next you would check whether the ERP gives every function the same order record. Where a stage waits only for data, you would redesign it to run in parallel. The source ties this to the integration stages in Figure 3.5, which move from internal to cross-enterprise integration. Last, you would decide where sensing (RFID, IoT) or analytics adds value, and which partners need the shared data. The sequence matters: redesign the process, then wire the data to it.

• If a handoff has no shared data record, then fix that handoff before buying analytics or AI, because models trained on fragmented data inherit the fragmentation.
• If you cannot name the strategic need (responsiveness, reliability, or relationship management) a system serves, then do not buy it.
• If internal functions still run on separate records, then finish intraorganizational integration before extending to partners (cross-enterprise integration).
• If a process is serial only because information arrives in sequence, then redesign it to run in parallel and share data at the same moment, as ASICS did.
• If a model's output conflicts with cost, service, or risk considerations the model does not see, then treat it as an input to the decision, not the decision, as the 'Making Decisions with Analytics' cases teach.

• Technology-first purchasing: adopting AI, IoT, or RFID because they are described as the 'intelligent supply chain' norm. The tell: no one can say which flow or decision the tool improves.
• Automating a serial process unchanged. The tell: the new system produces the same delays, now with a dashboard.
• Partial integration: one or two functions share data while others use separate records. The tell: marketing, operations, sourcing, and logistics report different numbers for the same order.
• Treating partner data sharing as a technical feed with no joint planning process. The tell: demand signals still amplify upstream, which is the bullwhip effect, despite connected systems.
• Blind trust in analytics output, or neglecting security. The tell: managers cannot explain a model recommendation, or the data shared with partners has no stated protection.

• ▸Supply chain strategy statement: one sentence naming the strategic need (responsiveness, reliability, or relationship management).
• ▸Flow and handoff: name the handoff (e.g., supplier to manufacturer) and which flow moves (product, information, or funds).
• ▸Current data holder: who owns the record at this handoff, and in which system?
• ▸Process structure: serial or parallel? If serial, note what waits on what.
• ▸Internal integration status: do marketing, operations, sourcing, and logistics share one record here? (yes/no and why)
• ▸Visibility gap: what you cannot see in real time at this point.
• ▸Candidate technology: ERP module, IoT, RFID, analytics, or AI, tied to the gap above.
• ▸Decision it feeds: the specific decision the data or model will change.
• ▸Partner and collaboration method: who receives the data, and via what process (e.g., CPFR, S&OP)?
• ▸Security and override: how the data is protected, and who can override the system and when.

1. 1Inventory every partner relationship and place it on a continuum from arm's-length adversarial to partnership. The source treats the shift from adversarial to collaborative as a defining trait of competitive supply chains, so you need to know where each relationship sits today. Use a relationship matrix (the text's Figure 11.3). Record the partner, what flows between you (product, information, funds), and your current stance.
2. 2Decide deliberately which relationships deserve partnership effort. Not every supplier needs one. Use the sourcing criteria for competitive bidding versus negotiation (Figure 6.4) to separate relationships you bid out from those you negotiate and develop. Write down the reason for each placement.
3. 3For relationships you move toward partnership, base them on the three terms the source names: trust, commitment, and fairness. Turn each into observable behaviors you can check, for example 'shares demand information', 'honors agreed terms under pressure', 'splits gains or costs by a stated rule'. Agree on these with the partner, not just internally.
4. 4Audit whether each relationship runs on trust or on power. The text contrasts trust-based and power-based relationships (Figure 11.5). List the levers you actually use: threat of rebidding, volume leverage, or shared planning and open information. Where power dominates and you want partnership, name the specific lever to retire.
5. 5Agree on a dispute resolution procedure before a dispute exists. The text treats dispute resolution procedures as a distinct, comparable set (Figures 11.6–11.7). Choose the procedure, the escalation order, and who decides, and put them in the contract or relationship charter.
6. 6Match negotiation style and tactics to the relationship type. The text covers negotiation concepts, styles, and tactics as their own topic. In a partnership, negotiate to preserve the relationship. In a bid-driven transaction, a harder price focus fits. State your style in the prep notes before each session.
7. 7Build visibility and joint planning into the relationship. The source ties lack of visibility and coordination to disruption, citing PPE and medical supply shortages during COVID-19. It also names collaborative methods such as CPFR and S&OP. Pick one shared-information routine, such as a shared forecast or a joint planning meeting, and put it on a calendar with named owners.
8. 8Develop deep partnerships in stages and review them on a schedule. The text presents a stepwise keiretsu partnership process (Figure 11.8). Move from one stage to the next only when the trust and fairness behaviors from step 3 are being shown. Review each partnership at a fixed interval and re-place it on the matrix.

The source describes a relationship decision that retailers face with Amazon. Target uses the Amazon website for its e-commerce. Nike tried Amazon and ultimately built its own online platform to serve customers directly. The stated reason is that some retailers are moving away from Amazon's platform because unauthorized sellers can undercut prices. Read through the steps above, Nike audited a platform relationship (step 1) and found that the partner's marketplace let third parties break its pricing, so fairness was missing and Nike lacked control over the customer relationship. Nike did not try to negotiate a fix. It brought the function in-house. Target stayed, which suggests it judged the relationship worth keeping. The lesson is that you decide per relationship, against explicit criteria, whether to keep, reshape, or exit. Note that the passages give only the outline of this case, so treat the criteria you apply as your own.

• If a relationship supplies something that is complex or hard to replace, and you want better quality, innovation, or design, then move it toward partnership based on trust, commitment, and fairness. The source credits such partnerships (single-sourcing is its example) with better quality, innovation, and design, lower cost, and more responsiveness.
• If the Figure 6.4 criteria favor competitive bidding for an item, then bid it and keep the relationship transactional. Don't spend partnership effort on it.
• If a partner's behavior undermines your core economics or customer relationship (the Nike/Amazon price-undercutting case), then you either restructure the terms or exit. More goodwill won't fix it.
• If you can't name the dispute resolution procedure for a relationship, then agree one before the next negotiation or contract renewal, not after a dispute starts.
• If you can't see your partner's inventory, demand, or capacity, then add a shared-information routine before adding volume or dependence. The PPE shortages show what a lack of visibility and coordination costs.

• Declaring a 'partnership' without changing behavior. The tell: the relationship is still run by threat of rebidding and the partner is told nothing about forecasts or plans, so it is power-based under a partnership label.
• Treating every supplier as a strategic partner. The tell: the same relationship effort goes to routine items that bidding would serve, and the effort is spread too thin on the relationships that matter.
• Leaving dispute resolution undefined until a conflict arises. The tell: the first dispute produces improvised escalation, arguments about who decides, and a damaged relationship.
• Applying one negotiation style everywhere. The tell: hard-bargaining tactics used on a partner you are trying to build trust with, or soft tactics used on a bid-driven transaction where price decides.
• Never revisiting where a relationship sits. The tell: the matrix has not been updated since it was first drawn, and a partner's pricing or marketplace behavior has shifted (as with the third-party sellers on Amazon) without any decision to stay, change terms, or exit.

• ▸Partner and what flows between us: Name the partner and list the product, information, and funds flows.
• ▸Current position on the relationship matrix: Mark arm's-length adversarial, transitional, or partnership, with a one-line reason.
• ▸Bid vs. negotiate rationale: Record the Figure 6.4 criteria you applied and the result.
• ▸Trust, commitment, fairness behaviors: Write one observable, agreed behavior for each of the three, and who checks it.
• ▸Trust-based or power-based audit: List the levers you actually use today and any you will retire.
• ▸Dispute resolution procedure: State the chosen procedure, escalation order, and final decider.
• ▸Negotiation style and tactics: State the style chosen for the next negotiation and why it fits this relationship.
• ▸Shared visibility routine: Name the shared forecast, planning meeting, or data exchange, with owner and frequency.
• ▸Review date and exit trigger: Set the next review date and the condition (such as a price-undercutting or fairness breach) that triggers restructuring or exit.

1. 1Pick one cross-functional process and name its start and end. The source stresses that organizational processes cut across many functions. The order-to-delivery cycle is the model case: customer order, credit authorization, order placement to a warehouse or DC, shipper arrangement, delivery.
2. 2Map every step in sequence and tag who owns it. Mark where work waits, repeats or hands off between functions. The source shows silos producing excess inventory, for example procurement ordering without knowing the sales team's changed forecast. Handoffs are where waste hides.
3. 3Find the constraint (Theory of Constraints, Ch. 3). Improve the step that limits the whole process's output first. Improving non-constraint steps does not raise system output.
4. 4Classify each problem as waste or variation. Waste is excess inventory, expediting, rework, or shipments to the wrong location. Variation is outcomes that spread around a target. Use Lean tools (kanban cards, visual signals) for waste. Use statistical quality tools for variation.
5. 5Measure variation against the specification. Collect data with the seven tools of quality and plot it on a process control chart. Check two things: is the spread wider than the spec range, and is the process centered on the spec? Chapter 10 treats these as separate problems (process variation vs product specifications; actual variation not centered on the spec range).
6. 6Put a dollar figure on the problem using the costs of quality (Ch. 10 framework). Rank the problems by cost so effort goes to the largest ones first.
7. 7Fix the root cause, then redesign the flow. Check whether serial steps can run in parallel, as ASICS did when it redesigned its distribution network from a serial process to a parallel one.
8. 8Hold the gain with monitoring, and extend it outward. Keep the control chart running and use visual signals so deviations are seen immediately. Then collaborate with suppliers and customers on cost and quality standards, because the source treats process improvement as a joint supply-chain decision, not a single-firm one.

The source describes the pre-SCM order-to-delivery process of the 1980s and 1990s, which took weeks to months. The customer ordered by telephone, fax or mail. The order was processed manually or by computer, then went through credit authorization, order placement to a warehouse or DC, and shipper arrangement. Errors were routine: inventory was out of stock, orders were expedited at extra cost, shipments went to the wrong location. Applying the method: (1) Map the five steps and note which function owns each. (2) Tag the out-of-stock and wrong-location errors as defects and the expediting as waste. (3) Find the slowest step. The passage does not say which one it is, so you would measure it. (4) Chart the cycle time to see its spread. (5) Share information across functions, since the source ties stockouts and excess inventory to teams not sharing forecasts. (6) Compare cycle time and error rates against the baseline. The source credits this kind of supply-chain mastery for Walmart's success: collaboration with suppliers, current data-gathering technology, and current transportation techniques. It does not give before-and-after figures, so you must set your own baseline.

• If the problem is queues, excess inventory, or waiting, start with Lean flow tools (kanban, visual signals). If the problem is inconsistent output against a spec, start with control charts and statistical quality control.
• If one step limits total throughput, then improve that constraint first (TOC). Improvements elsewhere will not raise system output.
• If the process is stable but off-center from the specification, then re-center it before narrowing the spread. If it is centered but too wide, then reduce variation.
• If the root cause sits with a supplier or customer, then take it into a joint collaboration on cost and quality standards rather than fixing only your side.
• If serial steps do not depend on each other, then redesign them to run in parallel (the ASICS network redesign).

• Improving a non-constraint step. The tell: local metrics improve but overall cycle time or output does not move.
• Treating improvement as a function-level project. The tell: a fix in one department produces excess inventory or stockouts in another, as when procurement is unaware of a forecast change.
• Reacting to every data point on a control chart as a problem. The tell: constant adjustments and no reduction in spread. Distinguish normal variation from out-of-control signals before acting.
• Pursuing waste cuts or quality targets without costing them. The tell: effort spread across many small issues while the largest cost-of-quality items stay untouched.
• Ignoring the people side. The tell: gains fade after the project ends. Lean in the source includes 'Respect for People' as a core element alongside the tools.

• ▸Process name and boundaries: state the first and last step (e.g., customer order to delivery).
• ▸Process owner(s) and functions crossed: list every function that touches the process.
• ▸Step map: list each step in sequence with its owner and cycle time.
• ▸Constraint step: name the step that limits throughput and the evidence for it.
• ▸Problem type per issue: label each as waste (inventory, expediting, rework) or variation (spread vs spec, off-center).
• ▸Measurement method: name the quality tool or control chart used and the data collected.
• ▸Cost of quality: estimate the cost of each problem to rank them.
• ▸Root cause and countermeasure: state the cause and the chosen fix (e.g., kanban, parallel redesign, shared forecast).
• ▸Control plan: name the chart, visual signal, and owner that will hold the gain.
• ▸Partner involvement: list supplier or customer collaborators and the shared cost or quality standard.

1. 1Map inputs and outputs for every supply chain member, not just your own site. The sustainability model in Chapter 13 (Figure 13.1) frames sustainability as the inputs and outputs of each member. Build a one-page table of tiers: supplier, manufacturer, distributor, retailer, and returns. List what each takes in and what it sends out.
2. 2Tag each SCM decision area with its environmental effect, following Figure 13.3. Use the four areas the preface names: sustainable sourcing, eco-friendly product design and packaging, sustainable manufacturing, and sustainable distribution. Write one line per area on the effect your current choice creates.
3. 3Pair every environmental item with its social counterpart. Figure 13.2 treats the two as interconnected, so one register row holds both. A distribution change, for example, is scored for its environmental effect and its labor effect together.
4. 4Locate your organization on the stages of sustainability implementation (Figure 13.5). Name your current stage and define the next one in terms of one concrete deliverable, so the gap is explicit.
5. 5Build a risk register that runs parallel to the sustainability map. Cover the exposure types the source names: global factors (tariffs, foreign government regulation, differences in transportation and technology, cross-cultural teams), demand versus supply uncertainty (Figure 6.5), security of products and information at every step, and capacity constraints in a mode or input.
6. 6Look for single-mode or single-input dependence and flag it as a disruption point. The text's trucking example is the template: a mode used in almost all logistics movements, with a labor constraint attached.
7. 7Stress-test for extreme events, not just average variation. Chapter 13 closes with a "fat tail" diagram. Read it as a prompt to ask what happens in the rare, severe case. The preface's COVID-19 disruption is the named case, and the stated response is redesigning more resilient supply chains.
8. 8Take the redesign decision with network structure in mind. The ASICS distribution network moved from a serial design (Figure 3.3) to a parallel one (Figure 3.4). For each flagged dependency, ask whether a parallel path can replace a serial one.
9. 9Use relationship channels to surface risk. Chapter 11 covers trust-based versus power-based relationships. Choose the relationship type for each critical supplier deliberately, and use it to share risk and sustainability information.

The passages give one concrete exposure, in the trucking section. Trucks are the most flexible mode, used to some extent in almost all logistics movements, and they require little fixed investment in vehicles. But stringent driver safety regulations keep labor requirements high, and some transportation companies cannot find enough qualified drivers, which creates a capacity constraint. Run this through the register. Step 1: distribution outputs depend on a carrier tier. Step 5: the exposure type is a capacity constraint, with a regulatory cause (safety rules) and a labor cause (driver supply). Step 6: because trucks touch almost every movement, the dependence is broad, so a shortfall spreads across lanes. Step 3: the same row carries a social line, since the driver-safety rules that create the constraint are themselves a social protection. Cutting that constraint by loosening safety is the wrong response. The response is a parallel path, such as another mode or carrier, in the spirit of the ASICS redesign. The source gives no figures for this case, so the register records the dependency and the mitigation, not an invented probability.

• If one mode, supplier, or input touches almost every flow, then log it as a concentrated dependency and design a parallel alternative, as with trucking and the ASICS serial-to-parallel redesign.
• If a sustainability action lowers an environmental effect but worsens a social one, then treat it as unresolved. Figure 13.2 ties the two together, so score them in the same row.
• If a risk is rare but severe (the fat-tail case), then plan for it explicitly instead of relying on average-case variation, and name the resilience response, as in the post-COVID redesign.
• If a supplier's practices are opaque, then move the relationship toward trust-based terms before demanding data. Chapter 11 distinguishes trust-based from power-based relationships.
• If a global factor such as a tariff, regulation, or transport or technology gap changes a lane, then re-run both the risk row and the sustainability row for that lane.

• Treating sustainability and risk as two separate programs. The tell: two registers with different owners and no shared rows.
• Mapping only your own facility. The tell: no entries for supplier or customer inputs and outputs, which Figure 13.1 says to include.
• Optimizing for average conditions. The tell: no scenario or entry for a severe, low-probability event, which is exactly what the fat-tail diagram flags.
• Fixing a constraint by weakening a protection. The tell: a mitigation for the driver shortage that relaxes safety rules, which trades a capacity risk for a social one.
• Listing risks without a named structural response. The tell: a register full of descriptions and no redesign choice, such as a parallel path, a second source, or a protected data flow.

• ▸Flow and tier: name the flow (e.g., outbound distribution) and the member(s) involved.
• ▸Inputs and outputs: list what each member takes in and sends out on this flow.
• ▸Decision area: sourcing, design/packaging, manufacturing, or distribution.
• ▸Environmental effect: one line on the effect of the current choice.
• ▸Social effect: one line on the labor or community effect of the same choice.
• ▸Exposure type: global factor, demand/supply uncertainty, security, capacity constraint, or extreme event.
• ▸Concentration check: does one mode, supplier, or input carry this flow? Yes/No, and which.
• ▸Current implementation stage and the next-stage deliverable.
• ▸Mitigation or redesign: the parallel path, alternate source, or protection, plus owner and review date.