Blog Benefits
In this Krasnow Programming study, we have discovered that blog technology is an effective tool:
- to establish feedback loops
- to distribute information collected from the interviews
- which can yield quantifiable statistics about who is accessing the data
Feedback Loops
A sampling of input from various Krasnow residents was necessary in order to develop a cohesive understanding about the way that a diverse group of people, and the work that they do, come together. By involving the end-users in the information gathering process, the body and depth of knowledge was increased. The expectation was that the resulting designs would be more informed, and performance based from the beginning.
Involving a greater number of people in the Programming phase required a greater degree of managing the acquisition and synthesis of the information -- for which the blog tool was well suited. The blog acted as a collective space which could be conveniently accessed according to an individual’s particular schedule and location, and he or she had the option to post anonymously. Establishing a virtual interface had the potential to create self-sustaining feedback loops; therefore, a greater audience could be targeted with a smaller amount of effort. A dialogue could be established where end-users could voluntarily view and respond to assumptions posted on the blog by the programming administrator and to ideas posted by their colleagues.
Distributing Information/communication
Among the end-user community….
The broadcast communication benefit provided by the blog tool effectively kept the end-users informed about the anticipated construction and alleviated some stress associated with “the unknown”.
Between the design teams and the end-users….
It was hoped that the blog would lure the data-seeking, competing teams and passively feed them relevant programming data that would ideally materialize in the designs.
Between members of the design and construction team ….
In the design and construction phases following Programming, the blog could become an electronic database available to all trades at any phase of design or construction which someone may enter the process. Thus, the design intent, or performance criteria, which was established at the beginning of the project would not get lost throughout the process. Contractors, subconsultants and interior designers would have access to this database of programming information.
Web stats
The blog yielded quantifiable data which indicated how successful it was performing at any point in the study. A web-tracking service was implemented to determine how many people visited the site, and more importantly, who was visiting the site. As mentioned earlier, the initial goal was to feed the collected programming data to the three competing teams. The web tracker service provided a good indication of which architects and contractors visited the blog, how often they returned, and which posts they accessed.
- to establish feedback loops
- to distribute information collected from the interviews
- which can yield quantifiable statistics about who is accessing the data
Feedback Loops
A sampling of input from various Krasnow residents was necessary in order to develop a cohesive understanding about the way that a diverse group of people, and the work that they do, come together. By involving the end-users in the information gathering process, the body and depth of knowledge was increased. The expectation was that the resulting designs would be more informed, and performance based from the beginning.
Involving a greater number of people in the Programming phase required a greater degree of managing the acquisition and synthesis of the information -- for which the blog tool was well suited. The blog acted as a collective space which could be conveniently accessed according to an individual’s particular schedule and location, and he or she had the option to post anonymously. Establishing a virtual interface had the potential to create self-sustaining feedback loops; therefore, a greater audience could be targeted with a smaller amount of effort. A dialogue could be established where end-users could voluntarily view and respond to assumptions posted on the blog by the programming administrator and to ideas posted by their colleagues.
Distributing Information/communication
Among the end-user community….
The broadcast communication benefit provided by the blog tool effectively kept the end-users informed about the anticipated construction and alleviated some stress associated with “the unknown”.
Between the design teams and the end-users….
It was hoped that the blog would lure the data-seeking, competing teams and passively feed them relevant programming data that would ideally materialize in the designs.
Between members of the design and construction team ….
In the design and construction phases following Programming, the blog could become an electronic database available to all trades at any phase of design or construction which someone may enter the process. Thus, the design intent, or performance criteria, which was established at the beginning of the project would not get lost throughout the process. Contractors, subconsultants and interior designers would have access to this database of programming information.
Web stats
The blog yielded quantifiable data which indicated how successful it was performing at any point in the study. A web-tracking service was implemented to determine how many people visited the site, and more importantly, who was visiting the site. As mentioned earlier, the initial goal was to feed the collected programming data to the three competing teams. The web tracker service provided a good indication of which architects and contractors visited the blog, how often they returned, and which posts they accessed.
Using the web statistics as an indicator of team presence on the blog, there was one team which had a consistent and significantly greater presence on the blog than the other two teams throughout the course of the study. While this particular team did submit a programmatically responsive design, it must be noted that there are other factors – such as budget and experience - which will justifiably weigh into the design team selection.
What began as a convenient and inexpensive method for programming proved to have larger applications in terms of information-sharing. It is my hope that you will see the investment of your time manifested in your existing and future environments.
posted by Meredith Banasiak, ANFA @ 3:41 PM
0 comments
