<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Logan Greer on Medium]]></title>
        <description><![CDATA[Stories by Logan Greer on Medium]]></description>
        <link>https://medium.com/@Logan_Greer?source=rss-222c8dfeb59a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*7BsgarC3A4S693Yz.jpeg</url>
            <title>Stories by Logan Greer on Medium</title>
            <link>https://medium.com/@Logan_Greer?source=rss-222c8dfeb59a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:01:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Logan_Greer/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Creating Client Presentations Like a Product Designer]]></title>
            <link>https://medium.com/@Logan_Greer/creating-client-presentations-like-a-product-designer-3464dee00246?source=rss-222c8dfeb59a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3464dee00246</guid>
            <category><![CDATA[presentations]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Logan Greer]]></dc:creator>
            <pubDate>Wed, 18 Nov 2015 19:14:55 GMT</pubDate>
            <atom:updated>2015-11-19T21:06:40.629Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xB1QFlJLH5TdOibgxfR7tA.jpeg" /></figure><p>Let’s face it, creating a client presentation deck sucks. Working within the confines of keynote slides (or powerpoint for the even less fortunate) is second only to working in spreadsheets when it comes to things most likely to make a designer scratch out their own eyeballs.</p><p>Recently, I have found myself being pulled more and more into projects at the pre-pitch stage and I began to notice that the process of creating a presentation deck was lacking something… a process.</p><p>All too often we have individuals from their respective departments use keynote slides as a dumping ground for one-off ideas and potential talking points. At which point some unlucky soul is tasked with making sense of everyones idea-vomit (aka bulleted-lists). It’s like taking a bunch of square railroad spikes and asking someone make them fit into tiny round pinholes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*Lzy1YEOcVIxFRuNlsPYAUQ.jpeg" /></figure><p>The more time I spent observing this lack of process, the more I began to think that it could benefit from the same design process I already use to build digital products. So I tried it… and it worked. Below is an overview of how I now create my client facing presentations:</p><h4><strong>UX Research:</strong></h4><p>This is where I try to do an evaluation of the room I am walking into; figuring out who the people in that room might be and what potentially motivates them. It’s the first step, and it’s important. I need make sure that I understand who my audience is before I create anything… it’s UX 101. I grab a blank space and brainstorm on the following:</p><ul><li><strong>Who are the people in the room?</strong></li><li><strong>What makes them tick? ( any potential anxieties or fears related to the topic)</strong></li><li><strong>What do they already know about this topic?</strong></li><li><strong>What do I want them to know about this topic?</strong></li><li><strong>How do they buy? (this could be buy in the sense of an RFP pitch or simply just buying into a creative idea)</strong></li><li><strong>How can I best connect with them?</strong></li></ul><h4>Define Success :</h4><p>After I have a handle on who my audience is, I try to determine what success means for both myself giving the presentation, as well as the people listening. Depending on the type of presentation, this definition can change but I should know exactly what it is I want to achieve. To get to this point, I write down the following sentences, pour some coffee into my bloodstream and fill in the blanks:</p><ul><li><strong>“ At the end of this presentation, I want the audience to feel …X”</strong></li><li><strong>“ At the end of this presentation, I want the audience to think …X”</strong></li><li><strong>“At the end of this presentation, I want the audience to do…X”</strong></li></ul><h4>Create A User Flow:</h4><p>Armed with all of the previous research, I start diving into the actual structure of the deck. At this point, my job is to move people from being introduced to a topic, through the core functions of the presentation and then conclude it all with a nice touch. After all, stories are just data with a soul. That soul has to have flow.</p><blockquote>“Stories are just data with a soul. That soul has to have flow”.</blockquote><p>I find the most effective way to structure an engaging presentation is to steal from classical story telling tropes. If you are unfamiliar with storytelling tropes, here is a great resource to get you <a href="http://www.designthroughstorytelling.net/periodic/">started </a>.</p><p>Once I have selected what type of trope will fit the presentation best, I jot down the important plot points of the trope:</p><p><em>Example using the “Hero’s Journey” trope (Think Star Wars):</em></p><ul><li><strong>Character gets introduced</strong></li><li><strong>Character is called to an adventure in a strange land</strong></li><li><strong>Character encounters hardship and wins an epic battle</strong></li><li><strong>Character returns home transformed</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*zqJzS9obzeGh077JPUMzwg.jpeg" /></figure><h4>Wireframe, Prototype &amp; UI Design:</h4><p>At this point, I’ve done my research and I have my proverbial north star established by my storytelling trope. I can start putting pixels to keynote slides. I usually begin this by typing out the headlines of slides, while considering the following guidelines:</p><ul><li><strong>If I only had 6 slides to tell this story, what would they be?</strong></li><li><strong>Headlines should be read like sentences that connect slides, do they follow a logical progression?</strong></li><li><strong>People tend not to remember things in the middle of a presentation (its called the </strong><a href="https://en.wikipedia.org/wiki/Serial_position_effect"><strong>Serial Position Effect</strong></a><strong>), so make sure to do some recall near the end of the deck.</strong></li></ul><p>Once the headlines are in place, I fill in the meat of the slides making sure that each piece of content on the screen is short and succinct, existing only to support the headline of the slide. After that, I add the creative and media assets that give the deck its visual hierarchy and pretty face.</p><h4>QA &amp; Testing:</h4><p>By this point, I have a good looking, well thought out presentation deck. Before I can pat myself on the back and call it a day, I need to run it through a quality assurance process. All too many times I have seen an amazing presentation get thrown into the toilet by a terrible Q &amp; A session after the fact. If your client is in charge of hundreds of thousands of dollars, chances are they are going to ask some tough questions. So I like to be prepared by testing my knowledge of the presentation material. Here is the process I follow:</p><ul><li><strong>Write as many questions as I can predicting what I can think the client may ask you about the presentation.</strong></li><li><strong>Sort those questions into 3 buckets, grouped by easy to answer, difficult to answer and cannot answer.</strong></li><li><strong>Develop a strategy for answering each category (for the cannot answer category, I identify other team members in the room who are qualified to tackled the question).</strong></li></ul><p>Once I feel confident with handling questions on the presentation, I rehearse… a lot. Schedule permitting of course (in reality, presentations don’t always come with cushy deadlines).</p><h4>Ship The Product:</h4><p>Last but not least is the delivery. All the hard work is done and the presentation is ready to go. By this point I’ve done my homework, I know the material and I can speak with confidence to any questions that might come up. For me, there is no better way to kill the pre-presentation jitters than simply having done the work.</p><p>Presentations are at the core of we do as creatives and as dreading as they can be, they are important. We shouldn’t look like we are herding house cats when we are in front of clients. After all, we can’t expect those clients to trust in our design process if we can’t even bring order to the presentation we are using to sell it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3464dee00246" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>