Yes — I believe simplifying complex topics is a critical part of my role as an engineering leader, especially when collaborating cross-functionally with product, design, sales, or customer success teams.
First, I focus on understanding the audience — what they need to know and why. For example, if we’re discussing system scalability with a product manager, I don’t dive into threads or queues — I might say:
"Think of the system like multiple checkout lanes at a grocery store — as traffic grows, we add more lanes to serve customers faster, while making sure we have enough cashiers and supplies."
Second, I use analogies, visual aids, and metrics to make the conversation tangible. For example, when explaining asynchronous processing via RabbitMQ, I might compare it to a "to-do list" where work is lined up and picked up by workers as they become available — this helps non-technical stakeholders grasp queuing and load balancing.
Third, I encourage open questions and feedback — I verify if I’m being clear, and adjust based on their reactions. My goal is to build alignment and shared understanding, not to impress with technical jargon.
I’ve found this approach helps the entire team make better, faster decisions while feeling confident about the technical direction.