taken from the linked site above |
A condensed explanation is shown above, and further reading on this can be found in the link, also given above.
This process makes quite a lot of sense when you think about it really. Observe, realise, and only then design. I think we subconsciously take this into consideration, but a much more in depth approach needs to be taken when we design for a user. In a way - everything is service design. If it has a purpose, a use, or a reason for it's existence, it provides a service, regardless of scale. Pin pointing ways in which to reduce, time, effort and complexity is good design, and all this can only be realised through laborious observations, that may be lengthly to complete, but are invaluable when reducing down to a final outcome.
For example, myself and a few class mates took a short trip to London for a conference for our course. While travelling through the business hub every morning for the three day event, I found it difficult to understand how to behave amongst hundreds of black shiny shoed business men, with their Starbucks lattes, broadsheets and pin striped suits, all of which silently walk at 10m/s. They automatically understood the tube etiquette, which seemed to change for this line only, compared to the likes of Whitechapel.
Do I need to go on a course before boarding? |
0 comments:
Post a Comment