Rating Widget field type (showing total and average of individual ratings), e.g. Star rating, Thumbs up/down, Likes, etc

Ideas & Features
1

Current User Experience Tensions and Limitations:

In the existing Fibery setup, while we have powerful tools to capture and organize information, there’s a noticeable gap in capturing granular feedback. Single select fields, while useful, can only store one value at a time, making it challenging to aggregate feedback from multiple users or compute averages. This limitation hinders our ability to provide a holistic view of user sentiment, especially for project teams aiming to collect and analyze feedback from various stakeholders.

Proposal: Rating Widget

What? A dedicated rating widget that allows users to provide feedback on a scale (e.g., 1-5 stars). This widget would automatically aggregate individual ratings, display an average, and show the total number of ratings.

Why & Benefits?

  • Aggregation & Averages: The widget can automatically aggregate individual ratings and display an average, offering a holistic and quantifiable view of user sentiment.
  • Granular Feedback: Enables users to provide more nuanced feedback compared to binary or categorical options.
  • Alignment with Strategy: As Fibery shifts its focus towards product teams and emphasizes feedback and insights management, this widget directly supports these core use cases. It aids in the collection of feedback, organization of insights, and prioritization of work based on feedback.
  • Enhanced User Engagement: A simple and intuitive way to engage users and gather feedback can lead to increased user interaction and satisfaction.

How Rating Widgets support Fibery’s New Positioning

  • Target Audience Focus:
    • Fibery’s repositioning emphasizes serving product teams.
    • Rating widgets cater directly to these teams’ needs for nuanced feedback.
  • Feedback & Insights Management:
    • The platform’s core is about capturing, aggregating, and prioritizing feedback.
    • Rating widgets provide a streamlined method to capture graded feedback and visualize aggregated insights.
  • Filling Functional Gaps:
    • Current tools may not capture the gradient of user sentiment effectively.
    • Rating widgets offer a more comprehensive solution, capturing a spectrum of feedback.
  • Reinforcing Commitment:
    • Introducing such widgets showcases Fibery’s dedication to evolving based on user needs.
    • It strengthens the platform’s promise to be the definitive tool for product teams.

Use Cases

Since I wear different hats in my projects, I will list the cases as user stories:

1. Feature Proposals:

  • Tension: As a Maintainer, gauging collective sentiment on feature proposals is challenging.
  • Resolution: Rating widgets capture individual feedback and provide an average, clarifying community preferences.

2. Insight Prioritization:

  • Tension: As a Contributor, scattered feedback makes prioritizing insights tough.
  • Resolution: Rating widgets offer a clear average sentiment, aiding effective prioritization.

3. Community Engagement:

  • Tension: As a Community Manager, I need more than a single value to understand community emotions.
  • Resolution: Rating widgets capture a range of feelings, enriching engagement data.

4. Continuous Refinement:

  • Tension: As a Project Member, select lists don’t aggregate community feedback effectively.
  • Resolution: Rating widgets show clear averages of community sentiments, guiding project improvements.
2

@Yuri_BC is the feature request about a dedicated UI feature for rating? Or can it be considered similar to a rating field? Stars or Rating Field Type

3

The other topic you refer to is as far as I see just a single select field.

My feature request here is about the submission and aggregation of individual user ratings, so that it also show the average or total of those ratings of all submissions.

There is a workaround but thats pretty complex: see No formula option available for Rule Action Filter which works for me.

In a system that can collect all individual submissions of a single select field of all users, such a submission is often called ‘flagging’ being a standalone instance that relates the current entity, the user and the submission value together, and allows to display things like totals and averages. This is a generic functionality that can be used for star rating, voting, moods, likes, thumbs up/down, spam flagging, plusone, etc.

This is such a widely used feature in collaboration, that the lack of it in Fibery is surprising to me. That is also why there is no ‘Like’ button in Fibery.

4

The way that Fibery works, entities are not ‘aware’ of other entities unless linked together in some way.
There is no way to add a calculation on the entity level that aggregates values from across all other entities in that database, unless each entity in the database is related to every other entity in that database :grimacing:

If you need aggregation calculations based on a subset of entities, then these entities need to be related in some way.
For example if you have Submission entities, each with an Importance value, and some Submissions are linked to a Feature, then you can have a formula on the Feature level to calculate the average Importance, e.g. Submissions.Avg(Importance)
If you want to have this value show on the Submission entities themselves, you can either add a lookup to the above solution, or you can calculate directly, e.g. Feature.Submissions.Avg(Importance)

If you want analytics across a whole database, then report view is the way to go.

1 Like