Day 202: First Browserflow Feedback

After I onboarded my friend Shiva to Browserflow, he sent along this doc with feedback:

It’s. Amazing.

Usually, when people make suggestions, it’s often not that useful. It’s only natural — designing a product requires a different way of looking at things than simply using it, so people often make suggestions that make sense at a micro-level but don’t make sense in the context of the entire system. Everyone’s great at identifying their problems, but not everyone’s great at identifying the solutions.

So it’s super exciting to get feedback from someone with good product sense because they have an eye for how things should be based on their experience using, analyzing, and designing many other products.

Shiva’s feedback is awesome because it’s concrete, actionable, and they all make sense. Many of the points he made were things that I knew I had to do, but having him point them out gave me the motivation to go ahead and hurry it up because it was clearly a pain point. I could tolerate looking at GET_TEXT and FOR_EACH because I’ve gotten used to them, so getting a reminder that they are really not that user-friendly was great. The product feels so much better already after implementing just that change:

Before:

After:

Really stoked on this new “get feedback and make changes based on it” stage of Browserflow’s development because it’s going to improve usability a ton.