Design Team UI·UX Presentation Guidelines

The official checklist for the design team’s UI·UX presentations

Version 1.1 (Last edited 29-March-2019)

Note: Please keep the presentation simple and under 15 minutes. No slides or Powerpoints are necessary. The presentation should demonstrate (1) your workflow during the execution of the project, and (2) a unique, fully developed application or service.

The following 5 elements should always be included within a UI·UX presentation.

1. Present the project constraints and design problems.

— — —

THIS IS THE MOST IMPORTANT STEP. Designers tend to forget and confuse (1) Project Constraints (Which are high level concepts that cannot be changed and are set in stone) with (2) Ideas for Execution (Which are detailed methods of implementing the Project Constraints), especially when multiple designers start working on long projects with iterations.

For instance, ‘The Client wants Users to be able to give multi-dimensional reviews’ is an abstract concept and requirement, which makes it a Project Constraint.

There are multiple ‘Ideas for Execution’ for this Project Constraint. You may implement this visually in bars, graphs, charts, or numbers, etc. Even if you may decide to change the ‘Idea for Execution’ in a subsequent design iteration (e.g. switching from graphs to bars), you must always check if the Project Constraint is met.

One thing we’ve noticed, is that once projects go over 2 months and several iterations, designers often fall into the trap of getting rid of Project Constraints when they don’t like an Idea for Execution. That’s wrong. The Project Constraints are immutable. What should be changed is the implementation method of the said concept, thus, the Idea for Execution.

Also, some Project Constraints may create Design Problems. For example, if the client is selling 120 variations of the same product on an eCommerce website, a UX design problem presents itself: “Including 120 variations of the same product may confuse Users, thus leading to less sales.”

Even when solving UX Design problems, you must always check whether the solution considers all the original Project Constraints.

It is extremely important that THIS STAGE BE COMPLETED BEFORE SCREENS ARE DESIGNED. Or else, you’ll be wasting a lot of time redesigning screens to fit the project constraints.

2. Present the research you have done for the project.

— — —

This should include, but not limited to (1) Competitor Analysis, (2) Market Research, (3) What remains the same in this project as compared to its competitors, and (3) What is different in this project as compared to its competitors.

3. Present the design philosophy behind the newly created UI·UX.

— — —

Please explain the idea behind the design. (e.g. Flat design, Skeumorphic design, Material design, etc.)

4. Present the original UI Kits that were used for the UI·UX.

— — —

The final UI UX must differ enough from the original UI Kit so as to prevent legal copyright issues. On the other hand, if you created a design from scratch, please explain the reasons behind your decision.

5. Present the actual design screens and the flow of the application or service.

— — —

Please demonstrate how the user would use the application service, from ‘signup’ to ‘delete account’.