The objective of Element I is to actually test and demonstrate that testing using the plans concluded in Element H. As both the qualitative and quantitative tests are completed on prototypes, an analysis of the results is done to understand and address potential areas of improvement. Furthermore, this is where feedback on prototypes from stakeholders is explored and used to improve designs and functionalities. As a recap, both of the testing formats will take the form of testing through user stories, and through feedback and testing from potential users.
User story testing took a far simpler, quantitative approach to testing all three Profectly prototypes. Unfortunately, the results of such were startling and disappointing. For all the prototypes, they had low scores due to the lack of features and such. Although this is discouraging, it shows that there is a considerable level of growth available for future prototypes in regards to educating the user with tutorials, having features for more social interaction amongst users, and providing more ways to increase motivation through competition and other possible engaging activities. As a feature in an app, user's having the ability to socialize and work together with others to accomplish their goals regarding procrastination is key, and the concept was highlighted in the front end in Prototype #2. Because it was only shown in the front end, there is plenty of room in a 4th or 5th prototype to demonstrate functionality for such features. It is reasonable to say that most of these user stories were not completed due to the lack of time and knowledge available to do so, because building a prototype that accomplishes all of that criteria would be a mostly finished app that would easily be ready for the market. In order to innovate on the features not accomplished by the prototypes though, a suitable front-end prototype would need to be developed and experimented with first to test how features would potentially function. From there, a prototype focusing on the back-end could be made to demonstrate how such potential would function. It is also important that some future prototypes would have both aspects of the fully working front-end and back-end.
For obtaining more qualitative testing and results from such, the team sought to get potential users testing the prototypes and giving feedback on such as addressed in Element H. There were three surveys made, all with very similar questions so that more cohesive data could be determined, for Prototype #2 testing of the front-end, Prototype #3 testing for the back-end, and just a general survey so that the team could get some basic feedback from those who didn't have an available device for testing. One of the key components to having the users testing the prototype was giving them a set of tasks to complete, so that the team could gain a better idea of the user experience. This would allow for crucial information in addition to the general feedback.
For the potential user testing & feedback, the results were expressive of areas that will need to be improved in the future. A specific data point of interest was the number of survey users who would consider using the finished project. Even though 38% is a decent-sized number of those who took the survey, compared to 85% of people who procrastinate, the statistic isn't great. It does show that Profectly's product has some potential but it also shows that there is plenty of room for improvement and innovation. This gap between the two data points is likely due to the there being some of the testers already having some sort of way to organize their life, or not wanting to use an app at all, as stated by some. In terms of improvement, this shows how Profectly should work towards adding making a more welcoming atmosphere and more useful features that will accommodate a wider audience and range of different types of people and users.
Some of the most prominent feedback found in the surveys was regarding visuals and information with tutorials. For the visual side of things, many of the users commented that the prototypes should have more color to be more visually appealing, which the team completely agrees with and should be a goal in the future once further functionality aspects and features would be completed. Having a solid, attractive, visually appealing is crucial to user engagement and retainment. For the tutorials aspect, a considerable number of potential users explained that whilst completing tasks, they sometimes struggled to find certain features or whatnot, and some even pointed out that an in-app tutorial would be beneficial to fix this problem. This is a substantial point because it doubles the importance of Profectly's need to educate and prepare the user properly so that they can effectively and efficiently use the app. Further, as a user story, the team should have been more prepared for this feature with the current prototypes and, therefore, should not neglect the importance of a tutorial, tips and tricks, etc. in future prototypes.