11
7 Comments

How to filter user feedback and decide what to build?

I'm sure you've moved into a flat at some point in your life.

There is a ton of stuff to consider beforehand; buying a fridge, making sure the bed fits your room, activating the electricity and so on...

All these are fundamental pieces that you need to be able to live in your flat.

If you rush yourself to buy any-and-every-thing, you'll soon realise that you don't need all that stuff! Like that IKEA milk foamer?

You first need to live there to understand what is missing; if existed, your life would be easier.

The same logic applies to building a lean digital product! There is many nice-to-have features you can develop (e.g. it'd be nice to add green color here)

Key is to differentiate nice-to-have features from must-haves if you want to build a lean product.

At Scrintal, we follow these 3 steps to prioritise what to build next:

#1: Ask qualitative questions to understand the problem

When someone wants to have a specific feature, we ask what is the underlying problem that they are trying to solve? If you know the real problem, the solution might be different and more effective than what the person thinks.

Perhaps dark mode is not a key factor in making some choose your tool over another one.

#2: Do others want the same thing?

We've kept Scrintal v.1 simple and lean. You can create Zettelkasten cards on an infinite canvas, write on them and connect.

90% of our users said they'd like to add images to cards because they work visually. So if we wanted Scrintal to serve their workflow, implementing this feature became a no-brainer. More urgent than the dark mode :)

#3: Decide together as a team

This is inspired by Micheal Siebel's video on how to build a product as a small startup.

We categorise all the feedback together as a team. Everyone voices their suggestion. We discuss why we think a feature set is more important than the other that requires prioritisation. We decide together what to build next. So everyones' voice is heard!

If you find this helpful, you can learn similar actionable insights on our blog and Twitter.

Have a clear filtering mechanism! Always question if that ONE Thing will make your life easier by solving a problem.

posted to Icon for group Ideas and Validation
Ideas and Validation
on January 13, 2022
  1. 2

    Thank you for sharing, Arda! I'm curious, what type of tools do you use within your team to keep track of these feature requests from users?

    1. 1

      Hello Kurt! Thanks for the question! We use only Scrintal as it is the web app we're building. So we consolidate, cluster and prioritise feature requests on Scrintal over an infinite digital whiteboard. That way we can zoom in and out to see the details and big picture at the same time.

      Obviously this is a biased answer but I hope it helps :)

      1. 1

        Thanks! Immediately after I sent that comment I realized that you likely use your own product. :-) Very cool! Thanks again for sharing.

        1. 1

          My pleasure Kurt :) Hit me up if you have any other questions. Take care!

  2. 2

    The Michael Siebel video 🙌

Trending on Indie Hackers
From Ideas to a Content Factory: The Rise of SuperMaker AI User Avatar 27 comments Why Early-Stage Founders Should Consider Skipping Prior Art Searches for Their Patent Applications User Avatar 21 comments Codenhack Beta — Full Access + Referral User Avatar 19 comments I built eSIMKitStore — helping travelers stay online with instant QR-based eSIMs 🌍 User Avatar 18 comments Building something...? User Avatar 12 comments Day 6 - Slow days as a solo founder User Avatar 11 comments