Back to resources

Effective Prioritization: A Balance of Timeline Planning, Rice, Precision, And Accuracy

Impact
Productivity
Roadmap
Prioritization

2 March, 2020

Herman Man
Herman Man

CPO at BlueVine

Herman Man, CPO at BlueVine, explains all of the different elements that have helped him develop effective prioritization.

Problem

In my career, I have learned a lot about effective prioritization, and I have learned different methods that have helped me learn what works best for me. The importance of prioritization is especially true when working with distributed teams.

One of the biggest problems with distributed teams is getting them aligned and doing it efficiently. Here are some of the crucial questions to consider:

  • How will you make sure communication is clear?
  • How do you know you're not doing a bunch of busywork?
  • How do you prioritize in a way so that teams will be able to scale?
  • How easy is it for the teams to translate the prioritization framework among themselves so they can produce something that aligns with the goals and objectives?

Actions taken

The first step in prioritization is understanding what you're solving and why. This understanding helps establish the when and how, which develops interchangeably.

With that, you want to make a couple of things apparent to start planning the timeline. Depending on the organization, this can take four to six weeks per quarter. The period needed to establish a timeline is dependent on the number of parties involved, and the culture of the organization with a big correlation to how precise they want the planning process to be.

We'll run the timeline through the right leads, our CTO, and our CEO, who are all very involved in the decision making process. We do this to make sure we’re in alignment and agreement with everything proposed for the quarter.

For example, when we launched our bank for small businesses, we had to start by figuring out how we were going to build it.

We broke the tasks and goals into chunks and said, "This quarter is really about the web app, and next quarter is about the mobile app."

And then, we needed to develop a framework around prioritization. For me, I use the Rice Prioritization Framework, which stands for reach, impact, confidence, and effort. This framework will give you some sort of unit of measure to work with and plan around.

The measure isn't necessarily useful in an absolute sense but becomes more useful from a relative perspective.

With reach, you pick a measure to follow, which could be the number of customers, or a dollar amount if it’s tied to revenue or CTS for example. You must be consistent with the reach measurement. If you are using the number of customers, you should use customers as your currency across all your estimates. If you are using dollars saved or dollars earned, then use dollars across all teams.

Impact becomes a multiplier of the work. Does it impact 1,000 people? Or does it impact the base of all my clients? It becomes this magnitude and unit.

With confidence, you must measure how confident you are in your work. How confident are you in your assessment of these numbers? How confident are you in the effort to build?

The last one, effort, is a measure of the work that a member of your team can complete in the timeline.

The whole idea here is not to be too granular, but to give you some sort of unit of measure that helps you understand how each factor will affect your prioritization framework. The score you calculate gives a numerical number that allows you to measure across everything you need to and compare against other items that are prioritized in your backlog.

That being said, the system can always be gamed in that it's garbage in, garbage out. What’s important is to be impartial or unbiased throughout. You can verify your work by what I call "the gut check" as you work through establishing the framework. You need to do a quick check to make sure that things align and make sense. Once you do that, you should have a semblance of a plan.

Mostly, you're trying to make something that's qualitative, a little more quantitative without replacing the full-on qualitative aspect of it.

Lessons learned

I have learned that this approach allows for a more predictable process over time. People will start understanding the principles by which you are prioritizing as it relates to the timeline, the process, and what matters most.

A predictable process allows people to be proactive so they can start planning and gather any necessary data or any critical information for the next quarterly planning process. They're already thinking about the prioritization process in general, what to do next and why it matters.

The other takeaway is that it drives precision. For me, precision and accuracy are quite different.

Think about it like you are shooting basketball hoops. If your shots are always making it in the net, you are accurate as it relates to the objective. For precision though, how much are you on with each shot? I could shoot five shots, and they all miss to the right hitting the same spot. I'm not accurate in terms of where the ball is landing, but I'm precise with those five shots.

This thinking allows you to be precise, which gives more visibility into relative priorities. That's important because, with precision, it helps you with prioritizing the right tasks.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

How to Build and Manage the First Product Roadmap for a Startup

19 January

Angel Jamie, Chief Product Officer at Yayzy, shares how he created the first product roadmap at a startup, and a simple process to keep it alive.

Alignment
Product
Meetings
Roadmap
Prioritization
Angel Jaime

Angel Jaime

CPO at yayzy

From Big Tech to Startup: Adding Value From Day 1

19 January

Angel Jamie, Chief Product Officer at Yayzy, recalls his transition from a well-established tech company to a sustainability startup, and the major differences he experienced.

Dev Processes
Company Culture
Impact
Team Processes
Cross-Functional Collaboration
Changing Company
Career Path
Performance
Angel Jaime

Angel Jaime

CPO at yayzy

How to Spark Sales-Driven Change

19 January

Nani Nitinavakorn, Sr Product Owner at Revolut, recalls her experience initiating a structural change to optimize her entire company.

Customers
Innovation / Experiment
Leadership
Meetings
Impact
Users
Nani Nitinavakorn

Nani Nitinavakorn

Sr Product Owner at Revolut

Analyzing a Problem for Real Causes and Coming to a Pragmatic Solution

7 January

Ranadheer Velamuri, Director of Engineering at Tesco, shares how he increased productivity by analyzing his problem and determining the best solution.

Alignment
Conflict Solving
Internal Communication
Productivity
Prioritization
Ranadheer Velamuri

Ranadheer Velamuri

Director of Engineering at Tesco

Decreasing Distractions During the Remote Workday

7 January

Ross Bruniges, Engineering Manager at Atlassian, shares his tips for a successful work-life balance, creating boundaries to decrease social distractions.

Salary / Work Conditions
Personal Growth
Productivity
Health / Stress / Burn-Out
Performance
Ross Bruniges

Ross Bruniges

Engineering Manager at Atlassian

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.