• Unit 5: Deliver & Document

    Unit 5: Deliver & Document



    Once the concept is final, all details need to be designed.  Meanwhile prototypes need to be built and tested on a small scale with a group of people that well represents the target group / visitors / audience. Testing inevitably results into surprises and revisions, as everything will not work out as planned. Consequently the Deliver stage often is an endless loop of improving, building and testing.  
    Once the design is relatively stable, the documentation of the design will require most attention. Often others will implement the design and need carefully prepared, unambiguous specifications so that they know what is needed. Often, dependent on the kind of deliverable specific standards exist for documentation, such as technical drawings for engineering, or service blueprints for service design.


    Case Study: Food exhibition: the devil was in the details

    For the exhibition eventually the concept was chosen and budget was reserved. It was time to finalize all 'details' but several unexpected challenges  made the development team working long days, even in weekends. For example, it was decided to have an interactive app that could be used  in the exhibition, to offer augmented reality (AR: an interactive experience of a real-world environment where the objects that reside in the real world are enhanced by computer-generated perceptual information). The idea was to show additional information, X-ray like images and the original ingredients 'circulating in the air' around processed foods.

    However, in order to have a good experience, the location and position of the smartphone should be established precisely. Due to the construction of the building, GPS and Wifi signals could not offer this accuracy. So the developers decided to use 'marker technology' whereby the camera of the smartphone detects markers to orientate the added layer of information. Although the first -rough - test were very promising, it became a nightmare for the team. Not every smartphone brand functioned well with the software that become so sluggish that visitors would see a kind of delayed rather than real time AR. It had to be optimized again a and again to give a good-enough experience. Also the app resulted in complicated privacy issues, as it used the camera. 

    The team had several of these unexpected issues, that required more time and effort than the development from start up to the choice of the concept!