Notes from SAIL: Cross-Cultural Engineering in Southeast Asia
The first thing I got wrong about SAIL was assuming the brief would be a brief.
In Singapore, an engineering brief is a document. There is a problem statement, a constraint list, a target metric, and someone in the room who can authoritatively tell you whether your interpretation of the problem is correct. By the time you start drawing on a whiteboard, the question has been closed.
In a village outside Đà Nẵng, the brief is a conversation, in three languages, with an aunt who has been collecting rainwater the same way for forty years and is politely curious about why three students from Singapore think she needs a pump.
I learned to stop drawing.
Two weeks, back to back
Indonesia then Vietnam, with no gap in between. Field work in the morning, root-cause arguments in the afternoon, LUMA design-thinking cards on a hotel floor at night. One session ran until 4am and I remember being surprised that nobody was in a bad mood — we were tired in the way you are tired after something that mattered.
The thing I actually learned about leading a team is embarrassingly simple: to be a good team leader you first have to be a good team player. My contribution on the worst nights was not direction. It was keeping the discussion alive with enough playful banter that people stayed in the room.
I also learned that the first ten words of a language do more work than the next thousand. Greeting someone properly in Bahasa or Vietnamese changed the temperature of a conversation before any engineering happened.
What works
A few patterns held across both Indonesia and Vietnam.
Show the prototype, do not describe it. Two minutes of demonstration outperformed twenty minutes of explanation, every time. The vocabulary for "vacuum-actuated" does not translate cleanly into Vietnamese. A bellows being pumped does.
Ask what already works. The community has solutions. They are usually constrained by something specific — a missing part, a seasonal failure, a maintenance burden — and the highest-leverage intervention is almost always to augment what works, not to replace it. We learned to ask "what part of this fails first" before asking "what would you like."
Default to local materials. A design that needs a part shipped from Singapore is a design that fails the day after we leave. The most useful refinements we made on-site were swapping printed PETG components for locally-sourced PVC fittings.
What I got wrong
I came in thinking the engineering was the hard part. The hard part was the listening, and the listening was made hard by my own language gaps. I am conversational in Vietnamese — meaning I can order food, ask directions, and follow about 70% of a casual conversation. That last 30% is where the brief lives.
Three weeks of intensive vocabulary work narrowed the gap. It did not close it. The most reliable thing I could do was bring a teammate or a community partner who could verify, in real time, that what I had heard was what had been said.
What stays with me
A small one. Towards the end of the trip a community elder asked, in Vietnamese, whether we had been there long enough to understand. The honest answer was no. The useful answer was that we had been there long enough to know that we had not been there long enough — and that the design we were leaving behind reflected that.
The engineering culture I want to build inside myself starts there.