The Effort Matrix.
A simple two-by-two for product teams who want to stop spending engineering effort on the wrong work. The way we think about prioritization at TCG.
Make room for the work that actually moves the product.
Your highest-impact work rarely gets the time, money, and energy it deserves. Sprints fill with smaller, easier asks, and your differentiators end up shipping at the same level of polish as everything else.
The Effort Matrix is how you fund that work. By identifying where you can lean on standards and templates, you free up senior engineering and design capacity for the experiences that define your product.
Signs your most important work isn't getting through.
- →
The work that would actually move the product keeps slipping to next quarter.
- →
It is hard to point to anything you shipped this year that meaningfully changed the product.
- →
Senior engineers and designers are stretched thin across every request instead of focused on the work that defines the product.
- →
You know what your highest-impact bets are; you just cannot find the time, money, or energy to make them great.
Plot every feature on two axes.
Relevance to value proposition on the vertical. Frequency of use on the horizontal. The quadrant tells you how much effort it deserves.
Effort Matrix
Delighters
Rare, complex paths where ease and reliability matter—users may expect a slog. Spend time getting these right.
Differentiators
This is why they bought the product. Spend time and money doing this better than anyone else.
Edge Cases
Rely on established patterns and templates from your design system.
Table Stakes
Use standard best practices and workflows from other products that your users are used to.
What each quadrant means in practice.
Delighters
High value · Low frequencyComplex, infrequent workflows that feel effortless when they matter most.
Users brace for a slog and get something considered. Rare paths that are high-stakes when they happen, so ease and reliability stand out. Get these right and you turn an uncommon moment into a story your customers tell.
- + High-stakes response actions like containing a host
- + Multi-step recovery under pressure
- + Deep data slicing for investigation or debugging
Differentiators
High value · High frequencyThis is why customers bought the product. Spend time and money doing this better than anyone else.
Differentiators are the workflows that justify your price tag. Users hit them every day, and they directly support your value proposition. Invest in custom design, performance, and polish here. This is where engineering effort produces the most leverage.
- + Core product workflows
- + Signature features competitors cannot copy quickly
- + The "aha" moments your sales team demos
Edge Cases
Low value · Low frequencyRely on established patterns and templates from your design system.
Rarely used screens that do not move the needle on value. Resist the urge to over-design them. A clean, consistent template from your design system is enough. Save the custom thinking for differentiators and delighters.
- + Admin-only configuration screens
- + Rarely accessed reports
- + One-off compliance flows
Table Stakes
Low value · High frequencyUse standard best practices and workflows from other products that your users are already used to.
Authentication, settings, role management, search. Your users expect these to just work. Reinventing them costs you time and confuses customers. Lean on familiar patterns and ship them quickly so engineering capacity stays focused on differentiators.
- + Authentication and SSO
- + RBAC, MFA, audit logs
- + Notifications and account settings
Run it with your team in an afternoon.
The matrix is most useful when product, design, and engineering are in the same room. The conversation about which quadrant a feature lives in is the actual value.
List the work on the table.
Pull together every feature, request, and backlog item under consideration. One sticky, one card, one row — whatever your team uses. The goal is a single flat list before you sort.
Place each item on the matrix.
For each item, ask two questions: How relevant is this to our value proposition? How often will users actually hit it? Drop the item into the quadrant that best fits. Disagreements here surface real strategy questions worth having.
Set effort by quadrant, not by item.
Assign your custom design and engineering investment to differentiators and delighters. Lean on standards for table stakes. Use design system templates for edge cases. The matrix sets the budget; the team executes against it.
Revisit it every quarter.
Items move. A delighter your users love can become a differentiator. A table stake can rise in importance after a competitor stumbles. Treat the matrix as a living artifact, not a one-time exercise.
A working tool, not a deck slide.
We pull this matrix into nearly every TCG engagement. It is fast to set up, easy for non-design stakeholders to engage with, and it produces decisions you can act on the same day.
The hardest part is not the framework. It is the honest conversation about what your product actually differentiates on. Once that is on the wall, where to invest engineering effort becomes obvious.
Want help applying this to your roadmap?
We run the Effort Matrix with product, design, and engineering teams to align on where effort should go before the next sprint starts. One working session. Clear answers.
Book a Working Session