🏢
BA Portfolio
  • 0️READING GUIDE
    • How to Read the Portfolio?
    • Front Page
    • Reading Guide
  • 1️Phase 1 - DISCOVER
    • Overview - Discover Phase
    • The TQ Building Problems
    • Acquiring deeper knowledge of the project's main topics
    • The working routines of the people at Fontys TQ - User Research
  • 2️PHASE 2 - DEFINE
    • Overview - Define Phase
    • Problem Definition and Solution Direction
    • Target Users Definition
    • First Concepts and Design Challenge Redefinition
  • 3️PHASE 3 - DEVELOP
    • Overview - Develop Phase
    • Creating the Scenario Flows
    • Creating the User Screen Flows
    • Ideation of Hardware Design
  • 4️PHASE 4 - DELIVER
    • Overview - Deliver Phase
    • Choosing Suitable Software
    • Device "Character" Face
    • Device Prototype and Validation
  • 5️Conclusions and Reflections
    • Project Conclusions
    • Personal Reflection
  • 🔎Attachments
    • Purchased Hardware Components List
    • Comparison Chart for Hardware Casts
    • Scenario Flows Test Notes
    • Hardware Designs
    • User Screen Flows
    • Scenario Flows
    • Project Proposal
    • Project Plan
    • Design Challenges Versions
    • Research Questions
    • Library Research Report
    • User Survey
    • User Interviews
    • Small Scale Prototype
Powered by GitBook
On this page
  1. Conclusions and Reflections

Project Conclusions

Even though the prototype is not completed at this moment, I am positive that the project has valuable findings and could show potential for the concept's future development.

At the start of the internship, I got a broad assignment connected to creativity because of my personal inspiration and some discussions with the client. However, I was not sure if my users even needed a more creative feel at the TQ Building. By doing various types of research in the first weeks I could gain not only knowledge on most of my research topics (such as the link between rest and productivity, surrounding environment effects, types of effective mind rests, etc.) but also get to know my users and validate that indeed a creative solution for the TQ Building is needed. Combining creativity-related and practicality-related problems, I came to an innovative concept that might change drastically the environment at TQ. The concept has been validated from the early stage gaining positive reactions from the user groups. Even though the idea was far too big to be fully working in time, my client believed the concept has potential and decided to support me on the sound part. Moreover, many long-term decisions for the future development of the project were taken such as a comparison of software platforms, hardware elements, cast designs, character research, etc. This means that all the current findings would come useful if the project is continued in the future because many decisions have already been made. The final prototype and validation have the goal to see people's reactions and attitudes towards a more realistic prototype so that the potential of the concept's effectiveness can be validated even more.

As for recommendations towards the next steps of the project, I believe a more accurate suggestion can be given after the final test. At this point, I can state that a project could be conveniently worked upon with the help of Web programming as both I and my client were successful to create the needed features with the help of a Web environment.

Last but not least, the client has been satisfied with the evolution of the concept during the whole project timeframe. He wanted my high-fidelity prototype to look real (but not necessarily fully functional) by the end so I can gain knowledge of the user's experience and answer if it is possible to use promoting breaks as a strategy of noise reduction in the open-spaced Fontys Stijp TQ Building.

PreviousDevice Prototype and ValidationNextPersonal Reflection

Last updated 1 year ago

5️