Responce and goals

Ah-Ha Moments! [One] The first light bulb was illuminated by the prototyping text. I wrote the phrase "perspective accuracy," which seemed insightful to me. By these words I'm referring to: what the prototype “means” to different members on the design team. When a prototype is created not only does everyone need to have input, but it has to evoke an accurate portrayal of the design intentions within various perspectives. [Two] The second flash comes from the same article. I came away with a distinction between three concepts… scenario, story and theme. A scenario is a specific task carried out upon the system; a story is an anecdotal understanding of an interaction with the system; and, a theme is a convergence of stories.
The generation of themes, within stories, (kinda) become scenarios. Whether or not those are intended or are truly part of the system, a theme of use is a very valuable tool. This helps to understand the way in which users perceive the functionality of the a system.


Three personal goals...
-- Gain knowledge of the tech. side of RSS and pod-casting.
-- Better understand the role of the webmaster in the business team
-- Improve my overall perspective regarding tech meets non-tech objectives.