(A) Product manuals
Basis for my quality guidelines:
1. Two essentials standards.
2. Network, best practice: Member of come.
3. My education: Also communication and language: Engineer (Master's degree), Aalborg University.
4. Prepared technical documentation for 22 years: Regardless of the product: Always the same challenges. I have learned to handle them.
Note: Terms of Business
NEW or "OLD"?
(A.1 ) NEW: I AM DEVELOPING instructions from scratch
- WORKPLACE AT YOUR PLACE: often necessary - for access to the product
- INPUT: WRITTEN (product data), ORAL (especially from product developers)
- GRAPHICS: Do I create in Canva - or from screenshots/photos?
- ENGLISH, GERMAN, DANISH: I need a list of technical terms from you.
- INSTRUCTIONS: Language and graphics must complement each other perfectly
(A.2) "OLD": I IMPROVE guidance
- USABILITY LAB: My role: The customer who sees the guide for the first time.
- COMPLETE CONTENT: Eg Installation, Operation, Maintenance, Disposal?
- BETTER STRUCTURE: From the table of contents: Find specific information
- ILLUSTRATIONS: One illustration for each message - hand in hand with the text
- TEXT: Reduce text volume by 20-40%. Simple, straightforward, correct language
Always the same benefits:
Win-win:
Fewer support calls
Complete, structured, illustrated, correct and simple. This is to avoid:
1.
The customer gives up and contacts support.
2.
The customer will choose another supplier in the future.
3.
You waste resources answering the same questions over and over again instead of solving it once in the documentation.
No agents:
Fast and Affordable
WAITING TIME (A): 30 minutes (due to documentation?)
TALK TIME (B): 3 minutes
I strive to:
Max Delivery Time (≈ A) =
2 x Production time (≈B), e.g.: I:
1st receives order Monday
2. begins the task on Tuesday
3. will complete the assignment on Wednesday.
