Project Demos

Finish something. Anything. Stop researching, planning, and preparing to do the work and just do the work. It doesn’t matter how good or how bad it is. You don’t need to set the world on fire with your first try. You just need to prove to yourself that you have what it takes to produce something. There are no artists, athletes, entrepreneurs, or scientists who became great by half-finishing their work. Stop debating what you should make and just make something.

~James Clear

Keep Going Illustration by Jolby from Gettoworkbook

Project Demo Basic Overview

• Do NOT create a supporting presentation.

• The focus is on the actual artifact you are creating and nothing else.

• You will demo your project in its current state.

Project Demo Framework

Project Demos will be held on designated Wednesdays. Each demo will consist of:

• Up to 5 minutes max of presentation and

• use the remaining time for feedback

• 10 minutes total

Review the rules of the critiques (AKA getting and giving feedback).

• Have a member of your accountability team take notes for you when your work is being critiqued and do not edit the responses, whether you agree with them or not.

Project Demo Detailed Info & Resources

• Because each student is working on individual projects, your project demo may vary, but you need to show something visible and concrete.

• You can also show multiple things for your project demo. Put each one in a separate padlet card.

• Make sure you review the Design & Production Workflow (AKA Pipeline) resources.

• For UI/UX for websites and apps, your project demo could include user workflow, user journey, and/or customer journey, sitemaps, wireframes/schematics, and/or clickable prototypes in the software of your choice.

  • This is an example of a good wireframe: https://fuzzymath.com/wp-content/uploads/2011/07/Fuzzy-Math-How-to-read-a-wireframe.pdf with the exception of the one paragraph of lorem ipsum text. Also do not use color.

• For animations/videos, your project demo could include storyboards, style frames, animatics, audio, and/or motion tests.

• If you're working on a game, you could include the story, character & other object sketches, interaction tests, levels, maps, puzzles, etc.

For additional information, visit project versions.

Document your feedback

Always document any feedback you receive on your process website and/or project management platform after any critique. This critique feedback post should include images of the current status of your project (prototype or version), a description of your project progress as it currently stands, and discussion of the feedback you received from the critique. How will this feedback improve your work and ideas?