In today's lecture we discussed the primary understanding of ICT that will guide the rest of the course. On the one hand, we have Wanda Orlikowski's concept of "technology-in-practice". Stemming from structuration theory (Giddens), this notion argues that technology (ICT in particular) cannot be understood in isolation; it has to be placed into a context of situated action. As with structuration, it claims both a bottom-up, as well as a top-down effect of the use of technology. Through "agency", users shape the meaning and utility of technological artifacts as well as modifying the set of installations, norms and interpretation schemes that guide its understanding and usage; as a result "structure" (rules and resources) emerges from the bottom-up. But it works the other way around as well, this emergent structure also influences further enactment of the technology by imposing limits to this (re)shaping of technology through use. As a consequence, ICT cannot be understood as embodying a particular structure, since such structure is continually changing and alternative structures emerge out of different uses of the artifacts. Furthermore, ICT cannot be said to stabilize after adoption, since it is continually being modified as well as modifying the user itself though changing his or her way of doing things. The example of the cell-phone was an obvious choice to illustrate this: a cell-phone is not the same today as it was ten years ago (or will be next year); it is also not the same for a teenager than for his grandparents; even though it may be the same exact model, they have different intent, frequency of use, satisfaction, emotional attachment levels, etc.
On the other hand and in parallel, we discussed the work of Terry Winograd and Fernando Flores from their seminal 1986 book on Computers and Cognition. Few authors have been able to capture the role of ICTs within organizations so lucidly and with such lasting impact. In fact, it could be said that little progress has been achieved in such broad understanding of ICT since its publication over twenty years ago. By rooting their work in cybernetics, systems theory (autopiesis in particular), hermeneutics (Heidegger, Gadamer) and philosophy of language (Searle), they proposed an understanding of organizations as networks of conversations. Nothing gets done without orders, promises, commitments or requests being made through speech acts. In fact, all conversations are action-oriented. ICT, of course, comes in as a way to support, shape or reconfigure these interactions. As with Orlikowski, ICT is not given a meaning in isolation but rather through use. The importance of ICT is thus not centered on its inherent (physical) properties but in the way in which it can alter the way people communicate. Moreover, as with any other technology, it remains hidden (transparent) when users are absorbed in (semi) automatic tasks (like driving or typing). It is only through breakdown that technology becomes visible and forces the users to be aware of it. Thus, Winograd and Flores suggest an emphasis on identifying contexts of breakdown as a way to both anticipate failures and provide mechanisms for preventing or dealing with them, as well as using such context as a basis for constructing a domain or context of application. Such context is best understood as an ontology which represents recurring patterns of interaction and failure and can be the basis for the design of the technological means through which such ontology can be employed in (re)shaping conversations.
In sum, we start from an understanding of technology which is dynamic and in continuous interaction with the user. ICT is not a device in isolation whose effects can be designed and measured directly. This should re-frame the design activity and the role of the designer and the user towards participatory, iterative (open ended) means. It should also provide the philosophical underpinnings for understanding ICT and society together.
Understanding technology as a dynamic and continuos interaction with users is a radically new idea for an engineer. we are centered in the technical aspects of the artifacts construction and practically never think of the impact on the users. Also, we are unaware that interaction with users afects our perception of the world.
ResponderEliminarI have a question: Is the concept of "technology-in-practice", also valid in the construction domain? When we are constructing our artifacts, should we start at the breakdown domain before entering the application domain? As engineers we start our solutions modeling the problem, in other words, we start modeling the application domain and much later we include the exceptional cases, perhaps this is the reason our artifacts often fail catastrophically
Comentarios por: José Manuel Burbano C.
ResponderEliminarConsidero que la tecnología en práctica puede ser vista de diferentes maneras, ya que actualmente se observa que la tecnología va evolucionando lo cual indica, que uno como ingeniero debe estar preparado para afrontar los diferentes cambios que se realicen, esto se ve reflejado a la sociedad en si, porque la sociedad va a estar muy involucrada con los cambios de tecnología como también la entrega de la información de diferentes maneras. La misma sociedad se encarga de dar una buena utilización a estas tecnologías recientes, porque dependiendo del modo que se utilicen esta puede crecer o caer en el intento.
Me parece interesante este tipo de lecturas porque uno como ingeniero se da cuenta que la sociedad depende de las TICs, pero me genera una inquietud si las tecnologías no evolucionaran a través del tiempo, que podría ocurrir en la sociedad?, ¿Se quedaría estática?, tal vez este tipo de inquietudes son vistas de manera pesimista, talvez nunca ocurra, pero de todas maneras uno como ingeniero debe estar preparado para afrontar las nuevas tecnologías que van apareciendo a medida que pase el tiempo.
------------------------------------------------
Comments by: José Manuel Burbano C.
I believe that the technology in practice can be viewed in different ways, as currently observed that the technology is evolving which indicates that an engineer must be prepared to address the different changes that are made, this is reflected in society itself, because society will be very involved with technology changes as well as the delivery of information in different ways. The same company is responsible to make a good use of these emerging technologies, because depending on how it can be used to grow or fall in the attempt.
I find it interesting reading this as an engineer because you realize that society is dependent on ICT, but it generates a concern if the technologies do not evolve over time, what would happen in society, the society would static?, perhaps these concerns are viewed in a pessimistic way, may never happen, but still an engineer must be prepared to deal with new technologies that appear as time passes.
The importance of the ICT was born in the people, for that reason it is not logic that the software creation and development is carried away from them or their activities sometimes. I think that start the course since this point of view helps us to focus in the important things around ICT like in the impact (good or bad) of them in the people behaviour, and not just the development process
ResponderEliminarI think that the actual software development teaching process must to cover in a different way this kind of issues because although they´re implicit in those processes, there are not a specification of them and their implications, in this way, the perspective of each student will be different about a problem or situation and the software will be made for help and it don´t imposed in an organization.
i don´t think that the society will be static without the actual ICT development, it will be different, maybe without many of the things that we have today, the development would be slowly, but a society must to grown up in one way or another.
@Gerardo. For us, you can take a look to software engineering theory; there you will be able to see that you can work a problem through organized iterations, giving you the possibility of reshape a problem and its solution while you work on it. In this way you can think on any problems’ possible break points while you model its solution
ResponderEliminarI believe that ICT has been created to help people, improving or automating processes, that is why people should be taken into account when designing a system. The technology has evolved considerably and technological tools have lost the means by which they were created, they have now taken on new meanings, but always keep a single idea: "Communication". But communication itself, has lost its meaning too, the same technology depersonalize communication, is that good or bad? that will tell future generations.
ResponderEliminarSomething that does not take into account the life cycle of software development is the "impact". If at the time of planning put efforts to create scenarios showing the possible impact it will have the software, we would be considering the appropriateness or not. However, in a society like ours (world in general) isn't important that the client is the devil, what the really matter is that he pays on time. :D
John Jairo Páez Rodriguez.
ResponderEliminarDadas las dos visiones acerca de la concepción de la tecnología lideradas por Ernst Kapp y Lewis Mumford y además la exposición del profesor, he podido entender dos cosas:
1. En el lenguaje común, el concepto de tecnología se utiliza en los artefactos que implican inversión de conocimiento, extensión de las facultades humanas y que revelan en su materialización un nivel de sofisticación en el uso de procesos de manufactura. Donde aclaro, solo se categoriza el artefacto.
2. La visión menos común, y por ende filosófica, entiende la tecnología como la relación entre los artefactos y las personas. Es decir, la tecnología no es el artefacto en sí mismo, sino lo que emerge cuando las personas interactúan con ellos.
En función de las dos visiones, entonces podríamos hablar de productos tecnológicos como el resultado de un proceso de diseño y construcción de artefactos, y la tecnología como la dinámica social que emerge en su apropiación.
En relación a los artículos: "The Spiritual Life of Projects" y "Development, global futures and IS research: a polemic", surgen las siguientes impresiones:
ResponderEliminar1. El eje central del desarrollo de una organización esta en las personas que la conforman, ya que ellas son las que realizan la mayoría de las actividades. Una persona que mantiene un equilibrio entre sus aspectos físico, intelectual, emocional y espiritual es una persona estable y tendrá más facilidad para comprometerse con el desarrollo de la organización.
2. Las TIC y en especial los sistemas de información ofrecen una oportunidad para apoyar el desarrollo de las personas, organizaciones y países. Dentro de este contexto, es importante trabajar en el planteamiento y desarrollo de proyectos que busquen encontrar solución a los problemas que aquejan a las personas, organizaciones y países. También dentro del desarrollo de las TIC se debe tener en cuenta la diversidad de las personas que las van a utilizar.
Juan carlos Guevara B.
Diego Alberto Rincón Yáñez
ResponderEliminarICT's should be a tool to get some advantage in the contexts of society, political, economic, social or technologic.
I think the society would not have to center in the technological artifacts, yes, they are important, but more important is the people who is going to use those artifacts, as engineers, like Gerardo says we focus in the technological aspects more that in people troubles