Hello Alex! Welcome back to your course, "UX Refresher for EdTech Strategy."
Introduction
In our last lesson, we built a crucial bridge between high-level business objectives (OKRs) and the specific UX metrics (KPIs) that your design work can influence. Now, we'll use that foundation to answer one of the most common and challenging questions in product development: "What should we build next?"
Today's lesson addresses the learning outcome: Use a feature prioritization matrix to evaluate and rank potential new features for an EdTech product based on their impact on learning outcomes and business goals.
You'll learn how to use a simple but powerful tool, the Impact vs. Effort matrix, to move beyond gut feelings and stakeholder pressures. We'll connect the "Impact" axis directly to the strategic goals and KPIs we discussed previously, ensuring your prioritization is evidence-based and aligned with both pedagogical and business success.
This lesson should take you approximately 60 minutes to complete.
Brief Recap:
Remember how we created a visual hierarchy linking an OKR like "Enhance learner engagement" to UX KPIs such as "Task Success Rate" and "Time on Task"? Keep that connection in mind. Those KPIs are exactly what we'll use to objectively measure the potential "impact" of a new feature.
1. The Challenge: Why Prioritization is Hard
As a designer, you've likely been in meetings with a long list of feature ideas, bug fixes, and stakeholder requests, all competing for attention. Deciding where to focus is a major challenge. Before we introduce a solution, let's look at why this is so difficult, especially in EdTech.
Please take a few minutes to read the introductory section of this article from Openfield.
- Reading Time: ~5 minutes
- Focus On: The two main reasons prioritization is a struggle: the tendency to treat all user feedback equally and the conflicting priorities of different internal stakeholders (e.g., developers vs. product owners).
This article highlights a core tension: as user-centric designers, we want to solve every user problem, but business and technical constraints are real. Without a structured framework, teams can end up chasing "squeaky wheel" requests or getting stuck in analysis paralysis. This is where a prioritization matrix becomes an indispensable tool.
2. The Tool: The Impact vs. Effort Matrix
The Impact vs. Effort matrix is a 2x2 grid that helps you visually categorize tasks to facilitate strategic decision-making. It's a cornerstone of product management and a fantastic way for UX designers to champion features that deliver real value.
To understand the matrix and its components, please read the following article from Product School.
Impact Effort Matrix & How to Use One + Examples (What Is the Impact Effort Matrix?)
- Reading Time: ~10 minutes
- Focus On:
- The definition of the matrix and its two axes: Impact and Effort.
- The characteristics of the four quadrants: Quick Wins, Big Bets, Fill-Ins, and Money Pits.
Impact Effort Matrix & How to Use One + Examples
This image from the Product School article shows the four quadrants of the Impact vs. Effort matrix. It visually plots tasks based on their value (Impact) and the resources required (Effort), guiding teams on what to prioritize.
Let's translate these quadrants into an EdTech context:
- Quick Wins (High Impact, Low Effort): These are your top priorities. They deliver significant value to learners or the business without requiring a massive investment.
- Example: Rewriting confusing instructions on a quiz page that has a high error rate.
- Big Bets (High Impact, High Effort): These are major, strategic initiatives that could be transformative but require significant resources and carry more risk.
- Example: Developing a new AI-powered tutor for personalized feedback.
- Fill-Ins (Low Impact, Low Effort): Sometimes called "Thankless Tasks." These are minor improvements that are easy to do but won't move the needle on your main goals. They can be useful to tackle during downtime.
- Example: A minor visual tweak to an infrequently used settings screen.
- Money Pits (Low Impact, High Effort): Avoid these. They consume valuable time and resources for little to no meaningful return.
- Example: A complete, costly redesign of a feature that data shows has very low user engagement and isn't core to the learning experience.
3. Defining the Axes: "Impact" and "Effort" in EdTech
The power of the matrix lies in how you define its axes. If "Impact" and "Effort" are just vague guesses, the tool loses its strategic value.
Defining "Impact"
This is where our last lesson pays off. Impact is a measure of how much a feature will contribute to achieving your product's OKRs. You can quantify this by estimating how it will affect your key UX and business KPIs.
To add more texture to your impact score, consider the rubric suggested in the Openfield article.
How to Prioritize UX Research Findings & Improve Features (Develop a prioritization rubric)
- Reading Time: ~5 minutes
- Focus On: The five facets for your prioritization rubric: Frequency, Severity, Prevalence, Effort, and Prominence.
When evaluating the impact of a potential EdTech feature, ask yourself:
- Prominence: Does this feature relate to a core learning activity (e.g., completing a lesson) or a secondary one (e.g., updating a profile picture)?
- Severity: Does the problem this feature solves block a user from learning, or does it just create minor friction?
- Prevalence: What percentage of your learners will this feature affect? Is it for a niche group or your entire user base?
- Business Goal Alignment: How directly does this feature support a Key Result, like increasing course completion or learner retention?
Defining "Effort"
Effort is an estimate of the total resources required to launch a feature. As a designer, remember that this is more than just development time. It includes:
- UX Research and discovery
- Design (wireframing, prototyping, UI design)
- User testing and iteration
- Engineering development
- Quality Assurance (QA) testing
Effort is best estimated as a team. A simple scale like T-shirt sizes (S, M, L, XL) or a point system (1, 2, 3, 5, 8) is often used to keep estimates relative and avoid getting bogged down in exact hour counts.
4. Activity: Prioritizing Features for an EdTech App
Let's put this into practice.
Scenario: You are a UX designer for "LinguaLeap," a language-learning app. The company has set a new quarterly OKR:
- Objective: Deepen learner engagement and daily habits.
- Key Result 1: Increase the average number of lessons completed per week from 3 to 5.
- Key Result 2: Increase the 7-day retention rate by 15%.
The product team has brainstormed four potential new features. Your task is to plot them on an Impact vs. Effort matrix to help decide what to focus on this quarter.
The Features:
- Daily Goal & Streak Tracker: A simple visual feature on the dashboard to let users set a daily lesson goal and track their consecutive-day streak.
- AI Conversation Partner: A sophisticated new mode where users can have spoken conversations with an AI bot.
- Profile Page Customization: Allow users to choose from a new set of avatars and color themes for their profile.
- Full Curriculum Overhaul: A complete rewrite and re-recording of the audio for the app's least popular language course, "Advanced Portuguese."
Let's evaluate and plot each one.
| Feature | Impact Analysis (vs. OKR) | Effort Estimate | Quadrant | Priority |
|---|---|---|---|---|
| 1. Daily Goal & Streak Tracker | High Impact. Directly targets the OKR by gamifying daily use (improving retention) and encouraging lesson completion. Affects all users (high prevalence). | Low Effort. A well-understood UI pattern. Requires design and front-end work but no complex back-end logic. | Quick Win | Do Now |
| 2. AI Conversation Partner | High Impact. Potentially transformative for learning and retention. A major differentiator. | High Effort. Requires significant R&D, AI integration, complex UX design for conversation flow, and extensive testing. | Big Bet | Plan Strategically |
| 3. Profile Page Customization | Low Impact. Unlikely to drive daily lesson completion or retention. A "nice-to-have" that doesn't affect the core learning loop. | Low Effort. Relatively simple UI work for the design and development teams. | Fill-In | Do if time permits |
| 4. Full Curriculum Overhaul | Low Impact. Affects only a small segment of advanced users. Does not address the broader goal of increasing daily engagement for the majority of the user base. | High Effort. Requires curriculum experts, voice actors, developers, and QA. A massive undertaking. | Money Pit | Avoid/Deprioritize |
This matrix gives you and your team a clear, strategic rationale for your priorities. You can confidently advocate for building the Daily Streak Tracker immediately, while scheduling discovery and planning for the AI Conversation Partner as a long-term strategic project.
Conclusion
Let's wrap up with the key takeaways from today's lesson.
Key Takeaways:
- Prioritization requires a system: The Impact vs. Effort matrix is a simple, visual tool for making objective decisions about what to build next.
- "Impact" is strategic: In EdTech, impact should be measured by how a feature contributes to learning outcomes and business goals (your OKRs and KPIs). Use criteria like prominence, severity, and prevalence to guide your assessment.
- "Effort" is a team sport: Estimating effort is a cross-functional activity that includes all resources needed to ship a feature, from research to development.
- The matrix drives action: It helps you identify Quick Wins to build now, plan for Big Bets, schedule Fill-Ins for lulls, and avoid Money Pits.
By mastering this framework, you elevate your role from a designer who executes tasks to a strategic partner who helps shape the product roadmap and ensures that design effort is always focused on what matters most.
Preview of the Next Lesson:
Now that we've used the matrix to decide what to build (let's say we're moving forward with a high-impact feature related to progress tracking), our next step is to design it. In the next lesson, you will design a wireframe or user flow for a feature that visually demonstrates how transparent progress tracking and personalized feedback can build learner trust. This will be a direct application of the prioritization we've just done.
Can't find a good explanation? Sign up and we'll make it for you
Sign up