<?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[Building Things on the Internet - Medium]]></title>
        <description><![CDATA[Curated by @bkrall —Picks of the best posts about building things on the web. - Medium]]></description>
        <link>https://medium.com/building-things-on-the-internet?source=rss----735f5e8aec20---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Building Things on the Internet - Medium</title>
            <link>https://medium.com/building-things-on-the-internet?source=rss----735f5e8aec20---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:05:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/building-things-on-the-internet" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What We’re Shouting For]]></title>
            <link>https://medium.com/building-things-on-the-internet/what-were-shouting-for-f8bebb193d9e?source=rss----735f5e8aec20---4</link>
            <guid isPermaLink="false">https://medium.com/p/f8bebb193d9e</guid>
            <dc:creator><![CDATA[Shout]]></dc:creator>
            <pubDate>Wed, 23 Jul 2014 15:37:38 GMT</pubDate>
            <atom:updated>2014-03-03T01:14:53.122Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*kIJ2pwLPljQGPinKPZP6ew.png" /></figure><p>Shout had a very exciting week. UrbanDaddy posted an <a href="http://www.urbandaddy.com/nyc/gear/29712/Shout_Buy_Your_Way_into_Any_Restaurant_New_York_City_NYC_Application">article</a> Tuesday afternoon and within a half hour our user base had doubled. The New York Post and <a href="http://www.refinery29.com/2014/02/63458/shout-app">Refinery29</a> followed; then, my proud, Jewish mother called to tell me Kelly and Michael were chatting about Shout. By 5 O’clock on Thursday, I was on the Pat Kiernan radio show. After I hung up, Pat’s co-host implied that Shout could soon be used to sell plots in a cemetery to the highest bidder. Boy, did that bother me.</p><p>After we received an inflow of new users, we locked down the platform. We did this to maintain quality and to stay true to our long term goals. Let me explain.</p><p>Shout has one main assumption: people in close proximity have complementary resources and needs and, if given the opportunity to communicate, can make exchanges and help one another. At the moment, we are striving to learn what is most essential when two strangers are entering a relatively synchronous transaction. What do they need to feel most comfortable? What can we do to facilitate their interaction, but not restrict it? These are the types of questions we are working to answer and your feedback has already been incredibly helpful.</p><p>Two weeks ago, Wes wrote his blog post about our Valentine’s day promotion. After a whirlwind 12 hours of flower deliveries throughout the city, we realized how fortunate we were to be a special part of everyone’s day. Setting aside my interest in the platform, it felt genuinely awesome to help a stranger. We were struck by the fact that there is no great way for someone to ask for, or offer, help. And so, our mission for Shout crystallized.</p><p>Some of you may have noticed that you can now “sell” things on Shout for free. This is only a hint of what is to come, but it taps into something larger that we are trying to accomplish. We want people who are nearby to be able to have spontaneous and extraordinary interactions and in doing so, help a fellow Shouter in need. We want Shout truly to be a community, not only an abstract, ethereal, Internet community, but a true community of people interacting in real time, in a real space.</p><p>Shout will either fail or succeed attempting to create a world where you can sit in a coffee shop and Shout for a charger or borrow something from a neighbor or sell your spot in line. If there is a reward attached to the Shout, great, if not, even better. What we care about is connecting people in close proximity with complementary resources and needs.</p><p>Henri’s first post referenced an early user who found Shout in FL., and then bought SNL tickets and a spot at RedFarm the day before going to the Superbowl. He said something that has stuck with all of us, “Having Shout is like having a friend in New York.” It may be overly sentimental, but it meant a tremendous amount to the team. It perfectly embodies what we are trying to accomplish.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8bebb193d9e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-things-on-the-internet/what-were-shouting-for-f8bebb193d9e">What We’re Shouting For</a> was originally published in <a href="https://medium.com/building-things-on-the-internet">Building Things on the Internet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You Can Already Code—You Just Don’t Know It Yet]]></title>
            <link>https://ednewtonrex.medium.com/you-can-already-code-you-just-dont-know-it-yet-862044601a5a?source=rss----735f5e8aec20---4</link>
            <guid isPermaLink="false">https://medium.com/p/862044601a5a</guid>
            <dc:creator><![CDATA[Ed Newton-Rex]]></dc:creator>
            <pubDate>Thu, 12 Jun 2014 14:33:31 GMT</pubDate>
            <atom:updated>2016-01-16T12:12:04.519Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/639/0*TtQ8lTOox4J6AUBW.png" /></figure><p>When someone tells you they code, it’s as if they’re calling you from inside the world’s most exclusive club. It’s probably a pretty great party in there, but you’ve got no idea how they got on the guest list and you’re fairly sure that even if they came out, floored the bouncer and physically carried you in, the bar staff would spot your trainers and you’d find yourself back on this side of the door in ten minutes. Like speaking Chinese or perfecting the moonwalk, coding is just one of those things you’ll never be able to do.</p><p>This, of course, is a complete myth. There’s nothing stopping you learning to code. In fact, you could start right now. Go on - don’t even read to the end of this post. Click <a href="http://www.codecademy.com/#!/exercises/0">here</a> instead. You’ll have written your first lines of code before you next check Facebook. Or <a href="https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Introduction">here</a> if you want to make a website. Or <a href="https://developer.apple.com/library/ios/referencelibrary/GettingStarted/RoadMapiOS/index.html">here</a> if you fancy giving an iPhone app a go. Like most things, getting started turns out to be as simple as Googling it and clicking on the first link that’s not an ad. Every coder out there has to start from square one at some point.</p><p>But you’re not really starting from square one. Because really, deep down, you already know how to do it. Code is instructions. You write the instructions, and the computer follows them. Any time you’ve given someone directions to your house, or typed in a sum on a calculator, or lined up a row of dominoes, you’ve essentially been coding. The person following your directions, you pressing the equals button, knocking over the first domino - that’s the code being run. Coding is pretty much teaching a series of steps to a computer, for the sole reason that it can follow those steps a hell of a lot quicker than you can.</p><h3>Twitter / edrex_: Learn to code. Because, deep ...</h3><p>Learn to code. Because, deep down, you already know how. https://medium.com/on-coding/862044601a5a ...</p><p>Running your first line of code and seeing it do whatever it was you told it to, you quickly realise this is something you could get used to. Most of us love giving orders, and when you sit down to code you’ve got what amounts to an uncomplaining, untiring, unerring servant literally at your fingertips. Sure, you have to issue your edicts in a fairly precise way - but ask nicely and it will do pretty much anything for you. And learning the language is easier than you might think; you’ll quickly find that amateur coders are probably the third best served group on the internet, losing out only to Google Incognitos and cat-lovers. For literally every problem you come across, someone will have had it before, asked the rest of the world about it, and received an answer that sounds like it’s been taken straight out of a computer science textbook. It’s as if Tim Berners-Lee is sitting in a room somewhere, scouring the Internet for helpless beginners, and answering each of their questions in turn under a different, ill-judged pseudonym. Bless him.</p><p>There’s the usual spiel about the astronomical salaries, the free lunches, the wearing hoodies to work - but you already know all that. Everyone has since they made that film about Justin Timberlake going to Harvard. No, a better reason to start coding, one that may trample all over your better judgement, is that it’s fundamentally creative. You just have to look at what some of the tech companies out there are doing - the Twitters and Apples of this world - to see that this much is true. Thinking that coding is the nerdy IT guy at work rebooting your computer is like thinking that music is what happens when the piano tuner comes round.</p><p>Let’s be clear - like anything, getting really good is tough. Unless you happen to be a 7-year-old, you’re probably not going to find time to rack up your 10,000 hours. But that’s not what most of us are going for, and it’s certainly no reason not to pick it up. So if you’ve ever thought you’d like one day to give it a go, treat today as that day. Or at least some time this week. Because, basically, you can already do it.</p><p><em>I started learning to code in 2011 and, since then, I’ve built </em><a href="http://www.jukedeck.com/"><em>Jukedeck</em></a><em>, a system that composes original music and gives you unique, bespoke music for your videos. I’d love to know what you think!</em></p><h4>Up next</h4><p><a href="https://medium.com/p/ece341fe81f5"></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=862044601a5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Entrepreneurial Advice Nobody Gives You]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://lincolnwdaniel.medium.com/entrepreneurial-advice-nobody-gives-you-d64515897dd2?source=rss----735f5e8aec20---4"><img src="https://cdn-images-1.medium.com/max/2432/1*ultGjHjDOeJRwJYO-mEzGw.jpeg" width="2432"></a></p><p class="medium-feed-snippet">You just have to go on a journey.  Vital lessons every business person needs to learn.</p><p class="medium-feed-link"><a href="https://lincolnwdaniel.medium.com/entrepreneurial-advice-nobody-gives-you-d64515897dd2?source=rss----735f5e8aec20---4">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://lincolnwdaniel.medium.com/entrepreneurial-advice-nobody-gives-you-d64515897dd2?source=rss----735f5e8aec20---4</link>
            <guid isPermaLink="false">https://medium.com/p/d64515897dd2</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[small-business]]></category>
            <dc:creator><![CDATA[Lincoln W Daniel]]></dc:creator>
            <pubDate>Sat, 20 Feb 2016 05:45:15 GMT</pubDate>
            <atom:updated>2019-12-10T12:45:06.139Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Accessibility for designers]]></title>
            <link>https://garrone.medium.com/accessibility-101-56f87f3d726e?source=rss----735f5e8aec20---4</link>
            <guid isPermaLink="false">https://medium.com/p/56f87f3d726e</guid>
            <dc:creator><![CDATA[Garron Engstrom]]></dc:creator>
            <pubDate>Fri, 03 Oct 2014 15:05:37 GMT</pubDate>
            <atom:updated>2014-06-10T02:39:58.314Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FwIB3BNun6vptuDN1m9ZXQ.png" /></figure><h4>Mind your RGB’s</h4><p>I began this year with the objective of learning more about accessibility, particularly as it pertains to design. So, at SXSW 2014 I attended as many workshops and talks on accessibility as I could:</p><blockquote><a href="http://schedule.sxsw.com/2014/events/event_IAP24940">Accessibility: Make it happen!</a> by Carol Gibson &amp; Susan Hewitt</blockquote><blockquote><a href="http://schedule.sxsw.com/2014/events/event_IAP22867">Mobile Accessibility &amp; 508 Compliance for Gov</a> by Jordan Sheckman</blockquote><p>For those less familiar with the concept of accessibility it comes down to understanding that the web is for everyone. It is easy to put on your blinders and think of your user as someone sitting at a desk with a high-res monitor and a mouse. While that may in fact be the majority of your users, you need to also take into account the needs of physically and cognitively impaired users as well as those in less-than-ideal situations (e.g. outside, low-res display, etc.). Here are a few quick tips with a focus on color. According to the <a href="http://www.w3.org/WAI/EO/wiki/Web_Accessibility_Basics">W3C</a>, interfaces, navigation and information must be:</p><h4>Operable</h4><p>This principle is almost entirely about alternative forms of input other than a mouse. Ensure your experience can be navigated and understood using a keyboard.</p><h4>Understandable</h4><p>The user must be able to read and understand the content as well as the overall structure of the website/experience. This principle is also very much about avoiding, understanding and correcting errors.</p><h4>Perceivable</h4><p>This is where I will focus because I recently ran into problems with a redesign I was working on. This principle is mostly about providing enough color contrast between the foreground and the background (in most cases, the foreground will be text). While redesigning an experience within my product at work I took a step back to do a quick audit on color contrast ratios using <a href="http://webaim.org/resources/contrastchecker/">WebAIM</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/159/1*evmi2LflDK_tSfUh2GtOKg.png" /></figure><p>To my surprise most of the new core colors we were implementing failed WCAG AA and AAA contrast ratios. Overall over 60% of our contrast ratios failed; this was a huge blow as it meant we needed to rethink our entire color palette. We are still working through the issues but we are glad we caught it early with such a quick and simple audit. It can be very easy as a designer to want to use color to either emphasize or de-emphasize certain elements but you need to be aware of how or even if certain subsets of your users will be able to perceive those elements.</p><p>This is an EXTREMELY high level view of accessibility. My goal was to share an anecdote about how easy it is for designers to do a quick accessibility gut-check. For those entrenched in this world, this may seem over-simplified and for those new to it, this is certainly not enough information. For the latter, here are some great resources to get started:</p><p><a href="http://alistapart.com/topic/accessibility">http://alistapart.com/topic/accessibility</a></p><p><a href="http://webaim.org/intro/">http://webaim.org/intro/</a></p><p><a href="http://wave.webaim.org/">http://wave.webaim.org/</a></p><p><a href="http://www.w3.org/WAI/">http://www.w3.org/WAI/</a></p><p><a href="https://medium.com/search?q=accessibility">https://medium.com/search?q=accessibility</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56f87f3d726e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our front-end development boilerplate]]></title>
            <link>https://medium.com/@thekevinjones/our-front-end-development-boilerplate-2bf2d3f3fdde?source=rss----735f5e8aec20---4</link>
            <guid isPermaLink="false">https://medium.com/p/2bf2d3f3fdde</guid>
            <dc:creator><![CDATA[Kevin Jones]]></dc:creator>
            <pubDate>Mon, 09 Jun 2014 17:18:06 GMT</pubDate>
            <atom:updated>2014-08-27T16:19:48.370Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RR2MvuhP2Uv9KmLql1Whfg.jpeg" /></figure><h4>Grunt, SASS, and everything in-between</h4><p><em>tl;dr The frontend boilerplate we use for starting new sites is now posted publicly here: </em><a href="https://github.com/kps3/kps3.boilerplate"><em>https://github.com/kps3/kps3.boilerplate</em></a></p><p>Grunt, Gulp, SASS, LESS, Handlebars, Underscore, Bower, and 100 different front-end development tools have been created over the last few years. What happened? Seriously, what the hell happened?</p><p>Front-end coding has changed dramatically over the past three years, and we’ve felt it at <a href="http://kps3.com/">KPS3</a>. Our projects have grown in size, and with that, in complexity. What used to work for a simple two page website doesn’t work for a large-scale web app or 800 page State website. After months, or more realistically, years, we have finally narrowed down our front-end development process and started documenting it.</p><p>We started by creating our boilerplate. The boilerplate is the basis for all new projects. It’s a combination of several different tools, and has undergone several different versions. You can see where it stands today <a href="https://github.com/kps3/kps3.boilerplate">here</a>. Note, our boilerplate requires several prerequisites: <a href="http://nodejs.org/">Node (for npm</a>), <a href="http://compass-style.org/">Compass</a> (gem install compass), and<a href="http://gruntjs.com/">Grunt</a> (npm install -g grunt-cli).</p><h3>Fo​undation vs every other framework</h3><p>We started using <a href="http://foundation.zurb.com/">Foundation</a> early on. It was one of the first responsive frameworks we used—and I’m happy we picked it. The simplicity and ease of learning, using, and adapting foundation to any project has made it a staple in our workflow. We don’t even create a site nowadays (unless specifically requested) that doesn’t use foundation as the base layer. This was our first real step in standardizing our front-end development stack.</p><h3>SASS vs LESS</h3><p>We started using LESS. It was our first dip into the world of advanced front-end development—and it didn’t go too well. We started using the javascript compiler that would just compile everything client-side. Terrible idea—don’t do it. We then moved to using a variety of LESS compilers, eventually landing on using a Watcher for PHPStorm. Things finally started to work well. We all used PHPStorm. We all used the Watcher. Our settings were all the same. Life was grand. And then we hired <a href="http://kps3.com/company/crew/jonathan-rutheiser">Jonathan Rutheiser</a>.</p><p>Jonathan joined the team about 7 months ago and has really helped us focus our front-end strategies. Armed with a wealth of SASS, Compass, and Mixins knowledge, he convinced us that LESS was the wrong approach. Sure, there are ways of getting the support for LESS, but it just wasn’t as easy as getting everyone up and running with SASS &amp; Compass. (Oh, and Foundation adopted SASS as their preference and the two play wonderfully together.) We all converted to SASS, and just kept using our Watcher in PHPStorm to compile everything. Just a minor change and all was right again. But, as our team grew we had to adapt our setup to work outside of a specific code editor. Each developer has a different coding style, a different editor of choice, and different settings unique to their environment. It wasn’t fair to ask everyone to use PHPStorm. So, we began modifying our process again.</p><h3>Grunt vs. Gulp</h3><p>To be honest, I can’t remember why we chose Grunt over Gulp. I’m pretty sure Gulp didn’t exist at the time, but I don’t know. Anyway, it doesn’t matter at this point. If you haven’t checked out <a href="http://gruntjs.com/">Grunt</a>, you really should. It’s fantastic. To explain it simply, we use grunt to enhance and compress our CSS and JS, optimize our images, and easily manage different templates and partials. If you’re interested in the details of what add-ons we use, go take a look <a href="https://github.com/kps3/kps3.boilerplate/blob/master/package.json">here</a>.</p><h3>The Git Repo</h3><p>So, how do we keep this all organized? We are constantly tweaking and enhancing our setup, and updating the “_Starter Template Folder” on our client server wasn’t cutting it. We didn’t know when it was updated and it was impossible to track our changes / updates. Git was the perfect solution—our designers, front-end devs, and back-end devs already all collaborate through it, so let’s use it for more than client projects. We created the <a href="https://github.com/kps3/kps3.boilerplate">boilerplate repo</a> and we each have it cloned down to our machine. Having our boilerplate in a Git repo makes updates a breeze and you can be sure you always have the latest version. It also makes it super easy to track updates, bugs, and continuously improve the project.</p><h3>Our process for each project</h3><ol><li>Open Terminal and navigate to the <a href="https://github.com/kps3/kps3.boilerplate">boilerplate repo</a> on your machine.</li><li>Do a “git pull” to receive any updates/bug fixes that may have happened since you last used it.</li><li>Copy the files from the boilerplate directory and paste them into your new project directory.</li><li>If you’re good with the basics, run “npm install” (you may have to sudo depending on your configuration).</li><li>If you’d like to add anything more custom, run “npm install [package-name] —save-dev”. This will install the module and add it to your package.json so others will get it.</li><li>Since we’re using both Grunt and Compass, there are two config files you can edit to your specifics needs: Gruntfile.js (grunt) and config.rb (compass).</li><li>Now that your settings are configured, navigate to your project directory in Terminal and type “grunt watch”. This will watch the directory for any changes. As files get saved and changes get made, Grunt will recompile all the styles, javascript, templates… basically all the magic.</li></ol><h3>Taking it further</h3><p>This is just a starting point. It may seem daunting at first, but it’s actually extremely easy after you get the hang of it. This combination of tools and process has allowed us to move faster with our front-end development and write cleaner, better code. We’re able to split up our template files how they’d actually be split up in an app development environment and create a more modular way of organizing our files. (Side note: this is a HUGE help when multiple developers are working on one project; having everything split out and modular has cut down on painful merge conflicts a ton.)</p><p>Now, I won’t say it’s perfect. We’re still running into some issues with different people’s tab sizes, tabs vs. spaces, and overall just coding styles—but I’d gladly take those issues over going back to front-end coding three years ago.</p><p>KPS3 Frontend boilerplate repo: <a href="https://github.com/kps3/kps3.boilerplate">https://github.com/kps3/kps3.boilerplate</a></p><p>Have any ideas on how it can be better? Found a bug? Contribute!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bf2d3f3fdde" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bezos’ lesson applied]]></title>
            <link>https://medium.com/@fabiozib/bezos-lesson-applied-18e7b1268c12?source=rss----735f5e8aec20---4</link>
            <guid isPermaLink="false">https://medium.com/p/18e7b1268c12</guid>
            <dc:creator><![CDATA[Fabio Zilberstein]]></dc:creator>
            <pubDate>Thu, 22 May 2014 14:37:22 GMT</pubDate>
            <atom:updated>2014-05-22T14:37:22.436Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qjoZvG8eX5ddhHl6D3cr5Q.jpeg" /></figure><h4>3 basic rules for better (web) service</h4><p>Some time ago I read an article summarizing the <em>modus operandi</em> that Jeff Bezos tried to infuse in Amazon animus in 3 key steps:</p><ol><li>Respect your customer (user).</li><li>Be innovative.</li><li>Be Patient.</li></ol><p>How this apply to our effort to improve our<a href="http://ec.europa.eu/digital-agenda"> web presence</a>? Let’s try to crack it in few lines:</p><p><strong>1. Respect our user (customers).</strong></p><p>The inversion of terms in and out of brackets is not casual as <strong>the first step is to realize who are our users, </strong>hopefully becoming customers.</p><p><strong>Users = people who (need to) “use” our website. </strong>They are <strong>not</strong>, for example, our hierarchy, pleased in seeing published a series of self-referencing information. It’s about creating a content offering addressing their need and that they can use in their work/life, not a 1-way broadcast of what we think it’s important and like to publish.</p><p>Respecting them therefore means:</p><p><strong>a)</strong> <strong>respect and value their time, that’s the most precious resource! </strong>Enough of pages worth 5,000 words and 25 attachments, written in a jargon that need translating BruxellesEnglish—-&gt;PlainEnglish. Our content must be immediately available, well indexed and searchable with a straightforward and natural navigation driving people to the correct info if they landed on the another page.</p><p><strong>b)</strong> <strong>Respect their needs. </strong>You cannot and should not decide for them as it’s not about your need to publish, but rather how can you help them achieving their goal with the visit. Ask them what they need.</p><p><strong>c) Respect their money (time=money)</strong> You don’t produce a homepage loaded with useless content that will never open on a smartphone on a train through remote valleys and that will cost them a salary in <a href="https://medium.com/user-experience-researche/537f4c46c629">roaming</a>!</p><p><strong>d)</strong> … and so forth, you got the sense of it</p><p><strong>2. Be Innovative.</strong></p><p>Can we innovate in the public sector? Yes of course! And we must I would say! It’s just a different way of innovating. For <a href="http://ec.europa.eu/digital-agenda">DAE</a> website we did it on several levels:</p><p><strong>a) Technological wise: </strong>taking established robust technologies like <a href="https://drupal.org/">DRUPAL Open Source</a> and break rusted working habits. <strong>Technology innovation does not necessarily mean being on the cutting edge, but innovate your own technological framework to improve your efficiency. </strong>With this shift for example:</p><blockquote>“We removed the technology out of the equation. It was so easy to use the interface that contributors did not (and could not) complain anymore about the tool and concentrated on producing quality content” <a href="http://www.twitter.com/ringrda">(David Ringrose)</a></blockquote><p><strong>b) Process wise: </strong>breaking a clustered way of producing content and conceiving internal and external communication across units and departments . Shifting the balance between centralization and decentralization according to the level of maturity of the community. Hence, it’s a “metrics drives quality” process and learning process for all people involved.</p><p><strong>Our choice is to couple a fully decentralized content production while centralizing the quality assurance with professional editor(s)</strong>. In fact the easiness of the tool allowed to move the content production closer to the experts without the intermediate layer of HTML savvy publishers.</p><p><strong>c) Corporate wise: </strong>we do not close ourselves in our corner enjoying a position of supposed excellence among departments, but we share it with our community of colleagues and drive them on the path we are convinced will prize efforts. Involving more colleagues we can test approaches against a wider panoply of needs, ensuring more future-readiness of the solutions.<strong> It’s a pendulum: we think big first, we start small and then grow up aiming at the big picture in mind.</strong></p><p><strong>3. Be Patient.</strong></p><p>This is the hardest. The world was not built in one day, even God needed six, the same we have to do in our work life: <strong>we have to put the seed and care for its growth, not just wait for it.</strong><br><strong>The caring part is fundamental and that’s where patience is needed:</strong></p><ul><li>To educate and train our colleagues,</li><li>to convince our stakeholder we are going in the right direction,</li><li>to go back to our user and check their needs…</li></ul><p><strong>Nothing is taken for granted and we have to build our portion of confidence and trust through every day deliverable.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/351/1*fthtj9eVSn8aiKCsULvv3w.jpeg" /><figcaption>I found this pic quite deep in meaning, if anyone knows the author please let me know.</figcaption></figure><blockquote><strong>As the old Chinese say “a journey of 1000 miles start with the first step”; and I would add “don’t forget to continue walking!”</strong></blockquote><p>Did you liked this story? I look forward your comments, tips, suggestions, tweets (<a href="http://twitter.com/fabiozib">@fabiozib</a>), linked readings, feedback… any sign of life ;)</p><p>I will do my best to reply to everyone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18e7b1268c12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[So you wanna learn how to design? Here are 7 things you can do right now to get started]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@cyn_koo/so-you-wanna-learn-how-to-design-here-are-7-things-you-can-do-right-now-to-get-started-d10d258206fd?source=rss----735f5e8aec20---4"><img src="https://cdn-images-1.medium.com/max/2400/1*KaGQ8A6cCqH40z0vc2TeDg.jpeg" width="2400"></a></p><p class="medium-feed-snippet">All you&#x2019;ll need is 20 minutes</p><p class="medium-feed-link"><a href="https://medium.com/@cyn_koo/so-you-wanna-learn-how-to-design-here-are-7-things-you-can-do-right-now-to-get-started-d10d258206fd?source=rss----735f5e8aec20---4">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@cyn_koo/so-you-wanna-learn-how-to-design-here-are-7-things-you-can-do-right-now-to-get-started-d10d258206fd?source=rss----735f5e8aec20---4</link>
            <guid isPermaLink="false">https://medium.com/p/d10d258206fd</guid>
            <dc:creator><![CDATA[Cynthia Koo]]></dc:creator>
            <pubDate>Thu, 17 Apr 2014 03:56:04 GMT</pubDate>
            <atom:updated>2018-11-08T08:51:01.908Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Squarespace: A Guerilla Usability Test]]></title>
            <link>https://medium.com/@__smp/squarespace-a-guerilla-usability-test-c5f70b708b82?source=rss----735f5e8aec20---4</link>
            <guid isPermaLink="false">https://medium.com/p/c5f70b708b82</guid>
            <dc:creator><![CDATA[Scott Price]]></dc:creator>
            <pubDate>Sat, 16 Aug 2014 02:25:28 GMT</pubDate>
            <atom:updated>2014-05-06T19:30:15.226Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DYW-NNhSJkIkWco2dr9AOA.jpeg" /></figure><h4>Overcoming the Learning Curve of Doom in a complex product</h4><p>Squarespace offers domain hosting and site design. It’s a beautiful product — and at every step in the engagement the customer is reminded of what their fledgling website could become.</p><p>But underneath compelling features and design options lay a few glaring usability issues threatening to frustrate new users away.</p><h3><strong>Intent</strong></h3><p><em>What pain points are likely to interfere with onboarding?</em></p><p>In selecting users, I screened based on whether they could jump into using a computer readily and were enthusiastic about building a website.</p><p>To create a consistent experience that simulates new user experimentation, I asked participants to complete a series of tasks.</p><ol><li>Select a template</li><li>Change the home page title</li><li>Change the color and font of that title text</li><li>Upload a picture to the home page</li><li>Switch to a new template</li></ol><p>With this list and a Macbook I went out into the world and shared an intimate experience of joy, frustration, success, failure, satisfaction and patience with complete and total strangers. It was pretty cool.</p><h3><strong>Categorizing pain points</strong></h3><p>As imaginable with a complicated product, several issues arose. After combing through notes and Silverback sessions I began sorting them into the bins shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y4_gSVyf8fZr20V286o5fg.jpeg" /><figcaption>categorizing pain points</figcaption></figure><p><strong>This is the typical experience narrative:</strong></p><p>A user rockets through the onboarding flow, selecting (and falling in love with) the beautifully curated templates representing the promise of what their website could be. The feeling of ownership was enough to get them to sign up with their name and email.</p><p>They mostly skipped or ignored the intro video and had some trouble navigating off of it. And then, once in the editor — some picked up on the cues and some didn’t. Those that struggled generally had difficulty understanding what they were editing and how to view these edits. This learning curve yielded frustration with navigation and was met with overzealous browser navigation, which frequently resulted in unintentional log out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iTzPHrZBipTdCeee3m-CAg.jpeg" /><figcaption>flow in which pain points were encountered</figcaption></figure><p>There’s a lot here, and we’re not going to solve it in a single post. But let’s take a look at some focused changes that may make a more cohesive and enjoyable experience as a whole.</p><h3><strong>Defining issues and suggested actions</strong></h3><ol><li><strong>Templates</strong></li></ol><p>The inconsistency <strong>across</strong> templates causes a great deal of confusion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qAo_bIvVPpxunUuuGK1Shg.jpeg" /><figcaption>disorienting template content</figcaption></figure><p>From a first time user perspective, having the navigation populated by specific terms associated with the template but with little or no relevancy to what the pages actually are immediately disorients a user who was just thrown into an editor they’ve never seen before— that beautiful template they fell in love with just moments ago has become a list of names or words that don’t really hold any meaning.</p><p><strong>&gt;What can we try?</strong></p><p>Have new users land in “Preview” mode instead of the editor (this already happens when switching templates). Allow them to begin to dabble with text content in the same framework as they were first exposed to it, creating a sense of familiarity and creating content that will ground them in the Content manager when they get there later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*730htq1A0tnbHunJtyuwag.jpeg" /><figcaption>Fact: puppies decrease user frustration</figcaption></figure><p><strong>2. Navigation</strong></p><p><em>“Where is my website?”</em></p><p>There are too many options — too many places to go and too many places to get lost. These options are represented by an unknown iconography and many of them aren’t going to be useful for some time to come.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RzwyBBrg7dJvUcF_CnLONA.jpeg" /><figcaption>seems reasonable to me</figcaption></figure><p>I can’t run analytics on a site I haven’t made a title for — I can’t sell products when I haven’t uploaded images yet. If we want customers to explore the full functionality and capabilities of our offerings — the editor is not the place for them to learn about it.</p><p><strong>&gt;The lowest hanging fruit</strong></p><p>There is an effort in place already to inform users of what “commerce” ($) is before they can interact with it. This is a great feature to test, however it allows no way to back out other than the “esc” key which inexplicably lands you in preview mode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/734/1*M5VLDCI2CoJ7wQoQYxo_7A.jpeg" /><figcaption>this pop up shows up when someone clicks commerce; but currently the only way out is through</figcaption></figure><p><strong>&gt;What else can we try?</strong></p><p>This is complicated and probably out of scope for an initial usability test. Increasing the clarity of site navigation may help users to avoid pitfalls. A few suggestions on that below.</p><p>The main things to consult here are consistency and expectation — after clicking an icon in the upper left corner to get to perspective mode — should the user now have to find the icon in the lower right to get back to the content manager? Probably not. Should the same icon send the user to two different places to edit content? Probably not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jRsXg7pO2A5WwmNlPkF25g.jpeg" /><figcaption>navigation elements</figcaption></figure><p><strong>3.</strong> <strong>Help</strong></p><p><em>“theme…theme, theme…..”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*y53Pf0sKT-VPphuiXoM9EQ.jpeg" /><figcaption>current search outcome</figcaption></figure><p>The most painful experience I witnessed was watching someone trying to swap out their template, and despite hovering over “Templates” once or twice and eventually resorting to the FAQ, ultimately not being able to. Because the word they kept repeating under their breath was ‘theme”. The expectation of certain words based on other brands in the space should be anticipated, especially in the help.</p><p><strong>&gt; What can we try?</strong></p><p>Create a thesaurus of terms so that people who have used other products can apply previous mental models and still find aid in the supporting documentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H_O8GwnpjgJOM9r828bqww.jpeg" /><figcaption>a simple and a more complex outcome of smarter search</figcaption></figure><p><strong>4</strong>. <strong>Keep Helping</strong></p><p>Occasionally, I’d look down at my notes, and look up to see a shrugging (or cursing) participant that had just been ejected back to the login screen. When it happened, and it did happen, it happened fast. What had they done? Resorted to browser navigation. Sometimes the back button brought the standard “Do you want to save your changes?” But it wasn’t always there, and it wasn’t always a successful safety net.</p><p>This is a sophisticated product, with an engaging and purposefully thought out flow. The user should not be using browser navigation to go anywhere. If they do resort to it, it is a sign of frustration. It is an error. And should be treated as such with an error message. And, in this, lies opportunity.</p><p><strong>&gt; What can we try?</strong></p><p>If a user starts using the browser navigation, send an error message with navigation clues or an invitation to search the FAQ or connect with support staff. This shouldn’t be overdone, but it may provide an opportunity to reach out to frustrated customers or to learn more about particularly confusing navigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Xp95P5cvn2biAgtTwCjuFw.jpeg" /><figcaption>specific and constrained user outreach</figcaption></figure><p>The messages would need to be specific and constrained. It definitely is a sensitive process but there is a lot to be gained by being able to identify a struggling user and ship them some timely help.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wYDP5E1Zysj_bHgJtoib7g.jpeg" /><figcaption>finding a balance between extremes</figcaption></figure><blockquote>There is a lot to be gained by helping a struggling user. — <a href="http://ctt.ec/689Un"><strong>Tweet this</strong></a></blockquote><h4>Next steps:</h4><p>These are suggestions based on observation. Their intent is to increase the joy of use of a complex and elegant product; a product seeking to solve the very challenging problem of simplifying website construction and management for non-technical users. These suggestions are put forth unsolicited, in an effort to create value for users and for Squarespace.</p><p>The next steps will always be to</p><ol><li>Test</li><li>Iterate</li><li>And do it all again</li></ol><p><em>I am not affiliated with Squarespace.</em></p><p><em>Shipping UX projects under Kate Rutter and Laura Klein @Tradecraft until July… happy to be here; happy to hear from you.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5f70b708b82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Key and Lock]]></title>
            <link>https://medium.com/@anthonypalicea/key-and-lock-edcb8ac7fa77?source=rss----735f5e8aec20---4</link>
            <guid isPermaLink="false">https://medium.com/p/edcb8ac7fa77</guid>
            <dc:creator><![CDATA[Anthony P. Alicea]]></dc:creator>
            <pubDate>Fri, 14 Mar 2014 14:09:30 GMT</pubDate>
            <atom:updated>2014-03-16T19:14:47.500Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*DvJIP5fHths8EQD2eB7GfQ.jpeg" /></figure><h4>Learn from interfaces that have endured</h4><p>In his seminal work <a href="http://www.amazon.com/gp/product/B00E257T6C/ref=as_li_ss_tl?ie=UTF8&amp;camp=1789&amp;creative=390957&amp;creativeASIN=B00E257T6C&amp;linkCode=as2&amp;tag=preneer-20%22%3EThe%20Design%20of%20Everyday%20Things:%20Revised%20and%20Expanded%20Edition%3C/a%3E%3Cimg%20src=%22http://ir-na.amazon-adsystem.com/e/ir?t=preneer-20&amp;l=as2&amp;o=1&amp;a=B00E257T6C">The Design of Everyday Things</a> (newly revised in 2013), Don Norman notes that with every new technology designers repeat the same mistakes of the past.</p><p>User experience designers should not fall into this trap, because a fundamental key to good UX design is <em>humility</em>. It takes humility to change a design based on user testing; and it takes humility to look back at technologies of the past that have endured, and show them their due respect.</p><p>One of the oldest and best interfaces has endured for thousands of years. The two part interface: key and lock. Let’s pull some software lessons from before there was software.</p><h4>Guessability</h4><p>The key and lock is <em>guessable</em>. Most doors have only one keyhole. The key looks like it fits in the hole. If you handed someone a key, and pointed them at its corresponding door, they would likely guess what to do even if they’d never done it before.</p><p>Both the key and lock follow <a href="https://medium.com/guessable-design/97c15f990dfe">DOTW (Do One Thing Well)</a> and it is hard for a user to get it wrong.</p><blockquote><strong>Make your interfaces <em>guessable </em>by minimizing ways to get it wrong. Reduce the number of elements in each interface, drawing a clear path to completing any given task.</strong></blockquote><h4>Security</h4><p>The key and lock’s primary purpose is security. Yet no one complains about it, because it works well and is not hard to use.</p><p>You must have the right key, and only the right key for the door to open. It takes special skill to open a door without the key, but no skill to open it otherwise.</p><blockquote><strong><em>Security </em>is important. It should keep things safe. It should just work. It should be trustworthy. Yet when you are authorized, security shouldn’t be an impediment to use.</strong></blockquote><blockquote><strong>Don’t think ‘difficult to do’ is a valid security paradigm. The people who break security won’t be impeded, just your users. Implement good security practices, but simple UI.</strong></blockquote><h4>Notifications</h4><p>One reason for the endurance of key and lock is not commonly considered. The key/lock paradigm provides user notifications. Attempts to tamper with a lock invariably leave evidence, like scratches for example.</p><blockquote><strong>Users value clear <em>notifications</em>, in security and all other actions. A good notification system can make the emotional difference between feeling cared for, and feeling uncertain and alone.</strong></blockquote><h4>Consistency</h4><p>Although generally one key fits in one door, using one key and lock teaches you how to use all of them. No matter the material, appearance, size, country, or epoch, key and lock pretty much works the same way.</p><blockquote><strong><em>Consistency </em>isn’t necessarily the most important element of UX. Clarity is arguably more important (consistently confusing isn’t good). However, there is value making certain elements of your UI consistent. Navigation, save/cancel, and error messages for example. A consistent interface makes the user feel like they have a chance of learning it.</strong></blockquote><h4>Feedback</h4><p>Key and lock provides instantaneous feedback. Usually the wrong key won’t even fit into the lock. If it does fit, the lock won’t turn. Although its annoying to run through a ring of keys looking for the right one, consider how quickly you are actually able to do it. That’s because of good feedback.</p><blockquote><strong><em>Feedback </em>is vitally important to any interface design. <em>Any and every action must have a clear, unambiguous, unmissable reaction. </em>Change your button’s text and disable it once it’s clicked, notify that the form saved properly, explain that an error happened and what to do to fix it. Provide good feedback.</strong></blockquote><h4>Useful Abstractions</h4><p>Few people truly know how the tumblers in a lock work, and fewer still could design them. Yet the key abstracts the user away from the inner workings of the lock, allowing them to focus on the task (opening or locking the door) rather than how the tool helps them accomplish it.</p><blockquote><strong>Software interface design is the act of building <em>abstractions</em>. We abstract the user from the inner workings, on the web for example, of HTTP, HTML, CSS, Javascript, and whatever server-side code involved.</strong></blockquote><blockquote><strong>No matter how hard you worked on your code, don’t let your ego or frustration leak those complexities into the interface; the user won’t understand them anyway.</strong></blockquote><blockquote><strong>Want recognition? Do a really, really good job of hiding all that thought and work; make a simple interface to all that complexity, and your users will thank you.</strong></blockquote><p>Interfaces that have endured for centuries have done so for a reason, because they rely on UX truths that work no matter what the technology.</p><p>Guessability, security, notification, consistency, feedback, and good abstractions are something that every interface (physical, software, or otherwise) should share.</p><p>Stay humble in your designs. Seek knowledge from interfaces that have endured the test of time. Build something that people will be happy to use, and you’ll be happy building it.</p><p>This article is an extension of the original UX Tumblr post here: <a href="http://goodinterfacebadinterface.tumblr.com/post/78244120499/the-key-and-lock-is-one-of-the-oldest-and-best">Good Interface, Bad Interface</a>, and reposted from <a href="http://www.anthonypalicea.com/post/key-and-lock">my blog</a>.</p><p>(if you like, follow me on <a href="https://twitter.com/anthonypalicea">Twitter</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edcb8ac7fa77" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why (Your) Personas Don’t Work (For You)]]></title>
            <link>https://avalot.medium.com/why-your-personas-dont-work-for-you-75c1abfcec94?source=rss----735f5e8aec20---4</link>
            <guid isPermaLink="false">https://medium.com/p/75c1abfcec94</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[personas]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <dc:creator><![CDATA[Antoine Valot]]></dc:creator>
            <pubDate>Mon, 08 Aug 2016 11:31:27 GMT</pubDate>
            <atom:updated>2016-08-08T11:32:24.269Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U-oUZx83g_7VpdlV37fkEA.png" /></figure><h4>And how to make them work (for you).</h4><p>There’s been a lot of articles and comments, <a href="https://medium.com/down-the-rabbit-hole/aa72d3cf6c69">here on Medium</a> and in <a href="https://signalvnoise.com/posts/690-ask-37signals-personas">other</a> <a href="http://www.uxmatters.com/mt/archives/2013/01/are-personas-still-relevant-to-ux-strategy.php">places</a>, about how horrible and terrible Personas are for software development. These articles are usually thoughtful and based on the real-life experience of their intelligent, successful authors. They all prove one thing very convincingly:</p><blockquote>They don’t really know what they’re talking about.</blockquote><p>What these people write about is completely missing the point of <a href="http://en.wikipedia.org/wiki/Alan_Cooper">Alan Cooper</a>’s simple and radical process of <strong>identifying a Primary Persona and its Goals</strong>… and then, after mis-applying the least important part of the process, they did not magically become better designers.</p><blockquote>You should not critique something you didn’t read.</blockquote><p>Alan Cooper’s books, <a href="http://www.amazon.com/Inmates-Are-Running-Asylum-Products/dp/0672326140/ref=la_B001IGLP7M_1_2?s=books&amp;ie=UTF8&amp;qid=1399737061&amp;sr=1-2">The Inmates Are Running The Asylum</a>, and <a href="http://www.amazon.com/About-Face-Essentials-Interaction-Design/dp/0470084111/">About Face</a>, explain quite clearly what the User-Centered Design process rests on. Personas are not the most important or central part of it. Here’s what Alan says, that matters:</p><h4>Observe the users</h4><p>Not “listen to” or “ask” or “survey” or, heavens forbid, “focus-group.” The verb is observe.</p><h4>Design for one user only</h4><p>Personas come in at this point, but the point is to identify the Primary Persona: The one that needs the system, and can’t make do with a UI designed for another persona.</p><h4>Design for user goals, not tasks</h4><p>That is the most important part of Cooper’s methodology: User Goals. You do the research to find out the truth about user goals. You write up a primary persona in order to contextualize and communicate these goals.</p><p>The point is that we need to design for the goals of the one user that matters most.</p><p>What are the three signs that you don’t understand Cooper’s process?</p><ol><li>You talk about “Personas” without having done ethnographic research. Personas you came up with, or that your client came up with, are not personas. They are just a mashup of a few people’s assumptions and prejudices. Calling guesses “personas” doesn’t make them so.</li><li>You talk about “Personas” without mentioning goals. Personas and Goals without goals are like a combustion engine without the engine: Just a lot of hot air and ashes.</li><li>You talk about “Personas” in the plural, without mentioning a primary persona. If you’re still designing your UX for multiple user types, calling them Personas won’t change the fact that they are, in effect, a design committee <em>in absentia</em>. Design by committee is bound to fail.</li></ol><p>If you’ve read and applied Cooper’s methodology, as instructed, without shortcuts or reverting to assumptions, and it failed to deliver results, then I’d love to hear about it. My main question is this:</p><blockquote>What client was smart and progressive enough to let you do the full, uncompromising UCD process? Can you thank them for me?</blockquote><p>The reality is that Cooper’s process is radical. It flies in the face of common sense in multiple, important ways, and it’s rare that you can convince a client to go along with such a counter-intuitive set of instructions.</p><p>To do UCD, I have to start by telling my client they don’t understand their market. They’ve been at it for years, I just walked into their office, and I’m telling them they don’t know what matters.</p><p>Then I have to get them to pay for a few weeks of flying me around to sit in their customers’ offices or homes, asking questions and looking over their shoulders. And then I will purposefully ignore most of their user groups while designing the product, and only aim to please some of them.</p><p>Most managers can’t stomach that. Most can’t deal with the hit to the ego that new customer insights can mean. Most can’t figure out how to accept the “designing for one user” principle. If they make you compromise (and in most cases, you should be ready to compromise or <a href="https://medium.com/life-tips/3957aa1cd89f">lose that client</a>), then don’t blame the methodology you did not really follow when problems crop up.</p><p>That’s another way you’ll know you didn’t do UCD right: If you didn’t have to fight some layer of management, you were just doing the same old.</p><p>So, fine, you can have your “Personas don’t work” mantra, but I’ll hold fast to mine:</p><blockquote>“Designing just for the Primary Persona’s Goals is hard,<br>but it works like a badass mofo.” <a href="http://ctt.ec/bB1sf">Tweet this</a></blockquote><p>It’s served me and my clients well.</p><p><em>Did you enjoy this rant? Did you not? Please leave a comment, let’s have ourselves a good argument!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75c1abfcec94" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>