Sunday, May 11, 2008

Week 8 - Context

Conflict can be seen as a way of learning more about what is working in a collaboration team and discovering how conflict can be resolved. Context has different definition in different cases. For example, in an architectural collaborative group project, context can be seen as a common goal that to be achieved as well as the background or environmental surroundings of the building itself.

The usefulness of the solution depends on the depth of your communication and understanding of the problem. For example by using proper context in communication, we can express and understand each other’s ideas effectively. However, without a context, people start going for different directions, and the collaboration will be messed up.

Once a group member has gained a deeper understanding of the other person, themselves and the conflict there is the relationship, the interaction and connection between those elements to be understood. As an example two group members may experience conflict over the distribution of the work load, but it might escalate a result of how they communicate their need to each other. When we alter how we see our group members we automatically change our definition of ourselves which then changes our understanding of the context of the dispute, the relationship and the nature of conflict generally. If it is possible for us to see our conflicts as opportunities and what fuels our negative attitudes towards conflict or get trapped in it? These answers can be found in the context we created for perceiving and engaging in our conflicts. Once you listen to your conflicts your group members can listen to you and together you can search for collaboration and constructive solutions. Context in term of collaboration, it is a way to bridge the gap between office and real time collaboration; structured content as offered by line of business systems and platform of formal and informal. It is important to gather enough information to understand context of an activities. Suppose we want to send email to a customer, we will need to have senders’ details, recipients, subjects, and contents of the email; we will also need to know the application that can navigate to business entity.

Both concepts and contexts are used in a broad sense, and can be interpreted into different ways. The concept can be seen as a solution to a context. Whether the concept will be influenced by the context depends on how we define the context and concept. A concept will be meaningless without a specified context.

An inferred design concept is unique to each individual although the context does not change. For instant, Opera House. A understands the concept of Opera House comes from orange peel, and B thinks the concept of Opera House comes from sailboats; but orange peels are considered to be the truthful concept because that is what inspires the designer.


An image showing different perspectives toward a design concept, edited by Andrea Zheng

Let us narrow it down to one person's perspective. Here we take the site of the building as the context of a design. If one’s concept of the design is taken and applied to a certain site, the concept may not be changed even the context changes from time to time. However, if one’s concept of the design is not taken yet, and will be applied to a different site, the concept may vary.

We can also interpret the function of the building as the context of a design concept. In this case, if the context changes, one’s concept will be changed as a consequence.

--------------------------------------------------------------

Reference:

Kenneth Cloke & Joan Goldsmith, Wiley San Francisco 2000, Resolving conflicts at work : a complete guide for everyone on the job

No comments: