Understanding Professional Responsibility in Engineering

"We just need a stamp" There is a reason Professional Engineers get uncomfortable when someone says this to them. It's because that sentence ignores everything that our stamp actually represents. Behind every seal should be: - Calculations - Material verification - Code review - Weld design - Load paths - Failure modes - Connection checks - Testing & Inspection requirements And sometimes the hardest conversation of all: "This does not work the way it is drawn." I know that can be frustrating for clients. Especially when they have already spent time on drawings, detailing, planning, pricing, or sometimes even full blown fabrication. But I would rather have an uncomfortable conversation today than explain tomorrow why something failed. Why someone got hurt. Why a company is in court. Why a family is missing someone at the dinner table. Engineering is not about putting a stamp on a piece of paper. It is about accepting responsibility for what happens after that drawing leaves your desk. This seal is not just a signature. It is a promise that I did everything I could to make sure people go home safe. Please understand that my oath is more important than any business relationship. #ProfessionalEngineer #EngineersCreed #SafetyFirst #AISC #ASME #ASCE #OSHA

Some obvious and not so obvious challenges of being a Principal Engineer   Paradox of Belonging: You are part of all teams, yet you are part of none. The role can be surprisingly isolating - you're connected to everyone but deeply anchored nowhere. It is important to find the right circles of trust, peer mentorship and individuals you can share your challenges with.   Freedom-Responsibility Paradox: You enjoy significant autonomy in being able to choose what to work on, however there is an implicit expectation and accountability for resounding impact. You constantly find yourself needing to validate if you are truly solving the right problems. The solve is to create an impact framework to assess your work's potential value while maintaining consistent feedback loops to validate not just progress but also the choices. The freedom isn't about doing what you want; it's about taking ownership of finding the highest leverage problems to solve.   Bandwidth Challenges: It is easy to become a "social resource" - the person in every meeting, involved in every key decision and helping everyone who asks. This leads to burnout from context switching, disconnect from hands-on tech and diluted impact across many initiatives. The trick is to transform from being a reactive social resource into a strategic force multiplier by establishing clear engagement frameworks, scalable solutions and protecting your bandwidth for high-leverage activities.   Being Truly Present: You find yourself physically present in one meeting while your mind is already racing ahead to the next three. This primarily stems from over-scheduled calendars with high-stakes decisions being made across multiple domains, leading to reduced effectiveness and lower quality decision making. You therefore need to create space between commitments and develop systems enabling full presence in fewer, more impactful discussions. The goal isn't to be in every meeting, it's to be fully present in the right ones.   Perfection Trap: As a responsible engineer, one always seeks to do a thorough analysis and exhaustive trade-off evaluation to make high quality decisions. However as PEs working on broader, ambiguous problems, you realize perfect decisions often compete with good enough decisions that offer progress and unblock teams. Accept that good decisions now is better than perfect decisions later. Authority Paradox: Contrary to perception, PEs possess little to no authority by default. While often being tasked with broader, cross functional initiatives, PEs lack the traditional levers of control. Unlike people managers, PEs cannot simply delegate tasks or make direct assignments. Instead, our effectiveness hinges on our ability to inspire, persuade and align diverse teams towards a common goal. PEs can't simply issue orders or delegate based on hierarchical authority. Rather, we must earn respect through a combination of technical expertise, strategic vision, and most crucially, trust.  

After spending 11 years in this industry, here’s my biggest lesson. It’s not about mastering every technical skill. It’s not about working the longest hours. It’s not even about delivering projects flawlessly. The biggest lesson? Managing interfaces is just as important as managing engineering. For years, I focused only on getting the job done. — I solved technical problems but overlooked communication gaps. — I followed procedures but didn’t challenge inefficiencies. — I assumed alignment would happen naturally between teams. I thought technical excellence alone would drive success. I believed that if I did my part, everything else would fall into place. I was wrong. The reality? — Projects succeed when teams collaborate, not just when engineering is sound. — Delays don’t just come from technical issues—they come from misalignment. — The best solutions come from those who bridge the gaps between teams. The moment I shifted my focus—everything changed. 1. Interfaces became opportunities, not obstacles. 2. Execution became smoother, with fewer last-minute surprises. 3. I became more than just an engineer—I became a problem-solver across disciplines. So if you’re reading this and thinking, “That’s not my responsibility”—think again. The best engineers aren’t just technical experts. They’re the ones who connect the dots.

Dear Mine Engineers and Candidates,🇿🇦 🎯 The Winder Section is where Leadership Meets Responsibility. If you’ve been appointed to the winder section, take a moment to understand this: You’re not just overseeing equipment—you’re safeguarding lives, influencing production flow, and anchoring the rhythm of the entire operation. This is not just another engineering duty. This is where safety meets leadership, where decisions carry weight, and where systems are as critical as the people using them. Here are key reminders for both newly appointed engineers and aspiring professionals: ⚙️ 1. Master the System, Not Just the Parts • Know the drive motor, braking dynamics, steel rope specs, control logic, and safety trips. • When things go wrong—your accountability is not shared. Contractors assist, but you carry the final signature. ✅ Takeaway: “I didn’t know” is never a defence. Learn deep. Lead strong. 🧭 2. Connect Engineering to Production • Every minute of winder downtime is a lost opportunity. • Understand your impact: tonnes moved, skips cycled, safety protected. • Your technical calls influence operational continuity. ✅ Takeaway: Engineering in this section is measured in results—not just plans. ⚖️ 3. Lead with Integrity and Precision • The Mine Health and Safety Act is your baseline—not your ceiling. • Stick to brake test intervals, OEM specs, legal inspections. • Say no to shortcuts—even when it’s unpopular. ✅ Takeaway: Choose courage over convenience. People’s lives depend on it. 🌱 4. Grow—and Grow Others • The winder sharpens crisis leadership and system thinking—embrace it. • Be the person who asks, learns, acts—and then teaches. • Elevate the next candidate through shared lessons and guidance. ✅ Takeaway: Don’t just manage the section—build a legacy within it. 🛡️ Final Thought “Some sections manage equipment. This one manages lives. Take the responsibility—and the privilege—seriously.” Let’s continue leading with discipline, commitment, and care. The industry is counting on you. #MineEngineers #EngineeringLeadership #WinderSystems #GCCResponsibility #SafetyFirst #Mentorship #FromTheShaft #MiningIndustry #AccountableLeadership #futureleaders #future #futureengineer #mining #mining life #miningnews #miningindustry #miningengineering #mininginvestment #miningsolutions #engineer #engineeringexcellence #mineengineers #mechanicalengineers #electricalengineer #gcccareers #gcc #gccengineers #mines #minesandworks #minesafety #minerals #southafrica #coachingandmentoring #gccminesandworks #lifecoaching #uj #universityofjohannesburg #university #johannesburg #dfc #doornfontein #campus #mechanicalengineering #industrialengineering #sibanyestillwater #engineeringmanager #rustenburg #inspiration #leadershipdevelopment #mentor #mentorship #Focus #dedication #career #perseverence

No Blame ≠ No Accountability In engineering, there’s often confusion between a no-blame culture and accountability. The two concepts are not mutually exclusive, and we need to be clear about the difference. A no-blame culture is essential for fostering innovation and encouraging people to learn from their mistakes without fear. However, it doesn't mean there’s no accountability. As engineers, we are accountable for our mistakes and for doing the jobs we were hired for: producing high-quality code, ensuring operational excellence, and preventing incidents. I've noticed that when we talk about accountability in incidents, there’s sometimes concern. People may say, "But we reacted quickly, and the problem was solved on time." While that’s important, and we expect fast reactions when things go wrong, this is not a substitute for doing things right from the start. We need to take responsibility when something goes wrong and acknowledge the impact it has on the business. Timely recovery is an expectation, not a justification for avoidable mistakes. Accountability means owning up to where we missed the mark and working on preventing those mistakes in the future. A no-blame culture should always encourage learning, but accountability is about holding ourselves to the highest standards, both in the work we produce and in how we respond to mistakes. Let’s ensure we understand the balance between learning from our mistakes and being accountable for our actions. #NoBlameCulture #Accountability #Leadership #EngineeringExcellence #QualityFirst #OperationalExcellence #ContinuousImprovement #GrowthMindset #TechLeadership #SoftwareDevelopment #Innovation

I still remember my first day at #civilengineering school, 30 years ago. The Dean stood in front of us and said: “Are you sure this program is for you? Or should you become a lawyer or a banker? Because if they make a mistake, people might lose money. If you make a mistake, people die - and you go to jail.” It wasn’t a warning, it was a challenge. And I took it. What makes civil engineering unique is this: every structure is a product, and every one is effectively a first of its kind. There’s no EVT, DVT, PVT, no alpha, beta, or “let’s see how it holds up in the lab.” You go from concept to site, from drawing to ground - and it has to work - most of the time :) That pressure teaches you to think clearly, act decisively, move fast, and take full ownership — because failure isn’t theoretical. As Herbert Hoover, himself an engineer, once said: “Engineering is the professional and systematic application of science to the efficient utilization of natural resources to produce wealth.” That’s what civil engineers do — we deliver real-world results, under pressure. And that mindset is powerful. It opens doors far beyond engineering: into leadership, innovation, entrepreneurship — anywhere decisions must be made with clarity and consequence. Yet for all that responsibility, many engineers don’t get paid like bankers or lawyers. Even though we carry more risk and create lasting value, we often fail to communicate that impact in business terms - and that’s why the gap persists. Too often, engineers get lost in complexity. We explain methods, models, and codes in detail, but forget to make the message simple and obvious. We mistake thoroughness for clarity - and lose the audience. As Einstein said: “Any fool can make something complicated. It takes a genius to make it simple.” And that’s where many engineers fall short - not in skill, but in simplicity. Engineers speak in precision, but the world listens in outcomes. If we can’t explain the impact of what we do in clear, simple terms, we can’t expect others to value it. That is a problem. I never waited to learn that - I’ve always been vocal and direct. From the beginning, I made sure people understood not just what I did, but why it mattered: in terms of cost, risk, and long-term performance. Not everyone liked it. In a world that prefers smooth talk and soft edges, plain speaking can make people uncomfortable. But as Churchill said: “You have enemies? Good. That means you’ve stood up for something.” That’s the lesson. Technical skill is your foundation. But if you want your work to be understood, your judgment trusted, and your contribution valued - you need to speak your value. Clearly. Confidently. Consistently. As Seth Godin said: “You’re not being judged by your efforts, but by how well you explain the impact of those efforts.” Don’t wait for your work to speak for itself — you speak for it.

✅RELIABILITY IS EVERYONE’S RESPONSIBILITY ➡️Reliability is not a function, a department, or a job title. 👉It is a way of working. 🔶Just as safety is not owned by the Safety Officer, reliability is not owned by the Reliability Engineer. 🔶They provide the systems, standards, and expertise — but results are created by daily decisions across the organization. ➡️Every design choice, every operating practice, every maintenance task, and every management decision either builds reliability or destroys it. 🔸Engineers design reliability in — or design failures in. 🔸Operators protect reliability — or consume it. 🔸Maintenance preserves reliability — or creates repeat failures. 🔸Planners enable reliability — or defer risk. 🔸Leaders set the culture — or accept breakdowns. 👉A Reliability Engineer cannot compensate for: ✔️Operating outside design limits ✔️Deferred maintenance ✔️Poor workmanship ✔️Short-term production pressure Just as a Safety Engineer cannot prevent accidents alone. ➡️Our expectation is simple: 👉Reliability is how we work — not someone else’s job. ✔️Leaders must protect time, resources, and discipline. ✔️Supervisors must enforce standards. ✔️Teams must own asset health as they own safety. ➡️When reliability is treated as a shared responsibility, we achieve: 🔸Predictable production 🔸Lower cost 🔸Safer operations 🔸Sustainable performance 👉This is not optional. ✅This is operational excellence. Reliability is built by design, operated by discipline, maintained by skill, and sustained by leadership. That is our standard. #reliability #rcm #leader

Be Responsible A new year is a good time to reflect on one key question every Candidate Engineer should be asking: Am I positioning myself to grow in responsibility? ECSA assesses readiness for Professional Engineer (Pr Eng) registration using the Degree of Responsibility (DoR) framework. This is not about job titles alone — it is about the level of engineering judgement, accountability, and independence you carry. Degree of Responsibility (simplified) A - Observation - Graduate / Intern B - Defined tasks - Junior Engineer C - Limited discretion - Engineer D - Significant responsibility - Senior / Design Engineer E - Full engineering accountability - Lead / Responsible Engineer ➡️ Key reminder: To register as a Professional Engineer, you must demonstrate at least one full year at Degree of Responsibility E. This is a minimum requirement — it is strongly advisable to remain at this level longer to build depth, confidence, and defensible experience. Typical progression Graduate → A → B → C → D → E → Pr Eng Progression is not automatic and not time-based alone. It depends on the responsibility you are given — and the responsibility you accept. As we start the year, take ownership of your development. Seek responsibility. Seek judgement. Seek accountability. Be Responsible.

Cyber-involved threats are now safety risks, and this PE Magazine piece makes a strong case that licensed engineers must treat cyber as a core design responsibility—not an afterthought. As our infrastructure becomes more connected, the line between “cyber” risk and traditional safety, reliability, and ethics has effectively disappeared. For licensed professional engineers, that means our duty to protect the public now extends deep into the digital domain, from control systems and sensors to cloud platforms and AI-enabled decision support. What I appreciate about this recent PE Magazine article is how it frames cyber-informed engineering as part of the engineer’s obligation to hold paramount the health, safety, and welfare of the public—not just an IT problem or a compliance box to check. It underscores that engineering without cyber awareness can unintentionally build in single points of failure, cascading outage pathways, and exploitable trust assumptions in critical infrastructure systems. If you work in energy, water, transportation, manufacturing, or any other sector that relies on digital controls, I encourage you to read it and reflect on how your practice, standards, and review processes are evolving to address these intertwined physical–cyber risks. Strengthening our cyber-informed engineering mindset is not only good risk management; it is central to maintaining trust in the engineering profession in a highly connected world. National Society of Professional Engineers, Institute of Industrial and Systems Engineers, Florida Engineering Society (FES), American Council of Engineering Companies of Florida (ACEC Florida), INCOSE, Florida Institute for National Security (FINS), Andrew Ohrt, PE, CISSP, Jeff Daniels, PhD, Anthony Dezonno, Brett Goodman, Justin Gregory, Bill Atkinson P.E., Fellow NSPE, Michael Coleman, ICE-CCP, Ⓥ, Bart Kemper, P.E., Susan Ronning, P.E., PMP, ASEP, Phil Laplante and others drive public safety. https://lnkd.in/eiQ_Ku2R