Summative presentations and hand-in
We'll start at 10:00 and we aim to wrap up by 3pm-ish.
In the morning you will present your work on Sharing is caring, the cause you chose to advocate through a one-pager. In the afternoon you will pitch your proposal for the Web Media micro-site, aka Our space.
| Which project? | Who? | How long? |
|---|---|---|
| Sharing is caring | Individual | 5 minutes per person |
| Our space | Team | 15 minutes per team |
For each project, prepare a pitch presentation.
As a pitch, you want to focus on the solution your site provides to a problem for your target users (less on the process).
Talk about them, not yourself.
The structure of your pitch is up to you.
A story is an effective and proven way to structure your pitch.
Humans have been telling stories for thousands of years, and our brains are wired to emotionally respond to stories more than to facts and figures. When someone tells you a story, the same areas of your brain and their brain get active. If they say "Danny kicked the ball..." your motor cortex, which coordinates your body movements, will fire up. That's how powerful stories are.
You can frame your pitch as a story in a couple of ways:
-
Challenge > process > outcome (from a client point of view)
-
Problem > solution > result (from a user point of view)
Your slides should help your audience focus on your key points. If you put too much text in your slides, you'll end up confusing people.
Tip: one point per slide.
Avoid showing what you are saying and saying what you are showing.
When you stand up to present your project, remember that everyone wants you to win.
If you're a little nervous, take a few deep breaths.
Throughout your presentation, get comfortable with silence. Everyone needs a bit of it to digest what you're saying.
Silence is better than bullshit.
Create a WEB14105-Name-Surname.md MarkDown document (where Name is your own name and Surname is your own surname, like WEB14105-Matteo-Menapace.md).
You can edit MarkDown documents with the Mou app on OSX, the MarkdownPad app on Windows, or online with Dillinger (all free).
In that MarkDown document, add the following:
- Sketches, concepts and storyboards
- Wireframes
- Research GDoc including target audiences, content structure & copy, and make sure I have permissions to comment on it
- Content strategy GDoc, make sure I have permissions to comment on it
- Formative video-presentation link, YouTube or Vimeo, make sure I have permissions to view it
- Link to your project code on GitHub
- Link to your project published on GitHub Pages, remember
gh-pagesfrom week 2?
- Interviews and survey insights
- Competitor analysis
- Personas
- Content map
- Content strategy
- Typesetting experiments
- Wireframes
- Moodboard
- Formative presentation
- Summative presentation, either as slides or a link to YouTube (in case you couldn't present in class)
- Link to your project code on GitHub
- Link to your project published on GitHub Pages, remember
gh-pagesfrom week 15?
- JavaScript for cats
- Make a drawing to illustrate how the Web works
- Get the Idea: capturing attention
- Infographic stories
- Copywriting is Interface Design
- Infographics, good and bad
- Interviewing humans
- Our space interviews
- Our space personas
- 10 common typography mistakes
- Web design myths
- Destroy the Web
- What did I learn?
Make sure all the folders, pages, documents & presentations you linked in your
WEB14105-Name-Surname.mdare publicly accessible (not just private to you). I don't want to be asking permissions to view this file while you're off :)
Upload and submit your WEB14105-Name-Surname.md through Moodle here learn.rave.ac.uk/moodle/mod/assign/view.php?id=81716
Deadline is Friday 10th of June 2016, 23:59! 👠