Open main menu

Changes

no edit summary
* '''Test the prototype''' with the relevant people -- students, faculty, etc., depending on what it is (see below some things to keep in mind as you test). Remember when you had to go out an interview someone on the first week of the challenge? Testing your prototype is similar to that: you might feel apprehensive about showing a prototype that doesn't look very polished to someone else, and that's understandable. Use some of the same strategies you used to set up your interview: introduce yourself and the project, establish a rapport with the other person, encourage him/her to be candid with you, and demonstrate you really care about what he/she says. You will find that people will be incredibly helpful, even flattered that you care about their perspective.
* '''Iterate'''. Based on what you learned about the problem or the solution, you might make a minor modification, learn that the you are solving for the wrong problem or make large changes in your strategy for how you solve the problem. Incorporate your learnings into creating a new prototype and test once again with the same person or different ones.
* '''Take a photo of people testing your prototypes,''' and include a short reflection about what you learned from the tests. If you are part of a Leadership Circle, combine all your photos and learnings into one submission.<br><br>{{Fmbox|image=none| style = style = border:5px solid #008b8bdimgrey; background-color:#f1fcf8lightgrey;|text=Due October 3 at midnight ET: A google doc containing a photo of people testing your prototypes, and a short reflection about what you learned from the tests. Drop this document into your campus folder in [https://drive.google.com/drive/folders/1BrL69LY4a-Pe1Cu4bQ6uaKcDbEH1n2JZ this Google Drive folder].}}<br>
:Here are some elements to keep in mind when you test your prototype:
* Do NOT sell your idea: Your goal is NOT to convince someone that your idea is good. You want to find out what can be improved.
* If you're the only candidate at your school, you may only be leading one project to start, but you should still take the position that the remaining projects need to be assigned to other people on campus.<br><br>
'''A consulting approach'''<br>
Approach your upcoming meetings with faculty and administration as though you are a set of consultants who your school has hired to recommend four to five projects to address the key issues facing the campus I&E ecosystem. What are those top four to five projects you believe your campus should implement in order to expand I&E on campus?<br><br>{{Fmbox|image=none| style = border:5px solid #008b8bdimgrey; background-color:#f1fcf8lightgrey;|text=Due October 3 at midnight ET: Link to completed/updated Strategic Priorities Wiki page.}}<br>{{Blue button|link=2020:Training/School Wiki Page Links|text=Click here to access your campus's strategic priorities Wiki page.}}<br>
On your Strategic Priorities wiki page, outline the four to five projects you have identified and refined by prototyping. Include not only the project name, but also the key tactics required to bring this project to life. Be as specific as possible, including assigning names of the team mates who will be in charge of each project. Make sure you review your plans with your uiguide and faculty champion(s) and take into account their feedback.<br><br>{{note2|'''Note:'''}} If you are a new campus on the program, you will be the first cohort to add content to the Strategic Priorities wiki page, but if you are a campus who already has Fellows, this page already will have content added by previous Fellows, and you should update the page to add your cohort's strategic priorities. Do this is reverse chronological order, so that the most recent set of priorities are at the top of the page, and clearly indicate to which cohort they correspond.<br><br>Visit the [[2020:Training/Submitting Assignments|Submitting Assignments]] page for more on how to submit this deliverable on the UIF Portal.
}}