Reflection Assignment - Storytelling

Challenge   As an IT analyst in the hospitality industry, I support the providers and clinicians using the  electronic health record.  It is not uncommon to hear about occasional slowness using the  software that supports the electronic health record. There are times when we need to dive  further when the excessive slowness occurs with the department as a whole. The challenge is  to find out what causes the slowness which can be the workflow performed, the user error,  hospital network, or even the application itself and then understand what can be changed to  provide the users with what they need and relieve the frustrations being experienced. The  stakeholders needed to buy in with having IT staff and ER staff working together to solve the  problem and even possibly provide a better solution.       Selection  The best way to see what is really happening is using the storytelling tool to really get into the  situation of the users, making sure their goals are being met for what they need to accomplish in  their daily work and not take away anything from the patient care experience.  Really finding out  “What is?” to then further investigate to see what we can get to work. As discussed in the Session 2  video on the storytell tool, using storytelling will allow us to know our audience better, understanding  workflows, and letting the stakeholders understand that the current state of slowness is not working  out, causing high frustrations.          Application  The IT staff sat down with each of the staff members, watched them perform their workflow, talked  with the staff on any slowness seen, captured recorded sessions to provide back to the software  vendor.  We also wrote down any suggestions that they would like to see to give to the vendor as  ways to improve the application. The network teams were brought in  to make sure there was  nothing going on with the network connection. Using journey mapping alongside using the  storytelling tool, we were able to sit down with the ER staff to really listen to the frustrations of the  staff, and watch their workflows so we were able to provide feedback to the staff. With all of this  information, we could inform the stakeholders on why changes needed to be made to better help the  staff have more success as well as provide information to the company that provides the software.         Insight  Using the storytelling tool, we could combine all the information gathered from the staff and then  were able to provide important insights into the stakeholders view showing how the infrastructure  and enhancements suggested from the staff needed to be improved to keep the ER staff from being  frustrated with the current state.  It was found that the network team needed to update some of their  equipment to provide the best possible outcome so it was good to include them in the storytelling.

Reflection Assignment - Storytelling

Approach  I think the Storytelling tool worked well for what we needed to accomplish, especially since we  needed to convince the stakeholders of certain things that needed to be changed to provide the  better outcome. I could see using the mind mapping tool in this process as well though, making sure  we had all our bases covered beforehand and making sure all stakeholders were involved. Having  the IT staff sit down and map out all the different questions or scenarios beforehand might have  been a good idea. The end result was that the Storytelling tool worked for what we needed.


Reflection Assignment - Storytelling Challenge As an IT analyst in the hospitality industry , I support the providers and clinicians using the electronic health record . It is not uncommon to hear about occasional slowness using the software that supports the electronic health record . There are times when we need to dive further when the excessive slowness occurs with the department as a whole . The challenge is to find out what causes the slowness which can be the workflow performed , the user error , hospital network , or even the application itself and then understand what can be changed to provide the users with what they need and relieve the frustrations being experienced . The stakeholders needed to buy in with having IT staff and ER staff working together to solve the problem and even possibly provide a better solution . Selection The best way to see what is really happening is using the storytelling tool to really get into the situation of the users , making sure their goals are being met for what they need to accomplish in their daily work and not take away anything from the patient care experience . Really finding out “ What is ? ” to then further investigate to see what we can get to work . As discussed in the Session 2 video on the storytell tool , using storytelling will allow us to know our audience better , understanding workflows , and letting the stakeholders understand that the current state of slowness is not working out , causing high frustrations . Application The IT staff sat down with each of the staff members , watched them perform their workflow , talked with the staff on any slowness seen , captured recorded sessions to provide back to the software vendor . We also wrote down any suggestions that they would like to see to give to the vendor as ways to improve the application . The network teams were brought in to make sure there was nothing going on with the network connection . Using journey mapping alongside using the storytelling tool , we were able to sit down with the ER staff to really listen to the frustrations of the staff , and watch their workflows so we were able to provide feedback to the staff . With all of this information , we could inform the stakeholders on why changes needed to be made to better help the staff have more success as well as provide information to the company that provides the software . Insight Using the storytelling tool , we could combine all the information gathered from the staff and then were able to provide important insights into the stakeholders view showing how the infrastructure and enhancements suggested from the staff needed to be improved to keep the ER staff from being frustrated with the current state . It was found that the network team needed to update some of their equipment to provide the best possible outcome so it was good to include them in the storytelling . Reflection Assignment - Storytelling Approach I think the Storytelling tool worked well for what we needed to accomplish , especially since we needed to convince the stakeholders of certain things that needed to be changed to provide the better outcome . I could see using the mind mapping tool in this process as well though , making sure we had all our bases covered beforehand and making sure all stakeholders were involved . Having the IT staff sit down and map out all the different questions or scenarios beforehand might have been a good idea . The end result was that the Storytelling tool worked for what we needed .