<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-10333058</id><updated>2011-04-21T18:00:59.278-07:00</updated><title type='text'>Piper and to the Moon!</title><subtitle type='html'>Musings on creative content, feathers I found at the park, and other relevant information...</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://piperandtothemoon.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://piperandtothemoon.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Piper and to the Moon!</name><uri>http://www.blogger.com/profile/02267220173370330790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>8</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-10333058.post-111025047131446211</id><published>2005-03-07T18:47:00.000-08:00</published><updated>2005-03-07T18:54:31.316-08:00</updated><title type='text'>Production and QA</title><content type='html'>Coming to most projects as the visual designer, it has been my experience that without a plan of attack established beforehand, the entire designing and implimentation process is painful and drawn-out.  I loved the charts from this reading, I will keep them handy for future reference.  They highlight the absolute need for considering every single aspect of the site long before any designing or creation processes start.  I have gotten deeply involved in a project's development only to have the creative director change course, either through changing software or a complete design change.  It was extremely frustrating, as it was a waste of my time as well.  These charts could be used to dispell a lot of confusion up front in regards to what the client (or creative director) is expecting.&lt;br /&gt;I can also see the need for using a similar system like those mentioned in the reading for my own projects.  Just to help set reasonable goals-be it the timeline, cost, need for content, etc.  I found this reading to be very helpful.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/10333058-111025047131446211?l=piperandtothemoon.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://piperandtothemoon.blogspot.com/feeds/111025047131446211/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=10333058&amp;postID=111025047131446211' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/111025047131446211'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/111025047131446211'/><link rel='alternate' type='text/html' href='http://piperandtothemoon.blogspot.com/2005/03/production-and-qa.html' title='Production and QA'/><author><name>Piper and to the Moon!</name><uri>http://www.blogger.com/profile/02267220173370330790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10333058.post-110901581026143003</id><published>2005-02-21T11:47:00.000-08:00</published><updated>2005-02-21T11:56:50.263-08:00</updated><title type='text'>RSS feed-complete information?  Not quite.</title><content type='html'>How does RSS (text or audio) change digital communication?&lt;br /&gt;&lt;br /&gt;The nature of RSS aggregation allows for more convenient and efficient searching.  The user can save time, avoid the distractions of multiple advertisements and off-topic queries, and get multiple hits on the topic he or she is looking for.  While this is a very useful tool for initial information gathering, I think the need for methodical, slow discovery and absorption of material is still absolutely necessary.&lt;br /&gt;&lt;br /&gt;While RSS pulls together key words or phrases, even articles or news feed on a certain topic, it is still at a very superficial level.  The search is automated; therefore the user looses a certain amount of control over their search process.  Also, those who know how to use it will use to a greater capacity and with greater success RSS.  That leaves a subjugated population and wealth of information that the user might not come in contact with just because they are content to end their search with what RSS offers.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/10333058-110901581026143003?l=piperandtothemoon.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://piperandtothemoon.blogspot.com/feeds/110901581026143003/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=10333058&amp;postID=110901581026143003' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110901581026143003'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110901581026143003'/><link rel='alternate' type='text/html' href='http://piperandtothemoon.blogspot.com/2005/02/rss-feed-complete-information-not.html' title='RSS feed-complete information?  Not quite.'/><author><name>Piper and to the Moon!</name><uri>http://www.blogger.com/profile/02267220173370330790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10333058.post-110835772252678099</id><published>2005-02-13T21:08:00.000-08:00</published><updated>2005-02-13T21:10:34.973-08:00</updated><title type='text'>Wertheimer's Gestalt</title><content type='html'>After spending my whole freshman year at design school reading Max Wertheimer's Gestalt theory, I guess it's fitting that the principles of gestalt be considered in a content creation class. Nothing should be considered without knowing the context. No concept or idea will be made lucid without contextualizing the surrounding information, bringing each piecemeal part of the composition into one cohesive whole. Nothing should be piecemeal. Ever.&lt;br /&gt;&lt;br /&gt;So now that the theory is there, how does one incorporate the precepts of gestalt theory into tacit, useful design? I think, that much like the Bauhaus school of art, the answer is already evident, at the forefront of all good design. To say form follows function would, in gestalt terms, implies that the design of a form must follow the needs of the function. And function can only be made clear the the contextualisation of all its elements, facets and uses. Once this is made clear, the form follows easily.&lt;br /&gt;&lt;br /&gt;One of my favorite sites which, ironically, is all about design theory, is adept in gestalt theory:&lt;br /&gt;&lt;a href="http://www.designobserver.com"&gt;http://www.designobserver.com/&lt;/a&gt;&lt;br /&gt;This site is in accordance with the main facets of gestalt theory, in that the context is clearly laid out for the viewer, the navigation, or continuation of threads of topics, is built in a hierarchical framework, allowing for chronological observation of a topic as it grows, hence further building a gestalt-framework for a clear understanding of the topics at hand.&lt;br /&gt;The design, minimalistic and subtle, reflects the theories and topics which abound on this site. The design informs the conversation. The conversation informs the design.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/10333058-110835772252678099?l=piperandtothemoon.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://piperandtothemoon.blogspot.com/feeds/110835772252678099/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=10333058&amp;postID=110835772252678099' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110835772252678099'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110835772252678099'/><link rel='alternate' type='text/html' href='http://piperandtothemoon.blogspot.com/2005/02/wertheimers-gestalt_13.html' title='Wertheimer&apos;s Gestalt'/><author><name>Piper and to the Moon!</name><uri>http://www.blogger.com/profile/02267220173370330790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10333058.post-110781227495617473</id><published>2005-02-07T13:12:00.000-08:00</published><updated>2005-02-07T13:37:54.956-08:00</updated><title type='text'>empathy for viewers</title><content type='html'>User experience is a highly amorphous term, in that each user's experience will be as unique as the individual.  That being said, there do appear to be common devices needed in any form of query: some kind of clear and easy-to-use system that yeilds satisfactory results.  Easy enough.  But what are the key factors that must be considered when developing a system that the general public will use?&lt;br /&gt;&lt;br /&gt;I found the contextual inquiries conducted by the Maya Design firm could be applicable not only in an actual environment like the Carnegie Library of Pittsburgh, but also in an online environment.  It would be a foolish assumption to state that all library-goers are looking for the same information, and all search for information the same way.  Therefore, it would be just as erronous to assume that all users online have the same needs.  To address the physical, cognitive and emotional needs of the viewer, it is necessary to not only walk a mile in the viewer's shoes, but to stay in that mindset throughout the research and design process. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/10333058-110781227495617473?l=piperandtothemoon.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://piperandtothemoon.blogspot.com/feeds/110781227495617473/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=10333058&amp;postID=110781227495617473' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110781227495617473'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110781227495617473'/><link rel='alternate' type='text/html' href='http://piperandtothemoon.blogspot.com/2005/02/empathy-for-viewers.html' title='empathy for viewers'/><author><name>Piper and to the Moon!</name><uri>http://www.blogger.com/profile/02267220173370330790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10333058.post-110722769342349354</id><published>2005-01-31T19:00:00.000-08:00</published><updated>2005-01-31T19:14:53.423-08:00</updated><title type='text'>group thinking.</title><content type='html'>As recently proven by the failures of the CIA, the whole notion of "group think" has dangerous implications.  In a supreme effort to build strong cases against supposed terrorists, the CIA allowed its view of the world to become myoptic and unbalanced.  With the zeal of true patriots, possibly matching the passions of the enemy, this collective group became so immersed in what they thought to be the truth, the first thing lost was, ironically, the truth they so desperately were seeking for.&lt;br /&gt;&lt;br /&gt;I think group thinking is not as uncommon amongst groups as one might think.  It comes in all forms;peer pressure, through the close bonds of friendship, and even through patriotism.   In regards to group thinking in a team environment, I think the only way to avoid such group thinking is obvious: tell everyone else they stink, that you are the boss, and that you won't have to get nasty if you just get your way. &lt;br /&gt;&lt;br /&gt;OK, just teasing.  Group thought probably creeps into the thought processes of groups in the most subtle of ways.  I'm not sure there is any way to avoid it completely.  However, while I think it's important to get along with the team, it's also important to remember that you all have a collective goal.  The goal can only be achieved through rigorous discussion and smart planning.  I would imagine that good planning at the first might aid in keeping roles clear, and rules straight. &lt;br /&gt;&lt;br /&gt;With the WOW group, I think that we all have such different interests and personalities, that  the possibility of a humogenous thought is unlikely.  However, by being mindful of the need for discussion, debate and constant revisions, I hope we can avoid group thinking entirely.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/10333058-110722769342349354?l=piperandtothemoon.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://piperandtothemoon.blogspot.com/feeds/110722769342349354/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=10333058&amp;postID=110722769342349354' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110722769342349354'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110722769342349354'/><link rel='alternate' type='text/html' href='http://piperandtothemoon.blogspot.com/2005/01/group-thinking.html' title='group thinking.'/><author><name>Piper and to the Moon!</name><uri>http://www.blogger.com/profile/02267220173370330790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10333058.post-110644123678058022</id><published>2005-01-22T16:23:00.000-08:00</published><updated>2005-01-22T16:47:16.780-08:00</updated><title type='text'>role playing?</title><content type='html'>While I thought some of the descriptions of the team members in the development team (from the web team roles reading) were absurd, I do see the inherent need for a well-rounded group of people in order for a project to be successful.&lt;br /&gt;&lt;br /&gt;I enjoy working by myself.  I like planning things for myself, and then doing it.  I like to do things like run races and triathlons, because it's a commitment that only I can make, and it's my ass on the line if I show up on race day unprepared.  I think that, like most people, I like to do things I feel I am good at. &lt;br /&gt;&lt;br /&gt;That being said, I think that makes me all the more willing to be part of a team where I feel it will be expected of me to contribute in the areas I am best qualified.  While I have definite opinions and aesthetic tastes about design, I know the design must be tightly interwoven with the content, the project objective, and the interests of everyone involved.&lt;br /&gt;&lt;br /&gt;I think the WOW group will fill the roles of the project is we see inherently fit.  As Brian said, it's an organic process, and we will all probably migrate towards roles that fit our personalities and strengths.&lt;br /&gt;&lt;br /&gt;To that end, I should say right now to my WOW team members that I am not a detail person.  I like thinking conceptually, visually.  I am great at fleshing out visuals to match the needs of the content.  But ask me to create a detailed site map and I am likely to run amiss.  That's not to say I wouldn't participate in the development of the site map, but in all fairness I think I should say upfront that my BFA was in Illustration, not HTML Development! :)&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/10333058-110644123678058022?l=piperandtothemoon.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://piperandtothemoon.blogspot.com/feeds/110644123678058022/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=10333058&amp;postID=110644123678058022' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110644123678058022'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110644123678058022'/><link rel='alternate' type='text/html' href='http://piperandtothemoon.blogspot.com/2005/01/role-playing.html' title='role playing?'/><author><name>Piper and to the Moon!</name><uri>http://www.blogger.com/profile/02267220173370330790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10333058.post-110643884196983071</id><published>2005-01-19T16:02:00.000-08:00</published><updated>2005-01-22T16:20:08.686-08:00</updated><title type='text'>Team experiences</title><content type='html'>My experience with teams has been limited to sports and work. I think I prefer the context of sports, as each team member's role is clearly defined, and the guy in the striped shirt can blow his whistle and kick anyone out who isn't playing by the rules. That being said, I think the work context is what is in question here, so without further digression...&lt;br /&gt;&lt;br /&gt;I think the most effective teams have clearly defined roles. There is an established chain of command, with people willing to fill all roles as needed.&lt;br /&gt;I think the most effective teams have an implicit trust in each other, a willingness to be open-minded, open to criticism without getting emotional, and a desire to get shit done. period.&lt;br /&gt;&lt;br /&gt;In regards to effective and preferred means of communication, I'm open to all methods.  For our group assignment in Kathy's class, email is probably the best way to communicate.&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/10333058-110643884196983071?l=piperandtothemoon.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://piperandtothemoon.blogspot.com/feeds/110643884196983071/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=10333058&amp;postID=110643884196983071' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110643884196983071'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110643884196983071'/><link rel='alternate' type='text/html' href='http://piperandtothemoon.blogspot.com/2005/01/team-experiences.html' title='Team experiences'/><author><name>Piper and to the Moon!</name><uri>http://www.blogger.com/profile/02267220173370330790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10333058.post-110643823891405986</id><published>2005-01-17T15:51:00.000-08:00</published><updated>2005-01-22T16:09:46.333-08:00</updated><title type='text'>a little test.</title><content type='html'>I had blueberries for breakfast.&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/10333058-110643823891405986?l=piperandtothemoon.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://piperandtothemoon.blogspot.com/feeds/110643823891405986/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=10333058&amp;postID=110643823891405986' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110643823891405986'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10333058/posts/default/110643823891405986'/><link rel='alternate' type='text/html' href='http://piperandtothemoon.blogspot.com/2005/01/little-test.html' title='a little test.'/><author><name>Piper and to the Moon!</name><uri>http://www.blogger.com/profile/02267220173370330790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
