<?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 Zach Dunn on Medium]]></title>
        <description><![CDATA[Stories by Zach Dunn on Medium]]></description>
        <link>https://medium.com/@zachdunn?source=rss-4f09d383ed05------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*FNPaO_1zEYB_4qBUJsiWkQ.jpeg</url>
            <title>Stories by Zach Dunn on Medium</title>
            <link>https://medium.com/@zachdunn?source=rss-4f09d383ed05------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 12:00:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zachdunn/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[You have to unbreak before you can invent]]></title>
            <link>https://medium.com/robin-powered/you-have-to-unbreak-before-you-can-invent-5b383c0af502?source=rss-4f09d383ed05------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b383c0af502</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Zach Dunn]]></dc:creator>
            <pubDate>Tue, 30 Jun 2015 15:08:50 GMT</pubDate>
            <atom:updated>2015-06-30T15:08:50.839Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*U0kt7BAL7ujQvm37zU-JUw.png" /></figure><p>“You want to make things better? Here’s a mop.”</p><p>The vision is to build something new — something that makes a difference. The reality? You’re spending more time crushing bugs instead of “it”. <strong>If your life was a movie, this would be the 30 second montage between good parts</strong>.</p><p>Someday soon you’ll earn the privilege of shipping big improvements. The type of releases that people won’t see coming, instead of saying “what took so long?”. You’re able to release features that your customers might not have asked for, but love once they see it.</p><p>Right now? You’re working on things that aren’t as glamorous. The password resets and email unsubscribes. Hearts and minds are rarely won in the transactional emails, but they’re easy to lose if you forget to have them.</p><p><strong>In product development your early users are sherpas.</strong> They guide you along the path to what’s worth building next, and they’re right most of the time. Compatibility with a new system, ability to edit titles, etc. Surprising your customers with a brand new and novel feature may sounds good, but it’s not the best problem you can solve for customers right now.</p><blockquote><em>With a stable full of horses and a bunch of stranded people, even Henry Ford would fix the problem before inventing an automobile.</em></blockquote><p>This kind of “let’s make [Insert feature here] less terrible next” thinking wears on people with a bigger vision. Three months into fixing bugs you step back and ask “When do I get to build the parts we planned on? The stuff nobody else is doing, and sets us apart? Is this what it’s supposed to be like?”</p><p>Yes.</p><p>A remarkable number of companies steadily unbreak things under the radar for at least 2–3 years before anyone hears about them, <a href="http://www.saastr.com/if-youre-going-to-do-a-saas-start-up-you-have-to-give-it-24-months/">especially in SaaS</a>. They hide in the noise of TechCrunch features and VC Twitter hailing the latest unicorns as benchmarks for success. Of course there’s nothing immediately wrong with this. Which article would you rather read?</p><ul><li>“This startup just raised $3M to change how you experience linear time”</li><li>“This startup just made another weekly release that makes their app more stable”</li></ul><p>The long tail update isn’t as notable. By the time the world discovers these companies, it’s <a href="https://www.youtube.com/watch?v=My9-cuOmc7w">a multi-year “overnight success” since the months of baby steps are rewritten into a grand effort</a>. Good product development is made in the trenches with these small improvements. Good press sometimes overlaps, but only as a nice side effect instead — never because it’s the goal</p><p>The future-minded get discouraged when they see relatable teams ahead of them. Meanwhile they’re stuck trying to fix another edge case with a Google API integration. Their <a href="https://www.quora.com/What-are-some-must-knows-about-starting-a-SaaS-business-from-scratch/answer/Jason-M.-Lemkin?srid=uKhY&amp;share=1">Minimum Sellable Product</a> foundation just isn’t done yet.</p><p>It’s normal. You’re doing fine. <strong>Focus on the stuff you need to get done to help the people who rely on you.</strong> The rest will sort itself out.</p><p><em>Originally published on </em><a href="https://robinpowered.com/blog"><em>Robin at Work</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b383c0af502" width="1" height="1" alt=""><hr><p><a href="https://medium.com/robin-powered/you-have-to-unbreak-before-you-can-invent-5b383c0af502">You have to unbreak before you can invent</a> was originally published in <a href="https://medium.com/robin-powered">Robin Powered</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Five Minute Culture]]></title>
            <link>https://medium.com/robin-powered/the-five-minute-culture-f53443d1b59b?source=rss-4f09d383ed05------2</link>
            <guid isPermaLink="false">https://medium.com/p/f53443d1b59b</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[work]]></category>
            <dc:creator><![CDATA[Zach Dunn]]></dc:creator>
            <pubDate>Fri, 27 Mar 2015 15:35:24 GMT</pubDate>
            <atom:updated>2015-03-27T15:35:24.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*3J8TbNAYBqTpbhI7Oq3F5g.jpeg" /></figure><p><em>A draft of this article was </em><a href="http://blog.robinpowered.com/"><em>originally published on Robin’s team blog</em></a><em>, where we write more on product design, startups, and the future of work days.</em></p><p><strong>If I spent five minutes alone</strong> with a random person in your company, would I get the right impression?</p><p>Earlier this week I spoke on a panel about company culture. Culture is a whale of a topic, but this panel’s common thread was how to grow something that works. Once you hit your stride, how do you actually explain it to others? More importantly, how do you know when the culture <em>works</em>?</p><p>Good culture shows up in results instead of manifestos. At <a href="https://robinpowered.com/about">Robin</a> we use a five minute culture metric.<strong> If I leave you alone with <em>anyone</em> on the team for five minutes, three things will happen by the time I return:</strong></p><ol><li>You laugh. At least once.</li><li>You learn something.</li><li>You have something to look up later.</li></ol><p><strong>What kind of people work here? </strong>The three items above have little to do with personality, and more how you approach the world.</p><blockquote>We don’t take ourselves too seriously and extend the same courtesy to others.</blockquote><p>We also spend a lot of time experimenting with new things. I could explain our culture like that, but the five minute impression is a showcase to how we live those beliefs.</p><p>Plenty of folks spend time writing down lists of things they believe. They’ll draft culture manifestos with nebulous statements like “We’re always learning” and “We challenge the status quo”.</p><p>What do those sentences look like in action? Manifestos have their place, but knowing what it looks like in the wild is different. We like our approach because it’s a simple way to introduce how our team works. Your list will almost definitely be different. For example, a customer service organization might have “They asked about something <em>you’re</em> interested in.” This is just what makes sense for us right now.</p><blockquote>Culture has to grow with the organization, otherwise it’s just policy with a trendier name.</blockquote><p>What happens in your team’s five minutes?</p><p><em>Originally published at </em><a href="http://blog.robinpowered.com/2014/02/the-five-minute-culture/"><em>blog.robinpowered.com</em></a><em> on February 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f53443d1b59b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/robin-powered/the-five-minute-culture-f53443d1b59b">The Five Minute Culture</a> was originally published in <a href="https://medium.com/robin-powered">Robin Powered</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lies, damned lies, and startup advice]]></title>
            <link>https://medium.com/robin-powered/lies-damned-lies-and-startup-advice-7f22207c2a86?source=rss-4f09d383ed05------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f22207c2a86</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Zach Dunn]]></dc:creator>
            <pubDate>Thu, 26 Mar 2015 03:48:42 GMT</pubDate>
            <atom:updated>2015-03-26T13:55:13.866Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*Oouy2q9IGwcqNWvXwZFrMA.gif" /><figcaption>“<a href="http://www.markstivers.com/cartoons/">Knowledge is Power</a>” Mark Stivers</figcaption></figure><h4>The first 10 suggestions are easy.<br>It’s the next 100 that get you.</h4><p>In the early days of a startup, you rarely know exactly who your product is best for. You’ll know the rough industry, and a vaguely empowering statement about the audience.</p><blockquote>“We’re changing the way [Insert booming market] companies manage themselves!”</blockquote><p>So you set out with a rally cry, and try to figure it out along the way.</p><p>You talk to a few people who work in the, let’s say… <em>pet</em> industry. People like kennel owners, dogwalkers, and veterinarians. You say “I’m building a thing that makes it easy for you to manage your business.” and ask how they currently manage appointments. They point to a handwritten binder in the corner. You have a stroke of genius. These people need management software!</p><blockquote>If there’s one thing software engineers go crazy for,<br>it’s finding something people still do by hand.</blockquote><p>A few months later you have a handful of early customers signed up. Your original assumptions were fantastically wrong. Fortunately thanks to beta feedback you’ve hit a stride and things are starting to go well.</p><h3>“I want to hear what you’re doing…”</h3><p>Then one day you get coffee with a person with years of experience. A decade ago they invented something a lot of people liked. Today they advise some local startups you hear are doing well.</p><p>They seem incredibly smart… and also don’t understand your idea. Actually, that’s not entirely true — they understand the product, but worry you’re “missing the <em>real </em>opportunity”.</p><p>Interesting.</p><p>What if you focused on payment processing for pet businesses? <em>That </em>seems to be a real pain point. After all, they own a dog and they have to write a check every time they go to the dog groomer because they aren’t set up to accept credit cards. If you did payments, they know a dozen companies that could use this. The inventory system your current customers use is nice, but not a gamechanger. Or as they say — the killer app.</p><blockquote>At this point there’s typically an extended pause.</blockquote><p><strong>You wonder if <em>this</em> is how successful people happen.</strong> Did you just witness a serial success cut through months of internal debate like proverbial butter and solve everything about your product within minutes of hearing it? Or are they guessing just as much as you, but with a bit more conviction?</p><p>Startups are supposed to be flexible, so you nod and say “That’s good feedback, thanks.” You say goodbyes graciously and think “I liked them, but we’re on different wavelengths.”</p><p>A week later you hear from mutual friends that the person thought you were “fascinating, but the business wasn’t there”. For some reason it stings more than you want to admit.</p><h3>How the struggle actually works</h3><p>This is the gray area adversity that’s hard to explain about the early days of product market fit.</p><blockquote>Adversity rarely comes neatly packaged as<br>“Your product idea sucks and you’ll never make it”</blockquote><p>Instead it comes camoflauged as “missed” opportunities. It trickles in as reasonable-sounding advice from people with successful track records. It’s the type of advice makes you ask “Should I redirect the team this week?” It’s the blank response from someone clearly ouside your target audience, but still pushes forward with “…right, but what’s the <em>killer</em> app?”</p><h3>How to keep a feedback filter</h3><p>When you first start, its hard to know signal from noise. Most founders start with an earnest belief that everyone’s feedback is worth listening to, especially since getting <em>anyone’s</em> attention early on is hard enough as is.</p><ul><li><strong>Good product vision</strong> is flexible on the path, but firm on the destination. (<em>e.g. “The best way for people to communicate live”</em>)</li><li><strong>Good advice</strong> moves you further down a path while respecting the destination. (<em>e.g. “What if you used chat instead of pigeons?”</em>)</li></ul><p>I like to weight feedback based on how close the person is to the action. <strong>Expertise expires as industry tools change.</strong> Would a horseshoe maker be a good transportation advisor to Henry Ford?</p><p>The awesome news? You get <em>really</em> good at filtering. I mean stupidly good. As you build expertise about how your customers work, you’ll learn where valuable feedback really comes from. Once you start valuing the right channels, your product will show the results fast.</p><p>Here’s my current list for <a href="https://robinpowered.com/">Robin</a>. It changes monthly:</p><ol><li>Customers</li><li>People who have built similar B2B SaaS in the last two years</li><li>Potential customers</li><li>People who have built similar B2B products</li><li>Everyone else</li></ol><p>In early days you should find people who believe enough to test the idea despite uncertainty. Some people will think you’re missing out. Ignore them. Not every problem can be solved inside a quarter. They’ll be back when you figure it out, and their insights will have little to do with the outcome.</p><p><strong>Some problems you have to see for yourself, otherwise they sound almost unbelieveable.</strong> Sort of like explaining to someone who’s never left the suburbs that finding city parking can take hours.</p><p>…you know something? <em>Those </em>people could really use management software.</p><p><em>Discussion</em>: <a href="https://news.ycombinator.com/item?id=9269141">https://news.ycombinator.com/item?id=9269141</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f22207c2a86" width="1" height="1" alt=""><hr><p><a href="https://medium.com/robin-powered/lies-damned-lies-and-startup-advice-7f22207c2a86">Lies, damned lies, and startup advice</a> was originally published in <a href="https://medium.com/robin-powered">Robin Powered</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sensors, Switches, and Screens: The Future of Invisible Devices]]></title>
            <link>https://medium.com/robin-powered/sensors-switches-and-screens-the-future-of-invisible-devices-cb288d27120a?source=rss-4f09d383ed05------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb288d27120a</guid>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[future]]></category>
            <dc:creator><![CDATA[Zach Dunn]]></dc:creator>
            <pubDate>Thu, 19 Mar 2015 14:30:28 GMT</pubDate>
            <atom:updated>2015-03-19T14:30:28.698Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This article was </em><a href="http://blog.robinpowered.com/"><em>originally posted Feb 2014 on Robin’s team blog</em></a><em>, where we write more on product design and the future of work days.</em></p><p>There’s a good reason why self-hosted web and mail servers are a rare find in 2014.</p><p>If cloud computing did one thing well, it’s that it made people think long and hard before buying a complete server themselves. Infrastructure is hard, and upgrades are expensive. Folks like Amazon and Google take away the hassle via service without the depreciating assets.</p><p>I think the devices will go the same way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*LEbLuEFEugidNN_ybNCFZw.jpeg" /><figcaption><a href="http://www.digitallumens.com/">DigitalLumens</a> is changing how large spaces use lighting on demand</figcaption></figure><p>Ten years ago, the idea of lighting controlled by a data center hundreds of miles away was crazy. Pretty soon, it’ll be smart resource management. Once a device connects to the internet, it doesn’t matter where the “brain” lives. There’s little reason for a thermostat to house its entire processing power on the wall. The bare essentials are much leaner than today’s standard. All you need are sensors, switches, and screens. Something to read from the world, something to write to it, and something to give people updates about what happened. Everything else can happen <em>anywhere</em>.</p><blockquote><em>Once a device connects to the internet,<br>it doesn’t matter where the “brain” lives.</em></blockquote><h4>What’s old is new again</h4><p>Imagine if your entire office ran off of virtualized hardware thousands of miles away. Desks populated with screens log in as you sit down. An even crazier version? What if the desk was in an airport lounge of a city you’d never been before?</p><h3>Ownership becomes Obsolete</h3><p>Here’s where we <a href="http://www.newsweek.com/clifford-stoll-why-web-wont-be-nirvana-185306">start the bold predictions</a>. In five years, the idea of owning most of today’s $300 devices will seem crazy. The biggest byproduct of IoT is a connected grid of devices, each of which is available for public use (free or paid) by others on the grid. Want to switch from Acme’s lighting system to a hot new startup’s version? Just run their app instead. Your lights don’t have to change, just the thing <em>orchestrating</em> them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/699/0*JU2M8HTYxI0y4mnv.jpeg" /><figcaption>Fridaire’s Future Kitchen from General Motor’s 1957 “Design for Dreaming”</figcaption></figure><p><a href="http://buildinternet.com/2013/08/we-were-promised-refrigerators/">The refrigerator</a> worked as an introduction to the Internet of Things because most families have them. People keep refrigerators around for years. Upgrades only happen if something breaks or as part of a remodeling effort. They are stable placements.</p><p>Stability doesn’t carry over to many other devices. How often do you replace your computer? Your phone? Technology moves fast, and keeping up with the latest OS is a challenge the more integrated systems get. <strong>For connected devices to have lasting power, they have to reduce to the simplest unit of function as possible.</strong> When you buy a lightbulb it has one job to do, and you immediately know when it quits.</p><p>Packing more features into a single device increases points of failure and obsolescence. Both are expensive in the long run. Your locking system might work fine, but this year’s upgrade added motion sensing. As time passes, these minor updates will make your device seem as antiquated as a first generation iPhone. The more technology involved, the harder it is to become a “timeless” piece.</p><blockquote><em>“Timeless” items are replaced if they can’t be fixed— not when a new model comes out. When’s the last time you felt that way about your </em>phone<em>?</em></blockquote><h3>Today’s revolving door of hardware is unsustainable</h3><p>If devices use a distributed model, features become the result of new points on the grid instead of replaced hardware. Individual devices have more lasting power. Replacement is cheaper, since you’d only have to replace smaller modules instead of the entire system. This reduces waste and ownership costs.</p><blockquote><strong><em>A good connected device grid helps everyone buy </em>less<em> stuff.</em></strong></blockquote><p>The Nest thermostat uses their <a href="https://nest.com/smoke-co-alarm/life-with-nest-protect/">smoke detectors</a> to extend motion sensors used for occupancy. If nobody’s around, Nest changes the temperature. Those sensors are $130 each. <a href="https://www.sparkfun.com/products/8630">The motion sensor part could be $10 each</a> and have five times the coverage if Nest could access the grid they were on.</p><p><strong>The future will make devices invisible.</strong> They will be less of a specific component and more the abstract sum of parts connected via network — like cloud hosting is today. To get there, we’ll have to help people see connected devices as a software evolution and not a revolving door of things destined for the junk drawer.</p><p>App experience will be a better investment over time than keeping hardware up to date. As software takes over the device market, margins come from building experiences and not marking up $200 in parts. <a href="http://buildinternet.com/2013/11/the-internet-of-islands/">Open sourcing only software is the wrong part of the equation</a> — especially as infrastructure. But <em>hardware</em>? That’s a much more interesting proposition.</p><p>Five years from now the only parts we’ll need in person are sensors, switches, and screens… <a href="http://thejetsons.wikia.com/wiki/Rosie">unless you count the robots</a>.</p><p><a href="https://robinpowered.com/"><em>Robin</em></a><em> makes workplace coordination easy by teaching offices to recognize you. We’re on a mission to make the work day delightful, one room at a time.</em></p><p><a href="https://robinpowered.com/"><em>Upgrade your office</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb288d27120a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/robin-powered/sensors-switches-and-screens-the-future-of-invisible-devices-cb288d27120a">Sensors, Switches, and Screens: The Future of Invisible Devices</a> was originally published in <a href="https://medium.com/robin-powered">Robin Powered</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How companies unwittingly let interns run their facilities]]></title>
            <link>https://medium.com/robin-powered/how-companies-unwittingly-let-interns-run-their-facilities-9c8864202453?source=rss-4f09d383ed05------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c8864202453</guid>
            <dc:creator><![CDATA[Zach Dunn]]></dc:creator>
            <pubDate>Tue, 13 Jan 2015 17:05:50 GMT</pubDate>
            <atom:updated>2015-01-13T17:05:50.679Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*tBlKdW0wg_uSHcb4khDOzA.png" /></figure><p><em>How interns with clipboards lead to incomplete data and unnecessary buildings.</em></p><p>If you give an intern a clipboard, they’ll take notes. If they take notes, you’ll end up with a new building… at least, that is if you’re not careful.</p><p>One of the weirdest office behaviors we’ve encountered at Robin is the “bed check”. A bed check is something that sounds like a hazing ritual, but in reality is a critical part of how growing companies manage facility decisions. They work something like this:</p><ol><li>Acquire an intern or staff member with free time.</li><li>Hand them a clipboard and pen.</li><li>Send them out around the building and have them write down what rooms they see in use, and by how many people.</li><li>Recommend the company add facilities when that usage feels high.</li><li>Repeat monthly.</li></ol><blockquote>“…and then based on what they tell us, we build more stuff.”</blockquote><p>That’s it. Intuition and interns. A surprising number of large companies make decisions about growth this way. You may be skeptical. I don’t blame you. It’s a problem where anyone watching rightfully says “Is this really the best way of doing this?”</p><p>Your office’s meeting spaces are a precious resource. Making sure your team can quickly find the space they need to get work done is hard for growing companies. Fortunately (like most office problems) you can fix this today. Three tips we learned to stop intern-lead construction and start making smarter decisions for your office:</p><h3><strong>1. Stop measuring room usage with calendars</strong></h3><p>People book defensively, and relying on what the schedule says alone won’t accurately show usage. Often when people book defensively it’s a symptom of a larger problem. They normally believe it would be hard to find space should they need it, so the mid afternoon standup becomes a two hour window in case times need to change.</p><h3><strong>2. Find out which people (or teams) use the room</strong></h3><p>Not all occupants are equal. If you’re basing planning decisions on the binary “occupied” you’re missing out on <em>why. </em>Are your meeting spaces held by the marketing team 80% of the time? Maybe that’s an opportunity to be creative with their department space instead. <strong>For good space planning, the “who” is a better starting point than “where”.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rXZTsiQZtec3_tMCn_Vh1g.jpeg" /><figcaption>Most breakout spaces operate outside a calendar. (<a href="https://static.robinpowered.com/blog/images/intern-facilities/cooper-breakout.jpg">Image source</a>)</figcaption></figure><h3><strong>3. </strong>Open up un-bookable spaces for meetings</h3><p>Meeting rooms tend to be the early warning sign of overcrowding, but today many offices design public space areas instead. The meeting room is reservable, but guiding people towards free <a href="http://officesnapshots.com/collections/breakout-space/">breakout spaces</a> or non-traditional work areas when rooms are occupied saves a lot of headache. The corner conference room isn’t available? Use the third floor break room instead. Without making these an option, most workers will default to meeting-room only mentalities that inflate usage numbers. It may also explain why Steelcase work studies show 40% of people spend about 30 minutes per day finding space to meet.</p><p>If nothing else, give your interns a break and get them back into the business of coffee runs… at least <strong>those</strong> have a measurable result.</p><p><em>This article was </em><a href="http://blog.robinpowered.com/"><em>originally posted on Robin’s team blog</em></a><em>, where we write more on product design and the future of work days.</em></p><p><a href="https://robinpowered.com/"><em>Robin</em></a><em> makes workplace coordination easy by teaching offices to recognize you. We’re on a mission to make the work day delightful, one room at a time.</em></p><p><a href="https://robinpowered.com/"><em>Upgrade your office</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c8864202453" width="1" height="1" alt=""><hr><p><a href="https://medium.com/robin-powered/how-companies-unwittingly-let-interns-run-their-facilities-9c8864202453">How companies unwittingly let interns run their facilities</a> was originally published in <a href="https://medium.com/robin-powered">Robin Powered</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How designing an invisible app almost killed us]]></title>
            <link>https://medium.com/robin-powered/how-designing-an-invisible-app-almost-killed-us-264d7f29ba10?source=rss-4f09d383ed05------2</link>
            <guid isPermaLink="false">https://medium.com/p/264d7f29ba10</guid>
            <dc:creator><![CDATA[Zach Dunn]]></dc:creator>
            <pubDate>Wed, 31 Dec 2014 18:31:30 GMT</pubDate>
            <atom:updated>2015-01-11T17:30:28.445Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*gdPTkAZrDnvgTjucGe5vvw.png" /></figure><p><em>Lessons learned from building automation products that give good feedback.</em></p><p>Without looking up, how many lightbulbs in your office are out? How strong is your phone’s signal? Unless you’re sitting in darkness or dropping calls… why would you <em>want</em> to know?</p><blockquote>“Nobody notices when things go right.” — Zimmerman’s Law of Complaints</blockquote><p>Problems, as it turns out, are the fastest way to bring visibility to your day’s mechanics. Everything is smooth sailing until it isn’t, and then whatever failed is suddenly the center of attention.</p><p>This makes the new class of automated tech really hard to get right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*dRrjkZhwmSxp12gXM-bYvw.jpeg" /><figcaption>For the muggle world, not all invisibility is magic.</figcaption></figure><h3>You have to earn invisibility</h3><p>Automated products hit a wall if you make them run silently in the background before teaching people how they work. Invisibility is earned, a lesson we learned the hard way.</p><p><strong>The quick and dirty background about our app:</strong> <a href="https://robinpowered.com/">Robin</a> is a room booking tool for offices that runs on mobile, web, and tablets. You can book from the apps directly, but there’s also a twist for mobile users — we can run in the background and use iBeacons to detect when you’re in a room, booking calendars automatically. This means your team stays updated with a live feed of who and what’s available.</p><p>The fact you don’t need to open the app to use it is where our problems start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*BsyiUWoQJBLDDG80TzRVXA.jpeg" /><figcaption>The original app showed where you were, and did everything else in the background.</figcaption></figure><p>Our early approach (as you can see in the screenshot above) was “Keep your phone in your pocket, we’ll handle the rest”. The thinking was that if people <em>just</em> had the app installed, we could do the rest automatically based entirely on presence data. It was a noble idea (aren’t they all?), but after our beta launched we quickly realized being so far out of the way created a new mess of problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*0nPf8r0eBL4paSSVL2mIHw.gif" /></figure><p>The challenge with “hiding the work” too early is people never learn how to do it manually — just ask anyone who’s walked into a closed door. In usability, these cues are called <a href="https://www.interaction-design.org/encyclopedia/affordances.html">affordances</a>, and are how (most) people manage to use everyday objects like chairs without instruction manuals. New tech already starts with a knowledge gap. Early on you’re better off automating 95% and requiring a button for the final 5% than skipping the education step.</p><p>Then there’s the issue of credibility. <strong>If you can’t see <em>how </em>a decision is made, it’s harder to trust the results.</strong> Amazon reminds you recommendations are “based on your purchase of X” for a reason.</p><h3>Missing feedback moments</h3><p>In our case, getting feedback from the beta was very difficult. We would talk to customers several weeks in and we’d hear “Oh, I actually haven’t opened the app recently.” Things were mostly working, but we had a visibility problem and our usage metrics alone weren’t telling stories we could act on — we were flying blind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*fwPI2UcKFMX-XJYDBsNKuQ.png" /><figcaption>“Oh weird, you’re not showing up yet.”</figcaption></figure><p>Worse still, when the app did have bugs it failed silently in the background. Our early users would notice Robin wasn’t working when they had room collisions or the web dashboard stopped showing a coworker.</p><blockquote>The only time people remembered we were there was when the app had issues, which is a terrible way of reintroducing yourself.</blockquote><p>Getting to this point was slow because when you’re working with a system with no screens it’s hard to give people feedback of “It’s working” without interrupting them constantly. On the other hand, by the time it’s not working you may not have the option to tell anyone — like only noticing a broken air conditioner after you start to sweat.</p><h3>What we missed</h3><p>Our first version fell into a trap of believing that solving the problem meant people didn’t want to think about it at all. <strong>In reality people really just wanted to think about it <em>less</em>.</strong> The lack of app feedback also muted the gratifying “I’m a superhuman” moment of a room recognizing you and jumping into action.</p><ol><li>Regular feedback is a big deal when you’re moving towards product market fit.</li><li>When you sell something that feels like the future, people want an easy way to show it off.</li></ol><blockquote>Our app was like the average Boston startup — it did useful things and forgot to tell anyone.</blockquote><h3>How to increase visibility</h3><p>We had an invisible man problem to solve. So how do you design an automated product to be more visible while still letting it, well… automate?</p><p>We asked five questions:</p><ol><li>How would a user discover if the app stopped working?</li><li>What events are worth interrupting a user’s day for?</li><li>How many decisions does the user have to make for the app per day? Week?</li><li>What other things change when the app is working? Think secondhand feedback. (e.g. Does it post to friend’s activity feeds? Update a display somewhere?)</li><li>How often does the app have new information? (e.g <a href="http://timehop.com/">Timehop</a> has 1 daily, chat apps have unlimited)</li></ol><p>Getting these answers allowed us to make more directed product decisions with feedback in mind.</p><h3>A reason to leave the pocket</h3><p>Compared to the browser version, mobile was a lame duck. We took tools that previously only existed on the web dashboard and made one-touch versions for the mobile app. If you pick good presets, most people don’t miss the extra options.</p><p>First we added the ability to search for free rooms, which was the first feature that gave people a reason to open the app regularly. The unexpected bonus was you could now use the app remotely, and check who was in the office from their commute. People liked that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*1yrZrc3Mt5tQksF3dPqrfA.png" /><figcaption>These sidebars were the first step to adding in-app actions</figcaption></figure><p>Being invisible also robbed users of their chance to explore new features as they came out. Today most app stores update in the background, so checking for new stuff doesn’t really make sense if you thought the app was supposed to run silently in your pocket. We had to retrain people to think of the app as a tool instead of a passive experience.</p><p>From there, our fixes broke down to three main points.</p><h3>#1 Ask for decisions</h3><blockquote>“This room is booked in 10 minutes. Find another one?”</blockquote><p>Just because the system can figure it out doesn’t mean it should. Optional control is a powerful UX tool. Decisions are part of why checking email (and recently <a href="http://slack.com/">Slack</a>) is so addictive — there are constantly new messages you can respond to. Asking users to make a decision also gains instant visibility at the exact moment when you’re doing something useful. <strong>Good decision notifications are an app’s version of humble brags:</strong></p><blockquote>“Hey I’m doing something useful here. Do you want to be involved?”</blockquote><p>When UX or technical issues get in the way of this process, we gain feedback a product team can act on. Read-only info often makes feedback about accuracy or speed instead of utility and output.</p><h3>#2 Add notifications</h3><blockquote>“Emily just arrived at the office”</blockquote><p>Hindsight is always 20/20, but at the time this one felt forced to launch with. The first version of the app focused on getting information <em>to</em> the platform and crunching the good stuff there. Notifications seemed like the opposite of good design since we <em>prided ourselves</em> in being out of the way.</p><p>On second thought, we realized almost all of our interactions started based on people being somewhere. <strong>With good notifications, we could connect users to context and decisions about a space at the exact moment it’s <em>least likely</em> to be intrusive.</strong> A bit like Foursquare tips but for room level.</p><h3>#3 Build the neighborhood</h3><blockquote>“Can’t we just have the iPad do it instead?”</blockquote><p>A common tech in modern-thinking offices are wall-mounted iPads. We originally resisted on account of it feeling a little clunky. Then we realized it wasn’t about the iPad as a centerpiece, it was about what they could do as wingman.</p><p>The device that triggers an action doesn’t <em>have</em> to show the feedback. By recruiting other devices in the neighborhood (i.e. coworker’s apps, <a href="https://robinpowered.com/features#tabletApp">wall-mounted iPads</a>) to show updates, we multiplied points of ambient feedback. Originally when you walked into a room running Robin, nothing changed. Now when you walk up to a room, the iPad shows your face as well as everyone inside. Even better? The phone stays in your pocket.</p><blockquote><strong>Interfaces become whatever devices are currently nearby</strong>.</blockquote><p>We believe this is how “UI-less” apps will grow in the physical world. It’s not so much about a “post-screen” experience as much as “Whatever screens are free”. This may sound squishy, but it’s early days and the industry still has a lot to experiment with. In the meantime, we’re focused on making stuff people can see and have opinions about.</p><p>As you build interactions for the next wave of tech, make sure the experience reminds users it exists. Picking the right parts of your product to un-automate will require some experimentation, and you probably won’t get it right the first time around. Fortunately, automation products are at the very beginning of their time to shine. <strong>There’s an elegance in minimalism, but there’s also a danger in being overlooked.</strong> Completely invisible may sound good on paper, but <em>just invisible enough</em>? That’s elegant.</p><p><em>This article was </em><a href="http://blog.robinpowered.com/"><em>originally posted on Robin’s team blog</em></a><em>, where we write more on product design and the future of work days.</em></p><p><a href="https://robinpowered.com/"><em>Robin</em></a><em> makes workplace coordination easy by teaching offices to recognize you. We’re on a mission to make the work day delightful, one room at a time.</em></p><p><a href="https://robinpowered.com/"><em>Upgrade your office</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=264d7f29ba10" width="1" height="1" alt=""><hr><p><a href="https://medium.com/robin-powered/how-designing-an-invisible-app-almost-killed-us-264d7f29ba10">How designing an invisible app almost killed us</a> was originally published in <a href="https://medium.com/robin-powered">Robin Powered</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>