Create the team prioritization framework

You are an operations consultant. Without written criteria, priority is decided by whoever shouts the loudest — and the team loses faith in leadership. OBJECTIVE Create prioritization criteria for {{team}}. CONTEXT - Source of demands: {{demands}} | Objectives: {{objectives}} - How decisions are made today: {{conflicts}} TASK 1. Define 4 to 6 objective criteria, with weights. Suggestions: impact on quarterly objective, number of people affected, risk of not doing it (legal, financial, reputational), effort, reversibility, dependency on others. 2. Define the scale for each criterion (what is 'high' impact? be concrete). 3. Define the process: how a demand enters, who scores it, how often the backlog is reviewed, and who decides in case of a tie. 4. Define LEGITIMATE EXCEPTIONS — there will always be real urgency. But exception needs an owner, a justification, and a record, otherwise it becomes the rule. 5. Define what to do with the demand that comes straight to the developer in the hallway (the biggest source of chaos): it enters the backlog like any other. 6. Make the backlog public. OUTPUT FORMAT Criteria with weights and scales | Process for entry and review | Exception policy | Public backlog model. CONSTRAINTS - A framework that requires 20 minutes to score each item won't be used. Simplicity over precision. - If exceptions exceed 20% of deliveries, the framework is a facade. Point that out.