Governing with Templates 207
You need to determine what should go in a template, com-
pared to what should go on the slide. To do that, you’ll need
to identify the varying types of content that your company
uses to convey its messages. One approach is to collect files
from many departments, audit them, determine communica-
tion patterns, and then build a template that meets the com-
munication needs of each organization appropriately.
The effective use of a template helps viewers become accus-
tomed to where the content will appear on a slide and give
them a sense that slide content is structured and aligned.
Content should not bounce from slide to slide. There’s nothing
more frustrating than having content jump around so much
that each slide becomes a puzzle that takes some study to
figure out where to start processing information. Titles and
bullet copy should appear in the same locations (unless you’ve
intentionally designed it that way to serve a purpose). By set-
ting the placement and divisions of space for your corporate
power-users, they will be able to recognize (and value) the
underlying skeletal structure, the reasoning used to develop
the template, and the rationale for them to use the template.
T!P
Believe it or not, before you start developing a
template, a conversation with your IT department
is in order.
• Ask the IT department what the migration plan
is for the company’s presentation application.
If the company is close to a major upgrade, get
that beta and begin a strategy on how to build a
template in the newest release of the application.
• If you create a template loaded with images,
query the IT department whether the organization
has adequate storage. Presentation files procre-
ate like bunnies, and a 1MB template might seem
innocent, but it can add up to terabytes in a single
department in a month.