Frameworks CMOs Can Use to Evaluate Competing Priorities
Use a tiered priority architecture that filters work against enterprise outcomes, matches the framework to the decision, and respects real capacity.
Five Principles for Evaluating Competing Priorities
- Filter requests against enterprise outcomes and nonnegotiable guardrails.
- Use weighted scoring for cross-functional portfolio choices.
- Match lightweight frameworks to each decision type.
- Adjust scores for dependencies, risk, and capacity.
- Review results and refine criteria with evidence.
The CMO Priority Evaluation Process
| Step | What to do | Output | Owner | Timeframe |
|---|---|---|---|---|
| 1 | Define enterprise outcomes, constraints, and mandatory work | Priority decision frame | CMO and executive team | Quarterly |
| 2 | Normalize requests with value, evidence, effort, risk, and owner | Comparable initiative briefs | Initiative owners | Before review |
| 3 | Select weighted scoring, RICE, ICE, MoSCoW, or WSJF | Fit-for-purpose evaluation | Portfolio owner | Per decision |
| 4 | Apply capacity, dependency, and portfolio-balance checks | Executable ranked portfolio | Leadership council | Monthly |
| 5 | Compare expected value with results and refine criteria | Updated model and decision log | CMO and Marketing Operations | Monthly and quarterly |
Use a Framework Stack, Not One Universal Score
CMOs should not use one framework for every decision. Begin with an outcome filter that asks whether the work advances two or three enterprise priorities, addresses a material customer or revenue constraint, and respects nonnegotiable guardrails. Requests that fail this test should not enter detailed scoring.
Use weighted scoring for major cross-functional investments. Typical criteria include revenue impact, customer value, strategic fit, urgency, confidence, effort, risk, and dependency load. McKinsey recommends supplementing financial return with complementary factors such as resilience, adaptability, and strategic importance so hidden assumptions become visible. For narrower decisions, use RICE or ICE for campaigns and experiments, value-versus-effort for fast backlog triage, MoSCoW for launch scope, and WSJF when cost of delay and job size matter.
Finally, apply a portfolio check. Sequence prerequisites before optimization, protect foundational data and governance work, reserve capacity for recurring operations, and set a work-in-progress limit. Scores support judgment; they do not replace it. Review operating priorities before each sprint, the cross-functional portfolio monthly, and strategic allocations quarterly. Compare predicted value with actual outcomes and refine the model when it rewards the wrong work.
Source: pedowitzgroup.com, 2026; mckinsey.com, 2025; gartner.com, 2026
TPG Point of View
Use a CMO Priority Architecture - outcome filter, fit-for-purpose score, capacity waterline, dependency sequence, and review cadence.
Why TPG? TPG's CMO advisory engagements combine current-state diagnosis, a 90-day priority plan, operating-system governance, and score-based channel and program decisions.
CMO Prioritization Framework Comparison
| Option | Best for | Pros | Cons | TPG POV |
|---|---|---|---|---|
| Weighted scoring | Annual, quarterly, and cross-functional portfolio choices | Customizable; transparent; strategy-linked | Can become complex or politically weighted | Use as the executive portfolio default |
| RICE or ICE | Campaigns, experiments, and optimization ideas | Fast comparison; confidence is explicit | Estimates can create false precision | Use below the portfolio level |
| Value versus effort | Early backlog and request triage | Simple; visual; quick to facilitate | Misses timing and dependency complexity | Use as a first-pass filter |
| MoSCoW | Launch scope and minimum viable releases | Clarifies must-have versus optional work | Stakeholders may label everything mandatory | Require a hard capacity boundary |
| WSJF | Time-sensitive work with constrained capacity | Accounts for delay cost and job size | Requires credible timing estimates | Use when sequencing changes economic value |
Frequently Asked Questions
Use weighted scoring for the executive portfolio, then adjust the result for dependencies, capacity, mandatory work, and strategic bets. No single formula should determine the final sequence.
Use RICE when reach can be estimated credibly and materially changes value. Use ICE when teams need faster directional scoring for tests or ideas with limited reach data.
Weight criteria according to the current strategy. Growth periods may emphasize revenue and time-to-value, while constrained or regulated periods may assign more weight to risk, resilience, compliance, or efficiency.
Define scoring anchors, require evidence and named assumptions, calibrate scores cross-functionally, separate proposal ownership from final approval, and compare predicted value with actual results.
Review delivery priorities before each sprint or planning cycle, the cross-functional portfolio monthly, and strategic resource allocation quarterly or when assumptions materially change.