7. Provide a program execution status
It is useful for the user to know whether NVivo is initializing, running or shutting down. If the software seems to be unresponsive, seeing a status message, like: 'initializing', 'running', 'paused' or 'shutting down' would be helpful to the user and a better alternative than using Windows Task Manager to double-check.

8. Show closing down status messaging
Further, if NVivo is slow in closing, it would be useful to show how it is progressing. This is very important; if the user thinks that it has stalled, he or she may "force quit" the program when it prevents Windows shut down. As failing to close NVivo down properly can corrupt the project file, thereby costing the user much more time, the value of accurate status messaging (and even warning the user 'do not force quit') should not be underestimated.

9. Provide better communication when there are errors
Just as Microsoft impresses with problem messaging linked to solutions via its Solutions Centre, so too should NVivo consider linking its error messages to online help. For example when I was trying to fix an NVivo installation, the message "Database component did not initialise" could have been made far more helpful by linking straight to an FAQ page with possible solutions.

Given that NVivo users are qualitative researchers, it is unlikely that many of them have experience troubleshooting software. Providing us with more thorough and helpful error messaging will provide an improved user experience just where we experience most difficulty.

10. Report on third-party interference
I have noticed that NVivo's timebar may be paused (at 67%) for several minutes when an important Windows 7 process runs (such as deleting a backup snapshot, running a backup, et al.).

NVivo stalled at 67 percent progress (6 June 2012)

It would be helpful if the user could be shown that third-party software has interrupted NVivo, ideally in the software itself. Even a notification from Windows OS would be helpful.

11. Offer a back-up file option
Just as Apple's OS X Lion introduced Versions to protect users' files, so should NVivo consider adding a 'backup' option in addition to 'auto-save'. For users whose files became corrupted and had failed to create a back-up, this prompter could be very beneficial.

12. Provide a video rewind shortcut
For researchers working with many video interviews, a rewind F button shortcut would be great. I recently started work on a PC laptop and simply having the F7 (play/pause) shortcut available is a real timesaver {after moving from Mac, where I did not have this option}.

13. Allow the user to set a volume limit
The user should be given an option that sets a limit to NVivo's volume. In working with listening to mobile phone videos of varied audio-quality through headphones, this would be useful to protect my hearing as I move from soft, low-quality files to very loud, high-quality ones and forget to change volume.

14. Offer a pseudonym generator
As qualitative research invariably involves the ethical requirement to protect the privacy of one's subjects, it would be a nifty value-add if NVivo added a pseudonym generator.

15. Provide an auto-save that does not auto-interrupt
I find auto-save very useful, and appreciate that this is probably an impossible request given the requirements of the 'save file' process, but it would be helpful if accepting the auto-save function did not automatically delete the incomplete timesheet entries a user was busy with. It would also be useful to be returned to the transcription block one was working on post auto-save, rather than being sent to the top by default. This can be irritating if working with a long interview and auto-save is set to be frequent.

I trust these ideas are constructive and helpful. Please let us know your thoughts in the comment box below, thanks.

About Me

> Subscribe to my posts/their comments

+ or simply follow this blog by email

+ LISTING

Thanks for viewing Travis Noakes' blogsite

Hope you enjoy reading these insights from my research into creative producers' digital identities, e-portfolios, digital hexis and infrastructure. Or my experiences as a design thinker and software user.