Planning the Bank Islam GoExplore Program: A Project Retrospective
As a Bank Islam Youth Ambassador, I planned and executed an industry visit bringing 20+ faculty students to Bank Islam KL HQ. This is an honest look at what went well, what almost didn't, and what I'd do differently.
When I became a Bank Islam Youth Ambassador (BIYA), one of the initiatives available to us was the GoExplore Program, an industry visit where students from our faculty visit a Bank Islam branch or headquarters for a firsthand look at real banking operations. The idea sounded exciting. The execution was a different kind of education.
The Brief
My objective was simple on paper: bring a group of students from my faculty at UniMAP to Bank Islam's Kuala Lumpur headquarters, coordinate logistics, and create a meaningful experience that connected classroom learning to industry reality. In practice, that meant managing 20+ participants across travel, scheduling, expectations, and institutional approvals simultaneously.
What Went Well
The biggest win was buy-in. I spent the first week not on logistics, but on communicating the value of the visit clearly to potential participants. That sounds obvious, but a lot of student event organizers skip straight to booking and end up with half the seats filled. By the time we opened registration, the spots filled within 48 hours.
The second thing that worked was building buffer time into every checkpoint. Universities have approval layers. Travel has delays. Industry visits have rescheduling risks. I learned to communicate timelines to participants based on the worst-case estimate, not the best case, and it made every step feel smooth even when it wasn't.
Communicate timelines based on the worst-case estimate. People appreciate the buffer far more than they'd resent a false promise.
What Almost Derailed It
Two days before the visit, a documentation issue surfaced with the university's approval chain. I had assumed the process was further along than it was. That assumption nearly cost us the whole trip.
The fix required two days of coordinating between three departments at short notice. We made it through, but the lesson was expensive to learn: never assume. Always confirm. Especially on anything with a hard deadline attached.
Three Things I'd Do Differently
- Start institutional approvals two weeks earlier than I think I need to
- Assign a co-lead specifically for communications, not just logistics
- Build a post-event feedback loop into the program design, not as an afterthought
The GoExplore Program ended up being one of the most valuable things I've been part of at university, not because it went perfectly, but because it demanded real problem-solving under real constraints. That's a different kind of learning than anything that happens inside a lecture hall.