Repository navigation
Expand file tree
/
Copy pathproblems.html
More file actions
199 lines (191 loc) · 13.7 KB
/
Copy pathproblems.html
File metadata and controls
199 lines (191 loc) · 13.7 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<link rel="icon" href="assets/web/favicon.ico" sizes="any">
<link rel="icon" href="assets/web/favicon.svg" type="image/svg+xml">
<link rel="apple-touch-icon" href="assets/web/apple-touch-icon.png">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>The problems I get called in for — Estay Dynamics</title>
<meta name="description" content="Five supply chain problems executives call me in for, the idea behind each, and a working tool that shows it.">
<link rel="canonical" href="https://kathuman.github.io/estay-dynamics/problems.html">
<meta name="theme-color" content="#1b2026">
<meta property="og:type" content="website">
<meta property="og:site_name" content="Estay Dynamics">
<meta property="og:title" content="The problems I get called in for — Estay Dynamics">
<meta property="og:description" content="Five supply chain problems executives call me in for, the idea behind each, and a working tool that shows it.">
<meta property="og:url" content="https://kathuman.github.io/estay-dynamics/problems.html">
<meta property="og:image" content="https://kathuman.github.io/estay-dynamics/assets/headers/og-image-1200x630.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Estay Dynamics — supply chain strategy and system dynamics">
<meta name="twitter:card" content="summary_large_image">
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Instrument+Serif&family=Inter:wght@400;500;600&family=IBM+Plex+Mono:wght@400&display=swap" rel="stylesheet">
<link rel="stylesheet" href="styles.css">
</head>
<body data-section="problems">
<a class="skip-link" href="#main">Skip to content</a>
<nav class="site-nav" aria-label="Main">
<div class="wrap">
<a href="index.html" class="brand">
<img class="brand-logo" src="assets/lockup/estay-lockup-dark.svg" alt="Estay Dynamics" width="163" height="36">
</a>
<button class="nav-toggle" type="button" aria-expanded="false" aria-controls="nav-links">Menu</button>
<div class="nav-links" id="nav-links">
<a href="problems.html" data-nav="problems">Problems</a>
<a href="services.html" data-nav="services">Services</a>
<a href="expertise/index.html" data-nav="expertise">Expertise</a>
<a href="index.html#tools" data-nav="tools">Tools</a>
<a href="about.html" data-nav="about">About</a>
<a href="contact.html" class="nav-cta" data-nav="contact">Book a conversation</a>
</div>
</div>
</nav>
<main id="main">
<div class="page-header">
<div class="wrap">
<div class="eyebrow">Problems</div>
<h1>The problems I get called in for.</h1>
<p class="lede">Each of these sounds like bad luck or a bad forecast. Each has a structural cause you can see, test and change. Every one links to a working tool that shows it.</p>
</div>
</div>
<section>
<div class="wrap">
<div class="service-block" id="p1">
<div>
<span class="tag">Problem 01</span>
<h3 style="margin-top:14px;">“We fix the same supply problem every year.”</h3>
<p class="sublabel mono" style="font-size:0.72rem;">Recurring problems</p>
<img class="illo" src="assets/illustrations/role-leadership.svg" alt="Fixes that fail: a quick fix relieves the problem, but after a delay its side effect brings it back" width="480" height="300" loading="lazy">
</div>
<div>
<dl>
<div class="spec-row"><dt>What it looks like</dt><dd>The same shortage, expedite or write-off returns each season. Each time it is blamed on a supplier, a planner or bad luck.</dd></div>
<div class="spec-row"><dt>What is going on</dt><dd>Recurring problems come from feedback and delays, not bad luck. Orders, stock, staffing and capacity react to each other late. Those late reactions recreate the problem.</dd></div>
<div class="spec-row"><dt>What to do</dt><dd>Map the loops with the people who run them. Then test changes on a model before trying them on the network.</dd></div>
<div class="spec-row"><dt>See it working</dt><dd><a href="https://kathuman.github.io/supply-pulse/" target="_blank" rel="noopener noreferrer">Supply Pulse</a> shows how quality holds, shelf life, hiring and a distant supplier turn a demand peak into empty shelves and expired stock. <a href="https://kathuman.github.io/claude-projects/lag-lab/" target="_blank" rel="noopener noreferrer">Lag Lab</a> splits an overshoot into its causes.</dd></div>
<div class="spec-row"><dt>Where it fits</dt><dd><a href="services.html#diagnostic">Disruption Diagnostic</a></dd></div>
</dl>
</div>
</div>
<div class="service-block" id="p2">
<div>
<span class="tag">Problem 02</span>
<h3 style="margin-top:14px;">“Planning keeps calling it forecast error.”</h3>
<p class="sublabel mono" style="font-size:0.72rem;">Overshoot after a demand step</p>
<img class="illo" src="assets/illustrations/problem-overshoot.svg" alt="After a demand step production overshoots; of 215 units above demand, 140 are necessary refill, 59 come from decision rules and 16 from the forecast" width="480" height="300" loading="lazy">
</div>
<div>
<dl>
<div class="spec-row"><dt>What it looks like</dt><dd>Demand steps up and production, stock and hiring overshoot. The review blames the forecast and buys a better one.</dd></div>
<div class="spec-row"><dt>What is going on</dt><dd>Overshoot after a demand step is the structure of planning, not the forecast. Part of it is stock and pipeline that must be refilled. Most of the rest comes from the decision rules.</dd></div>
<div class="spec-row"><dt>What to do</dt><dd>Separate the necessary refill from what the rules add. Then change the rules, which is cheaper than a better forecast.</dd></div>
<div class="spec-row"><dt>See it working</dt><dd><a href="https://kathuman.github.io/claude-projects/lag-lab/" target="_blank" rel="noopener noreferrer">Lag Lab</a> runs the same step three ways and splits the overshoot exactly. In its example, a perfect forecast removes only 7% of it.</dd></div>
<div class="spec-row"><dt>Where it fits</dt><dd><a href="services.html#diagnostic">Disruption Diagnostic</a></dd></div>
</dl>
</div>
</div>
<div class="service-block" id="p3">
<div>
<span class="tag">Problem 03</span>
<h3 style="margin-top:14px;">“We don’t know which disruption would really hurt us.”</h3>
<p class="sublabel mono" style="font-size:0.72rem;">Unclear exposure</p>
<img class="illo" src="assets/illustrations/role-cpo.svg" alt="A disruption cuts off a concentrated low-cost supplier while a second source keeps the plant supplied" width="480" height="300" loading="lazy">
</div>
<div>
<dl>
<div class="spec-row"><dt>What it looks like</dt><dd>The risk register scores dozens of threats. Nobody can say which closure would stop shipments first, or for how long.</dd></div>
<div class="spec-row"><dt>What is going on</dt><dd>Exposure is time-to-survive versus time-to-recover, not a risk-register score. A site is exposed when its stock and alternatives run out before the disruption ends.</dd></div>
<div class="spec-row"><dt>What to do</dt><dd>Screen the main sites and routes on both times. Then price the responses that close the gap.</dd></div>
<div class="spec-row"><dt>See it working</dt><dd><a href="atlas/index.html">Global Disruption Atlas</a> replays real disruptions on live chokepoint data and costs the responses. <a href="https://kathuman.github.io/claude-projects/network-stress-test/web/" target="_blank" rel="noopener noreferrer">Network Stress Test</a> finds which single site failure costs most, and what insuring against it costs.</dd></div>
<div class="spec-row"><dt>Where it fits</dt><dd><a href="services.html#diagnostic">Disruption Diagnostic</a> · <a href="services.html#flexibility-study">Network Flexibility Study</a></dd></div>
</dl>
</div>
</div>
<div class="service-block" id="p4">
<div>
<span class="tag">Problem 04</span>
<h3 style="margin-top:14px;">“We’re committing capital on one forecast.”</h3>
<p class="sublabel mono" style="font-size:0.72rem;">Capital on a single forecast</p>
<img class="illo" src="assets/illustrations/problem-capital.svg" alt="Building full scale now leaves idle capacity; staged expansion adds capacity at demand triggers as uncertainty resolves" width="480" height="300" loading="lazy">
</div>
<div>
<dl>
<div class="spec-row"><dt>What it looks like</dt><dd>A new plant, warehouse or second source is approved on one demand forecast. Flexibility appears only as a note in the margin.</dd></div>
<div class="spec-row"><dt>What is going on</dt><dd>Flexibility has a price you can calculate. The right to stage, defer, expand or lease has a value that can be set against committing now.</dd></div>
<div class="spec-row"><dt>What to do</dt><dd>Value each option against the best fixed design. Then set the triggers for the decisions that can wait.</dd></div>
<div class="spec-row"><dt>See it working</dt><dd><a href="https://kathuman.github.io/claude-projects/real-options/" target="_blank" rel="noopener noreferrer">Real Options for Network Design</a> compares committing now, the best fixed design, waiting, staged expansion and leasing on the same uncertain demand.</dd></div>
<div class="spec-row"><dt>Where it fits</dt><dd><a href="services.html#flexibility-study">Network Flexibility Study</a></dd></div>
</dl>
</div>
</div>
<div class="service-block" id="p5">
<div>
<span class="tag">Problem 05</span>
<h3 style="margin-top:14px;">“Commercial, supply and network decisions move at different speeds and collide.”</h3>
<p class="sublabel mono" style="font-size:0.72rem;">Decisions at different speeds</p>
<img class="illo" src="assets/illustrations/problem-clockspeed.svg" alt="Commercial decisions change weekly, supply monthly and network over years; out of step, they collide" width="480" height="300" loading="lazy">
</div>
<div>
<dl>
<div class="spec-row"><dt>What it looks like</dt><dd>Commercial promises change in months, the supply chain in a year, the network in years. Each function is right on its own, and the company still misfires.</dd></div>
<div class="spec-row"><dt>What is going on</dt><dd>Clockspeed mismatch is a design problem, not a coordination problem. Decisions that take effect at different speeds have to be planned together.</dd></div>
<div class="spec-row"><dt>What to do</dt><dd>Make the three speeds visible in one model. Then pace the fast decisions to what the slow ones can support.</dd></div>
<div class="spec-row"><dt>See it working</dt><dd><a href="https://kathuman.github.io/claude-projects/clockspeed/" target="_blank" rel="noopener noreferrer">Clockspeed Balancing</a> lets a leadership team fly a company for 20 years and see what each mismatch costs.</dd></div>
<div class="spec-row"><dt>Where it fits</dt><dd><a href="services.html#diagnostic">Disruption Diagnostic</a></dd></div>
</dl>
</div>
</div>
</div>
</section>
<section class="tight">
<div class="wrap">
<div class="panel" style="display:flex; justify-content:space-between; align-items:center; flex-wrap:wrap; gap:20px;">
<div>
<div class="eyebrow" style="margin-bottom:10px;">Next step</div>
<h2 style="font-size:1.5rem;">Recognise one of these? Start with a short conversation.</h2>
</div>
<a href="contact.html" class="btn">Book a conversation →</a>
</div>
</div>
</section>
</main>
<footer>
<div class="wrap">
<div class="footer-grid">
<div class="footer-about">
<a href="index.html" class="brand"><img class="brand-logo" src="assets/lockup/estay-lockup-dark.svg" alt="Estay Dynamics" width="163" height="36"></a>
<p>Supply chain resilience and network design, delivered as an interactive tool your team keeps. Copenhagen.</p>
</div>
<nav aria-label="Work with me"><h2>Work with me</h2><ul>
<li><a href="problems.html">Problems</a></li>
<li><a href="services.html">Services</a></li>
<li><a href="about.html">About</a></li>
<li><a href="contact.html">Book a conversation</a></li>
</ul></nav>
<nav aria-label="Expertise"><h2>Expertise</h2><ul>
<li><a href="expertise/systems-analysis.html">Systems analysis</a></li>
<li><a href="expertise/real-options.html">Real options</a></li>
<li><a href="expertise/network-design-optimization.html">Network design optimisation</a></li>
<li><a href="expertise/simulation-digital-twins.html">Simulation and digital twins</a></li>
<li><a href="expertise/maritime-cyber-physical-risk.html">Maritime and cyber-physical risk</a></li>
</ul></nav>
<nav aria-label="Evidence"><h2>Evidence</h2><ul>
<li><a href="index.html#tools">Tools</a></li>
<li><a href="case-studies.html">Field notes</a></li>
<li><a href="technical-depth.html">Technical depth</a></li>
<li><a href="lab.html">Lab</a></li>
<li><a href="atlas/index.html">Global Disruption Atlas</a></li>
</ul></nav>
</div>
<div class="footer-row">
<span>© <span id="year"></span> Estay Dynamics · Daniel Alberto Sepulveda Estay, PhD</span>
<span>Engagements are independent and unaffiliated with any current or former employer.</span>
</div>
</div>
</footer>
<script src="script.js"></script>
</body>
</html>