Annual Planning Prioritization

Posted by Jeff Dwyer

Sep 16, 2024 2:52:57 PM

As Forcerank surpasses 100,000 votes, we’ve been diving deep into user behavior to understand how people leverage our platform, and the insights are crystal clear! Talking to customers a significant trend has emerged from our research, revealing that a whopping 22% of all questions are centered around annual planning and prioritization. When we add quarterly planning and annual budgeting into the mix, more than one-third of all the questions on Forcerank are focused on the most critical issues that our organizations face—what truly matters most.

 

Here’s a breakdown of the top categories on Forcerank:

  • Annual Priorities (21.6%): Leaders are continually using Forcerank to ensure they stay focused on their biggest long-term goals.
  • Project Priorities (18.6%): Deciding which initiatives to tackle next can be a challenge. Forcerank helps users cut through the noise and focus on projects with the most impact.
  • Idea Ranking (18.6%): Got a ton of ideas floating around? Forcerank’s intuitive ranking system ensures that the best ones rise to the top.
  • Quarterly Priorities (9.8%): Breaking down yearly goals into actionable quarterly steps is where planning meets execution.
  • Conference Topics (6.9%): Companies are using Forcerank to align on themes and topics for their most important gatherings.
  • Annual Budgeting (3.9%): Budget allocation is key to organizational success, and Forcerank is being used to make these financial decisions clearer.

While these are the major players, other notable categories include Mission Statements, Weekly Priorities, and even Complexity Evaluations—showing the versatility of Forcerank to handle everything from the highly strategic to the tactical.

Unlock New Ways to Use Forcerank in Your Organization

As you can see, planning and prioritization dominate Forcerank activity. But that’s just the tip of the iceberg. Let’s explore some of the cool ways Forcerank can help your organization make data-driven decisions, fast.

1. Streamline Strategic Planning

With over 1 in 5 questions related to annual priorities, it’s clear that users rely on Forcerank to focus on the “big picture.” Whether you’re planning for the upcoming year or rethinking your long-term objectives, Forcerank can help your team rank strategic goals based on collective input, ensuring alignment from top leadership down to individual contributors.

2. Tackle Project Overload

When you have too many projects on the table, Forcerank helps to sort through the chaos. By gathering input from across the team, you can identify which projects should be prioritized and which ones can wait. No more endless debates about which initiatives are truly essential!

3. Budget with Confidence

Allocating budgets can be tricky, especially when everyone has a different opinion about where the money should go. Forcerank’s annual budgeting category gives your team a platform to weigh the pros and cons of each spending area, ensuring that funds are allocated to the most critical needs.

4. Optimize Conference Planning

Getting everyone on the same page for big events like conferences can be daunting. Whether it’s deciding on the main themes, speakers, or breakout sessions, Forcerank gives you the power to engage stakeholders early and reach consensus efficiently.

5. Evaluate New Ideas

Forcerank is not just about planning and priorities. With almost 20% of votes going to Idea Ranking, it’s also the perfect tool for innovation. Let the best ideas from across your organization surface naturally, ensuring that everyone’s voice is heard and the most impactful ideas are pursued.

6. Assess Candidates and Complexities

From ranking candidates for key positions to evaluating the complexity of new projects, Forcerank can help you navigate hiring decisions and project feasibility with objective, data-driven results.

7. Enhance Fun and Culture

You might not expect it, but 2.9% of votes relate to topics just for fun! Forcerank helps teams stay engaged by offering a platform to rank fun ideas, team-building events, and cultural improvements, showing that it’s not all just work—there’s time to foster company culture too.

The Takeaway

Forcerank is more than just a ranking tool; it’s a platform that helps organizations align on their most critical decisions, from long-term strategy to budgeting, from project management to innovation. The data shows us that prioritization is top of mind for many of you, and Forcerank is the best way to ensure that your team’s priorities are not just set—but agreed upon.

As we hit 100,000 votes, there’s never been a better time to explore all the ways Forcerank can transform how your team approaches decision-making. Whether it’s for strategic planning, project prioritization, or sparking new ideas, Forcerank puts the power of collective insight in your hands.

Are you ready to make your next big decision with confidence? Start using Forcerank today and watch your team’s priorities come into clear focus.

 

 

more

Topics: Decision Analysis

But what IS the Minimum Lovable Product?

Posted by Jeff Dwyer

Mar 30, 2014 5:42:00 PM

1932367_586020724821528_1670933366_n

You've probably seen this adorable image already and if it won't convince you, nothing will. So we'll start from an assumption that you're trying to make something lovable. But what does that really mean? I'm trying to release a large new feature for my product. I want to get it into beta as quickly as possible. Do I ship what we have? Does it need "just-one-more-thing?" 4 more things? 10? There are 18 important features I can think of off the top of my head that it doesn't have. Which ones do we build before Beta? What is the minimum lovable product?

Oh and I'm on a team with 5 other extremely talented and opinionated people who've sat in on the same user tests of the Alpha as well. They probably have some opinions too... So what do we do? And how do we avoid a 3 hour planning meeting?

Here's how to decide what features to build:

  1. Get all the options on the table. 
  2. Have everyone think hard about the problem by themselves.
  3. Have everyone propose a prioritized plan of action. We need everyone to wrestle with the trade-offs and put a stick in the ground, because it's only by wrestling with these choices ourselves and seeing that there's no one right answer that we will be able to accept a final plan that we may not entirely agree with.
  4. Compare the results. Analyze outlier opinions. Look for agreement.
  5. Put together a plan. (Together if possible, or just have Directly Responsible Individual do it)

Let's see what this process looks like if we use ForceRank to coordinate. First we'll build a questions and define a list of choices. In this case it's all the possible features we could build. We also add a "Release Beta" choice and tell people to prioritize it at the point where they think we should release.

Screen_Shot_2014-03-30_at_5.41.23_PM

 

Then we just send an email to our colleague and they can jump right in and start ranking the choices.

Screen_Shot_2014-03-30_at_4.38.03_PM

Success! Now we have responses from my 5 colleagues. You can see the overall preferences of the group on the right. The results are colored so that we can easily see outliers. It looks like Mike and I generally agree. But you can see that when I hover over the second choice on Mike's list I actually ranked it much much lower. Sounds like we should discuss that one.

 

Screen_Shot_2014-03-30_at_4.38.56_PM

Mike and I generally agreed, but if we compare my opinions to Chase's we can see that there are some real differences. Indeed the groups 17th priority was something Chase thought should be #4! Since Chase is the UX expert, it sounds like perhaps the engineers need to understand why we're rating those things on the bottom.

Screen_Shot_2014-03-30_at_4.39.13_PM

Finally we can also compare everyone's results against the overall scores as calculated by our algorithm.

Screen_Shot_2014-03-30_at_4.40.03_PM

I hope this has given you a good idea for how to systematize the discussions you have around feature development for your product. The goal is to have smarter, better, faster discussions. Using a system like this you'll find you don't even need to discuss some options because they're either unanimously important or unimportant. On the flip side, the major disconnects in your group will, quite literally, glow red and allow you to focus in directly on what matters.

Try ForceRank Free

Happy Product Releasing to You!

 

more

Topics: Decision Analysis, Product Design

Counting Votes Is Hard

Posted by Jeff Dwyer

Feb 9, 2014 1:22:00 PM

It all started one day when we tried to count the votes.

So you know how ForceRank.it works right? Your group ranks all the choices, then we add up how many points each choice gets and boom, we show which choice is the most popular.

Right?

Well, it turns out that this is one of those cases where "the obvious way" can produce very unintuitive (and hence arguably "wrong") results.

How is that possible?

Let's see an example. This is a poll that one of our users created to figure out what topic should be the subject of his tech talk. Give it a quick look and you'll see that three out of four people had the same first choice. So picking a winner should be easy right?

Screen_Shot_2014-02-09_at_12.43.23_PM

But that's not what happened. 

The first version of our algorithm picked "Mapreduce and KIR" as the winner. How is that possible you ask? Well, let's do the math together and add up how many points each option should get. I'll highlight just those options below.

Screen_Shot_2014-02-09_at_12.45.29_PM

So with 9 options each, "Mapreduce and KIR" gets: 9 points from Matt, 7 from Jessica, 8 from James and 6 from Greg, totalling 30.

And Newbie HBase gets: 1 from Matt, 9 from Jessica, 9 from James and 9 from Greg, totalling 28.

Hrrmph

We dubbed this the "Matt Ball" effect, but the more canonical description is that our algorithm has failed the "Majority Criterion", which states: "if one candidate is preferred by a majority (more than 50%) of voters, then that candidate must win".

So what did we do?

Well, we went to the wikipedia and dug into Voting Systems. Unsurprisingly it turns out that there's been a lot of high quality thinking on this subject. We looked into a number of methods and the one that seems like it is the best fit for ForceRank was Schulze Method. In a nutshell, Schulze breaks down the voting into a ton of mini ranking between each combination of options, what they call a "pairwise-analysis". Next it does a neat bit of graph magic to pull out a series of winners.

The result, is that it is guaranteed to ace the "Majority Criterion" (which our previous method failed) and a number of other conditions as well.

The only real downside is that Schulze method is a bit more difficult to explain, but at the end of the day it delivers an answer that feels much more intuitively like the "fair" winner of a vote.

Screen_Shot_2014-02-09_at_12.56.07_PM

Next Up?

Next on our list is building in ways to see the patterns in your group's rankings. There's a lot of really interesting information to be gleaned from the data that ForceRank provides and it's our goal to help you get a quick and easy to comprehend understanding of the complex nature of your groups preferences, and the outliers within.

Try ForceRank

more

Topics: Tech, Decision Analysis


   

What is ForceRank?

ForceRank is a prioritization tool for product managers. It helps people identify priorities, make tradeoffs, compare results and finalize a plan.

Try ForceRank

Recent Posts

Recent Posts

Follow Us