Phase 3 · Module 1 · From Lighthouse to System
Wk 7 · 90-min workshop + ~6 hrs (wk 7–8)
🎓 PHASE 3 · MODULE 1
Without a system you get "Maintenance 2", "Miller's trick", duplicate instructions — and after 3 months, nobody finds anything. 25 minutes of architecture now beat 5 hours of cleanup later.
<30 sec
to any instruction
4–7
main categories
0
years in titles
☑️ The workshop — 90 min, 5 steps
Design the library (25 min)
Sort primarily by MACHINE/AREA ("where is the CNC-3 instruction?"), use case as a tag. 4–7 main categories.
Set the naming scheme (15 min)
[Area] · [Task] · [Variant] — "CNC-3 · Tool change · Aluminum". No years in titles — versioning happens internally.
Make the web editor routine (20 min)
Phone for recording, web editor for maintenance: bulk edits, versioning, multiple editors. Who trains when?
Migrate the existing instructions (20 min)
Categorize, rename to the scheme, tag — and spot the GAPS. The gaps are gold: they are your next backlog.
Scaling plan (10 min)
2–3 new areas, one named person per area, status check every 2 weeks.
☑️ Homework wk 7–8 (~6 hrs)
Set up the architecture in GIRI
Web-editor training for 2–3 multipliers
~1 hr per person
Migrate all phase-2 instructions
~3 hrs
Start the first 5–10 new instructions in the new areas
For module 2: which machines need content on-site, which languages?
⚠️
The 3 killers
- Keeping the scheme "flexible" — everyone invents their own. The scheme is mandatory.
- Staying app-only — works at 15, dies at 60. Learn the web editor.
- "100 instructions in 3 weeks" — nobody does that. 30–60 is ambitious AND doable.
ℹ️
Drill question
A worker suggests: "Let's name instructions however they come to mind — the scheme restricts us." What do you say?
Verwandte Artikel
Next: Module 2 · Scaling with Leverage