Professionalism in Engineering Collaborations

The quality of your product is capped by the quality of your relationships. Specifically: Your relationship with engineering. You can have perfect strategy, brilliant insights, clear roadmaps. None of it matters if your eng team doesn't trust you. The trust markers nobody talks about: LOW TRUST: - Engineers ask for everything in writing - They push back on timelines defensively - They go silent when you ask for ideas - They build exactly what you spec, nothing more HIGH TRUST: - They tell you when your idea is bad - They proactively suggest better approaches - They ship things you didn't ask for that you needed - They protect you from your own mistakes Here's what most PMs get wrong: They think trust comes from being right. It doesn't. Trust comes from: - Admitting when you don't know - Taking responsibility when things go wrong - Defending eng decisions to stakeholders - Not throwing them under the bus when timelines slip The shift: Stop trying to be impressive. Start being reliable. The best PM-eng relationships feel like partnerships, not transactions. Your eng lead should feel comfortable saying “That's a terrible idea” to your face. If they don't, you don't have trust. You have compliance. And compliance doesn't build great products. What changed when your engineering relationship went from transactional to trusted? #ProductManagement #Engineering #Trust #Collaboration

After years of managing rocky relationships between product and engineering leaders, these are the top 5 things I've learned you can do to make these partnerships great: 1. Foster Strategic Action: Maintain a well-thought-out backlog of problems that acknowledges potential risks and strategies for overcoming them. This approach keeps engineers engaged, solving real customer issues, and builds trust across teams. 2. Simplify Processes: Introduce only necessary processes and keep them straightforward. Maintain a regular schedule of essential meetings and minimize ad-hoc interruptions to give engineers more time to focus. 3. Collaborate on Solutions: Instead of dictating solutions, work closely with engineers to understand problems and explore solutions together. This partnership leverages their technical expertise and aligns efforts with customer needs, enhancing innovation and ownership. 4. Respect Technical Debt: Recognize and prioritize technical debt within the product roadmap. Trust engineers to identify critical technical issues that need addressing to keep the product competitive and maintain high-quality standards. 5. Build Relationships: Spend time with your engineering team outside of regular work tasks through meals, activities, or shared hobbies. Building personal connections fosters trust and improves collaboration, making it easier to tackle challenges together effectively. I’ve seen amazing product and engineering partnerships and some not-so-great ones. Teams that take the time to improve their relationship really see the benefits. While natural tensions exist, the best teams put in the effort to work well together, resulting in more successful products. #techleads #product #engineering

I have worked in both kinds of workplace settings. In some, professionalism was at its peak. Feedback was clear, communication was respectful, and there was a shared sense of ownership in every project. Even on the busiest days, you knew everyone was on the same side, working toward the same goal. In others, clients were so difficult to work with that every conversation felt like walking on eggshells. Feedback came in bits and pieces, often through indirect comments instead of direct conversations. The lack of clarity did not just make the process harder, it drained creativity and slowed everything down. Experiencing both has made one thing clear to me. The difference between smooth, productive work and constant friction is not talent, budget, or resources. It is professionalism and communication. When professionalism is present, trust is built. When communication is clear, problems are solved quickly. Together, they create an environment where people feel valued, ideas flow freely, and work gets done not just faster, but better. Without them, even the most talented teams and the best ideas can fail to deliver their full potential. Professionalism and clear communication are not “soft skills.” They are performance drivers. They determine whether a team thrives or simply survives. What is one example of professionalism you have experienced that made work feel effortless?

𝗜'𝘃𝗲 𝘀𝗲𝗲𝗻 𝘁𝗵𝗶𝘀 𝗽𝗮𝘁𝘁𝗲𝗿𝗻 𝗿𝗲𝗽𝗲𝗮𝘁 𝗶𝗻 𝗲𝘃𝗲𝗿𝘆 𝗰𝗼𝗺𝗽𝗮𝗻𝘆 𝗜'𝘃𝗲 𝘄𝗼𝗿𝗸𝗲𝗱 𝗳𝗼𝗿. Seven companies. Ten years. Same lesson. Technical problems rarely break teams. People problems do. Early in my career, during a high-pressure plant shutdown, two teams miscommunicated over a valve handoff. One team believed the sequence was complete. The other was still waiting for confirmation. The shutdown was costing the company over $1 million per day. And yet the delay wasn't caused by equipment or skill. It came from one thing: a moment where respect slipped, and everything else followed. That day taught me something no procedure manual ever has: Every company has standards. But the only standard that protects culture, trust, and performance is the one professionals set for themselves. I call it The Respect Code. 𝗙𝗼𝘂𝗿 𝗽𝗿𝗶𝗻𝗰𝗶𝗽𝗹𝗲𝘀 𝗜 𝘄𝗶𝘀𝗵 𝗲𝘃𝗲𝗿𝘆 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿, 𝗳𝗿𝗼𝗺 𝘆𝗲𝗮𝗿 𝟭 𝘁𝗼 𝘆𝗲𝗮𝗿 𝟮𝟱, 𝗹𝗶𝘃𝗲𝗱 𝗯𝘆: → Treat others' things better than your own. ↳ Equipment and systems are someone's reputation. Leave them clearer. → Treat others' time as valuable as yours. ↳ Delays and vague asks cost real money. Clarity pays. → Treat others' feelings as real as yours. ↳ Pressure lands differently. Respect the human before the output. → Treat others' boundaries as if they were laws. ↳ Capacity is limited. Protecting it improves safety and trust. I wasn't always this way. I used to think being right mattered more than being respectful. When I started living by this code, everything shifted: → Cleaner handoffs → Stronger collaboration → Higher trust in every room I walked into I wasn't always this way. I used to think being right mattered more than being respectful. When I started living by this code, everything shifted: → Fewer conflicts → Cleaner handoffs → Stronger collaboration → Higher trust in every room I walked into 𝗛𝗲𝗿𝗲'𝘀 𝘁𝗵𝗲 𝘁𝗿𝘂𝘁𝗵: Respect is the quiet operating system behind high-performing teams. And the most respected professionals aren't the loudest, they're the most considerate. ❤️ Repost to remind someone that leadership starts with respect 🔔 Follow Dima Abu-Khaled for evidence-based personal and career growth tips

I often teach a class on communications for civil engineers and it is a reminder that being a great engineer is not just about calculations and design. You can have the best technical skills in the world, but if you cannot communicate your ideas clearly, to clients, contractors, agencies, or the public, your impact will be limited. Engineering is full of complex concepts, and explaining them in a way that different audiences can understand is a skill that takes practice. Here are five key communication skills that every engineering professional should master: Writing with Clarity: Whether it is a technical report, an email, or a proposal, writing should be clear, concise, and to the point. Long-winded explanations or vague wording lead to confusion and misinterpretation. Presenting with Confidence: Engineers often need to present findings, designs, or project updates to teams, stakeholders, or decision-makers. Speaking clearly, making eye contact, and organizing information logically can make a big difference. Listening Actively: Communication is not just about talking. Engineers need to listen to clients, project teams, and regulatory agencies to understand concerns, gather requirements, and avoid costly mistakes. Adapting to Different Audiences: The way you explain a project to a fellow engineer is not the same as how you explain it to a city council or a community group. Knowing how to adjust your message for different audiences is essential. Handling Conflict Professionally: Disagreements happen in projects. Whether it is negotiating with contractors, addressing design concerns, or responding to public opposition, engineers must know how to navigate conflict calmly and professionally. I have seen students who were hesitant about communication at the beginning of the course completely change their approach once they realized its importance. These skills do not just help in the workplace. They help engineers lead, influence, and bring ideas to life. #Engineering #CivilEngineering #CommunicationSkills #Leadership #ProfessionalDevelopment (Chart source: ESMI)

People approach process and relationships differently. We know this.. research confirms it but what does it really mean in practice? These aren’t just preferences. They’re deeply embedded operating systems. Picture two planning meetings: one in Central Europe, the other in Central America. In Central Europe, professionalism is often shown through structure, precision, and clear workflows. This result-oriented approach values timeliness and preparation, and trust is earned through accuracy and adherence to process. In Central America, trust is built through relationships, mutual respect, and adaptability. Planning is more of an evolving conversation than a rigid sequence. This relationship-driven approach values human connection as the foundation for collaboration, where the “who” can matter as much as the “how.” At the core of both is trust but trust is built differently across cultures. Some trust people. Some trust roles. Some trust rules. Others trust results. “Do I trust the system?” Or, “Do I trust the person?” When these differences aren’t recognized, misalignment can erode confidence and stall progress. One side may see the other as disorganized; the other may see rigidity. The real risk isn’t the difference it’s assuming the other side is wrong. When acknowledged and bridged, these differences can become a strength, building deeper trust and more effective collaboration across cultures.

The best design decisions I’ve made weren’t mine alone. Early in my career, I thought being a good designer meant having all the answers. I’d present and defend my design choices like my credibility depended on it. That mindset changed during my first cross-functional design hackathon. We had 48 hours to create an AI-powered rental platform. I came in ready to drive the design but quickly realized how incomplete my perspective was. Engineers surfaced technical constraints I hadn’t considered. The PM kept grounding us in user pain points and success metrics. The researcher and data team shared data that completely reshaped our feature priorities. At first, it felt uncomfortable. Like I was failing if I wasn’t the one driving every design decision. But I learned something important: as a product designer, the goal isn’t for design to arrive with a fully formed solution. The solution is shaped by user needs, business goals, and technical reality. My role is to help define the problem, explore viable solutions, and shape the product vision alongside PMs, engineers, and researchers, using evidence, constraints, and user insight, then translate those decisions into clear, usable designs that guide the product from ideation to development. That experience shaped how I work and how I think about collaboration. Now, collaboration helps me: 👉 Reduce the risk of building the wrong thing because assumptions are validated by other team members early. 👉 Move faster with fewer handoff failures because engineers are involved from the start 👉 Design systems and patterns that scale 👉 Make trade-offs that are defensible and measurable, grounded in research, data, and technical constraints. All of these ensure my solutions are clearer, more feasible, and far more likely to solve the right problem. Over to you 👇 I’d love to hear how other designers work with PMs, engineers, and researchers to solve the right problems. Feel free to also respond if you are a professional who has to collaborate with a team.

Why Collaboration Is the Key to Effective ES&PC/SWPPP Plan Design A few years ago in Georgia, a controversy arose between CPESCs and Professional Engineers (PEs) over who was better suited to be the ES&PC Plan (also known as the SWPPP) designer of record for NPDES permitted construction sites. At the heart of the debate was a genuine concern: How do we ensure erosion, sedimentation, and stormwater pollution are effectively controlled during construction? After years of experience in this field, I’ve found the question itself may have missed the mark. The most effective SWPPPs aren’t created by one profession alone; they’re built through collaboration. ⸻ The PE Advantage: Engineering Strength. Professional Engineers, particularly civil engineers, bring critical expertise in: Hydrology and hydraulics, stormwater detention and retention design, and site grading, infrastructure tie-ins, and long-term planning. A PEs work is essential when it comes to designing post-construction stormwater systems that meet regulatory standards and structural requirements. The CPESC Advantage is a Field-Focused Compliance mindset. CPESCs contribute deep, specialized knowledge in: Construction-phase erosion and sediment control, BMP selection, placement, and practical installability, NPDES compliance from NOI to NOT, and Pollutant transport pathways and sediment behavior. Their strength is in designing plans that work in real conditions—not just on paper. Why Both Are Essential When plans are designed without collaboration, we often see: Overengineered or under-detailed BMPs, Poorly phased control measures, Compliance failures in the field, and Plans that don’t reflect the realities of site access, weather, and construction timelines. But when PEs and CPESCs work together, we get: ✅ Accurate stormwater calculations and constructible BMPs ✅ Integrated site design and phase-appropriate controls ✅ Legal defensibility and regulatory compliance ✅ A SWPPP that protects water quality and project timelines So in closing, instead of asking, “Who’s better suited—CPESC or PE when designing a NPDES permit required SWPPP?”, let’s ask: “How do we build the best plan possible by combining our individual professional strengths?” I believe that at the end of the day,, our surface water quality depends on collaboration, not competition. After all we all know that egos are not what protects our watersheds, it’s our willingness to see the bigger picture by combining our strengths that will give us a wiser more thoughtful approach to improving and maintaining the chemical, physical and biological integrity of our nations water quality. ⸻ #NPDESTraininginstitute #SWPPP #ErosionControl #NPDES #CPESC #ProfessionalEngineer #Stormwatertraininginstitute #ConstructionCompliance #GeorgiaWatershedsmatter #FieldReadyPlans #CleanWaterAct #CivilEngineering #Teamwork #ESPCplansequalswppps

Specs don’t build buildings. People do. Construction failures rarely happen because drawings were missing. They happen because intent was lost between the page and the field. You can have flawless specifications and still fail when: • The installer doesn’t understand why a detail exists • Materials are substituted without understanding system compatibility • No one on the team is empowered to pause work when something isn’t right Specifications define requirements — but people execute judgment. The most successful projects consistently share the same traits: • Engineers who listen to field experience • Craftsmen who respect engineering constraints • Teams aligned around outcomes, not silos When collaboration breaks down, problems get buried. When collaboration works, problems get solved early — quietly and efficiently. Collaboration isn’t a “soft skill” in construction. It’s a structural requirement. #ConstructionManagement #Preservation #Teamwork #Masonry #EngineeringExecution