<?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 Austin Gardner-Smith on Medium]]></title>
        <description><![CDATA[Stories by Austin Gardner-Smith on Medium]]></description>
        <link>https://medium.com/@gardnersmitha?source=rss-d232c7eb906------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*0HZcqUeIN5H4nccQ.jpg</url>
            <title>Stories by Austin Gardner-Smith on Medium</title>
            <link>https://medium.com/@gardnersmitha?source=rss-d232c7eb906------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 18:54:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gardnersmitha/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[Spreadsheet Culture vs. Deck Culture]]></title>
            <link>https://medium.com/@gardnersmitha/spreadsheet-culture-vs-deck-culture-6421f2c5e871?source=rss-d232c7eb906------2</link>
            <guid isPermaLink="false">https://medium.com/p/6421f2c5e871</guid>
            <category><![CDATA[excel]]></category>
            <category><![CDATA[presentations]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Austin Gardner-Smith]]></dc:creator>
            <pubDate>Fri, 18 Nov 2016 15:15:22 GMT</pubDate>
            <atom:updated>2016-11-18T15:46:23.713Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9o1JdpzCuIjCFuRB." /></figure><p>In the past 3 years I’ve worked in two incredibly different environments — one that’s almost exclusively data-oriented, filled with data scientist and engineers; another that’s almost entirely language- and visually-driven, filled with strategists and writers and creatives.</p><p>Both approaches have their benefits — and both are reflective of the type of work the company produced: analytical software in the first case, creative marketing in second. But I can’t help but think that each might have swung a bit too far to one side of the pendulum and is missing out by not having a cultural respect for the others’ craft of choice. I’ve certainly learned tons from working in both kinds of organizations, but not everyone has benefited from this same kind of cross-pollination.</p><p>It strikes me that the most common manifestation of this divide in culture is the relative dexterity and comfort that the two organizations have with two very specific types of software applications: spreadsheets and presentations (decks, in the vernacular).</p><p>At my former company, we lived and died in spreadsheets. We constantly analyzed data in Excel in order to complete our day-to-day work, and almost everyone in the company was expected to know how to work with large amounts of data in Pivot Tables, to construct Vlookup functions, and more. But we also used spreadsheets to communicate — the most common form of presentation involved a Google Sheet on screen in a room; the most common form of collaboration involved sharing one of these documents. It was a dominant interaction pattern within the company.</p><p>In the agency world, the weapon of choice is the presentation — and our bar is not the corporate powerpoints full of text and starbursts. Presentations are generally expected to be fully-formed stories and visually immersive documents. Whether designed for print or screen, there is an expectation that these documents look beautiful and tell a compelling story. There is respect for this craft within the organization, and ideas often judged by how well they are expressed in this medium. There is a great deal of effort spent on fit and finish.</p><p>There are positives and negatives to each approach. Spreadsheet culture places a premium on the gathering of content, its validity, cleanliness and structure. It’s focused on find the answers — communicating the answers to another audience is often an afterthought. It’s easy here to find an incredible solution, only to have it fall on deaf ears.</p><p>Deck culture focuses on delivering the information in an appealing manner, sometimes exchanging the value of additional investigation or analysis. It’s very possible in this mode to create a stunning and compelling story that answers the wrong question, or answers the right question incorrectly.</p><p>I’ve learned a lot from each culture — and no matter which side of the spectrum your company falls on, I think there’s value in embracing the mode of communication that works best. But if you can, try to learn the tools of trade for both sides — decks and sheets — together they can do beautiful things.</p><p><a href="http://blog.austingardnersmith.me/tag/presentation/">#presentation</a> <a href="http://blog.austingardnersmith.me/tag/data/">#data</a> <a href="http://blog.austingardnersmith.me/tag/culture/">#culture</a></p><p><em>Originally published at </em><a href="http://blog.austingardnersmith.me/spreadsheet-culture-vs-deck-culture/"><em>blog.austingardnersmith.me</em></a><em> on November 18, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6421f2c5e871" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shutting Down Side Projects]]></title>
            <link>https://medium.com/@gardnersmitha/shutting-down-side-projects-d55b825a2481?source=rss-d232c7eb906------2</link>
            <guid isPermaLink="false">https://medium.com/p/d55b825a2481</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[side-project]]></category>
            <dc:creator><![CDATA[Austin Gardner-Smith]]></dc:creator>
            <pubDate>Tue, 01 Nov 2016 14:24:08 GMT</pubDate>
            <atom:updated>2016-11-01T20:29:28.769Z</atom:updated>
            <content:encoded><![CDATA[<p>For as long as I can remember, I’ve had a couple of side projects going. Often, they’re software projects that help me exercise my coding brain and get to know new technologies; other times they’re more content-oriented, sometimes they’re explorations of a potential business ideas. Sometimes they’re a little bit of all of these things.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I8xNi0fPQ4jtIRnD.png" /></figure><p>In the past, I’ve been relatively content to let these things peter along on their own schedules, and not particularly stressing about whether or not they come to full fruition. But I’ve got some new demands on my attention that are forcing me to be a little more strict with my time (new house, new job, new puppy, new baby — just a few). The bottom line — it’s time to shut some shit down, at least for now.</p><p>I’m not quite done with this process, but the first thing I did was make a list of the projects in flight — I counted 8 of them:</p><ul><li>Personal Blog (this blog)</li><li>Periodic Table of Marketing Metrics (content resource for beginning digital marketers)</li><li>DIYM (online digital marketing course)</li><li>Quantopian Algos (trading algorithms)</li><li>Stockdash (stock management web app)</li><li>Zeke (homeowner concierce app)</li><li>Stock Picking (daily/weekly technical analysis routine)</li><li>Ember Fire (physical product idea)</li></ul><p>These are all in various stages of maturity, have different “MVP” requirements, different levels of effort required, and varying prospects for any kind of remuneration, financial or otherwise. But one thing is for certain — spreading my energy across this many avenues is formula for inaction. <em>There is simply no way I have enough time to make all of these a reality.</em></p><p>This alone was a crucial reality check for me — while I could easily have named all the projects that took up some of my attention, writing them all down helped to put it in perspective. I’d be lucky make one or two of these come to life. So how to prioritize them?</p><p>I had to get a handle on my time. Turns out this, too, was less than I would have guessed. Without changing anything major in the other parts of my life, I have about 8 hours a week of time I can <em>count on</em> to dedicate to these projects, and of those only about 2 are consecutive blocks where a large chunk of work could be knocked off. A full 4 occur during my commute in 30 minute intervals with limited connectivity. So we’re really talking somewhere in the neighbor of 3–4 hours of “all-systems-go” working time. Whoah. Big reality check number two.</p><p>So far, the only decision I’ve made is that this blog is a worthy investment for some of that time — namely the 30 minute morning commute blocks. It produces a work output that has both personal and professional benefits, fits neatly in the available time block, and hopefully begins to force a little more discipline and habit into my side project approach.</p><p>As for the rest of the projects, I’ve yet to determine which ones live, die, or take a different shape. But I can guarantee some of them will need to die.</p><p><a href="http://blog.austingardnersmith.me/tag/product/">#product</a> <a href="http://blog.austingardnersmith.me/tag/productivity/">#productivity</a></p><p><em>Originally published at </em><a href="http://blog.austingardnersmith.me/shutting-down-side-projects/"><em>blog.austingardnersmith.me</em></a><em> on November 1, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d55b825a2481" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Where Is Fintech’s Killer App?]]></title>
            <link>https://medium.com/@gardnersmitha/where-is-fintechs-killer-app-5a5f8245275a?source=rss-d232c7eb906------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a5f8245275a</guid>
            <category><![CDATA[investing]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Austin Gardner-Smith]]></dc:creator>
            <pubDate>Tue, 01 Nov 2016 01:29:30 GMT</pubDate>
            <atom:updated>2016-11-01T01:56:38.092Z</atom:updated>
            <content:encoded><![CDATA[<p>At this point, there are literally hundreds of FinTech companies out there, vying for my access to by bank accounts and my assets. I’m an early adopter type, and I’m particularly interested in the intersection of tech and finance. But here’s the thing — while I’m excited about the innovation in the space, I’m using very little of it — I just can’t seem to find a value prop that’s strong enough to get me to change my behavior. I haven’t found my killer fintech app. And I’ve been looking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1Fs4J08ZRTV_aasb." /><figcaption>Sexy money image. Unsplash is great.</figcaption></figure><p>It’s not that I feel my current systems don’t have weaknesses — in fact, I’m constantly frustrated by the difficulty of doing what I consider relatively simple tasks, from true-ing up monthly expenses to rolling over 401k’s to aggregating stock picks from a variety of different sources. And while there are some viable fintech alternatives to the legacy systems, I’ve yet to find any that are truly transforming my experience.<a href="http://blog.austingardnersmith.me/where-is-fintechs-killer-app/#fn:1">1</a></p><p><strong>Expense Tracking</strong></p><p>Fifteen years after Mint’s launch, I’m still looking for a personal expense tracking tool that functions as well as my spreadsheet-driven system. My most recent trial is <a href="http://personalcapitcal.com/">Personal Capital</a> — and while I find that it does a better job with many things than others I’ve tried, I’m not getting much from using it — it seems there’s always some piece of data that’s missing, mis-categorized, or otherwise invalid, making the complete picture I’m getting not quite accurate, rendering the picture itself pretty useless.</p><p><em>What my killer app might look like:</em> something that tells me in real time what’s going on with my spending without being obnoxious, something that can differentiate “outlier” purchases from normal monthly expenses/patterns, something that helps me understand the real life implications of my behavior. It’s a complicated ask, but one I think is within technology’s grasp.</p><p><strong>Investing</strong></p><p>We look immediately to Wealthfront and Betterment here as the leaders in the “robo-advisor” space, but we’ll soon see nearly every major banking institution roll out their own version of the same technology. These offerings are likely to make the role of the traditional financial advisor obselete (at least for all but the top 1% of investors), but there’s nothing really magical about them. I could easily build the same ETF portfolio in my brokerage account in about ten minutes, set up automatic investments, and be done with it. I’ll concede that this action isn’t obvious and easy to everyone, and that these robo-advisors greatly simplify the process. They even throw in a few bells and whistles like tax-loss harvesting that are not snap-your-fingers easy to do. But they’re not fundamentally changing the game.</p><p><em>What my killer app might look like:</em> a way to invest that is uniquely tailored to my needs, including my need for (the illusion of) control. Something that will give me an easy way to dial up or down risk in the portfolio, something that will provide guidance on when to increase/decrease positions according to pre-defined plans. I’m aware that most research points to the fact that passive strategies outperform active ones, but I still think we can do better than giving every single investor the same mix of 7 or 8 ETFs and calling it a day.</p><p><strong>Trading</strong></p><p>Trading is a mildly lucrative hobby for me at this point — but something I spend a fair amount of my time on. I’ve developed a whole bunch of routines, most of which could be fully automated. I’ve started building some <a href="http://github.com/gardnersmitha/stockdash">software</a> to help my own process, but maintaining it and continuing my own development is more time consuming than it’s worth at this point. I’ve started to play around with algo trading on <a href="http://quantopian.com/">Qunatopian</a> (ridiculously smart company/concept) and that is definitely a step-change from what’s previously been available. But as far as the average (read:non-developer) trader is concerned, there’s not a ton of technology out there that’s truly transforming the game. Simple problems like position sizing, screener management, and effective note-taking haven’t been solved, making it difficult and onerous for many traders to track, manage and execute on potential trades.</p><p><em>What my killer app might look like:</em> an app that can help aggregate all my sources of ideas into one place, help me quickly evaluate them and store my evaluations for later, and that ultimately learns from my decisions as I go, eventually presenting ideas to me based on my past behavior and the available data signals. Think super-smart Tinder for stocks.</p><p>I think fintech is maybe the most interesting space out there right now, and I’m pumped about all the innovation that’s happened so far. But I’ve not yet found my killer app. Maybe you’re building it right now.</p><p><em>Notes</em></p><p>1: I do believe fintech to be truly disruptive; it’s causing a massive industry to rethink its practices and forcing innovation. This is a good thing. What I’m saying is that to the consumer, these are only new ways of doing the same things — mostly replacing a human interface with a technological one.</p><p><a href="http://blog.austingardnersmith.me/tag/product/">#product</a> <a href="http://blog.austingardnersmith.me/tag/fintech/">#fintech</a></p><p><em>Originally published at </em><a href="http://blog.austingardnersmith.me/where-is-fintechs-killer-app/"><em>blog.austingardnersmith.me</em></a><em> on November 1, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a5f8245275a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Amazon Alexa Ruined My Other Interfaces]]></title>
            <link>https://medium.com/@gardnersmitha/amazon-alexa-ruined-my-other-interfaces-923eecbcc1bf?source=rss-d232c7eb906------2</link>
            <guid isPermaLink="false">https://medium.com/p/923eecbcc1bf</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[voices]]></category>
            <category><![CDATA[amazon-echo]]></category>
            <dc:creator><![CDATA[Austin Gardner-Smith]]></dc:creator>
            <pubDate>Fri, 28 Oct 2016 14:05:22 GMT</pubDate>
            <atom:updated>2016-10-28T14:39:12.988Z</atom:updated>
            <content:encoded><![CDATA[<p>Two days ago I walked in the door, cracked a frosty beverage, and uttered a now-familiar refrain: “Alexa, what’s the news?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/0*s2pHvpXm8gcWZ192.jpg" /><figcaption>Not my actual Echo. Also not my actual book collection.</figcaption></figure><p>Silence. I asked again. Still nothing. And so I walked over to my Echo only to find that it was — gasp — unplugged (my wife has never cared for my relationship with Alexa; that’s a topic for another post). So here I was, just a guy, in his kitchen, talking out loud to an imaginary woman.</p><p>Thing is, it’s not the first time this has happened recently, or the only context. When I hop into my car, I find myself wanting to ask Alexa to tune the radio station or turn up the heat (Siri via CarPlay is a faint shadow of the Alexa experience). When I’m away from home, it’s the same — I miss the ease and convenience getting the forecast while my hands are busy selecting a jacket, or finding out if the Bruins are playing while I’m doing the dishes.</p><p>These are first-world problems, to be sure, but until I bought an Echo it wasn’t clear to me just how many daily use cases there are for which a voice is the perfect interface, nor how wide the experience delta is between a “good” voice interface (Siri) and a “great” one (Alexa). <a href="http://blog.austingardnersmith.me/alexa-ruined-my-other-interfaces/#fn:1">1</a></p><p>This is a pattern that’s repeated itself in technology time and time again — we didn’t know how tedious a DOS interface was until we were presented with a high-functioning GUI with a mouse, we didn’t realize how poor the keyboards on our Blackberrys were until we experienced a high-quality multi-touch screen, and we won’t accept that voice can be a dominant interface until we experience a high-functioning version in our day-to-day lives.</p><p>But in each of these cases, the interface(s) that came before are marginalized for us in many ways, even if they’re not driven out to pasture forever.<a href="http://blog.austingardnersmith.me/alexa-ruined-my-other-interfaces/#fn:2">2</a> And it certainly feels to me like Alexa has started to do this to many of the other interfaces I use.</p><p><a href="http://blog.austingardnersmith.me/tag/product/">#product</a> <a href="http://blog.austingardnersmith.me/tag/ux/">#UX</a> <a href="http://blog.austingardnersmith.me/tag/voice/">#voice</a></p><ol><li>We still have a long way to go, and Alexa is far from perfect. But in my experience she’s far more reliable, accurate and conversational than Siri. Maybe we could come up with a standard of measure for voice interfaces? Something like the percentage of first interactions where the response is expected/correct? <a href="http://blog.austingardnersmith.me/alexa-ruined-my-other-interfaces/#fnref:1">↩</a></li><li>Marginalized is perhaps more negative way to look at the situation; specialized would be the opposite view. What we’re really talking about is a reduction of the number of use cases for which a given interface is ideally suited. For example, just because I could dictate this post into a voice interface doesn’t mean I will — the keyboard/screen combination is still a more ideal interface for the task at hand. <a href="http://blog.austingardnersmith.me/alexa-ruined-my-other-interfaces/#fnref:2">↩</a></li></ol><p><em>Originally published at </em><a href="http://blog.austingardnersmith.me/alexa-ruined-my-other-interfaces/"><em>blog.austingardnersmith.me</em></a><em> on October 28, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=923eecbcc1bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Context Switching and Product Usage]]></title>
            <link>https://medium.com/@gardnersmitha/context-switching-and-product-usage-7845b8f18926?source=rss-d232c7eb906------2</link>
            <guid isPermaLink="false">https://medium.com/p/7845b8f18926</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[context]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Austin Gardner-Smith]]></dc:creator>
            <pubDate>Thu, 27 Oct 2016 13:49:54 GMT</pubDate>
            <atom:updated>2016-10-27T14:15:46.892Z</atom:updated>
            <content:encoded><![CDATA[<p>I switched jobs a few months ago — and with the switch came a transition to a new machine, something I’ve done many times before. While this gets a bit easier each time thanks to increasing reliance on the cloud and my own personal routines, it’s never quite seamless. It’s been a few months now, but a couple times a week I find myself reaching for an application or visiting a web app and finding either the application or my credentials missing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*czS334fewjYTE-Bj." /><figcaption>Switches. Get it, switches?!</figcaption></figure><p>Aside from being mildly annoying, it got me thinking about how a big the impact of a sudden shift in job, location, connectivity or lifestyle can have on the digital products we use. There are applications I spent almost my whole day in at my last job that I hardly touch now, and vice versa. And there are apps that I use in a completely different manner.</p><p><strong>Apps I’m using more:</strong></p><ul><li>Google Docs</li><li>Apple Mail</li><li>Apple Messages</li><li>Keynote</li><li>Excel</li></ul><p><strong>Apps I’m using less:</strong></p><ul><li>Sketch</li><li>Slack</li><li>Google Sheets</li><li>Jira</li><li>Google Hangouts</li><li>Whiteboards (analog, but worth mentioning)</li></ul><p>Some of these are simply functions of having a completely different job. I’m not really managing product backlogs any more, so it’s natural that Jira would fall off completely.<a href="http://blog.austingardnersmith.me/context-switching-and-product-usage/#fn:1">1</a>Keynote falls into this category as well — I’m doing far more presentation work than in the previous role, and we place a greater emphasis on presentation design. Excel has replaced Google Sheets for many functions because I’m looking at larger data sets and can’t live without a proper pivot table, which Google Sheets still doesn’t compete on. <a href="http://blog.austingardnersmith.me/context-switching-and-product-usage/#fn:2">2</a></p><p>Other changes are driven by changes in office &amp; corporate culture. My new company is still super reliant on email for day-to-day communications, and while a few groups have adopted Slack is still primarily in the hobby phase of adoption and isn’t a reliable communications channel. And while not necessarily an application, per se, my use of whiteboards has drastically decreased, as we tend to use written documents as discussion guides around a table instead of collaborative editing on a whiteboard. <a href="http://blog.austingardnersmith.me/context-switching-and-product-usage/#fn:3">3</a></p><p>All these changes are to be expected — but the key insight for me is that these context changes aren’t necessarily something a good product person would be able to pick up by looking at Mixpanel or raw usage stats — they require qualitative understanding of the where, when, how and why people use products that can only be gathered by talking to real people in a non-scalable way. But there’s no doubt to me that these insights are at least as valuable as the sum total of quantitative data most PMs look at every day.</p><p><em>Footnotes</em></p><p>I do miss have a well-groomed public backlog of tasks and am looking to replicate this way of working with less software-specific product, suggestions welcome. ↩</p><p>Google sheets scripting, on the other hand, blows Excel out of the water IMO. Vanilla JS scripting FTW! ↩</p><p>I hate this part. The problem is that the document owner ends up trying to interpret feedback from a group that is often vague and unclear and coming back with a revision that may or may not match what the rest of the group had in their head. This means we sometimes take 3–4 turns to get something right because key visuals or phrases are getting lost in translation. ↩</p><p><a href="http://blog.austingardnersmith.me/tag/product/">#product</a> <a href="http://blog.austingardnersmith.me/tag/ux/">#UX</a></p><p><em>Originally published at </em><a href="http://blog.austingardnersmith.me/context-switching-and-product-usage/"><em>blog.austingardnersmith.me</em></a><em> on October 27, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7845b8f18926" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Giving and Getting Great Demo]]></title>
            <link>https://medium.com/@gardnersmitha/on-giving-and-getting-great-demo-459a63ff2856?source=rss-d232c7eb906------2</link>
            <guid isPermaLink="false">https://medium.com/p/459a63ff2856</guid>
            <category><![CDATA[product-marketing]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[demo]]></category>
            <category><![CDATA[sales]]></category>
            <dc:creator><![CDATA[Austin Gardner-Smith]]></dc:creator>
            <pubDate>Wed, 26 Oct 2016 13:20:57 GMT</pubDate>
            <atom:updated>2016-10-26T19:40:42.627Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the past few days we’ve been looking into buying a new toolset for monitoring and tracking our PR efforts. It’s been enlightening in a number of ways, but the biggest thing it’s provided me with is an opportunity to watch how other companies sell, and to digest a bit about what makes a good demo different from a just OK demo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WHsS88_D5RYVlYc5VUvNbQ.jpeg" /><figcaption>May your screen shares not shit the bed.</figcaption></figure><p>I spent the better part of three years prior to this on the other side of the table (er, screenshare) demo’ing software and attempting to get potential customers to quickly understand the value inherent in our offering. It can be a tricky proposition — lots of unknowns, little face-to-face contact, high probability of distraction, near-certain failure of screen sharing tools.</p><p>But maybe the biggest challenge is conveying — in 60 minutes or less — the value inherent in a software product that took months to build. It’s all too easy to fall into the trap of the familiar, glossing over features that seem obvious to you but are brand new to your customer; and still easier to go the other way — gushing over the new feature you just shipped, without realizing that it’s a shiny “nice-to-have” for the majority of your customers, not a pivot point for them to purchase.</p><p>It’s easy to say, but hard to remember: the only goal of the demo is to eliminate product objections and move the prospect closer to close. It’s decidedly <em>not</em> to show off how smart you are, how much product you’ve built, or how often you ship. These are the things that go into the product — they should be felt and seen but not heard in your demo.</p><p>All that said — I’ve been impressed with the quality and consistency of demo’s we’ve seen so far. Here are a few things I thought contributed to the highest quality demos:</p><ul><li><strong><em>Use my data.</em></strong> The demos that included my own company’s information into the demo were by far the most relevant — they allowed me to see myself using the software and immediately grasp the use case. If your product is such that you can find (or build) a way to support this, I highly encourage you to do so. It takes more time to build each demo, but I’m willing to bet the success rate will make up the difference in volume.</li><li><strong><em>Focus on use cases.</em></strong> It’s still pretty common (and easy) to give a demo where you talk about features first and then back into use cases: “This is our X feature. It can do Z,Y,B. This can be really helpful when trying to accomplish A,B,C.” That’s a lot of combinations of things the feature might do, and it’s not easy for me to wrap my head around which one makes sense for me. Instead, try something like: “Let’s imagine you have to accomplish task A. To do that, you would use feature X in this manner. If you want, you can also use feature X for task B and C.” It’s a subtle but important difference. Customers don’t tend to think in features (even those of us who are product people).</li><li><strong><em>Ask questions that demonstrate expertise.</em></strong> These are questions that generally start with “Are you guys currently doing X?” where X is a relatively advanced/high value activity that your product makes easier. Customers will give you a half-hearted “yes” as they take a note that they should start doing this. This helps in two key ways: it establishes your authority on the topic at hand, and makes customers think that using your product will make either be better or appear better at their job. And there’s no more instinctive motivator to buy than that.</li><li><strong><em>Handle the swings.</em></strong> Shit’s going to break in a demo. That’s just the way it goes. The best presenters realize quickly when something is broken and move on, instead of trying to triage the problem on the spot. Even if you manage to fix it there and then — the impression left is that the product is buggy and hard to use. You’re better off if you quickly acknowledge the issue and move on to the next feature/use-case. These can also be good times to flip back to a reliable/home screen and check for understanding with the customer. Never hurts to have a second tab open and loaded before the demo to make this flip seamless.</li></ul><p>Giving good demos is hard, but incredibly valuable for those companies who can get it right. I’ve really enjoyed being on the other side of a few good ones recently and I’m looking forward to seeing more.</p><p><a href="http://blog.austingardnersmith.me/tag/product/">#product</a> <a href="http://blog.austingardnersmith.me/tag/presentation/">#presentation</a></p><p><em>Originally published at </em><a href="http://blog.austingardnersmith.me/on-giving-and-getting-great-demo/"><em>blog.austingardnersmith.me</em></a><em> on October 26, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=459a63ff2856" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Blockchain & The Post Privacy Page]]></title>
            <link>https://medium.com/@gardnersmitha/the-blockchain-the-post-privacy-page-4920fb083e36?source=rss-d232c7eb906------2</link>
            <guid isPermaLink="false">https://medium.com/p/4920fb083e36</guid>
            <dc:creator><![CDATA[Austin Gardner-Smith]]></dc:creator>
            <pubDate>Thu, 11 Jun 2015 15:28:03 GMT</pubDate>
            <atom:updated>2015-06-11T15:28:03.284Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve long been the cynic among my peer group who constantly promotes the “privacy is dead” trope, and I pretty much believe it. There’s really no way to avoid the fact that most of us live in public, and that increasingly more of our lives will be captured, indexed and quantified. If people want to find out who I am, what I do, where I live and what I’ve been up to — it’s not that hard. Despite the measures we can take to protect this information, there are few barriers that can stop a determined and technically savvy inquirer from eventually getting to the goods. I’ve come to terms with that.</p><p>But what would happen if we take the post-privacy concept to its logical extreme? Could one actually go on the offensive and publicly share all of his data as a measure to fully cement that my identity belongs to me? I don’t know what this looks like just yet — but here are some of the things I’ve been thinking about:</p><ul><li>Could I publish a web page with all of my personal data, open to the world? I’m talking name, date of birth, social security number, the whole kit. Maybe even credit card numbers and passwords, eventually.</li><li>Could some sort of &lt;meta&gt; tag or other schema embedded in the page that lets a crawler or bot know that this is my official stuff? Or could the page be hosted on a service that essentially serves as the official home of open source identity?</li><li>Can we use the <a href="https://en.bitcoin.it/wiki/Block_chain">blockchain mechanism</a> for identity protection?</li></ul><p>Of these, the last point is perhaps the most interesting. Instead of a single, canonical reference or identifier, can we use a collective mechanism to verify identify? I think that’s a really neat idea.</p><p><a href="http://blog.austingardnersmith.me/tag/products/">#products</a> <a href="http://blog.austingardnersmith.me/tag/blockchain/">#blockchain</a></p><p><em>Originally published at </em><a href="http://blog.austingardnersmith.me/the-blockchain-the-post-privacy-page/"><em>blog.austingardnersmith.me</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4920fb083e36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Notifications Deserve To Be First Class Citizens of UX]]></title>
            <link>https://medium.com/@gardnersmitha/notifications-deserve-to-be-first-class-citizens-of-ux-a5c8a574a8d6?source=rss-d232c7eb906------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5c8a574a8d6</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Austin Gardner-Smith]]></dc:creator>
            <pubDate>Wed, 25 Mar 2015 03:06:39 GMT</pubDate>
            <atom:updated>2015-03-25T03:10:43.191Z</atom:updated>
            <content:encoded><![CDATA[<p>I first started thinking more about notifications and alerts when <a href="http://blog.austingardnersmith.me/why-yo-isnt-dumb-at-all-yo/?utm_source=Medium&amp;utm_medium=Social&amp;utm_term=%23products&amp;utm_campaign=All%20Posts">Yo!</a> became popular almost a year ago, but as the Apple Watch gets closer to being a real thing in the wild and as I’ve spent more time tinkering with mobile app concepts I think it’s still something worth talking about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*yxsQsp6W1Un5aDYl.png" /><figcaption>Been thinking a lot about how notifications can be used in a new product I’m building for homeowners.</figcaption></figure><p>A lot of times, we think of alerts from the applications we use as the sugar that sits on top of a well-designed user experience. In reality, notifications and alerts are probably the most critical interaction mechanic we have — most days they’re the primary reason I open many apps on my phone. With some apps, they’re the only way I interact on any given day.</p><p>All this gets me wondering if it’s time we started thinking about notifications &amp; alerts as their own “layer” of UX, not just a group of features. The best mobile app developers are clearly already thinking this way, and obviously manufacturers and OS makers are finding more ways to make these interactions part of the native experience. But it’s not yet (or doesn’t seem to me, at least) an area of UX that gets paid the same attention as other parts of our apps like nav elements and touch area or gestures.</p><p>In light of the recent release of the Apple Watch and others like it — maybe the first class of devices designed to function almost exclusively at the notifications layer — it certainly seems like we ought to start thinking about them like first class citizens of UX. I think they’ve earned it.</p><p><strong>Original Notes for this Post</strong></p><p><em>Note: This is something new I’m going to start adding to my posts. Most of the time, this is how a post starts for me: a thought followed by a couple of bullets and questions. Sometimes it ends up being more insightful than the finished post itself, so I’m just going to leave these here on the off chance they spark something. Let me know if you think they should stay or go in future posts.</em></p><p><strong>Notifications/Alert Layer</strong></p><ul><li>A whole layer of HCI/UX, not just a feature</li><li>What’s fundamentally different about it?</li><li>What’s it particularly useful for?</li><li>What % of interactions it could make up in the future?</li><li>Can you make a diagram for the whole UX ‘stack’ from lightweight to immersive? Is it mobile only?</li><li>iOS 8 interactive notifications/OSX notification center/Google Now</li><li>The watch as a device for the notifications layer</li><li>Information vs. action mechanic</li></ul><p><a href="http://blog.austingardnersmith.me/tag/products/">#products</a> <a href="http://blog.austingardnersmith.me/tag/ux/">#UX</a></p><p><em>Originally published at </em><a href="http://blog.austingardnersmith.me/notifications-layer-ux/?utm_source=Medium&amp;utm_medium=Social&amp;utm_term=%23ux&amp;utm_campaign=All%20Posts"><em>blog.austingardnersmith.me</em></a><em> on March 25, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5c8a574a8d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>