Principles of Design

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!

When Style Disrupts Safety: A Lesson in Product Design Today, while driving behind the sleek Mahindra BE.6E, a futuristic and stylish EV, I experienced something unexpected. The car in front of me braked suddenly. I had maintained a safe distance, so I stopped comfortably. But something felt off. Why did the braking catch me off guard? Then I realized: The brake lights were too subtle. The taillights are designed as a thin rectangular LED strip, stunning to look at, no doubt. But the brake lights occupy only a tiny section on the top edge of that strip. Visually stylish, but functionally weak. In real traffic conditions, where immediacy and clarity are critical, this design doesn’t help other drivers react intuitively. This reminded me of a fundamental product design principle: Aesthetics must never come at the cost of usability. A good product delights not just by how it looks but by how well it works. Whether we’re designing: • A mobile app • A banking interface • Or a car’s tail lights …it’s our job as product managers and designers to make sure the experience is not just elegant, but intuitive, accessible, and safe. Lesson for us in Product Management: Design for the user’s reality, not just the brand’s imagination. Functionality and clarity should never be hidden behind a glossy UI, whether it’s a screen… or an LED strip on a car. #ProductManagement #UXDesign #Usability #AutomotiveDesign #DesignThinking #BuildWithEmpathy

🪂 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.

A place can be well connected on paper and still fail on foot. That is rarely because walking was overlooked altogether. It is because other priorities were given more weight when the scheme was being shaped. A station may sit nearby, but the route to it feels indirect.   A mixed-use scheme may look compact in plan, but key destinations still feel disconnected in practice.   A district may have the right components, but the walking environment between them is exactly where the access strategy starts to come apart. That rarely comes down to one major failure. More often, it is the cumulative effect of smaller decisions, such as: • a crossing placed for traffic flow rather than the desire line   • a route that is technically available, but not obvious at first glance   • active frontage giving way to dead edges at exactly the wrong point   • directness traded away to protect servicing, parking, or vehicular convenience   • comfort and perceived safety treated as secondary to movement efficiency elsewhere In earlier posts in this series, I wrote about mobility being shaped under pressure and resolved through trade-offs. Walkability sits inside both. Because pedestrian environments do not usually fail through lack of infrastructure alone.   They fail when directness, crossings, legibility, and comfort are repeatedly traded away in favour of other priorities. That is what makes walkability more than a public realm question. It is also a question of hierarchy. Who is being given priority in the space?   What kind of movement is being protected?   And at what point does walking stop shaping the scheme and start adjusting to decisions already made? That matters because what happens on foot is not separate from the rest of the mobility strategy. It affects whether interchange feels straightforward or awkward.   Whether short distances remain competitive with being dropped at the door.   Whether access feels integrated, or simply pieced together afterwards. You can improve connectivity.   You can strengthen public transport provision.   You can refine operations. But if walking conditions are weak, the cost shows up elsewhere. Journeys feel longer than they are.   Interchange feels less intuitive than it should.   And the gap between technical connectivity and real usability becomes much harder to close. So the question is not whether walkability matters. It is whether it is being taken seriously early enough to shape the scheme, rather than being left to deal with the consequences of decisions already made. That is often the difference between a place that is connected   and a place that is genuinely easy to access. ⸻ 👉🏻 In your experience, what tends to be traded away first in walkability: directness, crossing priority, legibility, or perceived safety? ⸻ This is the seventh post in Thinking Mobility, a weekly exploration of how mobility shapes cities.

How to Understand the Game Through Space: A New Model to Analyze Offensive and Defensive Efficiency in Football ⚽️📊 At the Football Intelligence & Performance Area of LALIGA, we’ve developed a model that combines advanced tactical analysis tools like the partial convex hull, Voronoi diagrams, and the collective centroid. While these may sound technical, their practical applications can revolutionize how we understand and train the game. Let me break it down for you. 🎯 3 practical takeaways for your day-to-day coaching: 1️⃣ The intersection zone: where matches are won (or lost). This is the most vulnerable defensive area and the most exploitable for the attack, especially in the finalization phase. We analyze: 📐 Zone size (m²): Is it well-protected? 🧍♂️ Number of attackers in the zone: How many rivals are influencing this space? 👉 Practical use: Design drills to enhance vertical passes, breaking movements, and defensive actions to minimize opponent impact in this key area. 2️⃣ The centroid: your team’s balance or imbalance. By comparing the centroid of the entire block with that of two lines (partial convex hull), we identify: - Depth imbalances: Is the team too stretched? - Width issues: Is the team well-positioned in attack or defense? 👉 Practical use: Adjust your defensive compactness or offensive width based on ball movement and match context. 3️⃣ Voronoi areas: measuring player involvement in both phases. a) Forwards in defense: We evaluate their pressing and space occupation based on whether the team defends with a high, mid, or low block. b) Full-backs in attack: We measure their influence and space usage in wide channels. 👉 Practical use: Focus on aggressive pressing by forwards or train full-backs to exploit width and maintain defensive balance in transitions. 🧠 Why does this matter? This model not only helps us understand how teams occupy space but also improves training and strategy. From fine-tuning movements within the block to making real-time tactical decisions, space is as valuable as the ball itself. ⚡️ 👉 For more details, visit the full article here: https://lnkd.in/d68AmSTv #FootballAnalysis #TacticalInsights #SportsScience #LaLiga #CoachingTools #FootballIntelligence #DataDrivenDecisions ⚽️📊

🧪Engineering Focus: Pipe Sizing & Pressure Drop Calculations 🌡️ Accurate pipe sizing is critical to achieving optimal flow, minimizing pressure loss, and reducing energy consumption in fluid systems. Here’s a streamlined guide with key technical formulas and considerations every engineer should know: 1. Define Flow Rate (Q) Use process data or equipment specifications Common units: m³/hr (cubic meters per hour) LPM (liters per minute) GPM (gallons per minute) 2. Select Design Velocity (V) Recommended velocity ranges (depends on fluid type and application): Water: 1 – 3 m/s Oil: 1 – 2 m/s Steam (low pressure): 20 – 35 m/s Compressed air: 10 – 20 m/s 3. Estimate Pipe Diameter (D) Use the continuity equation: Formula: D = √(4 × Q) / (π × V) Where: D = pipe inner diameter (m) Q = volumetric flow rate (m³/s) V = velocity (m/s) Tip: Convert Q to m³/s if originally in m³/hr or LPM before using this formula. 4. Calculate Pressure Drop (ΔP) Apply the Darcy-Weisbach equation for head loss due to friction: Formula: ΔP = f × (L / D) × (ρ × V² / 2) Where: ΔP = pressure drop (Pa) f = Darcy friction factor (use Moody chart or Colebrook equation) L = pipe length (m) D = pipe diameter (m) ρ = fluid density (kg/m³) V = velocity (m/s) 5. Account for Minor Losses Include pressure losses due to bends, tees, valves, etc. Formula: ΔP_total = ΔP_friction + Σ(K × ρ × V² / 2) Where: K = loss coefficient for each fitting Use standard tables for K-values 🔍Engineering Insight: Oversized pipes = higher material cost, but lower energy loss Undersized pipes = higher velocity, more friction, higher pumping power Smart sizing is about optimizing both CAPEX and OPEX 💬 Have you ever had to redesign a system because the pressure drop exceeded expectations? Let’s connect and exchange ideas on how to get it right the first time! #PipeSizing #PressureDrop #DarcyWeisbach #FluidDynamics #MechanicalEngineering #ProcessDesign #HydraulicCalculations #PipingDesign #EngineeringPrinciples #LinkedInEngineering

What can we learn about communication from a Lego instruction manual? If you’ve ever built a set from the LEGO Group, you know the manuals are almost entirely visual. No long explanations. Just step-by-step images guiding you forward. Before a designer ever creates those instructions, they spend at least a year immersing themselves in their audience. They study what a five-year-old can do versus a ten-year-old. What frustrates them. What excites them. What feels intuitive. Only after that deep understanding do they craft the story of how the bricks come together. Now, here’s the twist that really excites me: Lego builds emotion into their manuals. If every page required the same number of pieces and the same effort, it would get boring quickly. Instead, they vary the experience. Some steps are quick wins. Others are more complex. You feel progress. You feel challenge. You feel momentum. There’s a lesson here for all of us. 1) Relevance: Do the research. Understand your audience before you craft your message. 2) Emotion: Even practical information can create anticipation and small victories. Use “you.” Use “we.” Bring people into the story so they experience it. That’s how you build communication that connects, brick by brick. 🧱

𝗛𝗮𝘃𝗲 𝘆𝗼𝘂 𝗲𝘃𝗲𝗿 𝘄𝗮𝗹𝗸𝗲𝗱 𝗶𝗻𝘁𝗼 𝗮 𝗿𝗼𝗼𝗺 𝗮𝗻𝗱 𝘁𝗵𝗼𝘂𝗴𝗵𝘁, " 𝗧𝗵𝗶𝘀 𝘀𝗽𝗮𝗰𝗲 𝗰𝗼𝘂𝗹𝗱 𝗱𝗼 𝘀𝗼 𝗺𝘂𝗰𝗵 𝗺𝗼𝗿𝗲 "❓ That's the magic of creativity in modern furniture design, It's not just about assembling materials, it’s about crafting solutions. When you rethink the obvious, you unlock a world of possibilities. Consider these questions : ➡️ What if a table could transform into a workspace ? ➡️ Can a sofa double as a guest bed ? ➡️ What if your furniture could adapt to your life, rather than the other way around ? This shift in mindset leads to innovative designs that redefine functionality. Creative furniture design breaks the rules and blends form with function, this approach results in : ✅ Space-saving solutions that make even the coziest apartments feel roomy.   ✅ Versatile pieces that adjust to your lifestyle, whether you’re working from home or hosting friends.   ✅ Hidden features that maximize utility, ensuring every inch counts. Whether you live in a tiny studio or a spacious home, the best furniture does more with less, without compromising on style or comfort. But remember, true innovation starts in your mind. Traditional design asks, "What can I build ?"   Creative design asks, "What problem can I solve ?" The future of furniture is adaptive, as our lives change, remote work, smaller spaces, evolving routines, our furniture must keep pace. 𝗦𝗼, 𝗵𝗼𝘄 𝘄𝗶𝗹𝗹 𝘆𝗼𝘂 𝗿𝗲𝘁𝗵𝗶𝗻𝗸 𝘆𝗼𝘂𝗿 𝘀𝗽𝗮𝗰𝗲 𝘁𝗼𝗱𝗮𝘆 ❓

#Multistage_Centrifugal_Pump Multistage Centrifugal Pump A multistage centrifugal pump is a type of pump that uses two or more impellers (stages) to increase the pressure of a fluid. Each stage adds energy to the fluid, making it suitable for high-pressure applications like boiler feedwater, water supply, and oil refining. --- How It Works: 1. Fluid Entry: Fluid enters the pump through the suction inlet into the first stage impeller. 2. Pressure Increase (Staging): The impeller rotates, transferring energy to the fluid and increasing its velocity and pressure. The fluid then flows into the next stage (another impeller) where the pressure is further boosted. This process repeats for as many stages as needed to achieve the required pressure. 3. Fluid Discharge: After passing through all the stages, the fluid exits the pump at high pressure through the discharge outlet. --- Key Parts of a Multistage Centrifugal Pump: 1. Impellers: Multiple impellers in series to boost pressure at each stage. 2. Casing: Houses the impellers and guides the fluid from one stage to the next. 3. Diffuser: Converts velocity into pressure and directs fluid between stages. 4. Shaft: Connects the impellers to the motor for rotation. 5. Bearings: Support the shaft and reduce friction. 6. Seal or Packing: Prevents leakage where the shaft exits the casing. 7. Suction and Discharge Ports: Inlet (suction) and outlet (discharge) points for fluid flow. --- Applications: Boiler feedwater systems. High-pressure cleaning. Reverse osmosis in water treatment. Oil and gas pipeline

Fundamental concepts every Frontend Engineer should know: (They don't really change, even with AI) 1️⃣ Beginner → HTML: semantic HTML and the DOM → CSS fundamentals: cascade, specificity, layout (box model, flex, grid) → JavaScript: common data types, timeouts, async/await, promises → Forms: how to build forms w and w/o JavaScript → Responsive design, CSS media queries → Networking: HTTP, caching, CDNs, HTTP/2, latency mitigation, and cache invalidation strategies 2️⃣ Intermediate → Accessibility: keyboard first, ARIA, screen readers, contrast, focus management → State management: App patterns and predictable component architecture → Component design: composition, props/inputs, pure components, separation of concerns → Media optimization: formats, responsive images, decoding, lazy loading → Browser basics: rendering engines, repaint vs reflow, layout thrashing → Rendering strategies: CSR, SSR, SSG, etc → Fonts: loading strategies, fallback stacks, and layout shift considerations → Testing strategies: unit, integration, visual, and end-to-end tests, plus testability practices → Deployment basics: static hosting, edge vs origin, cache lifetimes, invalidation recipes 3️⃣ Advanced → Build systems and module formats: bundlers, tree-shaking, code-splitting → Security basics: XSS, CSRF, CSP, secure headers and safe handling of user input → Privacy and permissions: cookies, storage, same-site rules, and browser permission prompts → Offline first-patterns: service workers, PWAs, and indexedDB basics → Internationalization: i18n / l10n approaches, pluralization, date/number formats → Maintainable CSS: utility vs component styles, BEM, CSS-in-JS tradeoffs, atomic CSS → Performance: Critical rendering path and performance optimization, including paint, layout, and compositing → Design systems: Building and maintaining design systems and UI components for the web 4️⃣ Expert → Local-first systems: Offline-parity, CRDTs, and optimistic replication → Front end tooling: Monorepo orchestration, AST transformations, and custom build pipelines → Server-driven UI: JSON-defined layouts, dynamic orchestration, and cross-platform consistency → Microfrontends: Decoupled deployments, module federation, and runtime integration → WebGL / WebGPU: Shaders, hardware acceleration, and high-performance rasterization → WASM: Polyglot execution, near-native performance, and memory management → Browser internals: V8 optimization, event loop deep-dives, and rendering engine mechanics. What else would you add? ——— ♻ Repost to help others discover 📕 Save the post so you don't miss it 💡 Follow me Yangshun Tay and my company GreatFrontEnd for more