Tonight, I'm meeting with JP at Vera to strengthen up our outline for this comprehensive procedural policy. (A true security policy is more than just security in the traditional sense, it becomes evident in every section of general venue procedure, and we have chosen to embrace that by creating a venue-wide procedural policy, rather than just show security policy, which will be merely a section of our large work)
Monday, May 10th, we're meeting with Greg again, to start getting the content into our outline.
This I am completely stoked for, and yesterday, had the chance to present the project to the membership's programming committee, and get them abroad. Feedback as been positive, and people are excited and already signing up for the membership-optional security training session we have tentatively planned for the 22nd.
However, I am no longer excited about my capstone project. I think the limitations of having to create something-- for an audience that isn't the audience I am working with and whom the final procedural policy is written for-- is, in my mind, too academic and not enough applied "to the real world." Based on my chats with people during my research, there isn't really anything tangible worth creating at this point. People in class want to see some sort of booklet thing basically illustrating how to give youth ownership. Which is ...nice (that's what we say about people/things we have nothing negative to say about but nothing else positive to say about either, isn't it?), and probably what I'll end up doing if I can't think up anything else more useful... but meh.
Wednesday, May 5, 2010
Sunday, May 2, 2010
relationships
can be so powerful.
Another reason to give teach, nurture, and give youth ownership: because they develop a respect and appreciation of the place, in a way that motivates them to protect the place, and to support it rather than do harm.
Another reason to give teach, nurture, and give youth ownership: because they develop a respect and appreciation of the place, in a way that motivates them to protect the place, and to support it rather than do harm.
even before
It's amazing the amount of preemptive steps that can, and should, be taken to prevent anything problematic from arising. From who you hire to making allies with the charismatic leader in the social group, most problems and situations can be discouraged and erased before they cause harm to anyone.
to inform
Phone tag finally came to an end, and Greg, Josh, and I had a meeting on Friday. Here is our timeline so far for rolling out the policy for Vera:
We timed the dates to coincided with our monthly meetings and quarterly members meetings because those are when we'll have the highest number of stakeholders all together to discuss, debate, and approve this project.
May 18: presentation of outline and open discussion at show staff/steering meeting
May 22: 3 hour show security training for staff (Tentative)
June-Sept: [meetings with various stakeholders (for sure staff and steering, potentially programming and board) at their monthly meetings, exact agenda and dates tbd]
Oct 14: Presentation at quarterly members meeting with proposed draft. By now, all stakeholders would have had a couple chances to give input on the policy between June-Sept, and a final committee vote of approval would have been taken to send the policy to a vote at this Oct 14th member's meting. Discussion would be on fine tuning and minor changes.
Jan 15: Presentation and vote of approval by membership at this quarterly member's meeting.
I'll have to revisit my plans on what to show for June. My project will very much be focused on bringing attention to the need for such a policy to be developed, but I'm not sure what tangible item is best for that, or if there's even need for one. I don't want to make something for the sake of having something to show...
I have another meeting this afternoon, so I'll see if that is useful in any way, and update later tonight!
We timed the dates to coincided with our monthly meetings and quarterly members meetings because those are when we'll have the highest number of stakeholders all together to discuss, debate, and approve this project.
May 18: presentation of outline and open discussion at show staff/steering meeting
May 22: 3 hour show security training for staff (Tentative)
June-Sept: [meetings with various stakeholders (for sure staff and steering, potentially programming and board) at their monthly meetings, exact agenda and dates tbd]
Oct 14: Presentation at quarterly members meeting with proposed draft. By now, all stakeholders would have had a couple chances to give input on the policy between June-Sept, and a final committee vote of approval would have been taken to send the policy to a vote at this Oct 14th member's meting. Discussion would be on fine tuning and minor changes.
Jan 15: Presentation and vote of approval by membership at this quarterly member's meeting.
I'll have to revisit my plans on what to show for June. My project will very much be focused on bringing attention to the need for such a policy to be developed, but I'm not sure what tangible item is best for that, or if there's even need for one. I don't want to make something for the sake of having something to show...
I have another meeting this afternoon, so I'll see if that is useful in any way, and update later tonight!
Monday, April 26, 2010
showing process
Kelsey brought up in class today a great question on the topic of the design process.
It's hard enough to understand our "design process." But how do we portray it? In a discipline that prides itself on the process as much as, if not more, than our product, what would our "process book" look like? In VCD and ID, you'd see ideation from rough sketches to computer generated mock ups or prototypes, to the finalized product. In design studies...?
Perhaps that is what makes us unique. Our varied background and the different contexts in which we do our work, informs different processes for each of us, in a way that does not lend itself to an idealized, standard DS "processbook."
It's hard enough to understand our "design process." But how do we portray it? In a discipline that prides itself on the process as much as, if not more, than our product, what would our "process book" look like? In VCD and ID, you'd see ideation from rough sketches to computer generated mock ups or prototypes, to the finalized product. In design studies...?
Perhaps that is what makes us unique. Our varied background and the different contexts in which we do our work, informs different processes for each of us, in a way that does not lend itself to an idealized, standard DS "processbook."
Sunday, April 25, 2010
only logical
I think it's been hard to illustrate to others what makes youth different in a way that creates the need for my project. I don't know why I didn't do this early, but it's time to create a persona!
Meet Quinn!
Quinn is a 17 year old junior in high school, living in the suburbs of Seattle. He is taking sound production classes at his local community college. Quinn plays the guitar (self-taught), and jams weekly with a band formed of his high school friends. His favorite artist is John Vanderslice. He can almost always be spotted wearing a band shirt, showing off his musical preferences. Quinn attends 3-7 shows a month, most of which are local, small indie bands. He generally also attends Folklife, Capitol Hill Block Party, Sasquatch, and Bumbershoot. He attends in-stores at Easy Street whenever it features a band he enjoys. Quinn downloads a lot of music, but also owns vinyl of all his favorite artists. He owns some cds, but mostly his cd collection consist of mixed-tapes from his friends. Quinn also burns cds of his prefered artists for his friends and acquantiances, although he is slowly shifting from phsyical disks to posting links on friend's facebooks.
Meet Quinn!
Quinn is a 17 year old junior in high school, living in the suburbs of Seattle. He is taking sound production classes at his local community college. Quinn plays the guitar (self-taught), and jams weekly with a band formed of his high school friends. His favorite artist is John Vanderslice. He can almost always be spotted wearing a band shirt, showing off his musical preferences. Quinn attends 3-7 shows a month, most of which are local, small indie bands. He generally also attends Folklife, Capitol Hill Block Party, Sasquatch, and Bumbershoot. He attends in-stores at Easy Street whenever it features a band he enjoys. Quinn downloads a lot of music, but also owns vinyl of all his favorite artists. He owns some cds, but mostly his cd collection consist of mixed-tapes from his friends. Quinn also burns cds of his prefered artists for his friends and acquantiances, although he is slowly shifting from phsyical disks to posting links on friend's facebooks.
Monday, April 19, 2010
What is DS?
Back to the ultimate question.
DS IS ABLE TO
be an adaptable process
communicate with diverse audiences
gather and synthesize disparate information
TO
find new relevant problems
connect design to outside fields
change/influence behavior, ways of thinking, society, and context
SO THAT WE CAN
understand how designs fit into larger systems
produce novel frameworks for understanding information
produce products that may be more traditional graphic or physical design, or a design for a system
DS IS ABLE TO
be an adaptable process
communicate with diverse audiences
gather and synthesize disparate information
TO
find new relevant problems
connect design to outside fields
change/influence behavior, ways of thinking, society, and context
SO THAT WE CAN
understand how designs fit into larger systems
produce novel frameworks for understanding information
produce products that may be more traditional graphic or physical design, or a design for a system
Subscribe to:
Posts (Atom)