To align network upgrade priorities with non-technical team members, employ frameworks like Value vs. Effort Matrix and MoSCoW for prioritization, showing high-impact upgrades and essential features. Use Enterprise Risk Management (ERM) to illustrate business risks from outdated systems and financial models like ROI and TCO to clarify long-term cost benefits. Tools like dependency mapping can help explain resource constraints, while scenario planning and balanced scorecards connect network improvements directly to productivity, growth, and business goals. This approach fosters strategic, collaborative decision-making across technical and non-technical teams.

To find common ground with non-technical team members when discussing network upgrade priorities, start by aligning IT goals with overarching business objectives. Avoid technical jargon and instead frame the upgrade benefits in terms of operational impact and business value, recognising that each department may have its own priorities. By presenting the network upgrades as part of the larger business strategy and showing how they enhance overall efficiency, security, or customer experience, you enable all stakeholders to understand the upgrade’s significance within the broader operational priorities. This shared perspective fosters support for aligned, strategic decision-making.

I mainly rely on reals scenarios or user behaviour (do this than that) to understand and/or explain what s happening. How the choices they do will impact the way they work or feel the IT. Using analogy with real things is a very usefull way to help understanding concepts. Finally the last step is the demonstration : doing the thing, showing what s really happening for them. And never believe they ve understood more than what I ve said. Saying "almost all case" is not the same as saying "all case except this specific one". Being clear in the meaning but avoid technical terms or implied thought.

common ground, explain the network upgrade in simple terms, focusing on how it improves business outcomes like efficiency and security. Highlight the cost savings or risk reduction it brings. Finally, prioritize upgrades based on their impact on business goals to align with non-technical team members' concerns.