mike/shopwisdom-site
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

SW copy: move framing off the production floor → the office systems

Browse Source 
Mike: SW isn't about production spaces / operating equipment — the pressure is on
the systems, which the office runs. Reframe the floor/production imagery to office-
systems know-how: veteran "machine runs hot/bad batch" → "how a quote comes together,
pricing call"; audit "on your floor / your production" → "a few focused hours with
your team … the quotes, orders, and systems your office runs on"; "setups/scrap" →
priced/quoted, mispriced jobs/stalled orders.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Michael Victory
2026-06-24 05:16:40 -07:00
parent 8ed9bd1ffd
commit 16d56a3895
2 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
continuity-audit.html
+5 -5
View File
@@ -87,17 +87,17 @@
<div class="wrap reveal">
<p class="eyebrow">What you get</p>
<h2>A short, focused engagement — <em>not</em> weeks of disruption.</h2>
<p class="section-intro">Built around a few hours on your floor, scheduled around your production.</p>
<p class="section-intro">Built around a few focused hours with your team, scheduled around your work.</p>
<div class="cards stagger">
<div class="card">
<span class="step-k">Map</span>
<h3>A knowledge&#8209;risk map</h3>
<p>Who holds the critical know&#8209;how — the setups, the fixes, the customer history, the judgment that isn't written down anywhere. The people, the roles, and the single points of failure.</p>
<p>Who holds the critical know&#8209;how — how jobs get priced and quoted, the customer history, the workarounds nobody documented, the judgment that isn't written down anywhere. The people, the roles, and the single points of failure.</p>
</div>
<div class="card">
<span class="step-k">Quantify</span>
<h3>An honest exposure read</h3>
<p>What it would actually cost you if a key person left tomorrow — in downtime, scrap, late jobs, and lost customers. The risks ranked, so you know what's urgent and what can wait.</p>
<p>What it would actually cost you if a key person left tomorrow — in mispriced jobs, stalled orders, late jobs, and lost customers. The risks ranked, so you know what's urgent and what can wait.</p>
</div>
<div class="card feature">
<span class="card-tag">Yours to keep</span>
@@ -119,8 +119,8 @@
<p>A short conversation to make sure an audit is the right starting point for you. If it isn't, I'll say so.</p>
</li>
<li>
<h3>Time on your floor</h3>
<p>A few focused hours seeing how the work really runs and talking with the people who hold the knowledge. Scheduled around your production, not the other way around.</p>
<h3>Time with your team</h3>
<p>A few focused hours seeing how the work really flows — the quotes, orders, and systems your office runs on — and talking with the people who hold the knowledge. Scheduled around your work, not the other way around.</p>
</li>
<li>
<h3>Your report &amp; roadmap</h3>