Common Mistakes In Engineering Project Management

𝗠𝗼𝘀𝘁 𝗣𝗠 𝗰𝗮𝗿𝗲𝗲𝗿𝘀 𝗱𝗼𝗻'𝘁 𝗳𝗮𝗶𝗹 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝗼𝗳 𝗮 𝗹𝗮𝗰𝗸 𝗼𝗳 𝗰𝗲𝗿𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗼𝗿 𝘁𝗼𝗼𝗹-𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲. They fail quietly from the small, daily habits that no one ever mentions on a resume. Here's the unvarnished truth about the eight traps I see again and again: 𝟭. 𝗬𝗼𝘂 𝗶𝗴𝗻𝗼𝗿𝗲 𝘁𝗵𝗲 "𝘀𝗼𝗳𝘁 𝘀𝗸𝗶𝗹𝗹𝘀." ↳ You're a master of Jira but a novice with people. Hard truth: Your team doesn't follow a Gantt chart; they follow a human being. Communication, empathy, and conflict resolution aren't "soft"—they're your most critical tools. 𝟮. 𝗬𝗼𝘂 𝗺𝗶𝗰𝗿𝗼𝗺𝗮𝗻𝗮𝗴𝗲 𝘆𝗼𝘂𝗿 𝘁𝗲𝗮𝗺. ↳ You were hired to lead, not to control everyone else's work. If you don't trust your team, you become their most significant bottleneck. 𝟯. 𝗬𝗼𝘂 𝗰𝗼𝗻𝗳𝘂𝘀𝗲 𝗯𝗲𝗶𝗻𝗴 "𝗯𝘂𝘀𝘆" 𝘄𝗶𝘁𝗵 𝗯𝗲𝗶𝗻𝗴 "𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝘃𝗲." ↳ Your calendar is packed, and you jump from meeting to meeting. But how much of that is actually moving the project forward? Many PMs drown in low-value work to look busy. 𝟰. 𝗬𝗼𝘂 𝗮𝘃𝗼𝗶𝗱 𝗰𝗼𝗻𝗳𝗹𝗶𝗰𝘁. ↳ Unresolved tension in the team doesn't just disappear. It festers. Addressing a conflict directly today prevents a crisis tomorrow. Leadership means having the uncomfortable conversations. 𝟱. 𝗬𝗼𝘂 𝗻𝗲𝗴𝗹𝗲𝗰𝘁 𝘀𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁. ↳ You think everyone is aligned because you sent an email. Wrong. Active alignment isn't a one-time event; it's a constant process. Without it, you're steering a ghost ship. 𝟲. 𝗬𝗼𝘂 𝗴𝗲𝘁 𝘀𝘁𝘂𝗰𝗸 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗰𝗼𝗺𝗳𝗼𝗿𝘁 𝘇𝗼𝗻𝗲. ↳ You do things "the way they've always been done" because it works. But the world around you is changing. If you stop learning today, you're irrelevant tomorrow. Agile isn't a framework; it's a mindset. 𝟳. 𝗬𝗼𝘂 𝗼𝗻𝗹𝘆 𝗰𝗲𝗹𝗲𝗯𝗿𝗮𝘁𝗲 𝘁𝗵𝗲 𝗳𝗶𝗻𝗶𝘀𝗵 𝗹𝗶𝗻𝗲. ↳ Your team is fighting through milestones, but the only recognition is the launch party six months from now. That's a motivation killer. Celebrate the small wins to maintain energy for the marathon. 𝟴. 𝗬𝗼𝘂 𝗰𝗵𝗮𝘀𝗲 𝘁𝗼𝗼𝗹𝘀 𝗶𝗻𝘀𝘁𝗲𝗮𝗱 𝗼𝗳 𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻𝘀. ↳ "If we just had this new AI tool, all our problems would be solved!" No. A tool is only as good as the process and the people using it. Focus on the problem, not the next shiny object. This isn't about being perfect. It's about becoming aware of the traps. Which one of these hits hardest for you (or your organization)? ♻️ 𝗥𝗲𝗽𝗼𝘀𝘁 𝘁𝗼 𝗵𝗲𝗹𝗽 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝗺𝗮𝗻𝗮𝗴𝗲𝗿𝘀 𝘄𝗵𝗼 𝗮𝗿𝗲 𝘀𝘁𝘂𝗰𝗸 𝗶𝗻 𝘁𝗵𝗲 𝗱𝗮𝗶𝗹𝘆 𝗴𝗿𝗶𝗻𝗱. 💾 𝗦𝗮𝘃𝗲 𝘁𝗵𝗶𝘀 𝗽𝗼𝘀𝘁 𝗳𝗼𝗿 𝗹𝗮𝘁𝗲𝗿, 𝗮𝘀 𝗮𝗻 𝗵𝗼𝗻𝗲𝘀𝘁 𝗰𝗵𝗲𝗰𝗸-𝗶𝗻 𝗳𝗼𝗿 𝘆𝗼𝘂𝗿 𝗻𝗲𝘅𝘁 𝗾𝘂𝗮𝗿𝘁𝗲𝗿. ➕ And follow Markus Kopko ✨ for more. #ProjectManagement #Leadership #CareerGrowth #PMO #Agile

15 Years -15 Don’ts After 15 years in EPC, I’ve seen things you wouldn’t believe. Some mistakes were painful, some almost funny, but all of them left a mark. Here are my top 15 Don’ts that can derail any project: 1. Starting without a proper RAM test or geotechnical survey, saving money upfront, paying much more later. 2. Ignoring safety, workers in flip-flops, even children or babies on site. Unbelievable, but I’ve seen it. 3. Choosing low-quality components, cheap at the beginning, expensive forever. 4. Leaving responsibilities unclear, when nobody decides, chaos decides. 5. Hiding problems, small issues turn into big ones if you don’t address them early. 6. Awarding subcontractors only on lowest price, change orders are then guaranteed. 7. Bad site logistics, the first truck arrives and nobody knows where to unload. 8. Skipping the golden table, endless disputes later about “what’s correct.” 9. Wrong cables, when the inverter terminals are too small, just splice a thinner cable underground (yes, I’ve seen it). 10. Leaving unfinished work with the comment: “That’s for the O&M team to handle.”! Construction is never complete if responsibility is pushed downstream. 11. Believing more manpower fixes delays, usually it makes them worse. 12. Unrealistic timelines, ignoring permits, supply chain, or weather. 13. Starting in autumn and expecting the same timeline as in spring, winter changes everything. 14. Assuming winter construction costs the same as summer, it never does. 15. Treating commissioning as “just paperwork”, instead of a critical system test. Your turn: Which Don’ts have you seen in your projects? Who can top this list? #AndreasBach #SolarEnergy #Renewables #EPC #BESS #ProjectManagement #ConstructionFails

3 mistakes I’ve made as a PM (so you don’t have to) I wish someone had told me these earlier. 🚨 Mistake #1: Saying yes too much I thought being a great PM meant keeping everyone happy, stakeholders, engineers, leadership. The result? A bloated backlog, scattered focus, and zero real impact. ✅ Lesson: Saying no is a skill. Prioritize ruthlessly! 🚨 Mistake #2: Relying too much on gut instinct I used to make decisions based on what “felt right” or what customers said they wanted. But what people say and what they actually do are different. ✅ Lesson: Let data guide you. Watch behavior, not just feedback. 🚨 Mistake #3: Thinking my job was to have all the answers I thought I needed to have the most information, the strongest opinion. Turns out, the best PMs don’t have the best ideas, we create the space for them to emerge. ✅ Lesson: Ask more questions, empower your team, and let the best ideas win. I still make mistakes, but these shifts help me everyday!

I've made every mistake on this list. Some cost me projects. Some cost me team trust. But all of them taught me what makes you a grounded experienced PM. You see most project failures aren't about missing tools or broken processes.(We all know that right?) They're about repeated mistakes we refuse to learn from. And after a decade managing complex projects, I've watched these 8 patterns destroy teams and I've been guilty of some myself. Here's what experience has taught me the hard way: → Saying yes to everything doesn't make you helpful. It makes you unavailable for what matters. → Skipping documentation feels efficient today. It costs you hours in confusion tomorrow. → Avoiding tough conversations doesn't keep the peace. It lets small fires become team-wide crises. → Holding all the information doesn't make you valuable. It makes you the bottleneck. → Chasing perfection delays real progress. Shipping, learning, and iterating beats assumptions every time. → Measuring hours worked rewards exhaustion, not excellence. Outcomes and impact are what drive results. → Neglecting your own growth while delivering projects is a slow road to irrelevance. → Taking credit for your team's wins might feel good briefly. But it destroys trust instantly. The difference between good PMs and great ones? Great ones learn these lessons early or recognize them fast when they appear. I've led cross-functional teams across multiple sectiors like health benefits and marketing technology. The projects that succeeded weren't the ones where I had all the answers. They were the ones where I learned quickly, documented clearly, and made the team visible. ✅️ Here's the key takeaway for you. Look at this list. Pick one mistake you're making (or made recently). Commit to doing it differently this week. Real leadership isn't avoiding mistakes. It's learning from them faster than everyone else. Which one of these hits closest to home for you? Drop the number below. Let's talk about it. Happy New Week. ----------------------------- And by the way... Our Live session comes up this Friday. Grab your seat if you haven't. Link in the comments Follow Benjamina for practical perspectives on #projectexecution, #leadership judgment, and #delivery under real constraints.

Spot project management red flags before they derail your success. Identifying and addressing red flags in project management is crucial for avoiding potential pitfalls and ensuring project success. Here are 10 Red Flags to watch out for: 1. Insufficient Resources Lack of budget, time, personnel, or tools can lead to delays and compromised quality. 2. Poor Risk Management No formal risk management process? Risks not identified and assessed can lead to unexpected problems. Always have contingency plans ready! 3. Focus on Cost Over Value Prioritizing cost savings over quality? This can result in poor deliverables and dissatisfied customers. Focus on maximizing value instead. 4. Lack of Clear Communication Effective communication is vital! A project manager must communicate needs and risks to gain stakeholder support and address issues promptly. 5. Single Points of Failure Relying on a single vendor or key individual without backups is a high-risk strategy. Always have backup plans in place. 6. Focus on Output Rather Than Outcome Prioritize overall outcomes and value delivered, not just task completion or deadlines. Align project goals with business objectives. 7. Unrealistic Timelines Setting arbitrary timelines without proper planning leads to rushed work, increased stress, and poor quality. Plan realistically! 8. Toxic Work Environment A culture that discourages raising concerns or punishes those who do can lead to significant issues. If team members feel unsafe to express their thoughts, critical problems may go unaddressed 9. Lack of Stakeholder Engagement Failing to involve all stakeholders? Understand their expectations and incorporate them into the planning process to avoid undermining project success. 10. Scope Creep Allowing changes without a formal change management process? This strains resources and delays the project. Manage scope changes formally. By staying vigilant for these red flags, you can proactively address issues before they escalate, ensuring smoother and more successful project outcomes. Feel free to share your thoughts or add any other red flags you’ve encountered in the comments! 👇

Ask any experienced project manager about the most common challenges encountered on a project, and you'll hear a variety of answers: a growing backlog of RFIs, compressed schedules, coordination issues, and procurement delays. These are all real — and undeniably demanding. However, after more than two decades in the industry, I believe the most critical risk doesn’t lie in the schedule, budget, or construction documents. It’s misalignment. If you’ve been in the field long enough, you know the signs. 1. The architect’s intent isn’t translating into the build 2. MEP trades are working off different versions of the plans 3. The owner’s rep is assuming decisions were already made 4. The GC is waiting for submittals that were never requested 5. Your team is “busy” but progress is unclear No major blow-ups… just a slow drip of small issues that compound over weeks. And suddenly, you’re in recovery mode, not execution. As project managers, we’re the integrators. We’re the ones tasked with turning plans into outcomes. And that means getting every player on the same page — and keeping them there. 1. Define Success — Not Just Scope - It’s not enough to have a spec book and a set of drawings. What does the client define as a win? What are the non-negotiables? What risks can they tolerate? Align on outcomes before chasing outputs. 2. Establish Roles and Decision Paths - On vertical projects, there are dozens of players, superintendents, consultants, trade leads, inspectors, commissioning agents. Clarify who owns what. Who reviews? Who approves? Who coordinates field direction when conflicts arise? 3. Create a Communication Framework - Update meetings are not alignment tools they’re just status checks unless you structure them right. Set a rhythm that supports decision-making: a. Weekly cross-discipline coordination b. Owner/architect/contractor (OAC) updates c. Rolling look-ahead reviews with field leads d. Proactive document control 4. Normalize Realignment - On long-duration builds, the plan will shift through design changes, site conditions, permitting, or resourcing. Revisit expectations, clarify adjustments, and reassign responsibilities. This isn’t rework, it’s refinement. 5. Lead with Clarity - Projects follow the tone you set. If your communication is reactive, so is the team. If your expectations are vague, coordination becomes guesswork. Precision isn’t optional it’s your greatest tool. Misalignment doesn’t announce itself. It creeps in through assumption, distraction, and silence. And by the time it shows up in missed inspections or rework, you’re already behind. Be proactive. Be deliberate. Be the one who connects the dots across the entire build. Because at the end of the day, our job isn’t just to manage plans, it’s to create alignment between vision, execution, and delivery.

One of the biggest risks in project execution is underestimating the role of project planning. Too often, planning is seen as a dreaded paper exercise or just a compliance formality—rather than the strategic backbone of successful delivery. When planning is sidelined, the consequences are real: 1.Unrealistic timelines that lead to delays and cost overruns 2.Weak risk management, leaving teams vulnerable 3.Poor resource allocation, creating bottlenecks and inefficiencies 4.Lack of accountability, making it hard to track and measure progress 5. When you need to claim CE, Delays and EOT you’re not able to prove it. Everyone needs to understand the project , the key milestones the critical path and follow the sequencing of the plan. Project planning is not a solo effort. It cannot be done by the planner in isolation. It requires collaborative input from supervisors, construction managers, project managers, clients, and all relevant stakeholders. Everyone must be in alignment. The plan should be agreed upon, signed off, and form part of the contractual agreement to ensure clarity, accountability, and mutual commitment. This plan will also inform the project success rating As project planners, we don’t just draw up schedules—we drive: • Project visibility • Execution efficiency • Risk mitigation • Alignment to strategic objectives • Optimise resources and project delivery. I remember one of my projects where the project planner wasn’t taken seriously—until the project hit trouble. Suddenly, everyone turned to the planner for solutions. I was then called an advisor, Now that the pressure was on, the very plan they disregarded became the project’s lifeline. Let’s shift the mindset. Planning is not a checklist item—it’s the foundation of successful execution. And when it’s time to claim progress or recover a struggling project, it’s the same plan that will save the day and company lots of money. #ProjectManagement #ProjectPlanning #StrategicExecution #RiskManagement #LeadershipInProjects #PlanningMatters #EnergySector #Substations #PowerStations #InfrastructureDevelopment #ConstructionProjects #EngineeringLeadership #ExecutionExcellence #ProjectControl #PlanningForSuccess #CostControl #ScheduleMatters #BuiltEnvironment #PlannerVoice #ProjectLeadership #MindsetShift #CollaborationInProjects #StakeholderAlignment #ContractManagement #TeamworkInExecution

My 10 mistakes introducing PLM. 🚩  1. Lack of clear objectives PLM initiatives start without a precise definition of: - What exactly should be improved (e.g., change processes, data quality, time-to-market, …)? - How success will be measured? - How do I balance diverging targets: function, integration, technology? - ALM, PLM and ERP are the most important IT-Systems along the PLC. How are functions and processes distributed and integrated? ➡️ Consequence: The project loses focus, becomes bloated, or fails due to unrealistic expectations. 🚩  2. Treating PLM as an IT project PLM is fundamentally a process and organizational transformation, not just a software. ➡️ Consequence: Poor involvement of departments leads to low adoption and inefficient workflows. 🚩  3. Unclear or conflicting processes Companies often attempt to implement PLM while their underlying processes: - do not exist, - are poorly documented, - differ across organizational units. ➡️ Consequence: The tool ends up digitizing chaos instead of improving it. 🚩  4. Scope too large / Big-Bang implementation Trying to deploy a comprehensive PLM system all at once is one of the most common pitfalls. ➡️ Consequence: Delays, budget overruns, and user frustration. 🚩  5. Insufficient Change Management PLM affects roles, responsibilities, and daily work habits. Common oversights: - weak communication, - missing training, - lack of key-user involvement, - lack of C-level involvement. ➡️ Consequence: Resistance, workarounds, and low acceptance. 🚩  6. Poor master data and document quality - inconsistent or duplicated data, - no data cleanup before migration, - missing standards (naming, numbering, classification, ...). ➡️ Consequence: Bad data stays bad—only now inside an expensive system. 🚩  7. Over-customization Companies frequently try to model every exception and satisfy every request. ➡️ Consequence: Complex, costly, hard-to-maintain systems that hinder upgrades. 🚩  8. Underestimating integration PLM relies on clean interfaces to systems like: CRM, CAD, ALM, ERP, MES, SCM. ➡️ Consequence: Media breaks, duplicate data, and process gaps. 🚩  9. Insufficient resources or the wrong project team PLM is often done “on the side": - no dedicated project manager, - limited internal PLM expertise, - weak executive sponsorship. ➡️ Consequence: Delays and unsatisfied never ending stories 🚩  10. Focusing only on basic design features Many PLM deployments center solely on CAD and E-BOM. But PLM should cover: requirements management, variant management, change management, service, ... ➡️ Consequence: PLM becomes an expensive CAD data vault rather than an enterprise-wide product backbone or PLM functions are taken over by CAD (Onshape) or ERP ✅ Summary Most pitfalls arise not from technology or functional coverage, but from strategy, processes, and change management. Organizations often underestimate the cultural and organizational change—and overestimate what the software alone can fix.

Common Mistakes in MEP Coordination – And How to Avoid Them MEP coordination plays a critical role in the success of any fit-out or construction project. Over the years, I have observed that many site issues don’t arise due to lack of effort, but due to gaps in coordination. Here are some common mistakes and practical ways to avoid them: 1)Late involvement of MEP teams: MEP inputs are often taken after civil or interior work has already progressed. -Solution: Involve MEP from the planning stage to avoid rework and clashes. 2)Incomplete or uncoordinated drawings: Working with isolated electrical, HVAC, plumbing drawings leads to on-site confusion. -Solution: Always work with coordinated MEP layouts and updated shop drawings. Involve all the stakeholders while execution to avoid any rework and delay. 3)Poor communication between stakeholders: Lack of regular coordination meetings creates misunderstandings among contractors, consultants, and clients. -Solution: Conduct weekly coordination meetings with clear action points. Agenda points to be circulated prior to discussion so that all the stakeholders get prepared themselves. 4)Ignoring site constraints: Designs that look perfect on paper may not be feasible on site. -Solution: Validate drawings with actual site conditions before execution. Highlight the deviation on site to the architect or consultant for solution. 5)No clear responsibility matrix: If responsibilities are not clear, no one takes ownership. -Solution: Define scope and responsibilities clearly for every agency. 6)Rushing execution without approvals: Starting work without final approvals often leads to dismantling and delays. -Solution: Follow a strict approval and release process. 7)Lack of quality and safety checks: Coordination is not just about layouts,it is also about execution quality and safety. -Solution: Use checklists and SOPs to monitor work on site.Arrange weekly visit of the consultant for quality inspection to avoid any rework further. Good MEP coordination is not about control, it’s about collaboration. When teams work together with clarity and planning, projects move faster, safer, and with better quality.

We’ve built for GoPro, Walmart, and 100s of hardware startups. Here are 8 mistakes I see $1.5M-funded founders repeat in pre-production: 1. If it can’t be quoted, it can’t be built. I’ve seen so many smooth prototypes that look great but aren’t designed for manufacturability. Then factories either ghost or quote 4x. Why? Undercuts and part geometry made tooling impossible. If your design isn’t quoting cleanly, it’s not a product yet. 2. BOM isn’t a budget - it’s a liability list. One team’s $38 BOM ballooned to $62 after sourcing revealed single-vendor parts and fragile components. Your BOM should protect your margin, not drain it. 3. Never tool before your tolerances are tested. A wearable team tooled early - then found a 12% failure rate in production. Tooling before DFM is just a bet you can’t afford to lose. 4. What works at 50 units fails at 5,000. We’ve seen battery doors crack, enclosures warp, and boards overheat - because the product was only tested at lab scale. CAD hides stress. Volume exposes it. 5. Design firms often don’t speak “factory.” A sleek prototype arrived with no draft angles, wall thickness issues, and unusable files. If they’ve never shipped 10,000 units, don’t trust them to design yours. 6. Getting one quote isn’t success - it’s a trap. One startup was quoted 35% above target and had no backup. We redesigned 3 parts and unlocked 5 new factories. No quote = no leverage = no plan B. 7. BOM rejection is where the bleeding starts. One team sent their BOM after raising $2.1M. 6 of 18 parts failed compliance or sourcing. If your BOM hasn’t been factory-reviewed, your roadmap is fiction. 8. Prototypes don’t prove scalability. DFM does. One team built a slick demo using CNC-machined parts. The clip-on enclosure fit perfectly. Everyone loved it. But when we prepped it for mass production, we found: - No draft angles for molding - Undercuts that required complex, expensive tooling - Assembly steps that added labor cost at scale It was never designed to be built at volume. What worked in a demo couldn’t be molded, tooled, or quoted. Prototypes can prove function. But only DFM proves you’re ready to scale. If you’re in pre-production with real capital at stake, DFM is your insurance policy. DM or comment “DFM” for the checklist, that’s saved founders six figures in mistakes (minimum).