Workflow: Knowledge Transfer

Estimated time: 2-4 hours (depending on trade complexity) Difficulty: Advanced Category: 🗂️ Organization Professions: Contractors, Small business owners

🌐 Languages: English Français

Use Case

You need to transfer your trade expertise to an employee, apprentice, or successor. This workflow helps you:

⚠️ Critical stake: 60% of craft small businesses lose key know-how when senior employees leave. Documentation = business sustainability.

Prerequisites

Step-by-Step Instructions

Step 1: Know-how mapping

Help me map my trade know-how for transfer:

MY TRADE:
[Ex: Plumber, Baker, Electrician, Carpenter...]

SCOPE TO TRANSFER:
[Ex: Condensing boiler installation, Puff pastry recipe, Three-phase electrical panels...]

RECIPIENT LEVEL:
[Beginner (entry-level) / Intermediate (certified) / Advanced (mastery)]

TRANSFER CONTEXT:
[Apprentice training / Retirement handover / Employee onboarding / Company documentation]

REQUESTED MAPPING:

1. THEORETICAL KNOWLEDGE (KNOW):
   - Fundamental principles (why it works?)
   - Standards and regulations (what's mandatory)
   - Calculations and sizing (key formulas)
   - Specific technical vocabulary

2. PRACTICAL SKILLS (KNOW-HOW):
   - Technical gestures step-by-step
   - Operation sequence (critical order)
   - Specific tooling and usage
   - Realistic execution times per step

3. PROFESSIONAL TRICKS (EXPERT KNOW-HOW):
   - Unwritten professional tips
   - Problem detection (warning signs)
   - Context adaptations (plan B)
   - Common beginner mistakes (and how to avoid)

4. TRADE SOFT SKILLS:
   - Customer relations (vocabulary, posture)
   - Safety and prevention (automatic reflexes)
   - Site/workshop organization (efficiency)
   - Unexpected management (composure)

5. EXTERNAL RESOURCES:
   - Reliable suppliers (contacts, delivery times)
   - Technical documentation (codes, technical opinions)
   - Continuing education organizations
   - Professional communities (forums, networks)

Format: Mind map structured by complexity level

Save: ~/Cowork-Workspace/transfer/[know-how]/mapping.txt

Step 2: Key procedure documentation

For each identified critical know-how:

Create detailed procedure sheet for: [Procedure name]

INFORMATION:

Difficulty level: [Beginner/Intermediate/Expert]
Execution time: [Realistic time]
Usage frequency: [Daily/Weekly/Monthly/Rare]

PROCEDURE SHEET STRUCTURE:

┌─────────────────────────────────────────┐
│ PROCEDURE SHEET: [Name]                 │
│ Version: 1.0 | Date: [Date]             │
└─────────────────────────────────────────┘

🎯 OBJECTIVE
[Expected result in 1 sentence]

⚠️ SAFETY / PRECAUTIONS
- Risk 1: [Description] → Protection: [PPE/procedure]
- Risk 2: [...]
- Points of no return: [Irreversible steps requiring verification]

🧰 REQUIRED EQUIPMENT

Tools:
- Tool 1 ([Precise reference if specific])
- Tool 2 (+ acceptable alternative)

Consumables:
- Material 1 ([Quantity for standard case])
- Material 2 ([Technical specifications])

PPE (Personal Protective Equipment):
- [Gloves/Goggles/Helmet/Mask...]

📋 PRELIMINARY CHECKS

Before starting:
□ Check 1 (ex: power cutoff)
□ Check 2 (ex: measure dimensions)
□ Check 3 (ex: substrate condition)

🔧 STEP-BY-STEP PROCEDURE

Step 1: [Action title]
Action: [Precise description]
Duration: [Time]
✓ Validation: [How to verify it's correct?]
⚠️ Common mistake: [What NOT to do]
💡 Pro tip: [Expert trick]

Step 2: [Action title]
Action: [...]
Duration: [...]
✓ Validation: [...]

[Repeat for each critical step]

🎓 KEY TAKEAWAYS

1. [Fundamental principle 1]
2. [Never commit this error]
3. [Time/quality saving tip]

🔍 FINAL QUALITY CONTROL

□ Quality criterion 1 ([Acceptable threshold])
□ Quality criterion 2 ([...]
□ Functional test ([How to test?])

📞 IF PROBLEM OCCURS

| Problem | Probable cause | Solution |
|----------|---------------|----------|
| [Symptom 1] | [Cause] | [Corrective action] |
| [Symptom 2] | [...] | [...] |

🔗 TO GO FURTHER

- Applicable standard: [Code/Standard...]
- Tutorial video: [Link if existing]
- Related sheet: [Complementary procedure]

Format: Printable A4 PDF (2-4 pages max per procedure)
Save: ~/Cowork-Workspace/transfer/procedures/[procedure-name].pdf

Step 3: Progressive training path creation

Design progressive training path for: [Recipient profile]

TRAINING OBJECTIVE:
[Ex: Train entry-level apprentice to basic plumbing installation autonomy in 6 months]

INITIAL LEVEL:
- Theoretical knowledge: [Acquired/Partial/None]
- Practical experience: [X months/years or complete beginner]
- Training diplomas: [Certificate, degree, none...]

TARGET LEVEL (at path completion):
- Mastered skills: [Precise list]
- Expected autonomy: [100% / 50% / 10% supervision / Autonomous]
- Targeted certifications: [If applicable]

PATH STRUCTURE:

PHASE 1: FOUNDATIONS (Weeks 1-4)
Objective: Acquire theoretical bases + observe

Theoretical modules:
1. [Module 1]: [Content] - Duration: [Xh]
   Support: [Sheet/Video/Presentation]
   Validation: [Quiz/Exercise/Oral]

2. [Module 2]: [...]

Practical modules (observation):
1. Observe [Procedure A] - [X times]
   Instruction: Note questions, identify key steps
   Debriefing: [Points to discuss]

2. Observe [Procedure B] - [...]

Phase 1 deliverables:
□ Basic knowledge quiz (score ≥80%)
□ Observation notebook with questions
□ Self-assessment motivation/understanding

PHASE 2: SUPERVISED PRACTICE (Weeks 5-12)
Objective: Execute basic gestures under supervision

Procedures to master:
1. [Simple procedure 1]: [Name]
   - Supervised attempts: 3 minimum
   - Validation criteria: [Quality, Time, Safety]
   - Target autonomy level: 70%

2. [Simple procedure 2]: [...]

Increasing complexity:
Week 5-6: Standard cases (ideal conditions)
Week 7-9: Real cases (site constraints)
Week 10-12: Complex cases (necessary adaptations)

Phase 2 deliverables:
□ Logbook 20 documented interventions
□ Self-assessment per procedure (provided grid)
□ Tutor evaluation (observation grid)

PHASE 3: PROGRESSIVE AUTONOMY (Weeks 13-26)
Objective: Complete autonomy standard cases

Autonomous missions:
1. [Intervention type A]: Remote supervision
   Volume: [X interventions/week]
   Debriefing: Weekly (feedback, blockers)

2. [Intervention type B]: Spot-check supervision
   [...]

Cross-cutting skills:
- Customer relations: Scripts + role-playing
- Time management: Realistic multi-site planning
- Troubleshooting: Methodical failure diagnosis

Phase 3 deliverables:
□ Portfolio 50 interventions (before/after photos)
□ Skills certificate (final assessment grid)
□ Recipient experience feedback (what helped/missed)

MILESTONE EVALUATIONS:

End phase 1: ❓ Theoretical knowledge
End phase 2: 🔧 Basic technical gestures
End phase 3: ✅ Operational autonomy

SUPPORT:

Checkpoint frequency: [Daily weeks 1-4, Weekly after]
Format: [15 min debriefing + logbook notation]
Mentor: [Tutor name + backup if absent]

TEACHING RESOURCES:

□ 12 procedure sheets (step 2)
□ 5 critical gesture videos (smartphone sufficient)
□ Printable assessment grids
□ Technical library access (codes, catalogs)

Format: 6-month Gantt schedule + module sheets
Save: ~/Cowork-Workspace/transfer/training-path.pdf

Step 4: Videos and visual supports

For complex technical gestures:

Create visual support for: [Technical gesture]

SUPPORT OPTIONS:

1. SHORT VIDEO (smartphone):

Preparation:
- Target duration: 2-5 min (limited attention)
- Plan: [List steps to film]
- Equipment: Smartphone + tripod/stable support
- Lighting: Natural light or site spotlight
- Sound: Voice-over OR text subtitles

Video structure:
00:00-00:15: Intro (objective, equipment, safety)
00:15-04:00: Numbered steps (close-up key gestures)
04:00-04:30: Final result + control points
04:30-05:00: Mistakes to avoid (close-up on error)

Simple editing:
- App: iMovie (free) or CapCut
- Additions: Step numbers + indication arrows
- Export: 720p (sufficient, light file)

Save: ~/Cowork-Workspace/transfer/videos/[gesture-name].mp4

2. ANNOTATED PHOTOS (if video impossible):

Shooting:
- 8-12 sequential photos
- Constant angle (reproducibility)
- Close-up critical details

Annotations:
- Indication arrows (red/bright yellow)
- Step numbers (large, visible)
- Short captions (5-10 words max)

Assembly:
- PowerPoint/Keynote: 1 photo per slide
- Final printable A4 landscape PDF

Save: ~/Cowork-Workspace/transfer/photos/[gesture-name]-visual-guide.pdf

3. TECHNICAL DIAGRAMS (for abstract concepts):

Tools:
- Draw.io (free, online): Circuit/plan diagrams
- Excalidraw (free): Clean freehand sketches
- Photo + tablet/iPad annotations

Examples:
- Electrical circuit: Standard diagram with wire colors
- Plumbing network: Isometry with dimensions
- Assembly sequence: Numbered exploded view

Save: ~/Cowork-Workspace/transfer/diagrams/[diagram-name].png

RECOMMENDATION BY TYPE:

| Know-how type | Optimal support |
|---------------|----------------|
| Repetitive manual gesture | Short video |
| Assembly/installation | Photo sequence |
| Operating principle | Annotated diagram |
| Failure diagnosis | Decision tree (text) |
| Customer relations | Script + audio |

Step 5: Sustainable knowledge base

Structure all created supports:

Organize transfer knowledge base:

FOLDER STRUCTURE:

~/Cowork-Workspace/transfer/
│
├── 00-INDEX-GENERAL.md (this file = table of contents)
│
├── 01-fundamentals/
│   ├── trade-glossary.md (technical vocabulary)
│   ├── standards-regulations.md (codes, standards...)
│   ├── calculations-formulas.md (sizing, flows...)
│   └── basic-safety.md (PPE, certifications, risks)
│
├── 02-procedures/
│   ├── [category-A]/
│   │   ├── procedure-A1.pdf
│   │   ├── procedure-A2.pdf
│   │   └── README.md (category index)
│   ├── [category-B]/
│   └── README.md (all procedures index)
│
├── 03-videos/
│   ├── gesture-1.mp4
│   ├── gesture-2.mp4
│   └── README.md (index with thumbnails)
│
├── 04-diagrams/
│   ├── technical-diagram-1.png
│   └── README.md (diagrams index)
│
├── 05-training/
│   ├── apprentice-path.pdf
│   ├── advanced-path.pdf
│   ├── assessment-grids/ (templates)
│   └── README.md
│
├── 06-external-resources/
│   ├── recommended-suppliers.md (contacts, pricing)
│   ├── manufacturer-documentation/ (PDF catalogs)
│   ├── useful-links.md (forums, tutorials, organizations)
│   └── README.md
│
└── 07-experience-feedback/
    ├── common-mistakes.md (case studies)
    ├── tested-innovations.md (new product feedback)
    └── apprentice-faq.md (recurring questions)

INDEX-GENERAL.md STRUCTURE:

# Knowledge Base [Business Name] - [Trade]

## 📊 Statistics
- Documented procedures: [X]
- Tutorial videos: [X]
- Technical diagrams: [X]
- Last update: [Date]

## 🎯 Path by profile

### Beginner (Entry-level/Apprentice)
Start with:
1. [Link] Trade glossary
2. [Link] Basic safety
3. [Link] Apprentice training path
4. [Link] 5 essential beginner procedures

### Intermediate (Certified/2 years exp)
Focus:
1. [Link] Complex procedures
2. [Link] Failure diagnosis
3. [Link] Customer relations management

### Expert (advancement)
Deepen:
1. [Link] Trade innovations
2. [Link] Complex case studies
3. [Link] Regulatory watch

## 📁 Access by category
[Links to each section with document count]

## 🔍 Quick search
**By keyword**: [Alphabetical index]
**By training duration**: [Index by required time]
**By difficulty level**: [Index by level]

## 📝 Contribute
This base evolves with the business.
To add content: [Contribution procedure]

MAINTENANCE:

□ Annual review (June): Verify procedure currency
□ Standards update: Upon new regulation publication
□ Continuous enrichment: New cases treated → documentation
□ User feedback: Integrated feedback form

ACCESSIBILITY:

- Storage: Local server OR cloud (Dropbox/Google Drive)
- Backups: Automatic weekly
- Versions: Git (if tech-savvy) OR dated folders
- Sharing: Read access apprentices, write access tutors only

Generate complete INDEX-GENERAL.md

Save: ~/Cowork-Workspace/transfer/00-INDEX-GENERAL.md

Example Prompts

Plumber - Condensing boiler installation

Map know-how:

MY TRADE: Plumbing-Heating
SCOPE: Condensing gas boiler wall installation (residential)
RECIPIENT LEVEL: Intermediate (certified + 1 year conventional heating exp)
CONTEXT: Employee skill upgrade training for new installations

Create:
1. Complete mapping (theory + practice + tricks)
2. 3 key procedure sheets:
   - Flue exhaust sizing
   - Heating circuit hydraulic connection
   - Commissioning and combustion adjustments
3. 3-month training path (1 installation/week supervised)

Include:
- Condensing specifics vs standard boiler
- Fatal errors (cold return, condensate slope)
- Efficiency optimization settings
- Common failure diagnosis (error codes)

Format: Complete knowledge base

Baker - Sourdough bread recipe

Document know-how:

MY TRADE: Artisan baker
SCOPE: Natural sourdough bread (house tradition)
RECIPIENT LEVEL: Beginner (certified with yeast only)
CONTEXT: Signature recipe transfer before retirement

Create:
1. Complete sourdough bread procedure sheet (kneading to shaping)
2. 5 min video: Signature "bulk fermentation" gesture + folds
3. Photo sequence: Recognizing good dough development
4. FAQ: 10 common beginner sourdough mistakes (sticky dough, no rise, excessive acidity...)

Critical points to detail:
- Sourdough refresh (timing, temperature, consistency)
- Dough hydration (flour adaptation, season)
- Resting times (visual detection vs timer)
- Oven temperature + steam (precise sequence)

Pro tips to include:
- Active sourdough test (floats in water)
- Optimal fermentation detection (touch, alveoli appearance)
- Signature scoring (angle, depth)

Format: 10-page A4 transfer booklet + video + photos

Electrician - Electrical panel troubleshooting

Formalize diagnostic expertise:

MY TRADE: Building electrician
SCOPE: Residential electrical panel diagnosis and troubleshooting
RECIPIENT LEVEL: Intermediate (electrical certification, new installation exp)
CONTEXT: Diagnostic methodology training (often neglected in initial training)

Create:
1. Diagnostic decision tree (symptoms → tests → solutions)
2. Safety checklist (before any live panel intervention)
3. 5 real case studies (anonymized) with step-by-step resolution
4. Annotated diagrams: Typical failed circuit per breakdown

Methodology to transfer:
- Customer questions (when? how? frequency?)
- Visual inspection (overheating signs, oxidation, loosening)
- Multimeter tests (logical order, safety)
- Hypotheses by elimination (most probable to rare)
- Correction validation (load tests)

Professional tricks:
- Tired breaker detection (vs actual overload)
- Neutral/phase inversion identification (without color)
- Unlabeled circuit identification (quick method)

Mistakes to absolutely avoid:
- Live testing without PPE (insufficient certification)
- Component replacement without root diagnosis (recurrence)
- Schematic modification without label update

Format: 15-page diagnostic guide + diagrams + printable decision trees

Troubleshooting

Difficulty formalizing tacit knowledge

Cause: “I know how to do it but can’t explain it” Solution: Structured interview method

TACIT KNOWLEDGE EXTRACTION TECHNIQUE:

1. AUDIO RECORDING during execution:
   - Activate smartphone recorder
   - Comment aloud DURING gesture
   - "I'm doing X because Y, checking Z, if W then..."

2. TRANSCRIPTION + QUESTIONING:
   Reread transcription and for each action ask Claude:

   "Analyze this transcription and identify:
   - Unexplained actions (automatic gestures)
   - Implicit decisions (why this choice?)
   - Detected signals (what triggers action?)
   - Unmentioned alternatives (plan B if doesn't work?)"

3. THIRD-PARTY OBSERVATION:
   - Film OR have apprentice/colleague observe
   - Request questions ("Why do you do that?")
   - Note questions → answers = documentation content

4. MEMORABLE FAILURES:
   - Recall past failed interventions
   - What went wrong? Why?
   - Since then, what systematic check added?
   → These checks = externalized tacit knowledge

Repeat on 3-5 executions to cover contextual variations

Lack of time to document

Cause: Operational activity priority Solution: Opportunistic incremental documentation

TIME-SAVING STRATEGY:

Document 1 procedure/month (vs all at once):
- Choose most often taught (immediate ROI)
- 2h concentration one calm Friday afternoon
- Pre-filled template (step 2) = 50% time saving

Delegate collaborative documentation:
- Apprentice writes draft after observation
- You review/correct/validate (30 min vs 2h writing)
- Apprentice learns by formalizing (double benefit)

Reuse existing:
- Already taken site photos → annotate
- Client explanation emails → adapt to sheet format
- Detailed quotes → procedure basis

Capitalize training:
- During apprentice/intern training, record
- Presented support = documentation basis
- Questions asked = automatic FAQ

Realistic schedule:
- 10 critical procedures = 20h invested
- ROI: -80% future new hire training time (100h+/year savings)
- Payback < 6 months if hiring/handover planned

Recipient resistance (not motivated)

Cause: Training perceived as constraint, no felt need Solution: Intrinsic motivation + recognition

ENGAGEMENT TECHNIQUES:

1. INVOLVE in design:
   "What would help you most to progress?"
   → Co-create path vs impose
   → Ownership + real needs adaptation

2. GAMIFY progression:
   - Visible milestones (badges, levels)
   - "Before/after" photo portfolio (work pride)
   - Skills development graph (progress visualization)

3. PROGRESSIVE AUTONOMY:
   - Not "do exactly as I say"
   - "Test, experiment in safe framework, we debrief"
   - Empowerment (trust) > infantilizing control

4. PUBLIC RECOGNITION:
   - Present to customer: "It's [Name] who did this part"
   - Value to colleagues (meeting/break)
   - LinkedIn recommendations (if employee)

5. CAREER PERSPECTIVE:
   - Targeted certifications (advanced degrees, qualifications)
   - Future responsibilities (team lead, site autonomy)
   - Skills-linked salary evolution

If resistance persists: Frank discussion needs/expectations (trade fit?)

Obsolete documentation (trade evolution)

Cause: Standards change, techniques evolve Solution: Versioning + annual review

DOCUMENTATION MAINTENANCE SYSTEM:

1. SIMPLE VERSIONING:

Header each sheet:
"Version 2.1 | Last update: 03/15/2024 | Next review: 03/2025"

Changelog end document:
v2.1 (03/2024): Added step X following new standard Y
v2.0 (01/2024): Complete overhaul (old process obsolete)
v1.5 (06/2023): Correction step 3 error

2. SYSTEMATIC ANNUAL REVIEW:

Schedule:
- June each year (slow construction period)
- 1 dedicated day
- Checklist: [Procedures list] → Status [OK/Update/Obsolete]

Update criteria:
□ New standard published?
□ New equipment used?
□ Error detected in sheet?
□ Better method identified?

3. CONTRIBUTIVE REPORTING:

Allow users to report:
- Procedure error
- Missing information
- Tested improved method

Simple form:
"Sheet [name] - Problem: [description] - Proposal: [correction]"

Quarterly report processing

4. REGULATORY WATCH:

Alert subscriptions:
- Professional organization newsletters
- Official standards bulletin
- Trade technical journals

Upon new applicable text:
□ Identify impacted procedures
□ Immediate update (don't wait annual review)
□ Team communication (meeting/email)

VERSION ARCHIVING:

Keep obsolete versions in /archives/ folder
Useful for:
- Understand practice evolution
- Decision traceability
- Trade history training

Variations

Transfer for business succession/takeover

Specific case: Craft business sale to external buyer

COMPREHENSIVE TRANSFER PACKAGE:

Beyond technical procedures, include:

1. CUSTOMER BOOK:
   - Intervention history (who, when, what)
   - Customer particularities (access, preferences, disputes)
   - Renewal cycles (maintenance contracts)

2. SUPPLIER NETWORK:
   - Sales contacts (name, phone, negotiated terms)
   - Average delivery times
   - Emergency alternatives (if stock shortage)
   - Dispute/return history

3. ADMINISTRATIVE ORGANIZATION:
   - Quote/invoice process (software, templates)
   - Schedule management (tool, method)
   - Mandatory declarations (IRS, certifications...)

4. COMMERCIAL KNOW-HOW:
   - Sales pitches by customer type
   - Pricing grid (how to establish price, margins)
   - Common objection handling
   - Referrer networks (architects, real estate agents)

5. COMPANY CULTURE:
   - Values (what differentiates vs competitors)
   - Reputation (customer reviews, word-of-mouth)
   - Quality commitment (beyond minimum standards)

Valuation: Complete package increases sale value (+15-25% vs "just clientele")
Timeframe: 6-12 months complete documentation preparation

Micro-learning video (smartphone generation)

Format adapted to digital native apprentices:

SHORT CONTENT STRATEGY:

Principle: 1 video = 1 gesture (2-3 min max)

Minimal equipment:
- Recent smartphone (integrated stabilization)
- Support/tripod ($10)
- Lighting: Natural light OR LED site spotlight

Efficient shooting:
1. Blank rehearsal (gesture fluidity)
2. Record 3 takes (keep best)
3. Basic smartphone editing (cut intro/outro)
4. Export 720p (quality/file size compromise)

Video library:
- 20-30 short videos > 3 long videos (attention span)
- Private YouTube playlist OR shared Dropbox
- Numbered thumbnails (learning order)

Engagement:
- Comments enabled (apprentice questions)
- Simple update (redo obsolete video)
- Mobile accessible (site, workshop)

ROI: 1h shooting+editing = 10-year reusable support (vs repeating explanation x20)

Augmented apprenticeship (digital + in-person)

Best of both worlds mix:

HYBRID MODEL:

IN-PERSON (irreplaceable):
- Manual technical gestures (touch, feeling)
- Real-time error detection (immediate correction)
- Customer relations (live observation)
- Unexpected situations (context adaptation)

DIGITAL (complementary):
- Theoretical review (videos, sheets)
- Procedure verification (mobile checklist)
- Work photo sharing (asynchronous feedback)
- Off-site questions (messaging)

TYPICAL ORGANIZATION:

Monday-Thursday: Duo site work (field learning)
Friday morning: Digital theory (videos, quizzes, discussions)
Friday afternoon: Week debriefing + next week projection

Tools:
- WhatsApp/Signal: Site photos + quick questions
- Dropbox/Drive: Mobile procedure sheet access
- Trello: Acquired/in-progress skills tracking

Advantages:
- Pace flexibility (digital at own pace)
- Progress traceability (digital portfolio)
- Permanent accessibility (evening/weekend reviews)

Best Practices

  1. Start small — Document 3 critical procedures before aiming for completeness
  2. Show, make do, let do — Classic effective pedagogical progression
  3. Feedback loops — Request doc user feedback for continuous improvement
  4. Visual priority — Photos/videos > long text (understanding +70%)
  5. Trade language — Use field vocabulary, not academic jargon
  6. Valued mistakes — Document common errors = prevention
  7. Living update — Evolving vs frozen knowledge base
  8. Recognize contributors — Value those who enrich documentation (collective motivation)

Golden rule: Transfer = short-term time investment, long-term time savings. 20h documentation = 200h repetitions avoided over 5 years.

*Back to Workflows Cowork Documentation*