After Alpha release, we plan to update you on the latest goings-on within the Rayo product. Currently, we have two "tribes" underneath our accessibility tool umbrella - Rayo browser and Rayo browser plugin.
Below is how we've progressed.
Post-Alpha release
We gathered up with Giang Nguyen to gain some in-depth insights into the technical aspects of the Rayo Alpha browser. From a user's perspective, our first version might need to level up a bit - That's why we decided to spend more time in the research and development of the browser product.
In the meantime, we also wanted to validate our market with a browser plugin. Here are some advantages we considered:
Faster to ship and iterate
Great to optimize for user experience and retention with the right features
The 5Ws Framework
Along with the benefits when choosing an extension-first strategy, we were also aware that a plugin needs to be light and fast and can serve the itchy pain points of our users.
Therefore, when Dung and I brainstormed the feature set for the browser plugin, we considered the following:
What is this?
What is the benefit for the user?
What should they do next?
To make our brainstorming process more structured and less painful, we applied the 5Ws questioning framework, which considers a feature from a perspective of Who, Where, When, What and Why.
Who: Who will be the users? What is their persona?
Where: Where will this feature be used? Under what context will it be used?
When: When will this feature be used?
What: What is this feature?
Why: Why do we need this feature in the first place? What is the user's goal? What is the user's need? Does the feature relieve a pain point for the user?
The Setup and Prioritization
We created five sections in Miro and write down Who, Where, When, and What as titles. Then we allowed ourselves to spend 5 minutes on each section.
After What, product features began to emerge, and we ended our brainstorm section by using insights collected from various prior user research and testing to answer the Why section.
To prioritize features, we applied the RICE scoring model, which stands for Reach, Impact, Confidence and Effort.
Reach: the number of people this feature can solve within a month
Impact: to what degree this feature can solve a user's pain points
Confidence: to what degree we are confident about the data and facts we already had
Effort: the cost and time it takes to build this feature
Bottom Lines
Despite all ups and downs, we pretty much enjoyed the process. We are now teaming up with Shiny, a browser extension expert in India to build the first version of the Rayo plugin. We cannot wait to update with you on our progress!
If you're excited to hear more from us, or is there's anything we could share more of, feel free to let us know via the comment section below!
Comentários