Login Change Management System with Target Data Store
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing change management solutions, such as emails, are often ineffective and inefficient in promoting feature adoption and controlling feature use among users, as they can be ignored and delayed, failing to provide timely and relevant information.
Innovation Solution
A change management system that configures target data stores with administrative inputs on service provider features and messages, pushing relevant information to users at login, utilizing a change management processor to compare user status with target data and display messages based on matches and mismatches, along with customizable time thresholds.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If email is used for change management, then users can receive feature information, but users may ignore emails and feel bombarded, reducing effectiveness
Solution Approach 1:
The patent introduces a notification system that acts as an intermediary between the service provider and users. Instead of directly emailing users, the system pushes notifications through the service provider's interface (e.g., in-app notifications, banners, or messages within the application), making the information delivery more reliable and engaging while reducing email fatigue.
Solution Approach 2:
The notification system allows users to control their own information reception by providing preferences and settings where users can choose which notifications they want to receive, when, and how. This self-service approach increases user engagement while reducing the burden of unwanted information.
2Loss of information
If email is used for change management, then users can receive feature information, but there is a time delay between receiving email and utilizing the service
Solution Approach 1:
The notification system delivers feature information to users at the moment they are most likely to use the service - when they log in or are actively using the application. This preliminary action ensures users receive information right before or during feature usage, eliminating the time delay inherent in email-based communication where users may check emails hours or days later.
3Loss of information
If generic change management communication is used, then all users receive information, but the communication is not specific to user's prior and anticipated feature usage
Solution Approach 1:
The notification system implements local quality by tailoring the content, timing, and delivery method of notifications to each user's specific behavior patterns, preferences, and usage context. Different users receive different notifications based on their individual characteristics rather than a one-size-fits-all approach, making the communication highly relevant and adaptable to each user's needs.
Solution Approach 2:
The notification system is dynamic and adaptive, continuously learning from user behavior and adjusting notification strategies accordingly. The system can modify notification content, timing, and frequency based on real-time user interactions, making the communication adaptable to changing user needs and preferences rather than static and generic.
Data Source
AI summary
A system and related method for change management at login. The method includes constructing an administratively prescribed target data store as a function of received administrative input prescribing a target feature and target feature-state, and related messages to push to a user upon occurrences of target feature mismatches and matches. Login information, including a username identifier, service provider identifier, and current use time-stamp are received for a user. A historical data store is queried to obtain a user status that associates the username identifier and the service provider identifier with a previously used feature, feature-state and a previous use time-stamp. The target data store is queried for the service provider. Determinations are made as to whether previous feature use matches target feature use. Messages are displayed responsive thereto.