Business units are clashing over project priorities. How do you decide what comes first?
When business units clash over project priorities, it can disrupt productivity and strain relationships. Using business architecture, you can align goals and streamline decision-making. Here are some strategies to help you decide what comes first:
Have any strategies that have worked for you in similar situations? Share your insights.
Business units are clashing over project priorities. How do you decide what comes first?
When business units clash over project priorities, it can disrupt productivity and strain relationships. Using business architecture, you can align goals and streamline decision-making. Here are some strategies to help you decide what comes first:
Have any strategies that have worked for you in similar situations? Share your insights.
-
Alignment with org's strategy is first and foremost. This is where business architecture team steps in to streamline the execution of a businses strategy. A balance scorecard / Norton Kaplan Strategy Map or similar frameworks will help organization to set objectives & their KPIs (derived from business drivers), mapped with different stakeholder's perspectives. A impact analysis on the value streams & capabilities highlights the necessary initiatives / programs required. Then projects are mapped to the objectives. Strategies are eventually translated through capabilities into a coordinated, prioritized and sequenced set of actions.
-
Start with a comprehensive assessment of each project's strategic alignment, potential ROI, and overall impact on the organization. Engage key stakeholders from all business units to understand their perspectives and challenges. Use a priority matrix to evaluate projects based on criteria such as urgency, financial benefit, resource availability, and risk. Foster transparent communication to ensure all parties are aware of the decision-making process. Implement a balanced scorecard approach to measure both short-term gains and long-term value. Ensure regular reviews to adjust priorities as business needs evolve. Maintain flexibility to adapt to unforeseen changes or opportunities.
-
To decide project priorities when business units clash, align projects with strategic goals, assess their impact and benefits, and consider resource availability and urgency. Use a prioritization framework to objectively evaluate each project and communicate decisions transparently to stakeholders. Regularly review and adjust priorities as needed to adapt to changing business environments.
-
When business units clash over project priorities, the Business Architect / Analyst helps align goals and streamline decision-making. The key is creating a win-win scenario by clearly defining organisational objectives, fostering cross-functional collaboration, and using data to assess project impact. Prioritise based on long-term strategic value, and ensure transparency in decision-making to avoid misunderstandings. Lastly, adopt an iterative approach to adjust priorities as needed. This promotes shared purpose, reduces friction, and drives productivity while maintaining positive relationships between teams.
-
If you really have that level of clash (business unit level), than probably you need to use the enterprise governance. If you did not setup beforehand, probably there's very little you can do as business architect to resolve. This decision-making process is the most important one to be defined and implemented in the governance when running projects in large matrix environments.
-
You need to take a look at the company vision and strategy. Align that to the capabilities of the organization. Watch out for pitfalls of investing too much into commodity capabilities. Spend time and resources on the capabilities that will be the differentiators for the organization. Every company has AP/AR/HR - this are commodities, lots of options and lots of ways to be innovative without taking away from the things that will set you apart. Figure that out and the priorities should reveal themselves.
-
When business units clash over priorities, I rely on a focused, data-driven approach, leveraging fusion teams to break down silos and foster cross-functional collaboration. I begin with a comprehensive assessment, aligning each project with strategic goals and evaluating factors like ROI, customer impact, urgency, resource needs, and risks. Fusion teams bring diverse perspectives to the table, enabling more innovative and balanced solutions. Using these insights, I facilitate clear, outcome-driven discussions to prioritize initiatives with the highest value for the organization. If alignment remains elusive, leadership input ensures decisions reflect broader priorities. It’s about driving impact through collaboration and synergy.
-
To resolve clashes over project priorities, align decisions with organisational goals. Use clear evaluation criteria like strategic alignment, ROI, risk mitigation, customer impact, and urgency. Create a value framework to score projects objectively, involve key stakeholders in discussions, and prioritise based on measurable benefits and overall impact. And, get the HIPPO out of the uneducated executive ears!
-
It is essential to have a structured approach for better decision making framework and Architecture can play a significant role in resolving conflicts over project priorities by providing a structured framework. By following structured approach with scoring system and prioritization matrix considering dependencies & constraints, ensure that project priorities are aligned with business objectives and resources are allocated effectively. Also be prepared to adjust to changing circumstances such as shift in market trends or change in business objectives. Have Business capability modeling, Value stream mapping and Architecture roadmap established to prioritize projects based on capabilities, processes and alignment with architecture roadmap.
-
Resolving Project Priority Conflicts with DMAIC When business units clash over priorities, the DMAIC framework (Define, Measure, Analyze, Improve, Control) can align goals and streamline decisions: • Define: Clarify organizational objectives and establish shared prioritization criteria. • Measure: Collect data on each project’s ROI, urgency, and resource needs. • Analyze: Identify root causes of conflicts, like unclear goals or resource constraints. • Improve: Implement a structured, consensus-driven prioritization process. • Control: Standardize and monitor the process to ensure alignment and continuous improvement. This approach fosters collaboration, minimizes disruption, and keeps teams focused on strategic goals.
Rate this article
More relevant reading
-
Business ArchitectureWhat do you do if your decision-making abilities are hindering your success in Business Architecture?
-
Business ArchitectureHow can business architecture professionals find purpose and meaning in their work?
-
Business ArchitectureHow do you foster a stakeholder-centric culture and mindset in your business architecture team?
-
Business ArchitectureWhat do you do if your failures in Business Architecture hinder your credibility and trust with stakeholders?