“A Project Gets Smoother with Agile Risk Response & Bridging Tech-Business”
In this Humans of KMS edition, meet Minh Ngo, Master of Computer Science, an Engineering Manager at KMS Technology, and hear his stories from the early days of project management with memorable stumbles, to becoming one of KMS's bright minds who consistently delivers brilliant solutions to clients.
For him, the most valuable lessons learned over more than 10 years of work are perhaps his sharpened problem-solving skills, maturity in balancing technical and business mindsets, the ability to build a team that isn't afraid to take risks, learn from failures, and confidently share their opinions.
From "Almost Missed Deadlines" to "Solve It, Don't Wait"
My most memorable experiences probably involve my first project and those times we almost missed deadlines. Back then, I either didn't foresee risks, or saw them but didn't share the issues with my leader soon enough. This led to unnecessary project glitches or delays. Later on, I realized that excelling in my role in a project isn't about shouldering everything; it's about maintaining a holistic view, identifying risks, and communicating effectively Now as a project manager, I always try to let my team have their own space to work, but at the same time, they also need to see the big picture and communicate effectively to ensure we together meet our commitments.
Take the "solve it, don't wait" approach – given the nature of our work, when it comes to consulting for clients, seamless coordination and accurate signal transmission to my team are crucial. I can't unilaterally decide on actions without aligning with clients, nor can I leave the team waiting too long for further directions. After several times experiencing that, I figured my own way: Stay proactive and always have a plan B. I’l clarify client needs by assessing product features, resources, budget, and timelines. Staying updated on the client’s business helps me provide suitable solutions with risk/cost analysis and a solid plan B. For timelines, I propose options and assume approval if I don’t receive a response by the deadline. This keeps clients aware of deadlines and encourages timely decisions.
Even though every situation can be different, I still prioritize understanding what the client truly wants, while staying ready with several options and a proper timeline - This helps me balance personal discipline with the necessary flexibility when working with clients.
Bridge Technical and Business Mindsets
I’ve learned that collaboration involves understanding the expectations of everyone—from clients and leaders to team members. My role is to grasp these desires and find common ground to foster effective cooperation, basically win-win.
Once, a project I was managing had a critical bug that, from my "technical" perspective, needed an urgent fix. I put the bug in the spotlight to my client, but their response was much slower than I expected, or perhaps it wasn't their priority at that moment. The technical me was frustrated that the bug lingered, yet I couldn't understand why the client wasn't as concerned. It was only later that I realized, from a business perspective, they might put factors affecting the business on top, a bug in the system - not a top priority. My finding after this: Balancing technical and business factors is crucial; technical solutions should address and meet the client's business needs, and the tech person must understand those needs on top of all things before jumping into the project.
My habit of reading about diverse topics and delving into the art of communication helps me understand the other person's perspective more easily, especially clients. I’ve focused on uncovering the "why" behind their needs and feedback. At the same time, I also need to let them know why I'm prioritizing work in a certain order, and then clarify this with my team members. I'll continue to break down requirements into smaller parts so the team can easily conquer them with technical strengths. Trying my best to proactively listen, along with an open mind and an analytical approach have helped me navigate more easily between these two (seemingly different) ways of thinking.
Fostering a Team Culture of Experimentation, Resilience, and Open Communication
Back when I was a student, I often organized club events, but I was also very strict, turning the tension to its highest sometimes. It got to the point where, after a few events, my peers would... avoid hanging out with me. Later, I realized that a relaxed atmosphere boosts efficiency. So, besides my technical expertise, I always want to have fun, be "goofy," and build a harmonious work environment to motivate the entire team. I'm meticulous in my work, I also want to be a cheerful, approachable person who fosters connections among everyone.
Above all, I'm committed to building a "mentally safe" place where team members aren't afraid to try, aren't afraid to fail, and are confident to voice their opinions to continuously learn and grow. Just as my former leaders created opportunities for me to grow up, I hope to do the same for my teammates – so that everyone can shine at KMS, or beyond,.
My greatest achievement isn't about managing big projects. Instead, it's about daring to take on those project challenges to improve myself, and quickly finding ways to make the project run as smoothly as possible. I've developed methods for planning, delegating tasks, and creating a space for the entire team to work as effectively and confidently as they can - I believe an ideal work environment is the foundation for every KMSer's "essence" to be maximized!