- A poster is more like a PPT presentation, than an essay.
The poster should be easy on the eyes... with
- few words
(lots of white space)
- large letters
Imagine you are in a room full of posters, all vying for attention.
A poster with small letters in dense paragraphs looks intimidating --
like you will have to concentrate to get anything...
Would you rather stop at
or one that looks easy to follow,
with big pictures, lots of white space, ...?
- Stand 2-3meters away from your poster.
You should be able to get most of the ideas from there -- ie, based only on
the figures, and without the "small print".
It is ok to use just PHRASES, rather than complete sentences, within BULLETs.
Extra words are problematic, as ...
If people are reading, they aren't listening!
- Many words make a poster look crowded, and
like it will be hard to understand.
⇒ potential viewers will go to another poster ...
- Many ComputingScience ideas correspond to some process,
mapping some specific type of input into some output.
If so, show a diagram
[ INPUT ] -> (Process) -> [ OUTPUT ]
Of course, there may be MANY different inputs (don't forget the background
and the "Process" may be complicated, built from many nodes.
You should then indicate how the OUTPUT is related to the INPUT.
Of course, that OUTPUT may itself be a process;
if so, you may want to have another diagram here.
- Use line breaks to help readers parse sentences
- Present the material primarily in TOP-to-BOTTOM columns,
rather than left-to-right rows.
(See also Presentation.
Otherwise, material presented primarily left-to-right
will cause the reader to slide left to right,
then jump back to the left margin, then slide to the right, then ...
This is especially problematic if you have many viewers -- as this
means the "sliding viewer" will be distracting to others!
- Use "Figure 1 ..." or "Table 3 ..." only if you need to refer to a
This is typically NOT needed, as you can just use proxity, or arrows, to give