Your team is divided on analytics project priorities. How will you navigate conflicting perspectives?

Align your priorities with Business/department and quarterly OKRs, objectives and vision. - If 2 priorities tie with OKR - look for the one that provides most valuable to business and your stakeholders - Or pick one which is a quick win and quickly adds to key results of your quarter - You may also start both deliverables in agile fashion by delivering value in each iteration rather than a big bang delivery. This allows you to divide your resources and conquer the targets 🎯together - By starting both pieces of deliverables parallel - allows you to keep momentum and resolve dependencies at the earliest possible rather than hitting on a showstopper in one project and then thinking of picking the next one. Ensure any resource constraints.

When the team is divided on project priorities, I propose evaluating the projects objectively based on their potential impact, delivery urgency, and available resources. By using data-driven decision-making, we can assess which projects should take precedence. The goal is to find a middle ground that addresses the key concerns of all parties, which may involve compromises or combining elements of different projects. This collaborative approach ensures our decisions are fair and aligned with our overall objectives.

Start by aligning the team on shared business goals. Facilitate open discussions where each person explains their viewpoint and the potential impact of their priority. Use data to evaluate and compare the value and urgency of each initiative. If needed, create a weighted scoring system to objectively assess priorities. Focus on collaboration, ensuring the team feels heard, and find a middle ground where high-impact projects get the attention they need while considering resource constraints.

I’ve developed a method for automatic prioritization of data initiatives once, and I’ve been using it for for a while now, with a few improvements since v1. I took into a count a few key parameters, such as the impact for some dimensions at the business and the complexity of development. Those two aspects are the most important, because they take into account what’s relevant for the business (impact) and what’s relevant for the team that will develop it (complexity). If you prioritize balancing those two aspects, you’ll have way more chances of getting it right.

“The secret of change is to focus all your energy, not on fighting the old, but on building the new." – Socrates To successfully implement new data protocols amidst team resistance, it's crucial to lead with empathy and clarity. Engage in open dialogue to understand concerns and foster collaboration. Provide comprehensive training to demystify the new processes, ensuring your team feels supported. Set clear expectations and milestones to track progress and celebrate wins. From my experience,this approach turns resistance into momentum, making the transition smoother and more effective.