Feedback in Pipelines

Here are some examples of rules and processes that can be created for receiving and ingesting user feedback in the Hedera Guardian application.

Examples of Rules and Processes when receiving feedback

Define feedback channels

Define the channels through which users can provide feedback, such as email, chatbot, in-app feedback forms, social media, or any other channels that are relevant to Hedera Guardian application.

Feedback forms are better ways to collect feedback. Here are some of the key benefits of implementing feedback forms for collecting feedback:

  • Ease of use: Feedback forms are easy to use for customers, as they don't require any special knowledge or technical skills. Users can simply fill out the form and submit it, making the process simple and streamlined.

  • Consistency: Feedback forms provide a consistent way to collect feedback, ensuring that all responses are organized and structured in the same way. This makes it easier to analyze the feedback and identify common themes or issues.

  • Efficiency: Collecting feedback through a form is often more efficient than other methods, such as phone or email. It allows customers to provide feedback at their own convenience, without the need for real-time interaction with a customer support representative.

  • Accuracy: Feedback forms can help to ensure that the feedback received is accurate and complete. The form can include specific questions and prompts to guide users in providing detailed and specific feedback, reducing the risk of misunderstandings or incomplete information.

  • Data analysis: Feedback forms can be easily analyzed using automated tools and software, allowing businesses to quickly identify patterns and trends in customer feedback. This can help businesses to make data-driven decisions and improve their products or services.

Overall, implementing feedback forms is an effective way to collect and analyze feedback, providing valuable insights into the needs and preferences of customers.

  1. JotForm is better suited for the Guardian application system, because it is a cloud-based form builder that allows users to create custom forms for a variety of purposes, including collecting feedback. Here is how it works:

    • Creating a form: Users can choose from a variety of pre-designed templates or start from scratch to create their own custom form. They can add different form fields, such as multiple-choice questions, text fields, and rating scales, and customize the form's design to match their branding.

    • Sharing the form: Once the form is created, users can share it with their audience through different methods, such as embedding it on their website, sending a link via email, or sharing it on social media.

    • Collecting responses: As users' audience fills out the form, JotForm collects the responses in a centralized location. Users can view the responses in real-time and analyze the data using JotForm's built-in reporting and analytics tools.

    • Integrating with other tools: JotForm integrates with a variety of other tools, such as Google Sheets, Salesforce, and Mailchimp, making it easy for users to automate their feedback collection and follow-up processes.

Link to illustration video : https://www.youtube.com/watch?v=VwC6g5Ym0RQ

Overall, JotForm provides a user-friendly and customizable solution for collecting feedback, with robust reporting and integrations to help users make the most of their feedback data.

Establish feedback guidelines

Establish guidelines for users to follow when providing feedback, such as being clear and specific about the issue, providing steps to reproduce it, and avoiding profanity or inappropriate language.

Here are the model guidelines for Hedera Guardian application.

At Hedera Guardian, we value your feedback and strive to continuously improve our application. To ensure that your feedback is actionable and can help us make meaningful changes, we ask that you follow these guidelines when submitting feedback:

  • Be clear and specific: When submitting feedback, please be as clear and specific as possible about the issue you're experiencing or the feature you'd like to see. This helps us understand the problem or request and determine the best course of action.

  • Provide steps to reproduce: If you're experiencing a bug or issue, please provide clear and concise steps to reproduce it. This helps us identify the root cause of the issue and work towards a resolution.

  • Avoid profanity or inappropriate language: We want to create a positive and respectful community for everyone using our application. Please refrain from using profanity or inappropriate language when submitting feedback.

  • Be constructive: Feedback is most valuable when it's constructive and offers suggestions for improvement. Please provide actionable and specific suggestions for how we can improve the application.

  • Include relevant details: If applicable, please include relevant details such as the version of the application you're using, the device you're using, and any error messages you're receiving.

By following these guidelines, you can help us improve Hedera Guardian and provide a better experience for all users. Thank you for your feedback and support.

Categorize feedback

Develop a taxonomy for categorizing feedback based on the type, severity, and source of the feedback. This can help in prioritizing feedback and identifying areas that require immediate attention.

Give users the option of selecting a category or tag when they submit feedback. For example, tags could be "bug report," "feature request," or "general feedback."

For Hedera Guardian application, here's a possible taxonomy for categorizing feedback based on type, severity, and source:

Type:

  • Bug report: Feedback that identifies a problem or issue with the application.

  • Feature request: Feedback that suggests a new feature or improvement to an existing feature.

  • General feedback: Feedback that does not fit into the other categories.

Severity:

  • Critical: Feedback that identifies a severe problem that prevents the user from using the application.

  • Major: Feedback that identifies a significant problem that affects the user experience but does not prevent usage.

  • Minor: Feedback that identifies a minor problem or a suggestion for improvement that does not significantly impact the user experience.

Source:

  • User feedback: Feedback submitted by users of the application.

  • Internal feedback: Feedback from internal stakeholders such as developers, testers, or project managers.

  • Customer support feedback: Feedback received through customer support interactions.

Security:

  • Feedback related to security vulnerabilities or concerns.

Performance:

  • Feedback related to the speed or efficiency of the application.

User interface:

  • Feedback related to the visual design or usability of the application.

Integrations:

  • Feedback related to the integration of the application with other tools or systems.

Documentation:

  • Feedback related to the documentation or help resources for the application.

Note: When collecting feedback, users should be prompted to select the appropriate category or tag to help prioritize and route the feedback to the appropriate team or individual for review and action.

Set up a feedback tracking system

Use a ticketing system to capture and organize user feedback. Assign each feedback item a unique ID and track its status throughout the feedback pipeline.

Here is an example of how to set up a feedback-tracking system for Hedera Guardian application:

  • Choose a feedback-tracking tool: There are many feedback-tracking tools available such as Trello, Asana, Jira, etc. But for the Hedera Guardian application Trello is recommend since it is very simple to learn and particularly, operate.

  • Create a feedback board: Create a board or a project in the feedback-tracking tool Trello and set it up with the necessary columns such as "To Do," "In Progress," "Completed," etc.

  • Add categories or tags: Add categories or tags to the feedback board to help categorize the feedback. As mentioned earlier, tags could be "bug report," "feature request," or "general feedback," or other categories relevant to your project.

  • Link feedback submission form (JotForm) to the feedback board: Link the feedback submission form to the feedback board using the tool's integration options. For example, if you are using Trello, you can use the Trello Power-Up to link the form to the board. Here is the link to refer to the Trello board integration with JotForm.

Assign feedback ownership

After the Trello board has been set up, assign ownership of feedback to specific team members or departments, such as product management or development, to ensure that feedback is acted upon in a timely manner.

Prioritize feedback

Prioritize feedback based on its severity, frequency, and impact on the user experience and your business goals. This can help in identifying critical issues that require immediate attention.

Monitor feedback progress

Monitor the progress of feedback items in the feedback board. Make sure that feedback items are moving through the columns and that team members are taking appropriate actions.

Close feedback items

When a feedback item is resolved, close it in the feedback board. This will help keep the board clean and ensure that team members are focused on active feedback items.

Analyze feedback trends

Use the feedback board to analyze feedback trends. Look for common themes in feedback items and use this information to prioritize future development efforts.

Provide feedback to users

Keep users informed about the progress of their feedback items. Send them regular updates on the status of their feedback and let them know when it has been resolved.

By creating the above rules and processes, it can be ensured that user feedback is collected, categorized, and acted upon in a timely and efficient manner, leading to a better user experience for the Guardian application.

Implementation

JotForm Account Setup

Step 1 :Create a profile on JotForm website and Login

https://www.jotform.com/

Step 2: Click on "Create Form"

Step 3: Click on (Start from Scratch)

Step 4: Select form Layout ( Classic Form )

Step 5: Add a logo for your organization

Step 6: Update the “Form” object to create a form heading

Step 7: Add different objects on your form by selecting from the options on the left hand side panel

Eventually the form should look like this

Note : A more HGF specific form should look like this

Step 8 : Publish the form

\

COPY LINK will give you the following url https://form.jotform.com/231232735256452

Note : This link can be placed on the Guardian application’s home page using a button or a link.

Step 9: Access the form by pasting the above url in the browser, and then populate & submit the form.

The above submission will send an email to the recipient.

The above submission will ALSO send an email to the sender..

Step 10: Check and verify the submitted data- Method 1

\

Step 11:Check and verify the submitted data- Method2

Trello Account Setup

Step 1 :Create a profile on Trello website and Login. Here's a step-by-step guide to creating a profile on the Trello website: https://www.trello.com/

Create Trello User Profile

1. Open your web browser and go to the Trello website (https://trello.com).

2. Click on the "Sign Up" or “Get Trello for free” button in the upper right corner of the screen.

Step 3: You will be prompted to create your account using a number of options. Select one of them to continue.

Step 4. Trello will send you a confirmation email to the email address you provided. Check your inbox and click on the confirmation link in the email to verify your account.

Step 5. Once your account is verified, you will be redirected to the Trello website. You can now start using Trello to create boards, lists, cards, and collaborate with others.

Create Trello Workspace

Step 1: After signing in to your account, create a "Workspace"

Step 2: Enter a name for your new Workspace, and choose the Workspace type.

Step 3: Click on the "Continue" button to create the Workspace.

Step 4: Once your Workspace is created, you can invite members to join it, create boards, lists, and cards, and start collaborating with your team.

Create Trello Board

Step 1: Click on the “Board” button displayed under a Workspace in the Trello interface.

Step 2: Click on “Create Your First Board”.

Step 3: Enter a name for your new board and click on the “Create” button.

Create Tags

Step 1: Create tags like "bug report," "feature request," or "general feedback," or other categories relevant to your project.

Step 2: Add categories or tags to the feedback board to help categorize the feedback.

JotForm and Trello Integration

Integrating JotForm with Trello can be a useful way to streamline your workflow and keep your team organized. Here is the summary of steps to do it, which we will elaborate in connection with the Hedera Guardian application.

Step 1: First, you need to have a JotForm account and a Trello account. If you don't have one, sign up for both.

Step 2: In JotForm, go to the form that you want to integrate with Trello. Click on the "Settings" button in the top menu, and then select "Integrations".

Step 3: In the Integrations menu, look for the Trello icon and click on it. Then, click the "Authenticate" button.

Step 4: A popup page will open in a separate window asking to check if you want to give Trello access to JotForm. Click on the “Allow” button.

Step 5: Select what type of integration you want, a.Create Card or b.Update Card. Select ”Create Card”.

Step 6: Select the board to which you want to create the card. Since it has integrated with Trello hence will show the list of Boards from Trello. Select “HGF_BOARD” board.

Step 7: Select a list from this board. Choose “To Do”

Step 8: Enter the field matching between JotForm and Trello. Finally click on “COMPLETE INTEGRATION”

Step 8: Click on “FINISH” button to complete the integration process.

Test the integration

Step 1: Fill in the feedback form at https://form.jotform.com/231232735256452 and submit.

Check the Trello board. There should be an entry done via integration.