Tool 1
RTR CARDS
The cards of Real-Time Research have become one of my favorite tools. They really don’t do anything more than start the conversations that build toward ideas, yet they provide a structured game element to the process that sets a tone for play in work alongside giving the facilitator the ability to frame the conversation. Each time we run RTR some groups have used these as a challenging constraint, while others simply let their conversations run into completely different topics from where they started. This flexibility is part of the value of the cards.
For you, and your use, the cards below are the latest iteration. They have been changed each time we have done RTR and you’ll want to alter them for your use also. Play with the types of cards, contents, and topics and you can really use RTR as a tool in any setting, classroom, or project. Have fun.
Theory Cards
Method Cards
Topic Cards
Tool 2
STRUCTURAL OUTLINE
Because there were four of us, we used a shared planning document to organize. This tool was key to making sure everything was set. In addition to the list of items needed, we had a rough breakdown of the time and roles played during the session. At the end are ideas for coming RTR sessions you may want to employ.
MATERIALS NEEDED
Session
• Printer for session room/RTR Booth (w/ associated cords)
• Notepads/pens/markers for each group.
• Power strips (for many active laptops) or check for outlets in room
• Create an e-mail address for RTR (so folks can send files to have printed)
• Clipboards (10)
• Paper (1-2 reams)
• Stapler, markers, pens, notepads, string, tape, portable file/organizer, file folders, easel w/ sheets of paper
Presentation Materials
• Set of Cards - Color glossy printing on card stock
• Keynote presentation (if wanted) and template for group presentations
• Consent and ethical research guidelines printed out
• Templates of data collection tools printed and ready
SESSION 1: THURSDAY (90 MINUTES)
Introduction (10 minutes)
C/E/K introduce the impetus for the project, talk about how everything is going to work, and – most importantly – set expectations. For example, the goal is to do real research here, but it will be fast and loose, in a prototyping and collaborative spirit. This introduction is also the chance for us to see who is in the room and strategize about how to divide into groups.
Divide into groups (5 minutes)
This is perhaps the trickiest step. We need to be sure that we have right-sized groups, and that the groups are balanced in some way. Groups could be randomly determined, or we could have a system, such as giving each person a color-coded index card corresponding to their identity (researcher, educator, designer, etc) and make sure that each group has at least 1 of each color. Typically in design exercises it is good to have people working with strangers, but since this experiment will last across the entire conference, there are advantages to taking advantage of existing social ties – so we might let people self-select groups.
Hand out cards (5 minutes)
Each group will have a set of cards. These are the things that we’re going to discuss in the call tomorrow. We’ll probably have at least two types of cards (such as methodology and topic) and each group should get a limited number, such as two of each type.
Trade cards (10 minutes)
Once groups are set with their cards, we’ll have a quick trading frenzy. We’ll set up a dozen additional cards on a table, and groups can put one of their cards down on the table and take another. They always have to put one down to take another, so that other groups all always have the same number of choices. This kind of thing helps groups feel like they are authoring their own parameters, and it is a nice bonding experience where they get to see who in the group is interested in what.
Brainstorm experiments (20 minutes)
OK, now the groups are set, they have their card-based parameters, they know what this session is about, and here’s the time when they actually begin to design experiments, using their parameters to guide them. The goal here is to think in guerilla terms – to figure out what they actually can do over the course of the conference. While this is going on in the room, we should have up on the screen a list of the resources and contexts available to them, such as the number and type of attendees in the conference, a list of breaks and meals where people can be corralled into doing a survey, etc. We might also create a handout that has this information. The goal of this first brainstorm is for the groups to come up with a concrete plan for their experiment. Twenty minutes goes quickly, but less time is better because it forces them to be decisive. The three of us can listen in on these discussions, but it’s better to not have too much input so each group can own what they are doing.
Quick critiques (15 minutes)
Here we pair up groups, so that each group can pitch another group their experiment, and can get feedback on their idea. This is an important moment in the design process, when you get outside criticism and support. Also, all the participants will realize that other groups are struggling just like they are, and this builds solidarity within a group and among all the attendees. It also helps set the stage for the second session, because attendees will want to see how the experiments of their matched-up group fared. The three of us will also sit in on these critiques and offer feedback.
Final planning (25 minutes)
The last section of the session is for groups to finish their planning, put together surveys, etc. They should be dividing the labor at this point among the people in the group, and we should have printers ready to print out what they need. Also, the three of us should be helping groups strategize the logistics of what they want to accomplish over the conference, since we won’t all meet as a group until the final session again. Groups should plan to present whatever it is they managed to do (or not do – there is no such thing as “failure” on the Real-Time Research planet) at the final session the next day.
IN-BETWEEN THE SESSIONS
This is harder for me to plan, because you two know the structure of the conference better than me. Ideally, we would have a table in the main concourse with a big sign that says “Real-Time Research.” At the plenary session, whenever we have a chance to make an announcement to the whole conference, we should tell people to stop by the table.
This table will be the central gathering place for attendees to come and pitch in as research subjects. Students or volunteers should be at the table the entire conference and be able to conduct experiments without the session attendees being there. One thing we might do is think of swag that a GLS attendee would get for being a subject, like a t-shirt or some candy, or be entered into a drawing for a prize (but I think a small prize for each subject is probably best).
I think we should expect that these experiments will probably not come together until lunchtime on Thursday, but even so, they still have more than a full day to gather data. We should expect that some groups may do much wackier things, such as design a social game for the conference itself, that won’t require the table and setup we’re going to provide.
SESSION 2: FRIDAY (90 MINUTES)
At this session our main goal will be to have groups share their experiences, for better or worse. The exact time each group has will depend on the number of groups, but we should aim for very short presentations and then spend most of the time on discussion.
Each group should appoint one responsible person to gather all of the materials and results from the group and send them to K/C/E. And perhaps we can promise to think about writing an article – or even some kind of short blog entry – about it.
ALSO...
SUNDRY STUFF
(ideas that came up as part of our article):
• add a session between (midway through as a kind of “check in” for participants) to make sure everyone’s on track?
• add a panel of judges to the final presentation & give out awards for various categories?
• have some example studies that we present in our intro?
• get some safari type “field hats” with cards stuck in them (like old “press” hats) so those who are running studies are clearly designated?
• get some “lab coats” for visual distinction when in field?
Tool 3
GOODIES
Setting up goodies also meant organizing a booth, or drop-in location for our RTR groups that served as a central station to pick up supplies, make copies, or come for help with anything they may need. The goodies list became set up document we used for the booth in addition to listing ideas for future conferences that you may make use of too. Short and sweet, the goodies list helped get ready for the non-session parts of RTR.
BOOTH
• Table SMD
• Table Cloth
• Big sign (“RTR: Real Time Research w/ GLS logo) Lamenated 2 - 2’ x 3’ Poster
• Printer for booth Sharing with new GLS printer.
• Internet connection here Wireless at MT
• Create an e-mail address for RTR (so folks can send files to have printed) Will cre ate on G-mail if no preferences
• Clipboards (10)
• Paper (1-2 reams)
• Other supplies: Stapler, markers, pens, notepads, string, tape, portable file/organizer, file folders, easel w/ sheets of paper
GOODIES
• t-shirts?
• decks of RTR cards
• CANDY (preferrably chocolates for CS)
• ”I Subjected” stickers
• Cute participation awards
POTENTIAL MATERIALS
(have a plan for access if needed):
• Full Time RTR Grad student w/ parking passes (to make supplies runs)
• Access to copy machine will be needed.
• Separate table, close to registration.
• Set up RTR forum/wiki/type thing for folks to stay in touch if wanted.
• Video cameras
• Digital cameras
• Tag boards/White boards w/ easels/public wall space
Tool 4
SLIDE TEMPLATES
Slides
Tool 5
GROUP SUMMARY FORM
GROUP CONTACT INFORMATION
Members E-mail
WRITING FOLLOW UP & CONSENT
With your permission, we would like to include your RTR Project Report in an edited book we are publishing online through ETC press .
There are two levels of participation – “extended abstracts” versus “book chapters.” For those of us who aren’t able to do any writing or editing outside of the conference time already given to the RTR project, we would publish your write up “as is” (with only minimal copy edits where necessary” as an “extended abstract” (2 pages or less) in the book. For those of us with a special interest in the RTR project and its publication, we would work with you to revise and expand your RTR Project Report as a peer-edited book chapter for the volume. Turn around time would again be relatively short but here you can take credit for a full peer reviewed publication with promise to make genuine contribution to the field. Either way, you get authorship on the piece included in the edited volume to reflect your intellectual ownership of the work.
Please indicate below if you are willing to publish your RTR Project Report as either an Extended Abstract or Full Chapter in our edited, online volume entitled “Real Time Research.” Also indicate who can serve as the main contact on your team (we will assume it is the first name listed if no other name is indicated as main contact). If you are unable to participate in either way, we still love you and will scrap your report.
Tool 6
REPORT TEMPLATE
RTR: Report Name
Author 1, Author 2, Author 3, Author 4, Author 5
Review & Research Question
Replace this text: In a paragraph or two summarize how your group came to your targeted research question and why you felt the question was important or interesting to study. If there is specific body of literature that brought your group to the question or helped you frame this work in some way, reference it here.
Clearly state your group’s research question.
Methods
Replace this text: Explain the method by which your group gathered data to answer your stated research question above. The methods described here should how you selected participants and the procedure that you used to gather data from those participants. If the data consists of a pre-existing set of information (such as anonymous forums), detail the nature of the data here . This section varies broadly across projected given the wide range of various project pursued as part of the RTR workshop; word your description carefully so the reader could replicate the process if they wanted.
In a second paragraph, explain the process your group chose for data analysis. What methods are you using to interpret the data you collected in order to answer the research question stated above Again, this section will be highly dependent on the kind of question your group decided to pursue.
Findings
Replace this text: After your group collects and then analyzes your data, record here any general conclusions, indications, or trends you see based on your investigation. Include not only the general characteristics of the data that you happen to notice but also findings that you didn’t expect to see. Given the iterative and quick turnaround of RTR, unexpected findings are common and part of what makes the experience fun and interesting.
Include any mini-charts, graphs, telling photographs or other visuals that help represent your project. Please do not include any images of participants themselves.
Conclusions & Next Steps
Replace this text: Explain the importance of your findings on a broad, more generalized level. What are the implications of your findings? What takeaways, if any, do you have from the project ? What did you learn?
In a second paragraph talk about if and how this project would be expanded or followed up on formally. Would you recommend a large scale version of this study or a modified version? Is it worth the effort of further work? Why? Why not? Are there follow-up questions you believe are worth pursuing?
Tool 7
GROUP ETHICS GUIDE
& CONSENT FORM
Any contact with people outside of the session with the intent to collect data becomes subject to common research guidelines. We ask you to adhere to these guidelines in any interactions for your group project at the conference.
Any and all data you collect as part of the project may be used in the final session along with your analysis and conclusions from the experience, however it cannot be used for outside publications beyond the RTR online book through ETC press. If you want to conduct further research based on this RTR project beyond the purview of this conference workshop, you must contact your own institution’s IRB board (if applicable) and obtain the necessary consent and approvals as deemed necessary. RTR is intended to function as an ‘open source’ venue for idea generation and dialogue between professionals in disparate domains here at the conference. Subjects explored as part of the RTR workshop are open for exploration elsewhere but not the data collected as part of this learning experience is not for use anywhere else, under any circumstances.
DO’S
On initial contact, use the script provided below & attain oral consent from all sources.
Remind people that all participation is voluntary at all times.
Identify yourself as an RTR participant at the conference.
Use this experience to create follow up research or products!
DON’TS
Collect any personally identifiable information.
Deceive as part of the study.
Inquire about any potentially embarrassing, personal, or intimate topics.
Force or “push” yourself on others at the conference.
CONSENT SCRIPT
Please use the following script to obtain oral consentfrom individuals before gathering any data:
“Hello, my name is .
I’m part of the “Real Time Research” session here at the conference and I am looking to gather information as part of the session. You were selected because .
There is no expected risk or benefit for being part of this study, other than this nifty sticker that says “I Subjected” which, we feel, is a clear benefit.
Any participation on your part is voluntary and you can exit the process at any time for any reason. We will neither collect nor keep no personally identifiable information.
Would you be willing to spare a bit of time to be part of RTR this year and get a cool sticker?”
Tool 8
FOLLOW-UP FORM
GROUP CONTACT INFORMATION
Name E-mail or IM
WRITING FOLLOW UP AND CONSENT
With your permission, we would like to include your RTR Project Report in an edited book we are publishing online thru ETC press .
There are two levels of participation – “extended abstracts” versus “book chapters.” For those of us who aren’t able to do any writing or editing outside of the conference time already given to the RTR project, we would publish your write up “as is” (with only minimal copy edits where necessary” as an “extended abstract” (2 pages or less) in the book. For those of us with a special interest in the RTR project and its publication, we would work with you to revise and expand your RTR Project Report as a peer-edited book chapter for the volume. Turn around time would again be relatively short but here you can take credit for a full peer reviewed publication with promise to make genuine contribution to the field. Either way, you get authorship on the piece included in the edited volume to reflect your intellectual ownership of the work.
Please indicate below if you are willing to publish your RTR Project Report as either an Extended Abstract or Full Chapter in our edited, online volume entitled “Real Time Research.” Also indicate who can serve as the main contact on your team (we will assume it is the first name listed if no other name is indicated as main contact). If you are unable to participate in either way, we still love you and will scrap your report and not make use of it in any published materials generated as a result of this workshop.
CONSENT FOR PARTICIPATION
I am interested in publication of our report as (sign and check):
Name
❏ Extended Abstract ❏ Book Chapter ❏ Neither
❏ Extended Abstract ❏ Book Chapter ❏ Neither
❏ Extended Abstract ❏ Book Chapter ❏ Neither
❏ Extended Abstract ❏ Book Chapter ❏ Neither
❏ Extended Abstract ❏ Book Chapter ❏ Neither
Replace this text: Explain the importance of your findings on a broad, more generalized level. What are the implications of your findings? What takeaways, if any, do you have from the project ? What did you learn?
In a second paragraph talk about if and how this project would be expanded or followed up on formally. Would you recommend a large scale version of this study or a modified version? Is it worth the effort of further work? Why? Why not? Are there follow-up questions you believe are worth pursuing?