Giving and Receiving Direct Feedback
The Core of Dutch Communication
In the Dutch workplace, professional efficiency is driven by a concept called 'Directheid,' or directness. Unlike many cultures that use the 'sandwich method' of wrapping criticism in compliments, the Dutch prefer to get straight to the point. For you as a technician, this means feedback about machine repairs or safety will be blunt, factual, and focused on solving problems immediately.
Task-Oriented vs. Person-Oriented
Understanding the difference between 'Taakgericht' (task-oriented) and 'Persoonsgericht' (person-oriented) is vital for your success. If a colleague says, 'This report is unclear,' they are criticizing the document itself, not your intelligence. In the Netherlands, feedback is simply data used to improve a technical process, allowing you to separate your ego from your mechanical work.
Hierarchy and Speaking Your Mind
Dutch companies often operate with a 'Platte Hiërarchie,' or flat hierarchy. This means you are expected to give feedback to your supervisor if you spot a technical error. Staying silent out of 'respect' for their rank is often seen as a lack of responsibility. Technicians are encouraged to 'geen blad voor de mond nemen'—literally meaning not to put a leaf before your mouth, or to speak your mind plainly.
Review: Culture & Hierarchy
Let's pause to review the cultural foundations of Dutch feedback. Click on the terms to refresh your memory on how hierarchy and directness work together in the workshop before we move on to practical scenarios.
Scenario: The ARBO Violation
Imagine you are working on a hydraulic press. Your colleague, Bram, is not wearing his safety glasses, or 'veiligheidsbril.' This is a violation of ARBO safety regulations. Instead of making small talk, a Dutch technician says: 'Bram, you aren't wearing your glasses. That is dangerous. Put them on.' Bram's professional response is simple: 'You're right, thanks for staying sharp.'
Techniques for Giving Feedback
When giving feedback, clarity is your best tool. Start by being objective: describe exactly what you see, such as a 'storing' or malfunction. Use 'Ik-boodschappen' or I-messages to keep the focus on your observation. Crucially, do not sugarcoat. Avoid words like 'maybe' if you are sure there is an error—being clear like 'Dit is fout' is more helpful than being vague.
Techniques for Receiving Feedback
Receiving blunt feedback can be a shock, but you can handle it professionally. First, remind yourself it is about the machine, not you. If the feedback is too vague, ask for a 'concreet voorbeeld' or concrete example. Finally, summarize what you heard to confirm, such as: 'So you're saying I should measure the voltage first next time?'
Review: Practical Feedback
You've learned how to deliver and receive feedback on the shop floor. Review these technical terms and techniques before we move into a practice scenario with your colleague, Bram.
Role-Play: Correcting Bram
Meet Bram. He's an experienced technician, but he just made a mistake on a wiring diagram. Tell him directly that the diagram is wrong and explain why using the techniques we've discussed.
Common Pitfalls to Avoid
Even with good intentions, communication can fail. The 'Sandwich Trap' is common: if you start with a compliment, a Dutch colleague might think everything is fine and miss the actual criticism. Avoid defensiveness; listen to the fact first before explaining the cause. Finally, avoid vagueness. Saying something is 'not great' is unhelpful; instead, state exactly why, like 'the tolerance is too large.'
Exercise: Respond to Feedback
Your manager has just given you some very blunt feedback about your maintenance log. Type your response in the box. Remember to avoid being defensive and ask for a concrete example to make the feedback actionable.