Dear Ken,
Thank you for pointing out the quotes mark around "needs", indeed I was trying to address something different than technical requirements.
In response to: "To speak of technical requirements is not to say that the system or the artefact needs anything. Systems and artefacts don’t require anything in the sense of needing something. Rather, this means that human beings must meet technical requirements if the systems or artefacts are to meet our human needs. Humans design systems and artefacts. After we build them, the systems and artefacts we build affect us."
I strongly agree with your last sentence. What I am looking for are system/artefacts that were designed with artificial needs, i.e. not technical requirements of material/hardware/softwre to operate per se, but needs that are encoded in the backstory of the design. If these needs affect how the system/artefacts operates, it's only becuase it was designed to have this additional need. More importantly, the goal of these artificial needs is to facilitate, or direct the users (i.e. people) towards interacting with each other. Moreover, I would be even more interested if *the only way* to meet these artificial needs would be by people having to collaborate with other people in close proximity.
An example that might help illustrate what I mean by artificial needs is the Tamagotchi. It's a toy, its character has the need to be fed/cared for, otherwise it dies. If one uses it, it will respond to these artificial needs.
-----------------------------------------------------------------
PhD-Design mailing list <[log in to unmask]>
Discussion of PhD studies and related research in Design
Subscribe or Unsubscribe at https://www.jiscmail.ac.uk/phd-design
-----------------------------------------------------------------
|