Data Gathering Through Observation

“Observation is a useful data gathering technique at any stage during product development” (Rogers, Sharp, & Preece, 2012). There are two types of observation in data gathering, observation in the field and observation in a controlled environment.

Reflections

Observation in the field is the best way to determine how a product will be used in day to day tasks. Knowing current state workflow and how to implement it or an improved version of it with new product use is very important. Right now the hospital I am working for is converting to Cerner’s Community Works electronic health record and health information system. I am a pharmacy analyst so I was involved in all events related to pharmacy workflow and integration with other departments last week. Cerner consultants came one site and went over our current state workflows to be able to decide which features would be suite our facility. During these events they observed a day in the life at the Crisp Regional Hospital Pharmacy to see the full process from order entry to medication dispensing. This helped our consultants see what our workflow strengths and weaknesses are so that we can work together to develop an even more productive workflow.

Thoughts

Regardless of which form of observation is used, it is important to utilize one of the two to understand how users will best be able to use a new product. You can create a top of the line product, but if you don’t understand how your users will utilize it and where it needs to fall into their workflow then you risk creating something that isn’t practical for the user.

References

Rogers, Y., Sharp, H., & Preece, J. (2012). Interaction Design: Beyond Human-Computer Interaction. Chichester: John Wiley & Sons, Ltd.



Comments

Popular posts from this blog

Evaluation Thoughts

Thoughts on Usability Testing

Interaction Types