Tackling the problem(20-30 minutes)
- Start with a hook
- What is the big aim - your overall philosophic goal.
- Explain the problem in the world you hope to tackle. Give us a history of the issue.
- Why is this important right now?
- Is this a new problem we need to solve, or or is this an old problem that a changing world can now fix?
- How has journalism tried to solve this before? Or has it?
- What is wrong with previous solutions that have been tried.
- What makes this a "good" problem in innovation under Studio 20's understanding of that term?
- How do you intend to solve this problem?
- How will your solution succeed where other solutions to the problem have failed before?
- What issues or challenges do you foresee? How do you plan to overcome them?
- Why are you the right person to solve this?
- Who is your partner, and why have you chosen them to test your solution?
- What metrics will you use to measure your success?
- Show us a rough schedule of work
- Sum up your thoughts
- Finish strong.
Start your Planning
- Identify our big aim, you overall philosophic goal.
- Pick a title
- Start developing an Elevator pitch, and be ready to recite it on demand
- Identify your constraints
- What are your final deliverables?
- Create a Work Breakout Structure
- Identify who your users will be.
- Use qualitative or quantitative methods to find out the qualities that your project will need to be a success.
Doing your analysis and design
- Create a user scenario based on your vision of how people will use your project
- Create a basic userflow diagram for your system
- Wireframe the important states of your system, be they screens, interactions, or physical configurations
|Having trouble nailing down an elevator pitch? Try this: "NAME is a NOUN that VERBS and by doing so it BACKGROUNDS"
Theme: Project design
- Elevator pitch
- A reminder of the background problem you're trying to solve
- A reminder of your project's scope and who your partner is
Proof of progress
- Longer description of how your project will work. Can include wireframes and userflows diagrams, mockups, or partially completed work to get the idea across
- What updates and changes have you made since you first conceived the project? What issues have you run into, and how are you handling them?
- Update of schedule
- Use a FORMAL CONCLUSION, as though this was a project pitch.
Completing the Agile Circle
- Update your plan, analysis and design based on the tester feedback and the class feedback from the last presentation.
Do your first round Implementation
- Create a rough implementation of your project, a first draft. It does not have to be perfect or complete, but it does have to reflect the final form the project will take. Something so that the class can give feedback on if the final thing will work or not.
Do your first round testing and evaluation
- Seek user feedback on your design.
- Tell us what you’ll fix for the final version of the project, and make any updates to the project Plan and Design required
When making your slides:
- Move as much text as possible into your Notes section, and practice presenting using it. That info can almost always be turned into images, graphics, flowcharts, or diagrams.
- Start moving titles that reflect the presentation writing process off the screen. Such as "Elevator pitch", or "Schedule"
Trouble with a conclusion? It must contain these two things:
- Sum up what you've said. What were your high points, and what do you want to reassure people about.
- What do you want your audience to do now? Do you want them to ask you questions? Engage in a discussion? Get to know the next speaker? Start a riot?
Theme: Final findings discovered and how they apply to the future of journalism.
This is not "Show and Tell" style as the other presentations have been, it should focus on your findings first, process and deliverable second.
You have completed an
experiment to prove a hypothesis. Was it true or not? Prove it to us using your deliverable as an example.
Create your presentation outline:
- Elevator pitch
- Demo or thorough walk-through of your project.
- Philosophic background - Why is this project important, and why is it important NOW
- Original Hypothesis and eventual findings What were your assumptions going in to this project
- Experimental process What did you do to get here. What were your biggest challenges?
- Evaluate your successes and failures Remember, by failures we mean your findings. Places where your hypothesis was proven wrong due to experimental failure. Remember, it's not a failure, it's a finding.
- Call to Action What are the future implications. What are your next steps - if someone was to continue the work you've started, who should they be and how should they do it.
- Give credit where credit is due
Make this presentation as long as you want - it's much easier to edit a large presentation down than start small and add things you left out.
All media, videos, and other demos must be embedded in the PPT presentation so there's no reason to leave it while speaking. If it's a software demo, take a video of it. If you need to scroll through a website, take a full-length screenshot and animate it to move slowly up.
Use the notes area of your PPT presentation. To practice using on-screen slides, use the Mac PPT option "Rehearse" which you can find under "Slideshow"
Screenshots should take up the entire screen of the presentation - don't artificially shrink them to make room for your own logos and graphic elements.
The final picture in the presentation should represent something you want people to remember. A stirring image or screenshot. No clip-art or stock photography, or the word "Questions?"
Make sure all slides are sent to Zoe the Monday before your presentation. By then they should be finalized and you will have already practiced a billion billion times over the weekend.