Sign up to save your podcasts
Or
Share Why Should They Use Our App/Feature? - Part 3 of 4 Part Series SA- 68
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Why Should They Use Our App/Feature? - Part 3 of 4 Part Series SA- 68
One of the key challenges, let's assume we develop an application and it is done. The key question is why should the internal users actually use it. Only if that question is answered in their minds very clearly, they're going to use the application. To inspire users to use it the following are some interesting insights
varadharajan srinivasan says - For me to explain the problem, I have to be in the right context of explaining the problem that they see as a problem. ? Are you in the right context of understanding the problem?
Deepak Sharma says- If you are able to connect to the scenario of the end user, the context. "Walking the Gemba" from lean, which is you are in the situation with that user and experiencing what they are actually experiencing in the day-to-day. Explain the developed feature contributes to the solution of that scenario only then the solution would make sense to them.
Sidambara Raja Krishnaraj says - To get the scenario right two popular tools help immensely. One is "Jobs to be done" and the other is "Value stream mapping". Also eliciting the "what is in it for me" for the user we're trying to provide. Using cocreating with the users to build a vision for the future for the solution and upcoming features. Prepare them well ahead before release.
Kumaran Anandan says- The insights shared by leader Nagaraja Srivatsan in how a Wall Street Journal article on adopting AI in retail and its relevance in healthcare and AI. Appeal to the user's identity and purpose as a person Every individual wants to be a better version of themselves. So this person sitting as a data entry person, you'd say you can be a much kinder, nice, caring person by making sure that you enter the data correctly. Because if you enter the data wrong, somebody's health will be affected. Convey to them - "You are a protector of somebody's health. Now to protect that person. This feature will help you." Finally, the context is about the user and not the feature.
View all episodes
By Tiny MagiqOne of the key challenges, let's assume we develop an application and it is done. The key question is why should the internal users actually use it. Only if that question is answered in their minds very clearly, they're going to use the application. To inspire users to use it the following are some interesting insights
varadharajan srinivasan says - For me to explain the problem, I have to be in the right context of explaining the problem that they see as a problem. ? Are you in the right context of understanding the problem?
Deepak Sharma says- If you are able to connect to the scenario of the end user, the context. "Walking the Gemba" from lean, which is you are in the situation with that user and experiencing what they are actually experiencing in the day-to-day. Explain the developed feature contributes to the solution of that scenario only then the solution would make sense to them.
Sidambara Raja Krishnaraj says - To get the scenario right two popular tools help immensely. One is "Jobs to be done" and the other is "Value stream mapping". Also eliciting the "what is in it for me" for the user we're trying to provide. Using cocreating with the users to build a vision for the future for the solution and upcoming features. Prepare them well ahead before release.
Kumaran Anandan says- The insights shared by leader Nagaraja Srivatsan in how a Wall Street Journal article on adopting AI in retail and its relevance in healthcare and AI. Appeal to the user's identity and purpose as a person Every individual wants to be a better version of themselves. So this person sitting as a data entry person, you'd say you can be a much kinder, nice, caring person by making sure that you enter the data correctly. Because if you enter the data wrong, somebody's health will be affected. Convey to them - "You are a protector of somebody's health. Now to protect that person. This feature will help you." Finally, the context is about the user and not the feature.