Design Reports

Writing about your design work is a good practice in general, to document your process and results. For us, these will serve double duty as early drafts of our eventual portfolios.

Learning Objectives


The goal today is simply to get you started thinking about what goes into a report. In practice, designers typically only write lengthy prosaic reports as a deliverable to summarize findings from user research (often to handoff to other designers). We’ll modify this approach a bit to produce reports about our work throughout the class, especially on solo projects. This will help you to document as you go, giving you plenty of content to help you put together your portfolio once class is over. It will also serve as the record of your work that you’ll review with one of the TAs in a 1-on-1.

Keep in mind

Suggested structure

1. Agenda of your report

The result of the agenda should be an outline of all the parts you are going to develop in your report. It is very useful for the reader to be able to quickly refer to the part(s) that interests him/her the most.

2. Overview

3. Part 1: UX

4. Part 2: UI

5. Part 3: Learnings & Next Steps

6. Appendix

In order to not overload the report, some elements might be added in the appendix such as:


Further Reading

See Also