Engineering Design Methods

This 3D-scanned ear not only restores people's face, but their life in hours. The Epithese Ear is redefining what’s possible in facial prosthetics. Every year, millions face the loss of an ear—not only with a huge physical impact, but also social burden. Now, a breakthrough in patient-specific prosthetics delivers what surgery alone couldn’t: Engineers and artisans built what medicine said couldn’t be done: → An ear sculpted with 0.1mm 3D scanning → 150 skin tones, seamlessly color-matched → Secure integration with bone-anchored titanium → Sculpted detail + texture, indistinguishable from life All from a studio that works more like a digital art lab than an operating room. The breakthrough? Immediate transformation—no waiting. From scan to new ear in less than 48 hours. Zero recovery, zero compromise. Why this changes everything: → Speed when it matters most A new ear, fit perfectly, before your next meeting—return to daily life with confidence restored. → Innovation, personalised → Real Impact In patient outcomes: -97% ear symmetry* -Zero rejection rate -Full social reintegration Every year, 1.5 million people require facial prosthetics: -60% report social challenges -Countless avoid public interactions This changes the narrative. Human's artistry using 3D Design tools—restoring more than appearance, rebuilding lives. These advances show a bigger shift: hyper-personalized, non-invasive medical solutions that merge rapid digital fabrication with hands-on craftsmanship. Follow me, Dr. Martha Boeckenfeld for more breakthroughs transforming people's life. ♻️ Repost to share these life-changing innovations. #MedTech #FacialProsthetics #HealthInnovation #FutureOfMedicine

Rick Rubin went on stage in Helsinki the day after my talk. Someone asked how he resolves creative differences with artists. His answer was simple: change the conversation from "I disagree" to "let's build it." Then he shared a story: An artist played him a song. The transition didn't work. Rubin told him so. The artist said, "We'll just cut that part in half." Rubin thought to himself: What a dumb idea. But he didn't say that. He said, "Let's try it." The artist played it. It worked. Rubin is a legend. He's produced everyone from Johnny Cash to Jay-Z. Instead, he bit his tongue and let the artist prove him wrong. The principle: when you make an idea tangible, it stops being the person's idea. It becomes something you can both look at objectively and improve together. Once you build it, the truth is obvious. Here's what this looks like in practice: Your designer wants to change the entire homepage layout. You think it's too risky. Instead of three meetings debating it, you say: "Let's build a prototype and test it with 50 users this week." Your sales team wants to restructure the pricing page. Instead of blocking it because you're worried about conversions, you say: "Let's run it as an A/B test on 20% of traffic for two weeks." Your engineer wants to rebuild a core feature from scratch. You think it's overengineered. But instead of killing it in the planning phase, you say: "Spike it out in three days and show me if the performance gain is real." You're not saying yes to everything. You're saying, "Let's find out." Rubin also said something that stuck with me: "If there's disagreement, I always side with the artist's vision. Because to them, it's their career. To me, it's just one piece of my portfolio." Most leaders think backing down makes them look weak. Rubin knows that siding with the person who has the most at stake makes better work happen. Your job isn't to be right. It's to create the conditions where the best idea wins. Stop debating. Start building. P.S. This insight is from this week's newsletter where I break down why Yamaha dominates while Steinway got sold to private equity: https://lnkd.in/efSqP_9K P.P.S. Access additional research links, the podcast, and the full archive in the first comment 👇 Thank you to Nordic Business Forum!

I've been using Clean Architecture for 6+ years. Here’s why I think it’s amazing. 👇 The biggest pain in enterprise systems? A lack of structure. Every project reinvents the wheel. Every team builds layers differently. And knowledge doesn’t transfer between systems. But there’s a proven way to fix this. It’s called Clean Architecture. It’s not about how many projects you create. It’s not about fancy patterns. ✅ It’s about the direction of dependencies. Inner layers (domain, app) define abstractions. Outer layers (infra, presentation) implement those abstractions. Never the other way around. That’s it. That’s the rule. You can package this as: - Layers (domain, app, infra, web) - Vertical slices (grouped per feature) - Components (layers + vertical slices) They all work — if you follow the rule. What are the benefits? - Modular code - Clear separation of concerns - Easy-to-test business logic - Faster onboarding - Loosely coupled components Clean Architecture has helped me ship excellent products. And I’ll keep using it because it works. Want to simplify your development process? Grab my free Clean Architecture template here: https://lnkd.in/eDgfyWKB

Optimization under uncertainty without stochastic optimization A friend of mine (former colleague from Princeton) and a top optimization specialist emailed me recently:   “If I have a way to quantify uncertainty from my data, how do I incorporate that uncertainty into the decision making process? (This is where stochastic programming, approximate dynamic programming, and a host of other techniques come into play).”   The idea that you have to use “stochastic programming” or “approximate dynamic programming” to handle uncertainty in optimization is simply wrong. These are tools that are popular in the academic journals, but rarely used in practice.   A far more powerful approach is to begin by thinking about how uncertainty would affect the solution to the problem, and introduce parametric adjustments, either to the objective function or (more often) to the constraints.   The first step is to recognize that the optimization problem being solved at a point in time is a surrogate – solving it is a policy for solving a sequential decision problem (as I illustrate in the graphic below).   There are two challenges getting this model to work well over time:   o You have to decide how to parameterize the model to make it work well over time. o Then, you have to tune the parameters, either in a simulator or by watching how it works in the field.   The simulator is your model, not the optimization model that produces the decision. This is where stochastic processes are represented. The tuning picks up the effects of uncertainty as the policy is simulated, avoiding the complexity of introducing uncertainty explicitly in the policy.   And remember – an optimal solution to the surrogate model is not an optimal policy… but if carefully designed, it might be quite good.   I call this approach a parametric cost function approximation (CFA). An illustration is provided on the webpage:   https://lnkd.in/dmh36K-c (“tinyurl.com/” with “cfapolicy”)   Or go to chapter 13 of my RLSO book:   https://lnkd.in/dB99tHtM (“tinyurl.com/” with “RLandSO”)   You can download chapter 13 from https://lnkd.in/eWTMDURh. 

🪂 How To Make Your Design System AI-Ready (https://lnkd.in/dtnpy7CM), a practical guide on how to reduce drifts, minimize mistakes, maintain context and improve the quality of AI-generated prototypes — with structured spec files, automated auditing and token layers. Put together by Hardik Pandya from Atlassian. --- 🔹 1. Design Decisions Are Infrastructure AI-generated prototypes often don't deliver consistently decent results because of tiny inconsistencies scattered all across a design system. Often it's decisions made but not documented, hard-coded values never cleaned up, or relying too much on AI making sense of mock-ups or design flows on its own. Unsurprisingly, better AI prototypes come from better data — but also from better human guidance. We shouldn’t assume that AI knows how to choose the right component, and how to design with accessibility in mind. It needs priorities, a clear path on how we make decisions, design principles, examples, do's and don'ts. In fact, we should treat design decisions as infrastructure. That means that every time we make a decision — not just a design decision, but even decision on how actually prioritize our work and how we make decisions around here — it must find a path into the spec file that is then consumed by AI. --- 🔶 2. Three Layers: Spec Files + Token Layer + Audit To ensure quality, we establish design principles, guidelines, rules in a form of “spec files”). It's structured Markdown files that include spacing rules, color choices, component usage guidelines, priorities etc. AI is going to read and reuse that spec file every time it's going to generate a prototype. Because the spec files are text files, it's much more cost-effective, but also much more accurate just because we don't rely on AI recognizing or decoding patterns from mock-ups, but gets specific guidelines instead. In fact, extending code is often a more effective way than generating code from mock-ups. Token layer lists and keeps updated all tokens used throughout the design system. AI always chooses from a closed set of named variables instead of inventing plausible values ad-hoc. An audit script catches what AI gets wrong. It scans the prototype and flags every hard-coded value and flags it if necessary. It can be a regular software doing that, with AI waiting for its feedback to come back. Finally, when a design system ships updates, a sync routine flags which spec files need updating. The goal is to make sure that AI always reads up-to-date, current specs, not the ones written against an outdated version. --- 🔺 3. Examples of AI-Ready Design Systems ⌾ Atlassian: https://lnkd.in/dVsGc3Cp ⌾ Carbon: https://lnkd.in/d4zq4WWb ⌾ CMS Design System: https://lnkd.in/dHHzV3en ⌾ Nordhealth: https://lnkd.in/d8C4j2ZA Yet again, AI can’t magically resolve technical debt or design debt — it needs guidance, decisions, priorities and principles.

🚗 Imagine this: You launch a new car model after years of effort. Production is smooth, the assembly line is world-class… but six months later, the headlines scream “Massive Recall.” Billions lost. Reputation damaged. All because of a design flaw that was locked in during the product development phase. Takao Sakai once said: 👉 “95% of Toyota’s profits are determined in the product development phase, not production.” And it’s true across industries: In aerospace, material choices made at the design table decide 80% of lifecycle costs. In electronics, overengineering features adds cost but not value. In manufacturing, late design changes cause delays that no production efficiency can recover. ⚡ The real challenge? Most companies pour their energy into fixing problems on the shop floor instead of preventing them during development. 💡 The smarter way: Apply Design for Manufacturability (DFM) & Concurrent Engineering. Run early simulations & prototypes to detect risks. Involve quality, supply chain, and production teams at the concept stage. Use Voice of Customer (VOC) to cut out features no one wants but everyone pays for. The truth is simple: ✅ Every mistake caught in design costs a fraction of fixing it in production. ✅ Every smart decision in development compounds into long-term profit. 🔑 What’s one thing your team does during product development that safeguards future profitability? 👇 Share your experience—it might spark ideas for someone else! #Lean #ProductDevelopment #DesignThinking #Innovation #BusinessExcellence #Quality #TQM

🌍 Half the towers, half the land. Welcome to the world of HVDC. This image shows two transmission systems, both operating at 800 kV. But there’s a big difference between HVAC (alternating current) and HVDC (direct current). 🏗️ On the left: 800 kV AC (two three-phase lines) ➤ Requires a right-of-way (ROW) width of ~320 ft (~100 m) ➤ 6 conductors (2 circuits × 3 phases) ➤ Large towers with wide phase spacing to reduce corona discharge ⚡ On the right: ±800 kV DC (one HVDC line) ➤ Only ~130 ft (~40 m) ROW width ➤ Just 2 conductors (bipolar configuration: + and −) ➤ More compact tower, lower profile, reduced EM fields and losses 🔍 Why HVDC is more efficient: ✅ 40–60% less land use ✅ Significantly lower losses over distances >600–800 km ✅ No reactive power = better efficiency and control ✅ Ideal for underground, subsea, mountainous, or densely populated routes ✅ Transmits up to 6400 MW on a single corridor 📌 Real-world example: Yunnan–Guangdong ±800 kV UHVDC (China) ➤ Length: 1,418 km ➤ Power capacity: 6400 MW ➤ Configuration: Bipolar overhead transmission ➤ Delivers hydropower from Yunnan to industrial Guangdong ➤ Reduces losses, land footprint, and CO₂ emissions 📐 HVDC isn’t just an alternative it’s how we optimize large-scale transmission: less land, lower losses, more power. #HVDC #UHVDC #PowerTransmission #EnergyInfrastructure#GridEngineering #ElectricalEngineering #SustainableEnergy #SmartGrid#HVACvsHVDC #ChinaEnergy

O-Rings: Why a Simple Rubber Ring Isn’t So Simple If you’re studying mechanical or aerospace engineering You’ve probably seen an O-ring Just a donut-shaped rubber part that seals two surfaces. Looks simple, right? But once you dive into analysis and simulation, you’ll realize: O-ring sealing is surprisingly hard to get right. 👉 Here’s why: 📌 Rubber Isn’t Like Metal Rubber behaves very differently from steel or aluminum. It stretches a lot, doesn’t compress much, and its stress-strain relationship is nonlinear. That means we need advanced models like Mooney-Rivlin or Ogden - not just Hooke’s Law. 📌 Contact Is Complicated O-rings work by pressing against surfaces. Modeling that contact - especially when there’s friction - is tricky. It can lead to nonlinearities that make your FEA (finite element analysis) struggle to converge. 📌 It’s More Than Just Shape Even though the geometry is simple, you have to consider temperature, pressure, and even fluid compatibility. Real O-rings deform, age, and sometimes leak - and you need to predict that. 📌 Manufacturing Tolerances Matter Small variations in dimensions can make or break a seal. In simulation, this means paying attention to the real-world tolerances you might ignore in the classroom. 📌 Failure Can Be Subtle Sometimes the O-ring extrudes, other times it loses pressure over time. And sometimes it just cracks from heat. These failures are hard to spot but in critical systems, the consequences are huge. 📜 Lesson? Don’t let the simple shape fool you. O-ring analysis is a great introduction to nonlinear mechanics, material modeling, and real-world engineering tradeoffs. #Engineering #CAE #FEA #ORings #MaterialScience #MechanicalDesign #LearnEngineering #Simulation #computationalmechanics

🔧 Pump Design Calculations & Hydraulic Procedures – A Practical Engineering Overview 🌊 When it comes to pump design, getting the numbers right means everything from system efficiency to long-term reliability. Here's a concise yet comprehensive breakdown of the key steps and calculations involved in designing or selecting pumps for industrial applications: 1. System Head Calculation Static Head: Elevation difference between suction and discharge points. Friction Head Loss: Head losses due to pipe length, fittings, and valves. Use Darcy-Weisbach or Hazen-Williams equations. Total Dynamic Head (TDH) = Static Head + Friction Losses + Pressure Head (if any) 2. Flow Rate Requirements Define based on process demand. Ensure appropriate volume transfer per unit time. Common units: m³/hr (cubic meters per hour) GPM (gallons per minute) 3. Pump Power Calculation Hydraulic Power (kW): P_hyd = (Q × H × γ) / 367 Where: Q = Flow rate (m³/hr) H = Total Dynamic Head (m) γ = Specific weight of fluid (kg/m³) Brake Horsepower (BHP): BHP = Hydraulic Power / Pump Efficiency 4. NPSH (Net Positive Suction Head) Prevents cavitation and protects the pump. Ensure: NPSHa > NPSHr Where: NPSHa = Net Positive Suction Head Available NPSHr = Net Positive Suction Head Required (from pump datasheet) Factors that affect NPSHa: Atmospheric pressure Vapor pressure of the fluid Friction losses in suction line Static suction lift/head 5. Pump Curve Analysis Match the system curve with the pump performance curve. Choose a pump that operates near the Best Efficiency Point (BEP). Avoid: Operating at shut-off head (zero flow) Operating at runout (maximum flow, low efficiency) Engineering Insight: A well-designed pump system is not just about moving fluid — it's about achieving performance, efficiency, and reliability through correct design and analysis. Let’s connect and share ideas if you're working with fluid systems, process engineering, or industrial design! #PumpDesign #Hydraulics #MechanicalEngineering #FluidMechanics #ProcessDesign #TDH #NPSH #EnergyEfficiency #EngineeringLeadership #IndustrialAutomation #CentrifugalPump #DesignEngineering

Today, I interviewed a candidate for our mechanical design team and asked what seemed like a simple question—yet, in my opinion, a very difficult one. Looking at a drawing of a shaft and a hole, I asked: “Do you think the shaft will fit into the hole?” As expected, the candidate quickly answered, “Yes.” So I added: “What if I told you I measured both with a calibrated vernier on-site, and they still don’t fit? Where do you think the issue might be?” Early in my career, I thought engineering assembly was just about tolerances with upper and lower limits. Later, I learned about clearance fits, transition fits, and interference fits with different tolerance grades. But real-world engineering is far more complex. Without knowing the manufacturing process, how do we ensure the shaft is truly straight and not bowed? (E.g what if that shaft is actually 3D printed when our 1st impression told us it should have been lathed?) If it's lathed, does that guarantee straightness across all materials? Most importantly, which standard are we using—ISO GPS, ASME GD&T, or GB? For example, ISO GPS follows the Independency Principle, meaning a shaft can have a slight curvature while still meeting spec in cross-sections. In contrast, ASME GD&T applies the Envelope Principle, where size tolerance also controls form variation—meaning the same shaft might actually fit. This is why engineering isn’t just about numbers. It’s about understanding the whole process, including: manufacturing processes, material properties, inspection methods, and—crucially— the fact that 'people do things differently'. Was I trying to trick the candidate? No. This question actually reflects our daily work: navigating technical challenges across companies, industries, and cultures, where even experienced engineers might disagree based on their background. Not even to mention with language barriers and regional differences, how much more complex things could become. That’s why we don’t assume—we ask, listen, and adapt. Only by keeping an open perspective can we truly solve engineering problems across borders. #engineering #design #manufacturing #quality #tolerance #standards #ISO #ASME #globalengineering