Learning Objectives

After completing this lecture, you will be able to:

• Understand the key concepts of prioritization frameworks for government ai in a government context
• Participate in structured workshop activities with real-world scenarios
• Connect prioritization frameworks for government ai to your agency's AI initiatives
• Identify next steps for applying these concepts in your role

Key Topics Covered

-
RICE, ICE, MoSCoW adapted for public sector constraints

-
Balancing impact, feasibility, and compliance

-
Government context for prioritization frameworks for government ai

-
Practical applications and next steps

Why This Matters for Government

Government agencies face a scarcity problem that private firms do not. Every AI project an agency wants to run competes for the same congressionally appropriated funds, the same shrinking population of cleared technical talent, the same backlog of ATOs and FedRAMP authorizations, and the same limited attention from the Chief AI Officer (CAIO) designated under OMB Memorandum M-24-10 (March 2024). At the same time, the opportunity surface is expanding: OMB M-24-10 has forced every agency to publish a use-case inventory, the National AI Research Resource (NAIRR) pilot (NSF, NIH, DOE, VA, NASA, NOAA, USDA, DOD, and partners) has unlocked new compute and data access, Executive Order 14110 (October 2023) has directed agencies to identify generative AI pilots, and the interagency CAIO Council is brokering shared services. In this environment, a disciplined prioritization framework is not a nice-to-have artifact for the strategy team; it is the operating mechanism by which scarce resources get pointed at the highest-value, highest-equity, most compliant work.

Without a framework, three dysfunctional patterns take over. First, loudest-voice prioritization: the project of the most senior person or the most aggressive vendor goes first regardless of impact. Second, compliance-panic prioritization: the agency lurches from one GAO finding or OIG audit to the next, always reacting and never building compounding capability. Third, shiny-object prioritization: generative AI demos dominate the roadmap even though the agency's real value is in back-office automation, benefits processing, or records management. Each pattern is observable in the case record. The IRS ID.me rollout in 2022 illustrates shiny-object and loudest-voice pathology: a high-profile identity vendor contract advanced without a disparate-impact test that a RICE or MoSCoW exercise weighted for equity would have flagged immediately. Michigan's MIDAS unemployment fraud detection ran for years on a prioritization logic that weighted 'recover improper payments' far above 'false accusations against legitimate claimants', producing roughly forty thousand false positives and more than twenty million dollars in settlements before the Michigan legislature restricted fully automated adjudication. The Dutch childcare benefits (toeslagenaffaire) scandal and SyRI both illustrate what happens when prioritization is driven by fraud-recovery politics without equity weight. Houston Federation of Teachers v. Houston ISD (S.D. Tex. 2017) shows the cost when institutional prioritization favors deployment over explainability. Compas (State v. Loomis, Wis. 2016) demonstrates the same pattern at the state level in criminal justice.

A sound prioritization framework for government AI has to do five things that generic product-management frameworks like RICE, ICE, and MoSCoW do not do out of the box. First, it must carry an explicit compliance lane: statutory mandates, OMB memoranda, NIST AI RMF GOVERN obligations, FISMA continuous monitoring, Section 508 accessibility, and Paperwork Reduction Act clearances cannot be traded away against feature work. Second, it must carry an equity weight for rights-impacting and safety-impacting AI under M-24-10, reflecting the agency's obligations to citizens who cannot choose another provider. Third, it must reflect capability building: early projects should pay forward by building evaluation harnesses, synthetic data pipelines, model cards, and incident-response playbooks that compound across the portfolio. Fourth, it must treat political viability as a constraint rather than a score: if a project lacks Congressional, OMB, or civil society support, that is a real obstacle, but it should not disguise itself as merit. Fifth, it must be auditable by GAO, the agency Inspector General, the appropriations committees, and the Privacy and Civil Liberties Oversight Board.

This lecture provides three classical frameworks (RICE, ICE, MoSCoW) adapted for that five-part government test, plus practice exercises and a case walkthrough. The goal is not framework mastery as an end in itself; it is the ability to run a transparent, defensible allocation of the agency's AI budget, talent, and attention so that the next ID.me, the next MIDAS, the next toeslagenaffaire does not happen on your watch. For CAIOs, program executives, and strategy leaders operating at L3 and above, prioritization discipline is the difference between an AI program that survives the next administration transition and one that becomes an IG case study.

======================================================================

TRANSCRIPT: Prioritization Frameworks for Government AI

======================================================================

What you will learn: How to prioritize competing AI projects using frameworks adapted for government context.

You have more AI project ideas than you have resources. Everyone wants their project approved. How do you decide which projects actually get funded and which ones wait?

Without a prioritization framework, decisions get made based on politics, loudness, or whoever has the strongest relationship with leadership. The best projects might get deprioritized. Less impactful projects might get funded. You waste resources on lower-value work.

This lecture gives you three frameworks--RICE, ICE, and MoSCoW--adapted for government context. You'll learn how to apply these frameworks, how to adapt them when government-specific factors matter, and how to defend your prioritization decisions to skeptical stakeholders.

WHY PRIORITIZATION FRAMEWORKS MATTER

Overview

Prioritization frameworks serve several purposes:

• They force you to make explicit trade-offs
• They remove politics from decisions
• They are defensible--you can explain your reasoning
• They are repeatable--you can apply them to all projects consistently

WHY THIS MATTERS FOR GOVERNMENT

Government prioritization is harder than private-sector prioritization because you're juggling multiple, sometimes conflicting objectives:

• MISSION IMPACT: Which projects best serve public mission?
• FEASIBILITY: Which projects can we actually execute with available resources?
• COMPLIANCE: Which projects address regulatory requirements or policy directives?
• EQUITY: Which projects improve service to underserved populations?
• RISK: Which projects have the least downside risk?
• POLITICAL: Which projects have stakeholder support?

CORE CONCEPTS

• RICE FRAMEWORK

RICE stands for: Reach, Impact, Confidence, Effort

For each project, score each dimension:

REACH (1-10): How many people does this affect?

1 = Handful of people

5 = Thousands of people

10 = Millions of people or fundamental capability

IMPACT (1-4): How much does this improve outcomes for affected people?

1 = Minimal improvement

2 = Some improvement

3 = Significant improvement

4 = Transformational improvement

CONFIDENCE (0-100%): How confident are you in your reach and impact estimates?

50% = Very uncertain

75% = Moderate confidence

100% = High confidence

EFFORT (weeks): How much work is required?

4 weeks = Minimal

12 weeks = Moderate

26 weeks = Substantial

RICE SCORE = (Reach x Impact x Confidence) / Effort

EXAMPLE

Benefits Processing Automation:

• Reach: 8 (affects 2M benefit applicants)
• Impact: 3 (reduces processing from 6 months to 2 weeks--significant for beneficiaries)
• Confidence: 85% (we've done similar projects)
• Effort: 20 weeks
• RICE = (8 x 3 x 0.85) / 20 = 1.02

Tax Fraud Detection:

• Reach: 3 (affects 50K suspected fraudsters)
• Impact: 4 (prevents fraudulent payment--transformational)
• Confidence: 70% (uncertain about detection accuracy)
• Effort: 24 weeks
• RICE = (3 x 4 x 0.70) / 24 = 0.35

Based on RICE, benefit processing wins.

• ICE FRAMEWORK

ICE stands for: Impact, Confidence, Ease

Simpler than RICE. Good for quicker prioritization.

IMPACT (1-10): How much business value does this create?

CONFIDENCE (1-10): How confident are you in impact?

EASE (1-10): How easy/fast is this to execute?

ICE SCORE = (Impact + Confidence + Ease) / 3

ADVANTAGES: Simpler, faster calculation

DISADVANTAGES: Doesn't account for scale or effort explicitly

• MOSCOWFRAMEWORK

MoSCoW stands for: Must have, Should have, Could have, Won't have

MUST HAVE (M): Regulatory requirement or critical mission failure if not done

SHOULD HAVE (S): Important but not critical; needed in medium term

COULD HAVE (C): Nice to have; would improve things but not essential

WON'T HAVE (W): Explicitly not prioritized this period

MoSCoW works well for government because it explicitly accounts for must-haves (compliance, mission-critical), should-haves (strategic value), and explicit won't-haves (things you're consciously deferring).

ADAPTATION FOR GOVERNMENT

When applying these frameworks to government AI, add explicit dimensions:

COMPLIANCE IMPERATIVE

Does this project address a regulatory requirement (OMB guidance, federal mandate, policy directive)?

Yes = Must prioritize higher

No = Can be deprioritized if other projects score higher

EQUITY CONSIDERATION

Does this project disproportionately serve underserved populations?

Yes = Increases priority weight

No = Standard priority weight

CAPABILITY BUILDING

Does this project build capability that enables future projects?

Yes = Increases priority weight

No = Standard priority weight

POLITICAL VIABILITY

Do you have stakeholder support (especially from elected officials)?

Yes = Can succeed

No = May face obstacles

This is a constraint, not a scoring factor--but it's real

PRACTICAL USE CASE

A federal agency had 12 potential AI projects. They applied the RICE framework adapted for government:

PROJECT A: Benefit Processing Automation

• Reach: 8, Impact: 3, Confidence: 85%, Effort: 20 weeks = RICE 1.02
• Compliance: Medium (addresses service delivery goals)
• Equity: High (serves vulnerable populations)
• Capability Building: Medium
• Political Viability: High
• PRIORITY: 1 (Clear winner)

PROJECT B: Benefits Fraud Detection

• Reach: 3, Impact: 4, Confidence: 70%, Effort: 24 weeks = RICE 0.35
• Compliance: High (addresses improper payment concerns)
• Equity: Low (doesn't directly serve vulnerable populations)
• Capability Building: High (builds fraud detection capability)
• Political Viability: High (leadership wants fraud reduction)
• PRIORITY: 2 (Strong case despite lower RICE)

PROJECT C: HR Recruitment Optimization

• Reach: 2, Impact: 2, Confidence: 60%, Effort: 10 weeks = RICE 0.24
• Compliance: Low
• Equity: Neutral
• Capability Building: Low
• Political Viability: Medium
• PRIORITY: Defer (Lower score, lower strategic value)

This analysis got buy-in because it was objective, explained, and accounted for government-specific factors.

Risk #1: OVERWEIGHTING POLITICAL VIABILITY

The temptation: A high-ranking official wants a particular AI project. You rank it #1 despite lower objective scores.

Why this fails: You invest in a lower-value project while higher-value projects wait. Over time, this erodes credibility in your prioritization process.

How to avoid: Political viability should be a constraint (does the project have sufficient stakeholder support?), not a scoring factor. If a project lacks support, work to build support rather than changing the prioritization framework.

Risk #2: UNDERWEIGHTING COMPLIANCE

The temptation: You score compliance as just another factor, equal to other factors.

Why this fails: You skip a must-do compliance project to do a fun discretionary project. Compliance issues cause problems later.

How to avoid: Explicitly separate must-have compliance work from discretionary AI projects. Do compliance work first. Then prioritize discretionary work.

Risk #3: IGNORING CAPABILITY BUILDING

The temptation: You prioritize projects based purely on immediate impact, ignoring whether they build capability for future projects.

Why this fails: You never build organizational capability. You remain dependent on external expertise. You can't sustain AI adoption.

How to avoid: Explicitly score capability building. Early projects should prioritize building capability, even if they have lower immediate impact. This is strategic.

Risk #4: USING FRAMEWORKS ONLY FOR COVER

The temptation: You apply the RICE framework but the real decision was made beforehand through politics. You use the framework as cover.

Why this fails: People figure out the decision was pre-made. Your framework loses credibility.

How to avoid: Actually use the framework to inform decisions. If the framework scores Project A #1 but you choose Project B due to other constraints, explain why clearly. Credibility comes from honest application and clear reasoning.

• FRAMEWORK SELECTION

Which framework is most useful for your organization? RICE is comprehensive. ICE is simpler. MoSCoW is good for must/should/could clarity. Which matches your decision-making style?

• PROJECT SCORING

Take 5 competing AI projects and score each using RICE. Calculate scores. Rank by score. Do the rankings make sense?

• GOVERNMENT ADAPTATIONS

For each project, assess: compliance imperative, equity consideration, capability building, political viability. How do these factors affect your prioritization?

• DEFENSIBILITY

For your top 3 projects, write a one-page explanation of why they're prioritized. How would you defend this to skeptical stakeholders?

• TRANSPARENCY

How will you communicate prioritization decisions to people whose projects don't get funded? How will you show you were fair?

• Use frameworks to remove politics from prioritization. This builds credibility.
• RICE is comprehensive but complex. ICE is simpler. MoSCoW is good for must-have clarity. Choose what fits your needs.
• Adapt frameworks for government. Explicitly account for compliance, equity, capability building.
• Separate political viability (a constraint--"do we have stakeholder support?") from scoring factors.
• Explicitly prioritize compliance and capability-building work, even if immediate impact is lower.
• Communicate your prioritization framework and decisions transparently. People accept tough decisions better when they understand the reasoning.
• Revisit prioritization quarterly. As circumstances change, priorities should change.

RICE Framework: Prioritization framework using Reach, Impact, Confidence, Effort dimensions. Produces scored rankings of projects.

ICE Framework: Simpler prioritization framework using Impact, Confidence, Ease dimensions.

MoSCoW: Prioritization framework that categorizes requirements as Must, Should, Could, Won't have.

Capability Building: Projects that develop organizational skills or infrastructure enabling future projects. Important to prioritize alongside immediate-impact projects.

Stakeholder Viability: Whether a project has support from people with influence or authority to affect its success.

You now have frameworks for prioritizing competing AI projects. The next step is selecting a framework, applying it to your projects, and using the results to inform decisions.

Choose a framework. Score your projects honestly. Let the scoring inform your decisions. Communicate clearly about why you prioritized what you prioritized.

That's how you build credibility in your prioritization process.

Take your proposed AI program. List all projects you're considering. Apply your chosen prioritization framework to each. Rank them. Write a summary explaining your top 5 priorities and why you deferred the others. This becomes your resource allocation document.

Prioritization frameworks are tools for making fair, transparent, defensible decisions about where to invest limited resources. They don't make the decisions for you, but they make the decision-making process more rigorous and credible.

Government organizations that succeed with AI use frameworks to guide prioritization. They make their reasoning transparent. They justify their choices. They build buy-in for their decisions, even from people whose projects don't get funded.

You're building that rigor now.

Government AI CLUB Certification Program

Level 3: AI Practitioner | Organizational Strategy | Lecture 1.7

A GOVT.CLUB initiative.

<- 3.1.2 AI Maturity Assessment
3.1.4 Building the AI Business Case ->

Start Your CLUB Certification

This lecture is part of L3: AI Strategist -- 80 hours of comprehensive government AI training.

Explore CLUB Certification

Related Lectures

L3
3.1.1 -- Developing an Organizational AI Strategy
120 min - Lecture + Workshop

L3
3.1.2 -- AI Maturity Assessment
90 min - Workshop + Tool

L3
3.1.4 -- Building the AI Business Case
120 min - Workshop + Template