Prioritization as code: An AI-supported framework for platform engineering (Eleanor Millman and Mina Tawadrous)
· Summarized
Key takeaways
- Develop a clear, impact-driven prioritization framework tailored to your organization's needs, including impact categories and adjustable weights.
- Document and review assumptions behind project scores like code—versioned, transparent, and revisited regularly—to improve clarity and decision-making quality.
- Leverage AI tools to surface relevant assumptions, connect initiatives to existing knowledge, and support faster, more informed prioritization debates.
- Maintain human oversight and validation in automated scoring processes to ensure context, judgment, and strategic alignment.
- Continuous iteration, stakeholder involvement, and adapting impact factors as organizational goals evolve are key to effective project prioritization.
Summary
Introduction and Context of SiriusXM's Platform Engineering
Eleanor Millman and Mina Tawadrous introduce the episode, sharing their roles at SiriusXM and the context for their work. They discuss how SiriusXM built a large-scale internal developer platform supporting 700,000 developers across various languages and tools, with diverse needs and skill levels. The challenges they faced in prioritizing features and projects without traditional metrics or a direct revenue link are highlighted, setting the stage for their innovative approach.
Development of a Prioritization Framework Based on Impact Factors
The speakers detail how they devised a prioritization formula inspired by RICE, incorporating impact, urgency, effort, and additional factors like internal stakeholder needs. They explain how impact is broken down into seven specific categories—development speed, runtime reliability, security, cost reduction, platform engineering efficiency, user trust, and data enablement. The impact factors are weighted and can be adjusted based on company priorities, with dynamic reassessment over time driven by developer feedback.
Implementing and Evolving the Impact Scoring System
The podcast explores how SiriusXM scores projects using impact factor ratings (0, 1, 2, 3, 5), incorporating user data and surveys to make ratings more objective. They emphasize the importance of documenting assumptions behind scores, treating them like code, and maintaining transparency through version control. Iterations on the model are driven by changing organizational priorities and data insights, making project prioritization more aligned and less emotionally charged.
Challenges and Solutions in Cross-Team Prioritization and Assumption Management
They discuss difficulties in reconciling conflicting assumptions between teams, illustrating how biases like the 'curse of knowledge' can impair accurate scoring. The concept of storing assumptions as code—versioned, visible, and timestamped—is introduced as a way to resolve assumption conflicts and improve decision-making. This approach shifts debates from emotional disagreements to fact-based discussions, fostering a shared understanding.
Using AI to Surface and Validate Assumptions
The episode introduces AI integration as a tool to surface relevant assumptions and past knowledge, reducing manual effort and improving recall. AI aids in connecting initiatives with existing data, assumptions, and company goals, while humans remain in the decision-making loop for validation. The use of AI enhances the scoring process, making it faster and more reliable, and helps maintain an up-to-date, collaborative assumptions repository.
Practical Steps for Building Your Own Prioritization Framework
Eleanor and Mina outline three steps for organizations to adopt a similar framework: define impact impact factors and weights aligned with company goals; score projects by documenting and reviewing assumptions; and integrate AI to improve the recall and validation of assumptions. They encourage continuous iteration and stakeholder collaboration to refine the model over time.
Q&A: Addressing Costly Projects, Stakeholder Conflicts, and Broader Application
The hosts answer questions from the audience, covering how to evaluate projects with potentially enormous costs, manage conflicts when the framework prioritizes differently from stakeholder desires, and extend the approach beyond developers to support non-technical users. They highlight the importance of transparent, data-driven conversations, and the flexibility to adapt impact factors for broader organizational needs.
Sponsors
- AWS · Thanks to AWS for sponsoring this episode.
- Databricks · Thanks to Databricks for supporting this episode.
Show notes
In this session from DX Annual, Eleanor Millman, Senior Staff Product Manager, and Mina Tawadrous, Associate Director of Product Management at SiriusXM, share how their platform engineering organization developed a prioritization framework for platform engineering teams serving hundreds of developers across a complex cloud platform.
They explain how they define and weight platform-specific impact factors, use developer data to refine priorities, and score projects more consistently. They also explore why prioritization debates often stem from conflicting, invisible, or outdated assumptions, and how SiriusXM began treating assumptions like code by documenting, versioning, and reviewing them in source control.
Finally, they demonstrate how AI can surface assumptions, connect initiatives to existing knowledge, and support project scoring while keeping humans in the loop. Throughout the session, they offer a practical framework for making prioritization decisions more transparent, data-driven, and scalable.
In this episode, we cover:
(00:00) Intro
(02:58) Building a platform engineering prioritization framework
(04:59) The seven platform engineering impact factors
(09:38) Using impact factors to score projects
(13:11) Using developer data to refine priorities
(16:33) Three ways assumptions fail
(17:40) Assumptions as code
(21:00) New problems created by assumptions as code
(22:00) Using AI to surface assumptions
(23:44) Building an AI-powered feedback loop
(25:44) Inside the AI prioritization tool
(28:18) Three steps to build your own framework
(30:02) Q&A #1: Evaluating high-cost projects
(31:30) Q&A #2: The cadence of iteration
(32:10) Q&A #3: When the framework conflicts with a stakeholder's priorities
(35:26) Q&A #4: Using the framework for non-developers
Referenced:
• AWS
• RICE: Simple prioritization for product managers
Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account