Non-disruptive Feedback System Using Preliminary Action
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing feedback systems interrupt users while they are using applications, consuming additional processing power and degrading user experience and hardware performance, which negatively impacts the quality of feedback.
Innovation Solution
A non-disruptive feedback integration system that detects specific events, captures system context, and allows users to provide feedback at a convenient time, reducing resource consumption and improving user experience by avoiding interruptive feedback operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If interruptive feedback operations are used to obtain user feedback, then feedback can be obtained, but user experience is degraded and processing resources are consumed
Solution Approach 1:
The system performs preliminary actions by detecting feedback triggers and capturing system context (screenshots, metadata, event information) before the user is prompted. This preparation is done in the background without interrupting the user's workflow, so when feedback is requested, all necessary information is already gathered and ready for immediate presentation.
Solution Approach 2:
The system introduces an intermediary layer that sits between the feedback request and the user. Instead of directly interrupting the user with feedback requests, the system uses trigger detection and context capture as intermediaries to prepare feedback opportunities, allowing users to provide feedback at convenient moments rather than being forced to stop their current tasks.
2Reliability
If interruptive feedback operations are used to obtain user feedback, then feedback can be obtained, but hardware performance is degraded
Solution Approach 1:
The system performs resource-intensive operations (screenshot capture, metadata collection, event tracking) as preliminary actions in the background before feedback is actually needed. This ensures that when feedback requests are made, the heavy lifting has already been completed, minimizing real-time resource consumption and avoiding performance degradation during critical application operations.
Solution Approach 2:
The system uses periodic trigger detection to determine when feedback opportunities arise, rather than continuously monitoring or constantly prompting users. By detecting specific events or time-based triggers, the system activates feedback collection only when appropriate, reducing overall processing load and allowing the application to maintain optimal performance between feedback events.
3Ease of operation
If interruptive feedback operations are used to obtain user feedback, then feedback can be obtained, but the feedback quality is degraded
Solution Approach 1:
The system uses feedback about user behavior (trigger events, application state, usage patterns) to intelligently determine when and what type of feedback to request. By analyzing this behavioral feedback, the system can present relevant feedback questions at appropriate moments, improving both user convenience and feedback quality by avoiding irrelevant or poorly-timed feedback requests.
Solution Approach 2:
The system captures system context (screenshots, metadata, event information) in advance before users are prompted for feedback. This preliminary capture ensures that when users do provide feedback, they have the necessary context readily available, leading to more thoughtful and higher-quality responses without requiring users to remember or reconstruct the original situation.
Data Source
AI summary
Disclosed herein are system, method, and computer program product embodiments for obtaining feedback in an explicit, non-disruptive manner. An embodiment operates by determining a trigger corresponding to a feedback event, where the trigger is associated with a particular application that is registered with a feedback application associated with the feedback event; detecting an application event corresponding to the trigger occurs during an execution of the particular application; receiving a screenshot of a user interface of the particular application at a time of the detecting; providing a notification indicating that feedback corresponding to the application event is requested; receiving a request to launch the feedback event; and receiving feedback corresponding to the feedback event via the feedback application.