project B:Interviews

From student
Jump to: navigation, search

HyperPublic : Home / Design Plan / Collaborative Design / Interviews




Contents

Atom Interviews

Workshop Atom 01

Date: 1/11/2011

London study trip

The trip will not be held right now, because not enough students want to join. Their problems are:

  • Not a clear enough agenda, and students don't want to put in effort in helping us arrange it.
  • There should be something special/attractive in the trip, something all students want to go to / do.
  • Costs are not clear enough.
  • Wednesday after the trip there will be a big Building Technology presentation.
  • During the weekend can be a problem for certain students

Pachube introduction

  • Nate likes to measure the fire, for the project including atom 10 and 11.
  • Jeanette (atom 08) will maybe use sensors for sensing wind and solar radiation and also people density around the site.
  • Esther (atom 09) might use this technology for counting cars around the site.
  • Atom 06 will be thinking of ways how to implement this technology into their design.

One side-note: We should have had a better working prototype owith an arduino measuring something, rather then a random number calculator for the introduction. We should give better examples, create content especially for the atoms with the given technology, fascinate them.

ProtoFab machine instructions

  • Too much common knowledge, we will organize smaller workshops to work with the machines themselves.

Open forum

  • Tables to work on, where u can leave your stuff without having to pack up your work every time u leave. It should be a mess, ProtoSpace is too neat.
  • Tables to store your models
  • ProtoSpace problem: the door is locked all the time. It isn't inviting to actually work here.
  • Concern: Make the physical design a non-permanent change.
  • Use tables 175-176-177 as a workspace, it is a better working environment then ProtoSpace (look up the up- and downsides of both places).
  • We should make the layout of the workspace less formal, now it is a clear student - teacher relation. Maybe put beanbags in a circle and beamer in the middle or even at the ceiling? Also a walk-away presentation isn't good to create interaction, it creates boundaries instead.
  • We should find a niche where we can work, not we are competing our own teachers, which we will loose obviously.
  • Not enough things 'to do' in the workshop, it was just a lecture (not enough content)
  • We should make content for the atoms, our own opinion, make it more explicit. 'Ready to bite tool chunks'


Atom discussion

Date: 25/10/2011

Working together

  • According to our questionnaire (see below), 100% of the atoms answered the survey want to work together. However only two groups to far are doing this.
  • Atom 10 and 11 are working together in a single project.

What are the main opportunities for atoms to work together?

  • Atoms can share their knowledge and research, if done efficiently, saving precious designing time. Some Atoms have (almost) the same concept, there is a lot of potential for these atoms to work together.
  • Atoms don't have to work 100% together (merge), they can also co-op: sharing just their knowledge and make each their own design per atom.

What are the main concerns atoms are not working together?

  • Costs too much time: next to the research, studio time and other classes, also trying to find common grounds with other atoms, let alone interacting with them feels like a waste of time. No one want to be a manager within a project, and u need one once it reaches a certain amount of students.
  • In order to work with other atoms, you need to compromise and sacrifice your own work, which is something you worked on for 6 weeks. This is a big step for most atoms, especially when the benefits are not fully clear. Atom 01 underwent this somewhat, started from almost scratch 2 weeks before the deadline, on the costs of a reduced grate.
  • Atoms are not getting marked extra if they are collaborating with other atoms. The teachers say they will get better design because of it, but atoms feel like they will only loose precious time, lowering their grates.
  • According to the teachers, atoms and individuals should specialize in order to make projects and thus better designs. Right now this is already happening in the different atoms, reducing the need to merge with other atoms.
  • In order to work together in bigger projects, there needs to be top-down hierarchy. With just students this is not possible because we are all equal. Also a big project takes more time then one semester to work as it should, there just isn't enough time.
  • Software tools are not tutored well in groups, u need to try it out alone, asking teachers when you are stuck at certain points.

What is needed to make for a better collaboration between atoms?

  • More physical contact between atoms, not just online. Because of all the time consuming other tasks we have it should not be a drag.
  • A good workspace, where we can leave our stuff and we can see what other atoms are making/doing. Place to put your physical models. This can either be ProtoSpace or the free tables 175-176-177
  • Idea: Use a webcam at these spaces in order to see who is occupying it, enhancing interaction (if there is someone there, other students will join to work together).
  • Workshops (for instance software tools or ProtoFab instructions)


Questionnaire

Date: 17/10/2011

We have created an online questionnaire for all students to reply to. With this first glance at the needs and ideas of the MSc1 Hyperbody students, we will try to understand in what way we can create a good way to respond to these needs.

The online questionnaire can be found here.
A summary of responses can be found here.

Based on the responses, we can already see the following:

  • Of all social media websites, Facebook would probably be the best way to reach most students.
  • All respondents would like to work together with other atoms, while none of them are doing that at the moment.
  • Almost none of the atoms have tried to create a collaboration between them and other atoms.
  • Almost all the students are interested in meeting the other students in an informal manner, for example in the Bouwpub.
  • There is a great demand in more knowledge about Graahopper and Rhino.



Interview Atom 06

Date: 13/10/2011

Key aspects

  • Up to now, Atom 6 has focussed mostly on analytical and theoretical research. They didn't work on an actual design yet, but have created a strong foundation to built upon for the rest of the semester.
  • When they feel the need to connect to other atoms to combine their strengths, they will do so. But at this moment they don't see a need for this.

Demands

  • Atom 06 is mostly interested in programming tools and tutorials.
  • In order to really understand the different programs available and the connections between them we should somehow list these and show how the interaction between these programs works.
  • Workshops explaining programs like Grasshopper and Processing organized by us are needed right now. This doesn't necessarily have to be with teachers guiding us, some clear explanation of tutorials will do fine. It is also very important that the goal of every workshop is clear, what are we making and how can we use this scripting building block within other scripts?
  • Rather then a forum with discussion, Atom 06 likes to have a clear information layout, with maybe a voting system for the next workshop topic or in general what certain atoms would like to learn.
  • Some sort of teachers question and answer history or archive is helpful. This way the same questions will not be asked multiple times, relieving the teachers and the students.
  • Atom 06 doesn't need a intermediate device in order to contact other atoms, but they do like some clearer image of every atom than the wiki is providing now.
  • An overview of past projects, maybe with workshops learning about these techniques and see what these projects are about.
  • Free coffee provided by Koen's free coffee pass will help a lot!


Interview Atom 11

Date: 13/10/2011

Key aspects

  • Atom 11 is still finding their true identity. After the phase one remarks on Wednesday 13 October they are planning to redefine their concept of intimacy: what is it all about, what is the scope within this concept, and how does it relate to the chosen physical means borders.
  • After they redefined their strategy for the next phase, we will contact them again in order to update this information.

Demands

  • Atom 11 needs more verbal connections to the other atoms or individuals within the atoms. Right now the incentive for this direct contact is non existing. According to this atom, verbal connections will give a much more clear image of other atoms and thus the connection to them.
  • A summary of the other atoms, about key aspects in their concepts and specializations within the individuals is needed to be able to quickly see who to contact for information or help. U need to be interested in another atom or person before u speak to them.
  • They like to have a instant feedback while using our platform. If this feedback takes too long, then the questions asked will be irrelevant by the time the answers are received.
  • When new information is gathered, related to this atom, they like to be notified directly. This is again because of the relevance of the information. Old information is most likely not useful anymore.
  • audio/video comments on questions or other relevant information. This way the information stream is much more interactive and easier to process then written texts.


Interviews Teachers

Walter A. Aprile

Date: 27/10/2011

  • There is a technical and a social challenge. The architectural space and the social environment. How do our actors (atoms + teachers) work socially?
  • Most software is social, u can work with this as part of your design. Make use of standardized systems: 50% of the software fails, everybody is trying to reinvent the wheel every time again.
  • In software there is always a pyramid structure: One person (or two in our case) have the right to edit everything, some persons can track bugs and are able to add minor content, lots of persons are users. There is a rule: 1 million - 1000 - 1, f u have a million persons using your software, only a 1000 will actively add content, and there will be only one main editor.
  • In order for people to use your software the tools must be simple and easy to use. No extra effort should be needed, the tool must be recognized instantly. Also the tools should give an added value to the users normal daily life routine.
  • Ask yourself: what is it that many people would like as a platform. Make one for free, then other people will follow (preferably physical, something people can touch. This is very much needed in interaction!). This is a proven concept. Try to find tools we architects use and use this in your design. In order to find these tools, first find similarities between our atoms, then try to build a platform on that.
  • There is a translation between the atoms concepts and the used technologies, we should do the translation, otherwise the groups will never come together on the same topics.
  • The big question: What makes it their interest to share their own knowledge? For instance Flickr! why do people put pictures on this site, showing off? easy way to share pictures? own portfolio or website? Make your own showing off section!
  • Idea: Make a booklet from the works and findings of the London study trip, a showing off platform. Let them work directly in the layout (google helps). The study trip should be interesting, there should be something unique in order for people to be interested immediately.
  • References: Jacques Tati - obstacles in architecture. Peter Greenway - The draughtsmen + The architects belly


mrs.prof.dr. F.M.T Brazier

Date: 27/10/2011

  • In order to have any kind of collaboration, there need to be a common language, knowledge about each other, and a certain level of respect. Also there should be trust between the users. The level of trust has to do with time, distance and relation. Also there must be a physical element in the design!
  • Users need to feel empowered if they are going to actively use a platform, they should feel a certain responsibility.
  • In order for people to use a system, it is very important to have a basic trust in the system. Therefor risk management. Trust + autonomous + interaction gives responsibility
  • Autonomous system. Usable on multiple levels in the design, from the scale of a single house to the whole city (Boulder Colorado USA)


dr. Stephan G. Lukosch

Date: 24/10/2011

  • Up till now there has been no fully satisfactory system developed for your problems.
  • Through interviews try to find common notions and deal with these with your designed system or platform.
  • For a case like we have now, Stephan used Youtube as a platform for making video interviews for every individual within a company. In these interviews the actors could send their own messages about their problems within a company, letting them in control of the asked questions.
  • With our social group consisting of 30 man, it is going to be hard creating a social collaboration.
  • Biggest problem: motivation. This is a big unknown. U don't give away your own information (work), which u can sell otherwise. Why will users put this information on a platform for free? Never ask too much of any user, use multiple small inputs to create a bigger whole.
  • If a platform is mandatory, then the quality of the added information on such a platform will be less (users will never put 100% effort if the task is a demand).
  • Reverence: Evangelische Kirche Germany Website. (Geistreich Website). Here a big community can ask questions, and make ideas with these questions, creating a social whole.
  • Organize workshops to create a beginning for an information database. People in these workshops will create the base information, then in the future users online will add information.


Tanja Buttler and Thieme Hennis (PhD Candidates)

Date: 24/10/2011

  • U should find a specific topic, and let the users collaborate on this topic.
  • Problem: why would the students use our platform (with the goal to let them work together), if there is no direct benefit added to it, only downsides? -> Make it mandatory? (minimal demand: work together with at least one other atom). Let the mark be influenced by it? Right now we will be marked according the success rate of the designed platform, other atoms should be marked the same way.
  • Flip van Haaren from IO has made a platform we are thinking of (Shareworks), which we might use for our goals.
  • Present the possible connections to the specific atoms. We have to think of those, and think of possible techniques involved (software tools for instance).
  • Think of ways to connect to other atoms to get the necessary input needed to design your platform. To get the input, don't ask them to give presentations (boring), rather debate them in, for instance, a workshop.
  • Which factors influence the likeliness of collaboration?


Dimitrie Stefanescu

Date: 16/10/2011


How do you communicate to your students?

  • Through usb stick and email, sending the workshop files to everyone at once.
  • Tutoring individuals is best, especially at the beginning. Once a problem pops up more then once, a classical half hour tutorial is needed.

How to improve this communication?

  • Longer (3 day) intensive workshops are really needed to get personal with the students and actually learning them the basic skills.
  • On the gh3d group there is a community with a lot of tutorials and basic scripts, here u can actually search the help for your exact problems.

What are your exact skills students can ask u about?

  • On my website there is some stuff about processing and grasshopper
  • The scripts I gave in the workshop are self explanatory for the students. Making a self explanatory script though is quite difficult. The examples I've used on the workshop actually took a week to prepare, and this was stuff which I already had.

Should be organize extra workshops to enhance the students skills in these programs?

  • Extra workshops are always welcome, however keep in mind that:

Learning these programming skills will take more then a few workshops. Actually messing around with these programs yourselves and ask us teachers about the problems you encountered will learn u a lot more.

  • Dimitrie initially proposed to teach processing half-a-day per week over one quarter, or even a semester. He got three days in the end to do it.

Do you know other skilled students/teachers who like to teach these skills to students?

  • A lot of students want to learn, but I don't know anyone who wants to engage in teaching. On the internet there are a lot of gurus who love to share all their knowledge though.



Roxana Palfi

Date: 16/10/2011

How do you communicate to your students?

  • Mostly through email, although this is probably not the most effective method.

How to improve this communication?

  • We (PAN architects) thought of a open source portal for better communication with the students. In this portal we would like to make scripts and tutorials (grasshopper) available for all students to use for free.

What are your exact skills students can ask u about?

  • I work in Generic Components, Grasshopper and Virtools.

Should be organize extra workshops to enhance the students skills in these programs?

  • Workshop and face to face meetings are always the best for moving forward.

Do you know other skilled students/teachers who like to teach these skills to students?

  • Unfortunately no. Almost all our fellow colleagues that graduated from Hyperbody have left the Netherlands.




Team

You

And us:

Joost Noorden
Koen Kegel


Please use our feedback form and help us improve.

Public progress document

Follow us on Twitter: @HyberPublicNL

Our website (under construction) : www.HyperPublic.nl













































































































































































































































































































Back to top


HyperPublic : Home / Design Plan / Collaborative Design / Interviews

Personal tools
Namespaces
Variants
Actions
Projects
Atoms
Toolbox