Huiming Teo

Do you lead with questions or answers? One of the most challenging things for me to learn was knowing when to share my ideas and when to hold back. I am still working on it. It's always exciting when I have what I believe to be a great idea. I want to share it with my team right away. However, over the years, I have realized that my team gets better results when I ask questions about how they would solve problems before I weigh in. As leaders, we often mistakenly think we must always have all the answers. However, presenting our ideas first may lead our teams to adopt them without exploring alternatives. After all, executing the boss's idea feels safer than taking risks. Leading with questions, on the other hand, encourages your team to understand the underlying principles and concepts. They're not just memorizing an answer but learning how to approach the problem. Consider the impact of these two different approaches: 1. Telling your team, "We should refactor this code to improve its efficiency using the quicksort algorithm." 2. Asking, "How could we refactor this code to improve its efficiency? Why might your proposed method be more effective?" Engaging with questions opens the door to innovative and creative solutions you may have yet to consider. When we respect others' ideas, we often discover that their solutions are as effective—or even superior—to our own. Encouraging your team to engage in critical thinking and problem-solving fosters a deeper understanding. Rote memorization, by contrast, does little to foster comprehension or the ability to apply knowledge in new contexts. Taking time to ask questions sends a powerful message to your team: You genuinely value their ideas and see them as critical contributors to the team's success. Getting people to come up with their own solutions is really powerful because it makes them care more about the results. When team members help create plans, they're usually more committed to making them work. So, the next time you have an idea for your team, resist the urge to tell them outright. Instead, consider what questions you could ask to guide them toward discovering the same solution. It's a great way to check your work. In doing so, you may not only empower them, but also put your own reasoning to the test. Good leadership isn't about having all the solutions. It's about guiding your team to find them independently. Remember, hiring smart people loses its point if you're going to do all the thinking.

493

21 Komen

Navigating the Night Before a Major Release: Using my 21 Disciplines... As I sit here, the night before a significant software development release, I can't help but reflect on the journey that brought us here. Three years ago, I left Singapore during the uncertainty of COVID-19 and found my new home at Spirit Airlines. This night, like many others before a major milestone, is filled with anticipation and the weight of responsibility. But it's also a testament to the power of discipline and preparation. Clarity of Vision: It's essential to keep the end goal in mind. The release isn't just about pushing new code; it's about enhancing Guest experience and driving business value. Preparation and Planning: Weeks of meticulous planning and countless iterations have brought us here. Every detail has been scrutinized, every potential pitfall addressed. Adaptability: Change is the only constant. Whether it's a last-minute bug fix or an unexpected challenge, being adaptable is key. We’ve built a culture that thrives on flexibility and quick thinking. Collaboration and Communication: Open lines of communication have been crucial. From developers, business analysts other leaders to testers, every team member has played a vital role. Tonight, our Teams channels are quiet... Calmness Under Pressure: Staying calm and composed is non-negotiable. It's easy to get overwhelmed, but I remind myself and my team that we've prepared for this. Breathing techniques and short breaks can do wonders. Accountability: Each team member knows their role and takes ownership of their tasks. This accountability ensures that no detail is overlooked and that everyone is aligned. Perseverance: There have been late nights and weekends sacrificed, but our perseverance is what sets us apart. It’s this dedication that ensures we deliver top-notch results. Feedback and Improvement: Post-release, we’ll dive into feedback. What went well? What can be improved? This continuous loop of feedback ensures we keep evolving and getting better. Integrity and Trust: Trusting in the process and in each other’s abilities is fundamental. Integrity guides our decisions, ensuring that we always do what’s right for our users and our business. Celebrating Small Wins: Tonight, we also take a moment to celebrate the journey. Every bug squashed, every feature perfected is a step forward. These small wins keep us motivated. As we prepare to hit that “deploy” button, I am filled with gratitude for the incredible team that stands beside me. It’s not just about the technology; it’s about the people and the discipline that drives us. Here’s to another successful release and many more to come! If you are looking for structure in the chaos, pick up my book. #21DisciplinesForSuccess #Leadership #SoftwareDevelopment #Teamwork #Discipline #SpiritAirlines #MoreFly #Motivation #Success

36

WFH - pro tip #6 - Make proper use of the saved time. When we #WFH, we can save personal time at various stages ⏲: the commuting time 🚌, the morning dressing time 🧙‍♀️, the preparing lunch time 🥧, etc. Then, what do we do of this saved time? With 16 years of #WFH experience, I’m sharing my sixth pro tip that allows me to excel 😉 : make proper use of the saved time when #WFH! Ad pause 📢: I know that my current post is controversy. We have different cultures, we are living in different countries / cities, we have different family situations, we are different ages. Anyway, I am not afraid of a respectful discussion 😉. Then, what do we do of this saved time? We can watch one extra episode of our best serie the evening 📺. Or we can finish one extra level on our prefer cell phone game 📱. In the same time, is it really a good usage of this saved time? I think this is not. For some of us, the saved time is used for the laundry drudgery party 🎉, or cooking, or others home tasks. This is better! In some case, this is the solution to decrease the overall stress. Nevertheless, if possible, let use this time to "invest in oneself"! Easy peasy: sleep more during the night or take a nap 🛌 (see my tip #1). There is the usual "let go to gym" 🤸‍♀️. We can also use the saved time to improve in our personal hobbies 🎨 or in our professional skills 👩‍⚕️. Finally, we can spend quality time with family or friends. On my side, I did a mix of those : I am using my morning "non-commuting time" into a 40 minutes walk 🚶‍♂️, no matter the weather. I am taking a power nap during the lunch time 🛌. During the evening, I am splitting my "non-commuting time" between the job (😅) and the family, supporting my partner in the evening process. We are lucky to be able to #WFH. Let make proper use of the saved time! The text is certified 100% "#humanbrain. The picture was done using MyEdit online, thanks to an AI face swap. Thanks for reading and have a nice day!

11

HIRING FOR PRODUCT MANAGER 🔥🔥🔥 ​​We're looking ~3 years-experience Product Manager at SuperApp (YC W18). Just like Lego boxes that fit on top of one another, we are looking out for someone who has experience that can be plugged together, customized and deployed anywhere. Someone who is passionate about product features, customer needs, market research, and taking up full ownership of business goals. . 🙍Product Manager ~3 years experience. Office: Alam Sutera (Hybrid) https://lnkd.in/dEQDjUXr (apply here) . Expectations in the first week ✅ Focus: Absorb and Learn ✅ Expectations: The key thing is to actively listen and learn as much as possible. This includes: - Meeting new people and understanding the company culture - Getting set up with your workspace and tools - Learning about the product and its functionalities - Introducing yourself to key stakeholders and understanding their expectations . Expectations in the first month ✅ Focus: Deep Dive and Understand ✅ Expectations: Now that you have a basic foundation, you should delve deeper into the product and its ecosystem: - Understand the customer base and their needs through various methods (customer calls, surveys, user research) - Learn about the competitive landscape and how your product positions itself - Familiarize yourself with the product roadmap and development process - Begin building relationships with your team members (engineers, designers, marketing) . Expectations in the first three months ✅ Focus: Apply and Contribute ✅ Expectations: With a solid understanding of the product and your role, you can start applying your knowledge and contributing more: - Participate in product roadmap discussions and suggest improvements - Develop a data-driven approach to product decisions using analytics - Start working on assigned projects and contribute to the product development cycle - Communicate effectively with stakeholders and keep them informed . Hiring Stages Round 1 : HR Screening Round 2 : Interview with Head of Product and/or CPO. Round 3 : HR Interview (offering). . Why work with us At Aplikasi Super, you have the opportunity to ✅ Flexible working hours at Alam Sutera or Surabaya. ✅ A flat and transparent culture. ✅ Enjoy a culture with opportunities for exponential growth and learning with 7 squads (cross-function). ✅ Laptop Ownership Program and Learning/Course Wallet after finishing probation. . How to apply If you're interested in the role, click the link above. If you know someone talented who might be a good fit, please let him know by mention his/her name or "like" this post so we can help others too! If you're curious what's SUPER Culture, you can check my other posts or SuperApp (YC W18). For any queries you have, DM me! . Sharing is caring. We're SUPER, we're together! ~~~ #hiring #opportunity #JadiSuper #productmanager #productmanagement #hiringproduct #job #jobalert #projectmanager #projectmanagement

42

4 Komen

When it comes to machines, my MacBook is my best friend—always there for me, except when it decides to update right before a deadline! 😅💻 If you can relate to it, share your fun tech stories in the comment section. 😄 #MacBook #Loyalty #TechLife #FunnyButTrue #Technology #Machines

42

6 Komen

Well, this is interesting. Got some person who reached out from Singapore asking for "Collaboration". They wanted US based project work that can be found on job boards or freelance websites (which btw, aren't reliable in any event) They wanted to ultimately use my laptop (through remote) and be able to find and bid for jobs and would share the profit with me. They cannot do it themselves because these websites would block their region or flag it so they wanted to use a US based IP. A VPN apparently does not work for them. Obviously, this is sus - I played along with it to see how far they would go. And yes, we had a video call! When asked about payment, they said that it would be after project completion. oh really? No person in the right mind would agree to that type of agreement let alone "loaning" them your equipment for remote access or even have you do the searching for them for free. Stay aware and alert folks! Desperate times I suppose but morally and ethically, to me at least, not right.

7

1 Komen

From being a Testing Engineer → Backend Development ⭐! (Sharing my colleague story) So, my friend who started his Software Engineering career as a Tester at Adobe, made a switch to development internally after dedicated more than 5 years!💪 For them, the decision was a difficult one but not an impossible one. Their transition was not at all easy and had its challenges to cross. So, here are 3 points that helped them greatly, hope they help you too → 1️⃣ If you dream of moving into Development, UPSKILL Rigorously. 👍 You need to have a solid understanding of not just DSA but System Design as well. Like, they dedicated significant time to learning new programming languages & tech to keep themselves updated. ✅ To become the best in topics, they revised it thoroughly and made sure to engage into projects. 2️⃣ The Testing Experience helped them a lot. It’s the background only that made them a better Backend Developer. 🙌 Their testing experience helped them design keeping the tests in mind which improved the Code quality. 3️⃣ Lastly, NETWORKING was the net worth. 💪 They made sure to extensively connect with like-minded people on LinkedIn & other platforms, which helped them get a lot of great opportunities. Now, I know switching careers, especially within such different domains of tech, is not easy, and has its own set of issues. However, if you really dream of moving into Development, and need the right support & guidance, I’d suggest taking the help of MAANG experts at Bosscoder Academy. Check them here: https://bit.ly/4b0gHmI Enrol in a course that’s specially designed for 7+ years of experienced professionals and get: ✅ Structured curriculum heavily focused on DSA & System Design. ✅ Live Weekend Classes, with Limited Batch Size with only experienced Working Professionals. ✅ Personal Mentorship from Industry Veterans working with MAANG. ✅ 24/7 Doubt Support & Placement Assistance for Senior Roles. #adobe #collab #development

46

1 Komen

Do you believe in power naps? I recently saw one of my teammates taking a powernap, after continuously working for certain hours,. It reminded me that I used to take this a lot in my early career. It was a way to rejuvenate your body from extra stress. We used to have something similar in our school days when if the teacher were in a good mood, they would ask us to head down for half an hour. Power nap does have a lot of advantages for our mental health. We can ask our body to hibernate while reducing extra stress and stop thinking about anything but relaxing. It can help in improving productivity, mood change, and so on. It can also help in controlling your sleeping hours. While I don't take this anymore during office hours due to busy schedules, I still find that very effective. These days post-workout, I take at least 15-20 mins of power nap. After draining all your energy, these few minutes of sleep are like a lifesaver. Have a great week ahead :) #life #health #fitness #corporate #office #powernap #work #energy #productivity #benefits

8

WFH - pro tip #8 - Have personal calls with your colleagues ☎! When we work at the office, we interact directly with a lot of people: our teammate, our peers, our boss, the colleagues in other service, etc. For sure, we discuss work. But we also have some personal discussions. We speak of our family , our passions, our pets 🐱 🐶 🐹. Each time we stand up and we "walk" 🚶‍♀️, we have a chance to meet someone. Sometime, we need a break... and we will walk to a colleague desk and have a "personal" discussion 🗣. Some decisions are made during informal hallway discussions, without the need of a formal meeting. During the lunch time, we will see and meet a lot of people. Time to time, we will eat in a restaurant and have fun 🎉. Finally, we can fix more simply a conflict when people are physically in the same room 🤼‍♀️. While when we #WFH, we have no physical interaction. During a webcam call, we are more serious ; we don't want to "waste" time. If we want to take a break, we will go in our kitchen in our home / apartment. During the lunch time, we will do personal stuffs. Then, we need to be fair. When we 100% #WFH, we have a lack of communication with our colleagues. What can be the impacts? 💡 Ideas and experiences will not spread across the company. One time, an office lunch discussion allowed me to figure out a solution to fix a problem of my team. 😮 Without personal conversation, our relationships will be a bit more superficial, we will have less compassion. After this long introduction: with 16 years of #WFH experience, I’m sharing my eighth pro tip that allows me to excel 😉: let have personal calls with your colleagues! Let schedule some regular virtual calls with some colleagues during the lunch time. I think we should limit those calls to 3 / 4 people. Let organize some online board games during the lunch time. Invite "every body". When we have a call related to the work, let take some time to have a personal discussion. As argued in my pro tip #5, let turn on our webcam. Finally, we should be able to ping someone in Teams / Slack and propose to have a personal discussion, not related with the work. The text is certified 100% #humanbrain. The picture was done using MyEdit online, thanks to an AI face swap. Thanks for reading and have a nice day!

16

1 Komen

As part of my ongoing Medium journey sharing management insights over the past 2 years, I published a new article on 5 key things to know before becoming an engineering manager. Having made the transition myself, I cover critical insights that can help prepare engineers for a management role: https://lnkd.in/dZFWDQtZ

25

I had to interview 10 year SWE and 8 year PM Mario Di Nucci on this hot take. Here's what I learned. There are 3 primary reasons why PMs in general are on the frontline for layoffs, alongside QA and recruiting: 1. Product is typically too layered 2. It’s challenging to quantify PM’s work 3. Most PMs are middlemen So my question was: are there any solutions? Here's what Mario answered: For 1 & 3 there are solutions, but they are still rare. The reasons are: For 1 - being too layered - it can be overcome: ↳ Team just have to stay disciplined with ratios. ↳ Generally, a better PM:Eng ratio is something lean like 1:10. ↳ And in terms of layering, having a product leader for every 5 or so PMs makes sense. "Trust is the key, so you cannot control what cannot be controlled. With proper OKRs system in place, you can synch teams across the company and making sure they are all performing (or maybe not) toward the same goals." For 2 - hard to quantify - a clear solution doesn't exist: ↳ A PM shares most metrics, that they own, with other functions. ↳ Engineering has tickets, Market has budgets. ↳ PMs have...? "Folks have proposed KPIs like conversion rate or user satisfaction to measure the work of a PM. According to my personal experience, these quantities are owned by multiple teams in the company, and maybe they are measurable successfully in the middle to long run. But, for sure, they cannot give the measure of what a single PM does." For 3 - middle-men - it can be overcome: ↳ The problem is PMs are usually not empowered. ↳ If PMs decide the solution and can say no, then that's ownership. ↳ But that model often breaks down as the PM tries to say no to an urgent request, but isn't able to, which upsets engineering. "When you are fully empowered to solely drive discovery, and choose the solution (the WHAT), PMs are not middle-men." In Mario's experience, only 1 out of 10 companies he worked at actually operate that way, though. Check out the complete interview here (free, no paywall): https://lnkd.in/gyA4rAEc

193

39 Komen

Really enjoyed my chat with Matt Hinds, CEO of Sauce, where we talked about transforming product vision into company strategy, partnering with CEOs, and protecting teams against planning busy work that gets thrown away in Q1. As we head into company planning season, here’s the tl;dr on how to get planning right: 📝 Define the strategy — Create a 1-pager (ok, maybe a 2-pager) that includes: the mission, what that means for customers in 3 years time, and investment areas for the next 12-18 months. 👥 Design the org — Spend a lot of time on org design so your teams reflect that strategy. 🎯 Clarify the investment areas — What’s even more important than what you’re investing in, is what you’re not investing in. Make sure your teams know what to focus on and what falls away. 🔨 Empower teams — Let the what’s and how’s come from the team. As a leader, it’s not up to you to dictate what we need to build. You need to empower your teams to decide that based on their in depth understanding of your customers and business. Curious to know what others biggest learnings have been when it comes to planning? Drop me a comment below and let's compare notes 👇 #product #startups #productmanagement

40

5 Komen

A while back, I joined Coding Your Career, a group made by Jonathan Hop. I'm working with a team to build what will hopefully be a real enterprise grade application. Senior dev set up a Vue/Nuxt application with Electron and C# backend. I pulled the code a couple of days ago. The Jest import wasn't working because Jest wasn't installed in the Node modules and the paths had some kind of issue, so I went in circles trying to get TS Jest working and the test to pass, over various still-confusing-to-me errors. But after several debugging circles, this one small error finally got debugged and the code is now running. MAN, THIS SURE FEELS LIKE OLD TIMES and like my real job. 😅 Hilariously, between this and some other stuff working out lately, I'm in an incredibly good mood towards my field again for the first time in a minute. Never thought I'd feel such joy and nostalgia at a debugging loop followed by code somehow being resolved through some means. (And by some means, I mean me switching CommonJS and ESNext and various syntax for module imports and various .js, .mjs, and .ts extensions for for the Jest config file and adding/removing things to Package.json, with some advice from good ol' ChatGPT along the way, until some combination of these means finally worked. Do I know what I am doing or know this framework yet? No! Do I feel excited to keep digging around and making this thing better? Yes!)

7

3 Komen

As a tech guy, upon reflection, I have learned many lessons late in life. Predominantly, the following are the most important ones. Work ethic is a choice, not a skill or talent. The ownership of work is what determines your place or worth. Deliverability is what matters the most, not 100% quality or astonishing communication. #SoftwareEngineer #LessonsLearned

12

2 Komen

PoC or MVP? That is the question. Choosing between a PoC (Proof of Concept) and an MVP (Minimum Viable Product) is not as straightforward as it may seem. Recently, I spoke with a founder grappling with this dilemma. While some may argue for jumping straight into MVP, I believe there’s a distinct time and place for both approaches, depending on the context and goals. As a developer, I see the differences between PoC and MVP development from a slightly different perspective. A PoC is all about proving a concept's technical feasibility. It’s a stripped-down version with minimal features, meant to validate whether the idea can work. The development process here is often quicker and doesn’t prioritize scalability or long-term use. Think of it as a quick test run—just enough to see if the foundation is stable. On the other hand, MVP development is a different ball game. It’s a product with core functionalities, ready to be introduced to the market and tested by real users. Here, user experience, scalability, and code quality matter because this is what your audience will interact with. Unlike PoCs, MVPs need to hold up under real-world conditions. At Pecode, we help founders make this decision based on their unique needs—whether that’s validating an idea with a PoC or launching a market-ready MVP. What stage of development is your startup in, and how are you deciding between PoC and MVP? #StartupDevelopment #PoCvsMVP #ProductDevelopment #TechInnovation #MVPDevelopment #ProofOfConcept #NoCodeSolutions #SoftwareDevelopment #StartupLife #ProductLaunch #Entrepreneurship #LeanStartup #TechStartups #Innovation

29

5 Komen

My eyes light up whenever I encounter a job listing for a Product Engineer. The idea of being a product-minded engineer resonates with me. It's a role that goes beyond writing code – it's about being deeply invested in the product's success, regardless of the specific title. Product Engineers are driven by a different kind of fire. They're not focused on winning technical debates, but rather on using their expertise to develop ideas and features that solve real user problems and make the product shine. But it's not just about cool features. Product Engineers understand the bigger picture – the company's business goals. They act as a bridge between the technical and business side, translating that vision into concrete engineering efforts. Every feature they build has a purpose, and they're curious to understand the *why* behind it all. This collaborative, business-minded approach makes Product Engineers invaluable assets, especially for fast-growing startups. If the idea of being a product engineer sounds interesting to you, you can read this in-depth article by Gergely Orosz about product engineer. https://lnkd.in/dWrQt7DB #softwareengineer #productengineer

21

8 Komen

🔍 Navigating different Customer mindsets in Product conversations 🤔 During the product awareness phase, I recently encountered two distinct customer personas. Portfolio Manager : "If it involves product ABC, I'm not interested. I'll step out at any point during the meeting." Company Founder : "I've already evaluated product ABC, but I'm all ears to hear your proposal." Persona 1: A cautious, results-driven approach, lacking openness to new perspectives. Persona 2 : A willingness to engage and consider new ideas, even after previous evaluations. This experience highlights how different mindsets can shape interactions and underscores the importance of empathy and adaptability in product conversations.

5

1 Komen

TGIF, Product folks! 📅 Here’s your 5–15 Dec rundown of can’t-miss events! The next week will be huge for AI lovers and product folks getting ready to sum up the year, get ready for 2025! 📚 Dec 9 - 5 AI Concepts Every PM Should Know by Yasi Baiani, Max H., Sara Davison, MAHESH YADAV (Google) Why attend: Master the AI fundamentals every PM needs to succeed in 2025 and beyond. 🔗 https://lnkd.in/e8tiCaJS ⚙️ Dec 9 - Building Products in 2025 with No-Code x AI by Harold D. Why attend: Discover how no-code tools paired with AI will redefine product development. 🔗 https://lnkd.in/eT3ssVwJ 📈 Dec 10 - Automating Your Work in 2025 with No-Code x AI by Shyvee Shi & Harold D. Why attend: Learn automation strategies to enhance productivity and efficiency. 🔗 https://lnkd.in/ebk_vyWR 🌟 Dec 10 - Rise to the Top: 2025 Playbook for Top 1% AI Practitioner Skills by Sara Davison & Tyler Fisk Why attend: Equip yourself with skills to lead in the AI-driven era. 🔗 https://lnkd.in/ekjZCuha 💼 Dec 10 - Unwritten Norms in PM Interviews by Shipra Malhotra (Eatsy) Why attend: Learn from an Etsy product leader on what PM interviews often don’t teach you. 🔗 https://lnkd.in/ePCHnEyh 📊 Dec 10 - Become an Executive in 2025 by Eric Nehrlich Why attend: Chart your path to executive leadership in a rapidly evolving landscape. 🔗 https://lnkd.in/eX-5NFaA 🛠️ Dec 11 - How to Build a Resume Optimizer with AI by Shaw Talebi Why attend: Create AI tools to make resume building smarter and more effective. 🔗 https://lnkd.in/eRcG7wG7 🎯 Dec 12 - Top Tips to Get Unstuck and Move Up in 2025 by Ethan Evans Why attend: Breakthrough career roadblocks with actionable insights. 🔗 https://lnkd.in/eAay9BXx 🚀 Dec 15 - AI Careers for Non-Coders by Aishwarya Srinivasan Why attend: Explore career opportunities in AI without a coding background. 🔗 https://lnkd.in/et3YCD3z Got another event I've missed? Drop it in the comments — let’s keep the inspiration rolling! 🥂 Cheers,

16

1 Komen

I've found that getting estimates from engineers and following up at the 50%, 75%, and 90% marks to be unreasonably effective. Check for confidence, rabbit-holes, or opportunities to cut or clarify scope. https://upfollow.app makes following up easier.

2