While usability tests are an excellent option for quick task-based behaviors, diary studies allow longitudinal data collection. Let me provide an example. While at Nintendo, we were tasked to improve the game development experience, which was composed of many software tools for a variety of roles. Think Adobe Suite for game development! Testing these individual products would have been a futile task without actually producing something with them due to the in-depth knowledge required to use the tool. So we did. Our department created an in-house game development team for the sole purpose of eating our dog food. Each day, the team members would compose diary entries for the UX Team. These compositions included their daily goals and the pain they experienced reaching them. We would then divide the feedback into a variety of categories from software bugs to unintuitive interfaces. Bugs would go to our quality assurance team for development improvements, while experience issues stayed with the design team, allowing us to dig deeper into the problem. For our purpose at Nintendo, diary studies became a pinpointing tool in a very complicated process.