How We Decide What To Build With Limited Resources
Using the Impact Effort Prioritisation Matrix to help us decide what new features to build.

“Design is a process of making dreams come true.”
–The Universal Traveler
As a product owner, product manager, UX, UI person, designer in Startup, we’re facing lots of problems but also got tones of ideas to seek a way to run and grow the business. That’s a challenges for us to decide what to build to find product market fit and making everybody dreams come true.
Before we define what features and product we’re going to build, we need to know our customer. In Cloudbreakr, we constantly observe our user from online community, forums, workplace, sales meetings, site reviews, support inboxes, Facebook. What questions do they encounter? What do they tend to do every day? What mentalities tend to hold them back? What haunts them? How do they speak? What’s their biggest challenge? What would bring them their biggest joy?

In Cloudbreakr, although we don’t have much resources, we keep sharing the problems, insights and ideas. It is important to documents those ideas and reviews it once a months. I like using Google Documents to do the product backlog when ideas are just an idea stage. Then I will copy and paste the ideas into the our Feature/Problems List, print it out and cut it into a small cards before the product design sprint meeting.

Solve Problems and Make Decisions Exercise
I take one of the methodology called Impact/Effort Matrix to help us make decisions and prioritise the features to build. It is important to let key team members to join this meeting like engineer, designer, sales & marketing, and make sure everyone understand the impact and effort of the features that we are going to build.
The Impact Effort Prioritisation Matrix (also called the Action Priority Matrix) is a decision-making exercise allowing its users to categorize ideas according to the effort needed and the potential impact.
Read more: https://www.tuzzit.com/en/canvas/impact_effort_prioritisation_matrix

The four sections of the matrix are:
- QUICK WINS (HIGH IMPACT, LOW EFFORT)
These are the most attractive ideas/projects, giving you a good return for relatively little effort. - MAJOR PROJECTS (HIGH IMPACT, HIGH EFFORT)
While these give good returns, they take a long time to complete and can be complex to execute. - WAIT (LOW IMPACT, LOW EFFORT)
Don’t worry too much about doing these — if you’ve got spare time, do them. - DON’T DO (LOW IMPACT, HIGH EFFORT)
Avoid these. Not only do they give low returns, they crowd out time which would be better used elsewhere.

Key takeaways
At the end of the meeting, we’ll leave with: What we’re going to build; Why we’re doing it (problems you’re trying to solve) and What success looks like(quantitatively and qualitatively). Then I will document it immediately and send to every team members. This document helps keep myself and my team focused and prevent design creep: if it doesn’t solve the problem or meet the goals or impact, it doesn’t go into the product development sprint. The next step I will start writing the Job Story into Teambition and planing for the next development sprint. 🤞🏽

