Strategies for Resolving Engineering Challenges

In reliability engineering, strategy improvement success hinges on identifying and resolving failure causes. However, a critical step that often determines the investigation's success is data collection. Collecting inaccurate or insufficient data risks addressing only symptoms—not the root cause—leading to persistent problems. 🛠️ Key Factors for Effective RCAs: Comprehensive Data Collection: Viewing the system holistically and gathering insights from all angles—historical data, environmental conditions, failure patterns, and operator input—prevents narrow conclusions and illuminates the root of the problem. Strong Cross-Functional Relationships: Collaboration between reliability engineers and maintenance/operations teams is essential. Reliability engineers bring analytical depth, while maintenance and operations teams offer practical, on-the-ground knowledge. This partnership fosters mutual trust and more complete investigations, as each team provides insights that would be overlooked if working in silos. Objective, In-Depth Interviews: Facilitating open discussions with maintenance and operations team members creates a safe space for honest feedback. In-depth knowledge from experienced team members can reveal critical failure insights that aren't evident in the data alone. Cross-Departmental Input: Bridging operations and maintenance perspectives builds a unified approach to RCAs. Operations may have specific knowledge about workload changes or procedural adjustments that affect outcomes, making their contributions invaluable to reliable, actionable RCAs. Holistic Analysis Techniques: Tools like 5-Why, Fishbone, and FMEA ensure comprehensive cause analysis. Validating findings with real operational data ensures that we address the core issues rather than just the surface symptoms. 📊 Data as the Backbone of Effective Actions: Accurate data and strong relationships translate into actions that address the true failure mechanisms, leading to reduced downtime, increased asset reliability, and optimized maintenance costs. In contrast, incomplete data or lack of cooperation can cause RCA efforts to miss the mark, leading to temporary fixes and higher costs. 🔹 The Role of Management Buy-In 🔹 For RCAs to drive sustainable change, management buy-in is essential. Leaders need to support the RCA process fully, holding teams accountable for actions across Operations, Maintenance, and Reliability. This commitment builds a reliability-centered culture, ensuring that RCA findings lead to lasting improvements. Our success as reliability engineers depends not only on precise data but also on strong relationships with maintenance and operations teams. These connections, combined with data-driven insights, allow us to implement solutions that address root issues, creating sustainable improvements that enhance equipment performance and team success. #RootCauseAnalysis #ReliabilityEngineering #Maintenance #Operations #TeamCollaboration #Data

Rethinking Requirements in Hardware Engineering Requirements management isn’t just about checklists—it’s the difference between effective collaboration and costly missteps. Here are once-unconventional approaches to requirements now embraced by top teams 1. From “Requirements” to “Design Criteria” Early systems engineers were part engineer, part lawyer. Someone had to create “techno-legal documents” to manage external contracts. These evolved into requirements. Many cultural issues stem from using requirements incorrectly–as a weapon rather than tool for collaboration. Not all requirements need to be treated as commandments. Reframing lower-level requirements as design criteria reduces resistance among engineers, empowering them to see requirements as flexible guidelines open to questioning and adjustment. This is what you want to inspire. 2. Culture of Ownership and Accountability Drives Agility A strong requirements culture is built when engineers “own” their work. Engineers must take responsibility for the requirements they design against, creating a culture of ownership, responsibility, and systems-mindedness. Assigning a clear, single-point owner for each requirement, even across domains, encourages each engineer to think critically about their area’s requirements, establishing ownership and trust in the process. Encouraging information flow between teams helps engineers see how their work impacts others, leads to reduced and stronger system integration. Requirements should be viewed as evolving assets, not static documents. You want engineers to push back on requirements and eliminate unnecessary systems rather than add more requirements, complexity, or systems. 3. Requirements as Conversations, Not Just Checklists Requirements aren’t just specs or checklists—they’re starting points for cross-functional discussions. Every problem is a systems problem, and to solve complex challenges, engineers must be systems thinkers first and domain experts second. In traditional settings, requirements stay isolated in documents. But when teams understand why requirements exist, where they come from, and who owns them—and engage in continuous dialogue—they blur the lines between domains and foster a systems-oriented mindset. This collaborative environment accelerates problem-solving, enabling engineers to align quickly and tackle challenges together. Instead of siloed requirements for each subsystem, drawing dotted lines and encouraging information flow between teams helps engineers understand how their work affects others. This cross-functional awareness leads to fewer misalignments and stronger system integration. When you see engineers make sacrifices in their own area to benefit the overall system, you know you are on the right track. There you have it. The full guide goes into specifics on how to start implementing these ideas in tools.

Often the advice I read about developing medical devices seems to assume an ideal world. But what about the messy real world where things go wrong, sometimes in a big way?  In this article in MPO Magazine my co-author Russell Singleton and I describe two methods to help overcome the challenges that arise in development projects in the real world. 🔷 Cross-functional analysis for robust problem solving: Cross-functional analysis through frequent technical design reviews is a proven method for solving the many problems that arise in product development projects. These reviews leverage diverse expertise to identify technical risks, develop solutions, and foster innovation. Truly cross-functional analysis requires bringing multiple points of view to analyze the product design and design problems, beyond the people directly involved in the design issue. The strength of this method depends on the diversity of expertise and perspectives of the attendees. Depending on the topic, the review team may include members from engineering, clinical, marketing, regulatory, manufacturing, customer support, and quality, as well as external experts. Note that these technical reviews are separate from and complementary to formal Design Reviews / Phase Reviews mandated in the company’s design control procedures. 🔷 Restarting in the face of a large obstacle: There are multiple ways a development project can be tripped up: markets are dynamic, competitors come out with unforeseen products, and some innovative technologies may be even more difficult to use than expected. When faced with a large obstacle, the team needs to stop and re-analyze the fundamentals of the product as if the project was back in Phase Zero. The key to finding a new path forward for the project is to revisit the original Phase Zero activities: - Understanding the customer’s job: Reanalysis of user needs and alternative ways to meet them - De-risking technology: Investigation of alternative technologies for the same product concept - Defining the product strategy: Investigate a different marketing strategy or regulatory strategy. This may seem like an extremely expensive way to address a large, unexpected obstacle, but to find a way forward for the project in these circumstances—to execute a pivot—requires looking broadly and questioning the product concept. The alternative is to cancel the project. For more on these methods, see the link in the comments to the full article. What methods have you found valuable for dealing with the bumps, large and small, in the road of new product development?

What can upper management do to enable a culture of collaboration—even in large projects with multiple teams and managers? Ever wondered how to make large, multi-team projects truly collaborative? In many organizations, a common challenge is ensuring that engineers feel empowered to contribute and learn across different parts of the same project. The good news? Leading companies are actively cultivating cultures that break down silos, fostering a much deeper understanding of the entire system. It’s about enabling engineers to see the bigger picture and contribute wherever their expertise is most valuable. Here are three powerful strategies that are gaining traction: 1. Implementing InnerSource Imagine applying open-source development practices within your company. Engineers are encouraged to contribute code, fix bugs, and propose enhancements to modules owned by other internal teams. This fosters shared ownership, promotes knowledge sharing, and builds a collective understanding of the codebase across the organization. It’s collaboration on a grand scale. 2. Organizing Around Value Streams or Features Instead of structuring teams purely by technical layers (e.g., frontend, configuration backend, observability GUI, observability backend, data plane, service plane), many networking and security companies now organize teams around end-to-end delivery of customer value or features. For example, you might see a dedicated Firewall Team, VPN Team, CASB Team, or DLP Team—each owning their feature across the stack, from UI and APIs to backend and data plane functions. This structure fosters holistic understanding and alignment within teams, ensuring that everyone grasps the full scope of a feature’s delivery. 3. Establishing Guilds or Communities of Practice (CoPs) These are groups of engineers from different teams who share a common interest or specialization (e.g., a “Cloud Security Guild” or a “Performance Optimization CoP”). They meet regularly to share knowledge, discuss best practices, and solve common challenges. CoPs transcend traditional team boundaries, enabling cross-pollination of ideas and continuous learning beyond the formal reporting structure. These approaches directly support the kind of system-wide thinking that’s crucial for effective debugging, resilient design, and growth into impactful architectural roles. They help engineers expand their horizons and take true ownership of the product’s success. #SoftwareEngineering #TeamCollaboration #InnerSource #DevOps #TechCulture #NetworkingSecurity #EngineeringLeadership #CareerGrowth #SystemDesign #Aryaka

Engineering teams are racing to ship GenAI systems. However, as these systems move from prototype to production, a common challenge emerges: strategically leveraging the ever-growing toolkit of LLM techniques and picking the right tool for the job. This 2x2 framework offers a more strategic mental model to help you decide when to apply which LLM technique and why—from boosting performance to minimizing risk. Here are the 7 common challenges and key patterns to address them: 📊 Lacking performance metrics? Need to measure progress? → Evals 📚 External model performing poorly or lacking context? → RAG 🔧 Internal or external model underperforming on specific tasks? → Fine-tuning ⚡️ Latency killing your user experience? → Caching 🛡️ Unreliable or unusable model output? → Guardrails 😊 Customer experience issues impacting adoption? → Defensive UX 👂 Unsure if your LLM features are truly helping? → Collect User Feedback For a much deeper dive into each of these 7 patterns, Eugene Yan's latest masterpiece is a must-read (link in the comments 👇)

You're confident a feature should take 3 days. Engineers tell you it will take 3 weeks. What can you do? Preventing over-engineering isn't about patronizing your engineers by telling them to "keep it simple" - help your engineers think about how to keep it simple with strategic constraint setting. → Lead with user outcome metrics, not feature completeness. This shifts engineers from "what could break" to "what moves the needle." When success is measurable, trade-off decisions become self-evident rather than endless debates. Example: Define success as "users complete checkout 15% faster" not "handles all payment edge cases." Engineers optimize for what you measure. → Explicitly separate v1 constraints from future extensibility. Engineers are trained to build for scale, so they'll default to over-architecture unless you give explicit permission to be tactical. This actually accelerates future iterations because v2 requirements are clearer. Example: Say "we're OK with hardcoding this for launch" rather than "make it scalable." Give permission for tactical debt with clear v2 timeline. → Anchor technical discussions in user data, not theoretical scenarios. Engineers naturally imagine worst-case scenarios because that's how they prevent systems from breaking. Real usage patterns help them distinguish between edge cases worth solving vs. premature optimization. Example: When engineers say "but what if a user has 10,000 items in their cart," pull out actual usage data. Real constraints beat imagined ones. —— A PM's job is not to restrict their engineers, it's to redirect engineering creativity toward the problems that actually matter. #productmanagement

Most engineers don't fail at fixing I&I problems.   They just accept the first solution presented. Why? Because it feels safer to: • Go with the consultant's $2M replacement plan  • Avoid questioning the "expert" recommendation  • Sign off on wholesale system replacements  • Choose the solution that "no one gets fired for" But here's the truth: NOT questioning the default solution is the riskiest move you can make. Remember that mountain community I&I study we completed? ↳ 90% of their WWTP flow was I&I ↳ Treatment plant operating at 9x necessary capacity   ↳ Initial recommendation: Complete system replacement   ↳ Our finding: 60% of problems in just 2 areas The difference? We questioned everything. https://lnkd.in/dY_eYZa4 Instead of accepting the standard "replace it all" approach, we asked: "What if we just fixed the 40% causing 90% of the problem? Result: Same outcome, 80% less cost. The best engineers aren't afraid to push back on expensive solutions. Challenge. Every. Single. Assumption. Next time a consultant hands you a massive replacement plan, ask: "Where's the data showing we need to replace everything?" Who cares if you ruffle feathers? The day you start demanding targeted solutions is the day you start being a true advocate for your community. What "standard practice" are YOU ready to challenge in 2025? Drop it in the comments - let's stop over engineering and start solving. #engineeringsolutions #infiltration #inflow #wwtpflow

🔍 When 5 Whys and 8D Don’t Work – The Problem Isn’t the Tool. It’s Deeper. Have you ever gone through a supplier’s 5 Whys or 8D report, expecting real answers — only to find yourself wondering if anyone really dug into the problem? Even worse, the same issue pops back up weeks or months later, unchanged and unresolved. Here’s the hard truth: ❌ The problem isn’t with the 5 Whys or 8D methodologies themselves. ✅ The problem lies in how they’re applied — or ignored. What does this usually mean? 🔹 The 5 Whys stopped too soon — at the first or second "why" — because deeper probing reveals uncomfortable truths no one wants to face. 🔹 The 8D is packed with generic, surface-level corrective actions like “retraining” or “awareness sessions” that treat symptoms, not causes. 🔹 There’s little to no evidence that the actual process or system was modified to prevent recurrence. 🔹 Technical issues are often handled as if they’re just paperwork exercises rather than real operational challenges. 🔹 Worst of all, sometimes these tools are just “ticked boxes” — done to satisfy the customer or audit requirements rather than to drive true resolution. 📌 Here’s the insight: If your root cause analysis isn’t driving change, it’s not problem solving — it’s theater. It’s a show for compliance, not a step toward excellence. So, what do you do when you hit this wall? ✅ Step one is recognition — acknowledge that the tools alone don’t solve problems; people do. ✅ Bring all relevant stakeholders together — supplier quality, engineering, manufacturing — and get boots on the ground. ✅ Challenge the status quo with tough questions — don’t accept easy answers. ✅ Shift focus from paperwork to proof — ask for evidence that corrective actions have been truly effective. ✅ Promote a culture of ownership — problems don’t disappear if no one owns them. In aerospace manufacturing and any high-stakes industry, recurring supplier issues are costly — not just financially but also in trust and reputation. Are you seeing recurring issues in your supply chain? What strategies have you found effective to push past superficial fixes and create real, lasting solutions? Let’s share and learn together. #RootCauseAnalysis #8D #5Whys #SupplierQuality #ContinuousImprovement #ManufacturingExcellence #ProblemSolving #AerospaceIndustry #Leadership #QualityCulture

Challenges and problems are inevitable in every organization. However, how we approach and solve these problems defines our success. 👾Problems can hinder growth and demoralize teams. 👾Effective problem-solving turns challenges into opportunities. 👾Collaboration and creativity are key. 👾Continuous improvement drives long-term success. 👾By fostering a problem-solving culture, we pave the way for innovation and growth. How can we effectively solve problems in our company? Why? Addressing the root cause of problems prevents recurring issues and promotes a proactive rather than reactive approach. According to a study by Harvard Business Review, companies that focus on root-cause analysis significantly improve their operational efficiency and employee satisfaction. 🍉Diverse perspectives lead to better solutions. 🍉Structured brainstorming encourages innovative ideas. 🍉Clear action plans ensure accountability. 🍉Regular monitoring and adjustments keep projects on track. 🍉Reviewing outcomes helps in learning and improving. What strategies do you use to tackle problems in your organization? Steps to Solve Problems Effectively in Your Company: Step 1: Identify the Root Cause ➟ Don’t just address the symptoms. Use tools like the 5 Whys or Fishbone Diagram to dig deep and identify the underlying cause of the problem. Step 2: Engage Your Team ➟ Collaboration is key. Involve team members from different departments to get diverse perspectives. This not only brings in new ideas but also ensures everyone is on the same page. Step 3: Brainstorm Solutions ➟ Encourage creative thinking. No idea is too wild at this stage. Use brainstorming sessions to generate a list of potential solutions. Step 4: Evaluate and Prioritize ➟ Assess the feasibility, impact, and resources required for each solution. Prioritize them based on these factors. Step 5: Create an Action Plan ➟ Develop a clear, step-by-step action plan. Assign responsibilities and set deadlines to ensure accountability and timely execution. Step 6: Implement and Monitor ➟ Execute the plan with agility. Monitor progress regularly and be ready to make adjustments as needed. Step 7: Review and Learn ➟ After the problem is resolved, review the process and outcomes. Discuss what worked, what didn’t, and how the process can be improved for future challenges. Solving problems is not just about fixing what’s broken; it's about continuous improvement and innovation. By fostering a culture that embraces challenges and encourages creative solutions, we can turn obstacles into stepping stones for growth. What problem-solving techniques have you found most effective in your organization?