Page History

Project Proposal and User Analysis

What We Learned

While creating the project proposal, we learned that it was a lot easier to get our creative juices flowing once we knew what we wanted to develop. Through the entire proposal process, we realized how important it was to conduct the interviews, especially in the case of Torch.

What We Would Have Done Differently

When we were trying to decide on a product, we at first were focusing on what was already out there rather than what was something that we wanted to use. We eventually learned, but if we had started from that mindset of creating something we wanted of use rather than improving something that was already in existence, we could've saved ourselves some time and thus, would have had more energy to devote to analysis and proposal of Torch. When we first started, we didn't really have a specific problem and we had some lofty goals. To be honest, we should've narrowed down our focus directly to the specific needs of self-guided tours rather than what does the user "find interesting" angle.  We should've narrowed in scope our User analysis so in the future it would've been easier to develop specific tasks and needs. Our interviews were more surface level than they should have been, and while designing our product, we had to delve more deeply, a task we could have avoided if we had done more comprehensive interviews originally.