Engineering Design Process Steps

🔬 How To Run UX Research In B2B and Enterprise. Practical techniques of what you can do in strict environments, often without access to users. 🚫 Things you typically can’t do 1. Stakeholder interviews ← unavailable 2. Competitor analysis ← not public 3. Data analysis ← no data collected yet 4. Usability sessions ← no users yet 5. Recruit users for testing ← expensive 6. Interview potential users ← IP concerns 7. Concept testing, prototypes ← NDA 8. Usability testing ← IP concerns 9. Sentiment analysis ← no media presence 10. Surveys ← no users to send to 11. Get support logs ← no security clearance 12. Study help desk tickets ← no clearance 13. Use research tools ← no procurement yet ✅ Things you typically can do 1. Focus on requirements + task analysis 2. Study existing workflows, processes 3. Study job postings to map roles/tasks 4. Scrap frequent pain points, challenges 5. Use Google Trends for related search queries 6. Scrap insights to build a service blueprint 7. Find and study people with similar tasks 8. Shadow people performing similar tasks 9. Interview colleagues closest to business 10. Test with customer success, domain experts 11. Build an internal UX testing lab 12. Build trust and confidence first In B2B, people buying a product are not always the same people who will use it. As B2B designers, we have to design at least 2 different types of experiences: the customer’s UX (of the supplier) and employee’s UX (of end users of the product). In customer’s UX, we typically work within a highly specialized domain, along with legacy-ridden systems and strict compliance and security regulations. You might not speak with the stakeholder, but rather company representatives — who regulate the flow of data they share to manage confidentiality, IP and risk. In employee’s UX, it isn’t much better. We can rarely speak with users, and if we do, often there is only a handful of them. Due to security clearance limitations, we don’t get access to help desk tickers or support logs — and there are rarely any similar public products we could study. As H Locke rightfully noted, if we shed the light strongly enough from many sources, we might end up getting a glimpse of the truth. Scout everything to see what you can find. Find people who are the closest to your customers and to your users. Map the domain and workflows in service blueprints and . Most importantly: start small and build strong relationships first. In B2B and Enterprise, most actors are incredibly protective and cautious, often carefully manoeuvring compliance regulations and layers of internal politics. No stones will be moved unless there is a strong mutual trust from both sides. It can be frustrating, but also very impactful rewarding. In B2B, people often can’t choose what they use and desperately need help to do their work better — and that’s exactly where designers step in, and can make a whole difference for people who rely on our work every day.

Your research findings are useless if they don't drive decisions. After watching countless brilliant insights disappear into the void, I developed 5 practical templates I use to transform research into action: 1. Decision-Driven Journey Map Standard journey maps look nice but often collect dust. My Decision-Driven Journey Map directly connects user pain points to specific product decisions with clear ownership. Key components: - User journey stages with actions - Pain points with severity ratings (1-5) - Required product decisions for each pain - Decision owner assignment - Implementation timeline This structure creates immediate accountability and turns abstract user problems into concrete action items. 2. Stakeholder Belief Audit Workshop Many product decisions happen based on untested assumptions. This workshop template helps you document and systematically test stakeholder beliefs about users. The four-step process: - Document stakeholder beliefs + confidence level - Prioritize which beliefs to test (impact vs. confidence) - Select appropriate testing methods - Create an action plan with owners and timelines When stakeholders participate in this process, they're far more likely to act on the results. 3. Insight-Action Workshop Guide Research without decisions is just expensive trivia. This workshop template provides a structured 90-minute framework to turn insights into product decisions. Workshop flow: - Research recap (15min) - Insight mapping (15min) - Decision matrix (15min) - Action planning (30min) - Wrap-up and commitments (15min) The decision matrix helps prioritize actions based on user value and implementation effort, ensuring resources are allocated effectively. 4. Five-Minute Video Insights Stakeholders rarely read full research reports. These bite-sized video templates drive decisions better than documents by making insights impossible to ignore. Video structure: - 30 sec: Key finding - 3 min: Supporting user clips - 1 min: Implications - 30 sec: Recommended next steps Pro tip: Create a library of these videos organized by product area for easy reference during planning sessions. 5. Progressive Disclosure Testing Protocol Standard usability testing tries to cover too much. This protocol focuses on how users process information over time to reveal deeper UX issues. Testing phases: - First 5-second impression - Initial scanning behavior - First meaningful action - Information discovery pattern - Task completion approach This approach reveals how users actually build mental models of your product, leading to more impactful interface decisions. Stop letting your hard-earned research insights collect dust. I’m dropping the first 3 templates below, & I’d love to hear which decision-making hurdle is currently blocking your research from making an impact! (The data in the templates is just an example, let me know in the comments or message me if you’d like the blank versions).

While it can be easily believed that customers are the ultimate experts about their own needs, there are ways to gain insights and knowledge that customers may not be aware of or able to articulate directly. While customers are the ultimate source of truth about their needs, product managers can complement this knowledge by employing a combination of research, data analysis, and empathetic understanding to gain a more comprehensive understanding of customer needs and expectations. The goal is not to know more than customers but to use various tools and methods to gain insights that can lead to building better products and delivering exceptional user experiences. ➡️ User Research: Conducting thorough user research, such as interviews, surveys, and observational studies, can reveal underlying needs and pain points that customers may not have fully recognized or articulated. By learning from many users, we gain holistic insights and deeper insights into their motivations and behaviors. ➡️ Data Analysis: Analyzing user data, including behavioral data and usage patterns, can provide valuable insights into customer preferences and pain points. By identifying trends and patterns in the data, product managers can make informed decisions about what features or improvements are most likely to address customer needs effectively. ➡️ Contextual Inquiry: Observing customers in their real-life environment while using the product can uncover valuable insights into their needs and challenges. Contextual inquiry helps product managers understand the context in which customers use the product and how it fits into their daily lives. ➡️ Competitor Analysis: By studying competitors and their products, product managers can identify gaps in the market and potential unmet needs that customers may not even be aware of. Understanding what competitors offer can inspire product improvements and innovation. ➡️ Surfacing Implicit Needs: Sometimes, customers may not be able to express their needs explicitly, but through careful analysis and empathetic understanding, product managers can infer these implicit needs. This requires the ability to interpret feedback, observe behaviors, and understand the context in which customers use the product. ➡️ Iterative Prototyping and Testing: Continuously iterating and testing product prototypes with users allows product managers to gather feedback and refine the product based on real-world usage. Through this iterative process, product managers can uncover deeper customer needs and iteratively improve the product to meet those needs effectively. ➡️ Expertise in the Domain: Product managers, industry thought leaders, academic researchers, and others with deep domain knowledge and expertise can anticipate customer needs based on industry trends, best practices, and a comprehensive understanding of the market. #productinnovation #discovery #productmanagement #productleadership

🌞 How I Designed a 15kW Hybrid Solar PV System (Step by Step) Designing a solar PV system isn’t just about choosing panels and batteries. It requires a structured approach that ensures the system meets real energy needs while staying efficient and reliable. Here’s the process I followed for my recent 15kW Hybrid Solar PV system design: 1️⃣ Energy Audit – I collected data on appliances, their wattages, and usage hours. This helped determine the daily energy requirement and peak load demand. 2️⃣ Site Survey – I assessed the location for roof/ground space, orientation, tilt angle, shading, and cable run distances. This ensures the design is practical and site-specific. 3️⃣ Data Processing in Excel – Using my customized Excel program, I analyzed the data to calculate energy consumption and accurately size the system. 4️⃣ Component Sizing – Based on the results, I sized the PV modules, inverter, battery bank, and charge controller to match the client’s demand. 5️⃣ System Design in AutoCAD – I created the schematic diagram, mapping out PV modules, inverter, batteries, and protection devices for clarity and implementation. 6️⃣ Simulation in PVsyst – Finally, I tested the design with PVsyst to validate system performance, efficiency, and real-world output. 💡 This process ensures the system is not just technically sound but also optimized for long-term performance and cost-effectiveness. ✅ By combining technical analysis, site assessment, and simulation software, I can deliver solar solutions that are reliable, sustainable, and tailored to client needs. 👉 Would you like me to break down one of these steps in detail in my next post? 📩 If you’re interested in a customized solar solution for your home, business, or project, feel free to reach out.

⚡ Utility-Scale Solar PV Power Plant – EPC & Grid Training Overview ⚡ Designing and executing a utility-scale solar PV plant is not just about installing modules; it’s about engineering the complete power flow from DC generation to grid synchronisation. This visual breaks down the end-to-end EPC & utility perspective of a solar PV power plant, exactly how engineers, DISCOMs, and utilities evaluate projects. 🔹 What this overview covers: 🔸 Solar PV Generation (DC Side): PV modules convert solar irradiation into DC power; performance depends on layout, tilt, temperature, and soiling control. 🔸 String & Combiner Architecture: Proper string sizing, protection, and combiner design ensure safety, reduced mismatch losses, and ease of maintenance. 🔸 Inverter System (DC → AC): Inverters act as the brain of the plant — managing MPPT, grid synchronization, harmonics, and protection compliance. 🔸 AC Collection & Protection: Well-engineered LT panels, earthing, and protection coordination are critical for plant reliability and fault isolation. 🔸 Step-Up Transformer & Evacuation: Voltage is stepped up to evacuation level (11/33/66 kV) to minimize losses during power export. 🔸 Switchyard & Grid Interfacing: Grid compliance systems including relays, CT/PTs, isolators, and breakers ensure utility-approved power injection. 🔸 Transmission / DISCOM Network: Power flows into the utility network following grid codes, evacuation limits, and scheduling norms. 🔸 SCADA, Metering & Monitoring: Real-time monitoring of MW, voltage, frequency, CUF, alarms, and performance ratios ensures bankability and grid trust. 📌 Why this matters for EPC & utilities: ✔ Better design = fewer losses ✔ Compliance = smoother approvals ✔ Monitoring = higher plant availability ✔ Engineering clarity = long-term asset performance Good solar EPC execution is about engineering discipline, grid compatibility, and lifecycle performance, not just MW installation.

Designing & Selecting the AC/LV Side of a Solar System ⚡ Proper selection of switchgear, cables, earthing, and protection on the AC/LV side of a solar system ensures efficiency, safety, and compliance with electrical standards. Here’s a breakdown of key considerations: 🔹 1. Switchgear Selection (AC Panels & Breakers) ✅ Voltage Rating: Matches system LV output (typically 400V AC 3-phase or 230V single-phase). ✅ Current Rating: 125%-150% of inverter AC output. ✅ Breaking Capacity: Withstands maximum fault current (e.g., 10kA–50kA). ✅ Types of Breakers: 🔸 MCBs – Small loads & distribution panels. 🔸 MCCBs – Main AC distribution & large inverters. 🔸 AC Isolators – Safe inverter disconnection. 🔸 Contactors & Relays – Automation & remote shutdown. 🔹 2. AC Cable Sizing & Selection ✅ Voltage Rating: 600/1000V LV or 1.8/3kV near transformers. ✅ Current Carrying Capacity: Choose based on ampacity & heat dissipation. ✅ Derating Factors: Consider temperature, grouping & burial method. ✅ Voltage Drop: Should be ≤1.5% from inverter to point of connection. ✅ Cable Type: 🔸 XLPE-insulated copper/aluminum cables for heat resistance. 🔸 Armored (SWA/AWA) cables for underground use. 🔸 Flexible cables for panel connections. 📌 Example: For a 100kW inverter (3-phase, 400V, 145A), 50mm² copper cable is typically required (based on ampacity & voltage drop limits). 🔹 3. Earthing & Grounding System ✅ System Earthing: TN-S, TN-C-S, TT, or IT (as per grid codes). ✅ Equipment Earthing: 🔸 Inverter frames, mounting structures & AC panels (≥16mm² Cu or ≥25mm² Al). ✅ Surge Protection Earthing: Separate earth pits, ≤5Ω resistance recommended. ✅ Earthing Conductors: ≥25mm² Cu for main earth connections. 🔹 4. Protection System (SPDs, RCDs & Overcurrent Protection) ✅ Surge Protection Devices (SPDs): 🔸 Type 1 – Lightning protection (if direct strikes possible). 🔸 Type 2 – General surge protection (for inverters & switchgear). 🔸 Type 3 – Local protection for sensitive electronics. ✅ Residual Current Devices (RCDs): 🔸 30mA – Personal safety. 🔸 100mA–300mA – Fire protection. ✅ Overcurrent Protection: MCCBs/MCBs sized at 1.25x inverter AC current. ✅ Anti-islanding Protection: Ensures grid safety by disconnecting during outages. 🔹 5. Compliance & Standards 🔸 IEC 60364 – Electrical Installations (LV systems). 🔸 IEC 60947 – Switchgear & controlgear. 🔸 IEC 61643 – Surge protection devices. 🔸 IEC 62477 – Safety of power electronics. 🔸 Local utility/grid codes for interconnection. 💡 Conclusion Selecting the right AC side components ensures: ✅ Safe & efficient power distribution ✅ Compliance with electrical standards ✅ Reliable protection against faults & surges #SolarEnergy #ElectricalDesign #RenewableEnergy #ACSide #SolarEngineering #SustainableTech

Practical end-to-end execution flow of a Solar Power Project (Ground-Mounted / PM-KUSUM / Utility Scale) — exactly how it runs at site level 👇 1️⃣ Project Kick-off & Pre-Execution LOA / PPA signing Site handover & boundary confirmation Topographical survey & soil investigation Grid feasibility & interconnection approval Project execution plan (timeline, manpower, machinery) 2️⃣ Engineering & Design Plant capacity finalization (DC/AC ratio) Layout design (string layout, inverter placement) Structural design (pile / foundation) Cable sizing & derating (DC, AC, HT) Earthing & lightning protection design SLD, GA drawings, BOM finalization 3️⃣ Statutory Approvals CEIG / Electrical Inspector approval DISCOM approval (net-metering / evacuation) Panchayat / land related NOCs (if applicable) PM-KUSUM specific approvals (if applicable) 4️⃣ Procurement & Logistics Solar modules Inverters (string / central) MMS structures DC / AC / HT cables Transformer, RMU, HT panel Earthing & lightning materials Logistics planning & material inspection (IRN) 5️⃣ Civil Works Execution Site clearing & leveling Internal roads & drainage Pile driving / foundation casting Inverter room / control room civil work Transformer & HT yard foundations 6️⃣ MMS Installation Structure alignment & leveling Torque tightening & marking Row-to-row & tilt angle verification Structure earthing continuity 7️⃣ Module Installation Module unloading & inspection Module mounting on MMS Clamp torque as per OEM Module serial number mapping 8️⃣ DC Electrical Works String formation DC cable laying (tray / trench) Proper routing & dressing DC connector crimping & polarity check DCDB installation (if applicable) 9️⃣ AC Electrical Works Inverter installation AC cable laying (inverter to LT panel) Transformer installation LT & HT panel installation HT cable laying & termination 🔟 Earthing & Lightning Protection Earth pit construction Equipment earthing (module, MMS, inverter, transformer) Lightning arrestor installation Earth resistance measurement 1️⃣1️⃣ Testing & Commissioning (T&C) DC insulation resistance (Megger test) AC cable megger & continuity test Inverter pre-commissioning checklist Transformer testing (IR, ratio, vector group) Protection relay settings Grid synchronization 1️⃣2️⃣ CEIG / DISCOM Inspection Submission of test reports Site inspection by authority Observation closure (if any) Charging permission 1️⃣3️⃣ Final Commissioning & Handover Trial run Performance verification As-built drawings O&M manuals Final handover to client 1️⃣4️⃣ Operation & Maintenance (O&M) Daily generation monitoring Module cleaning Preventive maintenance Breakdown maintenance Monthly & yearly performance reports 🔑 Key Execution Focus Areas ✔ Safety (PTW, PPE, LOTO) ✔ Quality checklists at each stage ✔ Documentation & records ✔ Coordination with DISCOM & CEIG

🔆 Best Way to Detail a Solar PV System Using PVsyst + ETAP + AutoCAD 1️⃣ Start with PVsyst – Energy & Concept Design 👉 Think: performance first, drawings later • Site & meteo data • Module–inverter selection • String sizing & losses • Shading analysis • Annual energy yield (kWh) 📌 Output used for detailing: • DC/AC ratio • No. of strings & modules • Cable loss assumptions • Inverter ratings ⸻ 2️⃣ Validate Electrically with ETAP – Engineering Reality Check 👉 This is where designs become engineer-proof • Load flow (AC side) • Short circuit & breaker sizing • Cable sizing (ampacity + voltage drop) • Protection coordination • Earthing & grounding checks 📌 Output used for detailing: • Exact cable sizes • Breaker ratings • Protection philosophy • Fault levels for SLD ⸻ 3️⃣ Detail Everything in AutoCAD – Construction-Ready Drawings 👉 This is what EPC & site teams trust Must-have drawings: • PV module layout (rooftop / ground mount) • String routing diagram • DC combiner box (DCDB) layout • Inverter & ACDB layout • Earthing & lightning protection layout • Single Line Diagram (from ETAP logic) 📌 Pro tip: Always match AutoCAD tags with PVsyst & ETAP names (e.g., INV-01, SCB-02, STR-15) ⸻ 🔁 Best Practice Workflow (Golden Rule) PVsyst → ETAP → AutoCAD → Feedback loop If ETAP changes cable or breaker size → 🔄 update AutoCAD 🔄 re-check losses in PVsyst ⸻ ⚠️ Common Mistakes to Avoid ❌ Beautiful layouts with wrong cable sizing ❌ PVsyst report not matching SLD ❌ Ignoring fault levels from inverter contribution ❌ Earthing shown but not calculated #SolarPV #PVsyst #ETAP #AutoCAD #SolarEngineering #PVDesign #RenewableEnergy #ElectricalEngineering #EPC #SolarLinkedIn

After 10,000 hours of user research, here's everything I've learned distilled into 9 key takeaways (that you can start applying today): 1. User research is the best insurance policy you’ll ever invest in. The earlier you research, the less risk you take on. - For every $1 spent fixing an issue during development, it costs $10 to fix in production. - Early insights save time, money, and reputation. 🔗 https://lnkd.in/eJVPUkBe 2. If no one is acting on your research, the problem isn’t them—it’s you. Insights only matter if they drive change. Here’s a simple formula to make your findings actionable: 1. Problem: What’s broken? 2. Impact: What’s the cost (time, money, frustration)? 3. Solution: What’s the fix? Stakeholders don’t ignore clarity. 🔗 https://lnkd.in/eBu7KEyG 3. Users often don’t know what they need—and that’s okay. Users are great at describing problems, but rarely solutions. - Don’t ask them what they want—ask what’s frustrating them, what workarounds they use, and how they solve problems today. 🔗 https://lnkd.in/eVBvDr9c 4. Pain points are treasure maps—follow them. Every time a user struggles, they’re handing you an opportunity to improve. - A client discovered users were copy-pasting passwords to log in. The fix? A password manager integration that reduced churn by 30%. The bigger the pain, the bigger the potential win. 5. Forget about tools—master the basics first. Fancier software won’t make you better at understanding your users. - A Google Doc and sticky notes can uncover world-changing insights. - Focus on asking the right questions, not which tool to use. 🔗 https://lnkd.in/eqhy3Tzr 6. The best insights come early—before anyone’s built anything. The most expensive mistakes happen when you skip research in the ideation phase. - Don’t wait for prototypes. Get in the field, talk to users, and validate assumptions before anyone writes a line of code. - Early research saves late regrets. 🔗 https://lnkd.in/ecBReAW8 7. Your stakeholders don’t care about “findings”—they care about results. Your report isn’t the product—impact is. Tie every insight to a business metric: - Churn? Reduced. - Revenue? Increased. - Efficiency? Improved. When insights = results, you’ll never struggle for buy-in again. 🔗 https://lnkd.in/eAzkpxub 8. Your job isn’t just to research—it’s to align teams. Most UX problems are rooted in misaligned goals, not bad designs. Use research as a bridge between teams: - Show designers, PMs, and engineers what users actually need (and what they don’t). Alignment creates momentum—and better outcomes. 🔗 https://lnkd.in/e3wyQr25 9. Good research challenges assumptions. If your findings aren’t making people uncomfortable, you’re playing it too safe. Dig deeper. Push harder. The most powerful insights don’t validate—they transform. Image via Midjourney

💡 Mapping user research techniques to levels of knowledge about users When doing user research, it's important to choose the right methods and tools to uncover valuable insights about user behavior. It's possible to identify 3 layers of user behavior, feelings, and thoughts: 1️⃣ Surface level - Say & Think This level captures what users say in conversations, interviews, or surveys and what they think about a product, feature, or experience. It reflects their stated opinions, thoughts, and intentions. Example: "I prefer simple products" or "I think this app is easy to use." Methods: Interviews, Questionnaires. These methods capture stated thoughts and opinions. However, insights may be influenced by social norms or biases. 2️⃣ Mid-level - Do & Use This level reflects what users actually do when interacting with a product or service. It emphasizes actions, usage patterns, and observed behaviors, revealing insights that may differ from what users say. Example: Users may claim they enjoy customizing app settings, but data shows they rarely change default options. Methods: Usability Testing, Observation. Observation helps to reveal gaps between what people say and what they actually do. 3️⃣ Deep level - Know, Feel and Dream This level uncovers deep motivations, emotions, desires, and aspirations that users may not be consciously aware of or may struggle to articulate. It also includes tacit knowledge—things people know intuitively but find hard to express. Example: A user might not realize that their preference for a minimalist design comes from the information overload of a current design. Methods: Probes (e.g., participatory design, diary studies). Insights collected using these methods will uncover implicit and emotional drivers influencing behavior. 📕 Practical recommendations for mapping ✅ Triangulate insights by using multiple methods. What people say (interviews/surveys) may differ from what they do (observations) and feel. That's why it's essential to interpret these results in context. For example, start with interviews to learn what users say. Follow up with usability testing to observe real behavior. Use probes for long-term or emotional insights. ✅ Align research with business goals. For product improvements, focus on usability testing to catch interaction issues. For innovation, use probes to generate new ideas from user insights. ✅ Practice iterative learning. Apply surface techniques (like surveys) early to refine assumptions and guide more in-depth research later. Use deep techniques (like probes) for strategic decisions and to foster innovation in long-term projects. 🖼️ UX Research methods by Maze #ux #uxresearch #design #productdesign #uxdesign #ui #uidesign