Enhancing Interdepartmental Design Communication

Design teams talk about product accessibility. Almost never team accessibility. “I need time to process before giving feedback.” That’s something I’ve heard more than once in design teams. It’s often followed by comments like: “I keep forgetting what we discussed.” “These emails are overwhelming.” At first, these can sound like performance issues. But sometimes they’re actually cognitive accessibility barriers. In the way teams communicate. Long emails with buried action items. Meetings with no written recap. Design reviews where feedback has to happen instantly. For people who process information differently, that kind of workflow creates friction. Most people won’t say anything. They’ll just work twice as hard to keep up. A few small changes can make a big difference: 1. Write decisions down Capture key points in a shared doc or Slack thread instead of relying on memory. 2. Put action items first TL;DR at the top. Tasks in bullet points. Context below. 3. Allow async feedback Not everyone processes ideas in real time. Figma comments or Slack feedback after the meeting works better. These are cognitive accessibility practices that benefit everyone. Designers spend a lot of time improving accessibility in products. It’s worth asking: How accessible are the systems we use to work together? What small change improved communication on your team? 👇🏽 Drop your answers in the comments. ♻️ Share and save this for your team. — ✉️ Subscribe to my newsletter for accessibility and design insights here: https://lnkd.in/gZpAzWSu — Accessibility note: The content of the attached image is included in this post for screen reader users.

A client asked: "Should product managers join design reviews so they can give better context to engineers?" I thought about this early in my career. Then I did the math. There literally weren't enough hours in the day to be a successful PM if I kept playing telephone. The model was fundamentally broken. The go-between model creates hidden costs My client was dealing with a pattern I see everywhere: An engineer misunderstands a UX flow. The PM spends hours playing telephone. The designer waits on feedback. Meanwhile, the sprint drags on. He asked: "Should PMs join design reviews to provide better context?" But that's treating the symptom, not the disease. The real question: "Why aren't designers and engineers talking directly?" 🪤 The go-between trap I've seen this pattern at over a dozen companies. When PMs become translators, three things happen: • Speed dies. Every conversation that needs to route through PM adds wait time. • Ownership vanishes. Engineers and designers stop feeling responsible for understanding each other. • Context gets diluted. Even the best PM can't capture every nuance. The "why" behind decisions gets lost in translation. You're building fragility into your team structure. If the PM is out sick for three days, you risk the whole system falling apart. 🔧 The real fix Don't add PMs to meetings so they can play telephone. Instead, solve the underlying problem: Help designers and engineers communicate directly. Some ways to make this happen: • Create shared rituals where design and engineering collaborate (not just handoffs) • Build communication skills through coaching, not by adding more process • Make sure that designers and engineers are talking in retros about how to improve collaboration. Yes, PMs should participate in design reviews. But as contributors, not translators. The goal isn't perfect handoffs. It's building a team that solves problems together. What communication breakdowns have you seen between design and engineering? And how did you fix them?

Is your process fostering collaboration or creating Siloes? Process design should be about breaking down walls, not building them higher! ️ Why it happens: We create Standard Operating Procedures (SOPs) to streamline work within departments. But focusing solely on department SOP can have unintended impact through the entire value chain. When processes are designed in isolation, departmental SOPs can create problems like: a. Limited visibility and alignment: Teams lose sight of the bigger picture and how their work impacts others downstream. For example, an overly rigid marketing SOP might not consider the impact on sales efforts if it delays the release of essential product information. b. Inefficiency: Departments end up working at odds, creating rework and delays. Imagine an engineering team finalizes a design without proper communication with manufacturing, leading to production delays due to unexpected technical challenges. c. Misaligned goals: Departmental targets might conflict with the overall company objectives. A sales team focused solely on closing deals might push for unrealistic deadlines that compromise product quality, ultimately impacting customer satisfaction. What's the fix? Design processes with the entire value chain in mind. This means considering how each step impacts other departments and contributes to the overall goal. How to do it: 1. Break down the silos: Start the design by focusing on the entire value chain, start to end. Involve different teams in the process design phase. This fosters understanding and collaboration. 2. Map the journey: Visually represent the entire process flow, highlighting interdependencies between departments. This enables greater visibility and leads to better collaboration 3. Focus on the big picture: Clearly define the end goal and how each step contributes to achieving it. Let the value chain translate the same and to all stakeholders how they are contributing to the end goal. By designing cross-functional processes, everyone gains visibility and works towards shared goals. #processdesign #collaboration #breakdownsilos #processexcellence

🏆𝐂𝐨𝐦𝐦𝐮𝐧𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝐢𝐬 𝐍𝐨𝐭 𝐚 𝐒𝐨𝐟𝐭 𝐒𝐤𝐢𝐥𝐥- 𝐢𝐭 𝐢𝐬 𝐚 𝐏𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐯𝐢𝐭𝐲 𝐌𝐮𝐥𝐭𝐢𝐩𝐥𝐢𝐞𝐫 🚀 In my experience managing cross-functional engineering groups of professionals on complex projects within automation, I have learned the following: Lack of communication does not delay projects-it silently kills project performance. On the other hand, improved communication has the power to improve culture and output within a team. Draw on what I have observed in actual environments, here is: 🔹 𝐂𝐥𝐚𝐫𝐢𝐭𝐲 𝐫𝐞𝐝𝐮𝐜𝐞𝐬 𝐜𝐡𝐚𝐨𝐬 When goals, roles, and expectations are clearly communicated, delivery efficiency improves. In one of our projects, structured weekly alignment reduced rework by 20% and improved on-time delivery to 95%. 🔹 𝐎𝐩𝐞𝐧 𝐝𝐢𝐚𝐥𝐨𝐠𝐮𝐞 𝐫𝐞𝐝𝐮𝐜𝐞𝐬 𝐫𝐢𝐬𝐤 Creating a culture where engineers can escalate issues early (without fear) helps identify risks before they become crises. This helped us maintain zero major audit deviations in regulated environments. 🔹 𝐋𝐞𝐚𝐝𝐞𝐫𝐬𝐡𝐢𝐩 𝐬𝐞𝐭𝐬 𝐭𝐡𝐞 𝐜𝐨𝐦𝐦𝐮𝐧𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝐭𝐨𝐧𝐞 Culture does not start with policies, it starts with leadership behavior. When leaders: • Listen actively • Align stakeholders transparently • Communicate trade-offs clearly Teams respond with ownership and accountability. 🔹 𝐂𝐫𝐨𝐬𝐬-𝐟𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐚𝐥 𝐜𝐨𝐦𝐦𝐮𝐧𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝐝𝐫𝐢𝐯𝐞𝐬 𝐢𝐧𝐧𝐨𝐯𝐚𝐭𝐢𝐨𝐧 Engineering, QA, IT, and Operations speaking the same language improves system integration and decision speed. In one digital transformation initiative, strong interdepartmental alignment improved operational efficiency by 35%. 🔹 𝐑𝐞𝐜𝐨𝐠𝐧𝐢𝐭𝐢𝐨𝐧 𝐬𝐭𝐫𝐞𝐧𝐠𝐭𝐡𝐞𝐧𝐬 𝐞𝐧𝐠𝐚𝐠𝐞𝐦𝐞𝐧𝐭 Communication is not only about problems but also about appreciation. Recognizing contributions builds trust and improves retention. 📌 The outcome? 𝐁𝐞𝐭𝐭𝐞𝐫 ��𝐮𝐥𝐭𝐮𝐫𝐞 → 𝐇𝐢𝐠𝐡𝐞𝐫 𝐭𝐫𝐮𝐬𝐭 → 𝐅𝐚𝐬𝐭𝐞𝐫 𝐝𝐞𝐜𝐢𝐬𝐢𝐨𝐧𝐬 → 𝐆𝐫𝐞𝐚𝐭𝐞𝐫 𝐩𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐯𝐢𝐭𝐲. Communication is not about talking more. It is about communicating with structure, intent, and accountability. As leaders, our job is not just to manage tasks. It is to create an environment where people perform at their best. What practices have worked in your teams to strengthen communication and culture? Let us discuss👇 #Leadership #TeamManagement #EngineeringLeadership #OrganizationalCulture #CommunicationMatters #ProjectManagement #IndustrialAutomation #DigitalTransformation #PeopleLeadership #OperationalExcellence #Satishkumar #Automation #UAE #Europe

Enhancing Coordination Between Architectural, Structural, and MEP Models in BIM In a BIM environment, seamless coordination between architectural, structural, and MEP disciplines is critical to reducing clashes, minimizing rework, and ensuring a smooth construction process. However, many projects still suffer from misalignment, inconsistencies, and communication gaps between disciplines. So, how can we improve multidisciplinary BIM coordination? 🔹 1️⃣ Establish a Clear BIM Execution Plan (BEP) ✅ Define roles, responsibilities, and data exchange protocols ✅ Standardize naming conventions, file structures, and modeling guidelines ✅ Set clear Level of Development (LOD) and Level of Information (LOI) requirements 🔹 2️⃣ Implement a Robust Clash Detection Workflow ✅ Use Navisworks, Solibri, or Revit Interference Check to detect conflicts early ✅ Conduct regular coordination meetings to resolve clashes before construction ✅ Categorize clashes into critical, moderate, and minor to prioritize resolutions 🔹 3️⃣ Work with Shared Coordinates for Spatial Accuracy ✅ Ensure all disciplines align to a common coordinate system ✅ Regularly audit models to prevent geometric misalignment ✅ Use a Common Data Environment (CDE) to manage file locations and references 🔹 4️⃣ Optimize Worksharing and Model Linking ✅ Use Worksets and Linked Models efficiently to avoid file overload ✅ Maintain consistent model updates and regularly synchronize with central ✅ Set clear visibility and discipline-specific view templates for clarity 🔹 5️⃣ Improve Cross-Discipline Communication ✅ Foster collaboration between teams rather than working in silos ✅ Schedule regular model coordination reviews at key project milestones ✅ Use BIM Collaboration Tools (e.g., BIM 360, ACC, or Trimble Connect) for real-time issue tracking 📌 Key takeaway: Effective BIM coordination is not just about software—it’s about clear workflows, strong communication, and a shared commitment to accuracy. When all disciplines work in sync, projects benefit from fewer clashes, smoother execution, and improved project efficiency. 👉 How do you handle BIM coordination challenges in your projects? Let’s discuss! ⬇️ #BIM #Coordination #DigitalConstruction #MEP #StructuralEngineering #ArchitecturalBIM #ISO19650 #ClashDetection #CDE #BIMManagement

Architecture is rarely a solo endeavor. Every project involves a web of consultants, engineers, contractors, clients, and internal teams. Yet, as many architects know, true collaboration often feels… elusive. Why? Because even the most talented teams can struggle with: • Misaligned expectations • Poor communication across disciplines • Delays in feedback loops • A focus on individual ownership rather than collective outcomes So how can we improve? 1. Set Clear Shared Goals: Everyone, from the client to the site engineer should understand the same vision. This reduces confusion and aligns decisions with the bigger picture. 2. Establish Communication Protocols: Tools like shared project platforms, regular check-ins, and clear documentation prevent messages from getting lost in translation. 3. Encourage Early Collaboration: Invite consultants and contractors into the process early. The more input upfront, the fewer surprises later. 4. Promote a Culture of Feedback: Constructive, respectful critique improves both designs and relationships. Encourage listening as much as talking. 5. Celebrate Wins Together: A project completed successfully is a team achievement. Acknowledging contributions fosters trust and loyalty. Great architecture isn’t just about drawings, it’s about people working together. When collaboration improves, so does design quality, efficiency, and even the joy of creating. The takeaway? Think of your project team like a choreographed dance: it looks effortless only when everyone moves in sync. The better the collaboration, the smoother the performance.

Key Interfaces between Electrical and Instrumentation Departments in an Oil and Gas EPC Project: Electrical Department 1. Power Distribution: Design and installation of power distribution systems, including switchgear, transformers, and cabling. 2. Motor Control Centers (MCCs): Design, installation, and testing of MCCs for controlling electrical motors. 3. Lighting and Earthing: Design and installation of lighting systems and earthing systems for safety. Instrumentation Department 1. Process Instrumentation: Design, installation, and testing of process instrumentation, including sensors, transmitters, and control valves. 2. Control Systems: Design, installation, and testing of control systems, including programmable logic controllers (PLCs), distributed control systems (DCS), and supervisory control and data acquisition (SCADA) systems. 3. Safety Instrumented Systems (SIS): Design, installation, and testing of SIS for ensuring process safety. Key Interfaces 1. Electrical Power Supply: Electrical department provides power supply to instrumentation equipment, such as transmitters, control valves, and PLCs. 2. Instrumentation Signal Transmission: Instrumentation department transmits signals to electrical equipment, such as MCCs and switchgear, for control and monitoring purposes. 3. Control System Integration: Electrical and instrumentation departments integrate control systems, such as PLCs and DCS, to control and monitor electrical and process systems. 4. Earthing and Bonding: Electrical department ensures earthing and bonding of instrumentation equipment to prevent electrical shock and ensure safety. 5. Cable Routing and Management: Electrical and instrumentation departments collaborate on cable routing and management to ensure safe and efficient installation. 6. Testing and Commissioning: Both departments collaborate on testing and commissioning of electrical and instrumentation systems to ensure safe and efficient operation. Benefits of Effective Interface Management 1. Improved Safety: Ensures safe operation of electrical and instrumentation systems. 2. Increased Efficiency: Optimizes system performance and reduces downtime. 3. Reduced Costs: Minimizes rework and reduces costs associated with errors or omissions. 4. Enhanced Collaboration: Fosters collaboration and communication between electrical and instrumentation departments.

𝗙𝗲𝗲𝗹𝗶𝗻𝗴 𝗹𝗶𝗸𝗲 𝘆𝗼𝘂𝗿 𝘁𝗲𝗮𝗺𝘀 𝗮𝗿𝗲 𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝗶𝗻 𝘀𝗶𝗹𝗼𝘀?   𝗧𝗵𝗶𝘀 𝗰𝗼𝗺𝗺𝗼𝗻 𝗶𝘀𝘀𝘂𝗲 𝗰𝗮𝗻 𝗲𝗶𝘁𝗵𝗲𝗿 𝗽𝗿𝗼𝗽𝗲𝗹 𝘆𝗼𝘂𝗿 𝗰𝗮𝗿𝗲𝗲𝗿 𝗼𝗿 𝘀𝘁𝗮𝗹𝗹 𝗶𝘁 𝗰𝗼𝗺𝗽𝗹𝗲𝘁𝗲𝗹𝘆.   Here are 6 proven, actionable strategies to break down those barriers and build a more connected, collaborative organization—starting today.   Corporate silos are when there are alternate departments that don't communicate.   It happens to all companies, despite their efforts.   As a manager, your ability to navigate these interdepartmental relationships can make your career. 🧭   Or doom it.   𝗛𝗲𝗿𝗲 𝗮𝗿𝗲 6 𝘄𝗮𝘆𝘀 𝘁𝗼 𝗯𝗿𝗲𝗮𝗸 𝗱𝗼𝘄𝗻 𝘁𝗵𝗼𝘀𝗲 𝘀𝗶𝗹𝗼𝘀 𝘀𝘁𝗮𝗿𝘁𝗶𝗻𝗴 𝘁𝗼𝗱𝗮𝘆.   1 - 𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗲 𝘁𝗵𝗲 𝗱𝗲𝗽𝗮𝗿𝘁𝗺𝗲𝗻𝘁𝘀 ✅Have your team connect with the team they work with. 💡In sales? Talk to the installers or fulfillment team.   2 - 𝗘𝗻𝗰𝗼𝘂𝗿𝗮𝗴𝗲 𝗮 𝗰𝘂𝗹𝘁𝘂𝗿𝗲 𝗼𝗳 𝗿𝗲𝗰𝗼𝗴𝗻𝗶𝘁𝗶𝗼𝗻. ✅Have your team send thank-you notes and copy the manager. You start this. 💡Have an install or order go well? Let them know you appreciate them.   3 - 𝗣𝗿𝗼𝘃𝗶𝗱𝗲 𝗰𝗮𝗿𝗲𝗲𝗿 𝗮𝗻𝗱 𝗷𝗼𝗯 𝗰𝗹𝗮𝗿𝗶𝘁𝘆. ✅You and your team engage with the other team for shadowing or ride along. 💡Pair up your team with a counterpart from the other department for 1/2 day and vise versa.   4 - 𝗣𝗿𝗼𝘃𝗶𝗱𝗲 𝗮𝗰𝗰𝗲𝘀𝘀 𝗮𝗻𝗱 𝘃𝗶𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆. ✅Have the leader of another department cover a topic on each of your team calls. 💡Have a promotion from the sales team? Have the sales manager teach it out on your call.   5 - 𝗔𝗹𝘄𝗮𝘆𝘀 𝗲𝘅𝗽𝗹𝗮𝗶𝗻 𝘁𝗵𝗲 𝘄𝗵𝘆. ✅When explaining what you do, also explain why you do it. 💡Have a longer process for fulfillment because of compliance? Explain that to the sales team.   6 - Ask how you can help. ✅A great partnership can be built on understanding and how to assist one another. 💡Installers struggling reading sales orders? Commit to educating the sales team on better completion.   𝗕𝗼𝗻𝘂𝘀: 𝗖𝗵𝗲𝗰𝗸 𝘁𝗵𝗲 𝗲𝗴𝗼 𝗮𝘁 𝘁𝗵𝗲 𝗱𝗼𝗼𝗿. ✅Assume positive intent and seek to understand, not blame. 💡Don't allow your team to bash another team, seek feedback to understand.   By providing support and transparency across the enterprise, you will improve morale, productivity, and the culture.   Trust me, I built my career on doing this, and it never fails.   P.S. Do this well and you will expose yourself to a completely different leadership team and elevate your brand. Talk about job security!   𝗧𝗲𝗹𝗹 𝗺𝗲 - 𝗗𝗼𝗲𝘀 𝘆𝗼𝘂𝗿 𝗰𝗼𝗺𝗽𝗮𝗻𝘆 𝗼𝗽𝗲𝗿𝗮𝘁𝗲 𝗶𝗻 𝘀𝗶𝗹𝗼𝘀? 𝗛𝗼𝘄 𝗵𝗮𝘃𝗲 𝘆𝗼𝘂 𝘁𝗿𝗶𝗲𝗱 𝘁𝗼 𝗯𝘂���𝗹𝗱 𝗰𝗼𝗵𝗲𝘀𝗶𝗼𝗻 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝗱𝗲𝗽𝗮𝗿𝘁𝗺𝗲𝗻𝘁𝘀? 𝗟𝗲𝘁 𝗺𝗲 𝗸𝗻𝗼𝘄 𝗶𝗻 𝘁𝗵𝗲 𝗰𝗼𝗺𝗺𝗲𝗻𝘁𝘀.   Like this post? Show me👇🏻 🔥 Engage 💬 Comment ♻️ Repost to your network. 📢Tell me in a DM   Hate it? - Tell me that too.   Want more?   Follow me here 👉🏼Matt Antonucci 🛎️  

𝐎𝐧𝐞 𝐨𝐟 𝐦𝐲 𝐛𝐢𝐠𝐠𝐞𝐬𝐭 𝐥𝐞𝐚𝐫𝐧𝐢𝐧𝐠𝐬 𝐡𝐚𝐬 𝐛𝐞𝐞𝐧 𝐚𝐛𝐨𝐮𝐭 𝐚𝐮𝐭𝐡𝐞𝐧𝐭𝐢𝐜 𝐜𝐨𝐦𝐦𝐮𝐧𝐢𝐜𝐚𝐭𝐢𝐨𝐧. Since CMF communicates emotive values through physical materiality, it's fascinating how material stories mean different things to different people - embedded in their experiences, aspirations, and imagination. When an engineer sees a finish, they think about manufacturability. When a marketer sees it, they imagine lifestyle stories and competitive advantage. When a user sees it, they look for lifestyle fit and aspirational value. 𝐄𝐚𝐜𝐡 𝐩𝐞𝐫𝐬𝐩𝐞𝐜𝐭𝐢𝐯𝐞 𝐢𝐬 𝐯𝐚𝐥𝐢𝐝, 𝐞𝐚𝐜𝐡 𝐢𝐧𝐭𝐞𝐫𝐩𝐫𝐞𝐭𝐚𝐭𝐢𝐨𝐧 𝐢𝐬 𝐫𝐞𝐚𝐥. Magic happens when we translate these experiences across different wavelengths of understanding. Not convincing anyone to see it your way, but building bridges between different ways of experiencing the same thing. The key is to first listen and comprehend what is being said; not just their words, but their concerns and viewpoints. Only then can you assess how it impacts the design work. This understanding shapes how you communicate, making ideas easier to accept because they're presented in a way that resonates with each person's perspective. 𝐁𝐞𝐜𝐚𝐮𝐬𝐞 𝐠𝐫𝐞𝐚𝐭 𝐂𝐌𝐅 𝐝𝐞𝐬𝐢𝐠𝐧 𝐠𝐨𝐞𝐬 𝐛𝐞𝐲𝐨𝐧𝐝 𝐬𝐞𝐥𝐞𝐜𝐭𝐢𝐧𝐠 𝐬𝐭𝐨𝐫𝐲 𝐀 𝐨𝐫 𝐁; 𝐢𝐭'𝐬 𝐚𝐛𝐨𝐮𝐭 𝐛𝐚𝐥𝐚𝐧𝐜𝐢𝐧𝐠 𝐦𝐚𝐧𝐮𝐟𝐚𝐜𝐭𝐮𝐫𝐢𝐧𝐠 𝐟𝐞𝐚𝐬𝐢𝐛𝐢𝐥𝐢𝐭𝐲 𝐰𝐢𝐭𝐡 𝐡𝐨𝐰 𝐩𝐞𝐨𝐩𝐥𝐞 𝐢𝐧𝐭𝐞𝐫𝐩𝐫𝐞𝐭 𝐚𝐧𝐝 𝐜𝐨𝐧𝐧𝐞𝐜𝐭 𝐰𝐢𝐭𝐡 𝐦𝐚𝐭𝐞𝐫𝐢𝐚𝐥𝐬. The success of CMF design goes beyond the final preference; oftentimes the success lies in the collective journey of understanding and alignment that got us there. #CMFDesign #MaterialDesign #Design #ProductDevelopment #Innovation #Communication

𝗛𝗼𝘄 𝘁𝗼 𝗕𝘂𝗶𝗹𝗱 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗕𝗲𝘁𝘄𝗲𝗲𝗻 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘀 𝗮𝗻𝗱 𝗢𝘁𝗵𝗲𝗿 𝗗𝗲𝗽𝗮𝗿𝘁𝗺𝗲𝗻𝘁𝘀 We draw systems - They draw budgets. We think in layers -They think in launches. Architects and business teams often speak different dialects, but we’re building the same product. So how do we actually connect? 𝘏𝘦𝘳𝘦’𝘴 𝘸𝘩𝘢𝘵’𝘴 𝘸𝘰𝘳𝘬𝘦𝘥 𝘧𝘰𝘳 𝘮𝘦: ✔️ Lead with the outcome, not the object (no one cares about your diagram until they know what it changes). ✔️ Ask more than you explain. Questions open doors faster than slide decks. ✔️ Design your language like your systems for clarity and reuse. ✔️ Earn trust before you ask for alignment. A casual coffee often solves more than a formal review. ✔️ Sit in on their meetings. It’s the easiest way to stop designing in a vacuum. Because architecture isn’t a separate function. It’s how we translate complexity into shared understanding across roles, goals, and tools. 𝘞𝘩𝘢𝘵’𝘴 𝘩𝘦𝘭𝘱𝘦𝘥 𝘺𝘰𝘶 𝘣𝘶𝘪𝘭𝘥 𝘣𝘦𝘵𝘵𝘦𝘳 𝘤𝘰𝘮𝘮𝘶𝘯𝘪𝘤𝘢𝘵𝘪𝘰𝘯 𝘢𝘤𝘳𝘰𝘴𝘴 𝘥𝘦𝘱𝘢𝘳𝘵𝘮𝘦𝘯𝘵𝘴? #ArchitectureLeadership #ArchitectCareer #ArchitectureCommunity #TechLeadership