<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Bokardo</title>
	<atom:link href="http://bokardo.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://bokardo.com</link>
	<description>Interface Design &#38; UX by Joshua Porter</description>
	<lastBuildDate>Sun, 29 Jan 2012 11:35:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Designing for the Next Step</title>
		<link>http://bokardo.com/archives/designing-for-the-next-step/</link>
		<comments>http://bokardo.com/archives/designing-for-the-next-step/#comments</comments>
		<pubDate>Mon, 16 Jan 2012 14:33:25 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[copywriting]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[Make them Care]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=2041</guid>
		<description><![CDATA[Note: this is an excerpt from my forthcoming book Make them Care! In a recent post (Why you should bury the sign up button) I told the story of a redesign I did in which people just didn&#8217;t want to click the &#8220;sign up&#8221; button on the home page, no matter how beautiful or sexy [...]]]></description>
			<content:encoded><![CDATA[<div class="note">
<p><strong>Note:</strong> this is an excerpt from my forthcoming book <a href="http://oneflightbooks.com" title="A book about product marketing and design">Make them Care!</a></p>
</div>
<p>In a recent post (<a href="http://bokardo.com/archives/why-you-should-bury-your-sign-up-button/">Why you should bury the sign up button</a>) I told the story of a redesign I did in which people just didn&#8217;t want to click the &#8220;sign up&#8221; button on the home page, no matter how beautiful or sexy that sign up button was. What I realized from that project is that there are cases in which no amount of visual design will significantly improve the state of things&#8230;instead we need to focus on making people <em>care</em>.  </p>
<p>Here&#8217;s another example. On cyber Monday this past November I received an email from the New York Times informing me that I could save 50% on a Times Digital Subscription. It was time sensitive…offered today only, so I had to act fast in order to take advantage. While I don&#8217;t read many emails like this, I did read this email because I think the New York Times is one of the better news outlets out there (although <a href="http://publiceditor.blogs.nytimes.com/2012/01/12/should-the-times-be-a-truth-vigilante/">now I&#8217;m not so sure</a>) and I have an iPad that I enjoy reading on. Perhaps the Times had something interesting here, so I kept reading. Here&#8217;s the email: </p>
<p><a href="http://www.flickr.com/photos/bokardo/6707539601/" title="New York Times email offer by bokardo, on Flickr"><img src="http://farm8.staticflickr.com/7005/6707539601_bcedb12c9d.jpg" width="474" height="500" alt="New York Times email offer"/></a></p>
<p>I ask you to notice several things about this: </p>
<ol>
<li><strong>It&#8217;s an offer about money.</strong> The primary content of this email is about the savings one would get for taking advantage of this offer. &#8220;Save 50%&#8221; is the first text you read and the most visually heavy content on the page. Variants of the message of &#8220;saving&#8221; are repeated throughout the email. The number one message this email communicates is that I can get a very good financial deal here.</li>
<li><strong>The email assumes the value of the offer is already known.</strong> There is almost no information at all about what a digital subscription from the New York Times is. The only clue are the few words in this sentence: &#8220;Award-winning articles, videos, blogs, and more &#8211; it&#8217;s all wrapped up in a perfect package…&#8221;. That is the only description of what one would actually get with this offer.</li>
<li><strong>I have to make up my mind immediately.</strong> The only call-to-action on this page is &#8220;Get it Now&#8221;. Clearly this is designed for people who already know they want a digital subscription, or have decided to get one after reading this email. People who click that button are people who have made up their mind&#8230;who have already decided that now they want to get it. </li>
</ol>
<p>Well, even though I&#8217;ve read the Times online for years I have no idea what a &#8220;digital subscription&#8221; is. I can already read the Times on my computer, my tablet, and my smartphone (I simply visit <a href="http://nytimes.com">nytimes.com</a> or the <a href="http://www.nytimes.com/skimmer/#/Top+News/">nice Skimmer app</a>), so I&#8217;m already receiving the Times &#8220;digitally&#8221;. What exactly is different about a digital subscription? The only thing I know about it is that I&#8217;m not currently paying for the Times but with a subscription I would have to…but I have absolutely no idea what I would get by doing that! </p>
<h2>A Straight-forward Fix</h2>
<p>The design solution to this is relatively straight-forward. </p>
<p>The first piece of missing information is my current status as a New York Times reader. Tell me what I&#8217;m currently getting by stating it plainly. Say something like: &#8220;You currently enjoy the free Times online edition, which includes loads of free content, including top news, sports, and political news&#8221;. This could be in pretty good depth, too. Reiterate the amazing breadth of content that the Times offers for free online…and perhaps showcase one or two amazing stories of late. It&#8217;s easy to assume that readers/users/people know their current status but in many cases they will not. </p>
<p>The second piece of missing information is the difference between where I&#8217;m currently at and where I could be…what exactly is being offered here? Explain what is included in the digital subscription. What additional content, commentary, and news is delivered if one were to subscribe? Is there a different delivery mechanism or app I would use on my various devices? How are they better? And don&#8217;t be generic here…&#8221;videos&#8221; and &#8220;blogs&#8221; are not compelling features of a digital subscription! I&#8217;ve got those in spades, baby. Show me…dive deep into the details about how this experience is superior to the one I currently have. The design problem here is to answer the question of what makes the Times videos and blogs different and better. </p>
<p>Remember that comparison is how people make decisions. The email the Times sent does not allow me to make the comparison they need me to. By sending an email with merely an offer to pay money the only comparison I can make is between not spending money and spending money…think about that for a second! I think we all know which one will be chosen. Choosing to not spend money is the rational choice here. So give people something to compare! Show the comparison between these two sets of information side-by-side and let people compare what they&#8217;re getting with what they could get. Paint a beautiful future for them! Never assume that people know anything about an offer…and strive hard to clearly communicate that comparison every single time you make the offer. </p>
<p>The Times email problem and the sign up problem from my last piece are similar. The designer(s) are trying to compress a process that takes time into an immediate decision with little information. In both cases the conversion rate is going to be low…very low…I would bet dollars to doughnuts the Times was not overwhelmed with the success of their Cyber Monday email campaign. </p>
<h2>Designing for the Next Step</h2>
<p>I call these design failures a failure to <em>&#8220;Design for the Next Step&#8221;</em>. When designs fail to provide an appropriate next step for users it stops them in their tracks. They simply click away to another web site, stop using an app, or otherwise leave. </p>
<p>So let&#8217;s dive into this fundamental problem of interaction design. It is easiest to start by putting the problem in context. <a href="http://bokardo.com/archives/designing-for-the-social-web-the-usage-lifecycle/">The Usage Lifecycle</a> shows the progression someone makes as they use your software over time. From a practical standpoint most people go through stages as they learn about, try out, make the decision to use, and continue to use your software. </p>
<p>Here is an example of what the Usage Lifecycle looks like: </p>
<p><img src="http://bokardo.com/img/usage-lifecycle.gif" alt="Usage Lifecycle" /></p>
<p>We can also dive down a level deeper and look at a stage in more detail. Here is how we might find the &#8220;Interested&#8221; stage of the Usage Lifecycle: </p>
<p><img src="http://bokardo.com/img/usage-lifecycle-breakdown.gif" alt="Interested stage of the Usage Lifecycle" /></p>
<p>These steps are stable for most software. When we fail to design for the next step, we break this progression in some way. Most designs suffer from one of the following ways to blunder:  </p>
<ul>
<li><strong>Moving too fast through steps.</strong> When you give people too little information and ask them to continue to the next step anyway. You&#8217;re asking them to move too quickly through a process that takes time. This happens a LOT, and usually results from a lack of context given by the designer. Too little explanation, too many competing screen elements, not enough examples or supporting content, all of these things contribute.</li>
<li><strong>Skipping a step.</strong> When you completely skip an important step. This usually happens early on in design…you simply don&#8217;t make it very far if you&#8217;ve skipped a step as your usage plummets. </li>
<li><strong>Steps out of order.</strong> Asking for billing information before showing shipping rates on e-commerce sites is a common example. This tends to stop people in their tracks, as people want to know what they&#8217;re going to pay before they enter their billing information. This is exacerbated because shipping costs are often higher than expected.  This is common in  app design as well. Using templates is an interesting example…sometimes you choose a template before creating a thing and sometimes you want to create the thing first. I&#8217;ve seen both ways make sense, depending on the object in question.</li>
<li><strong>Showing a step too early.</strong> Timing is important, too. Take pricing, for example. Pricing is a signal, and if your pricing is relatively high it is easy to dissuade people from buying if you show them prices before you&#8217;ve convinced them of the value of your product. Another example is asking people to share your app with friends upon initial entry…while you may get some activity from happy clickers, you are asking your users to share something they are not yet familiar with. This will not only frustrate them but also stop some of them in their tracks. Better to share when appropriate, after they&#8217;ve had success with the software. </li>
<li><strong>Automating a step while taking control away from users.</strong> In general, software and hardware is an augmentation of human thinking and action, so automating tasks is usually very helpful. But in recent years we&#8217;ve seen software go way overboard. Sites that tweet for you without your permission. Apps that auto-friend you with others. The crucial aspect is control. If you do something for someone while keeping them in control you are usually good. Do something for someone and take away their control of it and you will have problems.</li>
<li><strong>Inappropriate next step.</strong> Or the next step might just be inappropriate, the wrong next step. This often happens when designers try to leverage some other action you take with what their ultimate goal is…when their priorities are not aligned with yours. </li>
</ul>
<p>For every interaction you design, think about why it&#8217;s not working in relation to these questions. Are you moving too fast? (likely) Did you display the steps out of order? Is the next step appropriate?</p>
<h2>Three Pieces of the Next Step Puzzle</h2>
<p>So how do we design for the next step? Well, every design situation is different and will require a different design. But in general there are three things we have to get right. Clearly communicating the current step, the next step, and how to get from here to there. </p>
<ol>
<li><strong>Clearly communicate the current step.</strong> As I explained above, the NyTimes were not fully supporting the current step I was on as a reader of the New York Times. They did not clearly communicate to me my current status, so their promise of a better status didn&#8217;t make much sense. This often feels like a recapitulation of the obvious…I&#8217;ve heard designers say &#8220;Why would I tell people something they already know?&#8221;. Fight this tendency! It&#8217;s always better to be clear about agreed-upon status than assume people know something.</li>
<li><strong>Clearly communicate the next step.</strong> The Times also failed to communicate the value of becoming a digital subscriber. This is a classic problem of not addressing real customer needs. The needs of NyTimes customers is to get better news than they&#8217;re already getting (to be better informed)&#8230;not to take advantage of an offer! So the task is to clearly communicate the future in which one is a digital subscriber and is better informed than they currently are now.
<p>If the Times had successfully communicated both the current and the next step, they would have allowed people to compare the two against each other and make a real decision. </li>
<li><strong>Clearly communicate how to get there.</strong> The Times did this well. They clearly communicated the offer and how to take advantage of it. The call to action was clear. Unfortunately, the Times didn&#8217;t satisfy the other two requirements so the offer fell flat for anybody except those who already decided to take advantage of it. </li>
</ol>
<p>Designing for the next step is a fundamental problem of interaction design. Almost every screen we design, be it in an app or marketing website, can be improved by really focusing on the steps and sequences of steps a user goes through. In our haste we often speed up the process too much, get steps out of order, fail to present an appropriate next step, or otherwise break the sequence. By re-assessing your app or site in light of these potential errors, you can discover the sequence and timing that your users need to successfully make it to the next step.</p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/designing-for-the-next-step/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Design is not Horsepoop</title>
		<link>http://bokardo.com/archives/design-is-not-horsepoop/</link>
		<comments>http://bokardo.com/archives/design-is-not-horsepoop/#comments</comments>
		<pubDate>Sat, 17 Dec 2011 12:37:49 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=2030</guid>
		<description><![CDATA[In his impassioned piece Design is Horseshit, YongFook suggests that the increased focus on designers as founders is misguided because design isn&#8217;t what makes most startups successful. In my recent post The Golden Age of Design in Startups I was bullish on designers as founders, so I&#8217;m here to call bullshit on Yongfook calling bullshit…or [...]]]></description>
			<content:encoded><![CDATA[<p>In his impassioned piece <a href="http://yongfook.com/post/14295124427/design-is-horseshit">Design is Horseshit</a>, <a href="http://twitter.com/#!/yongfook">YongFook</a> suggests that the increased focus on designers as founders is misguided because design isn&#8217;t what makes most startups successful. </p>
<p>In my recent post <a href="http://bokardo.com/archives/the-golden-age-of-design-in-startups/">The Golden Age of Design in Startups</a> I was bullish on designers as founders, so I&#8217;m here to call bullshit on Yongfook calling bullshit…or something like that. (actually, the idea of &#8220;calling bullshit&#8221; seems silly to me…why not just respectfully debate a point?)  </p>
<p>Yongfook&#8217;s argument is that design is not the reason why startups are successful. He suggests that startups are successful when they &#8220;create value&#8221; and in his view &#8220;Design enhances value, it does not create it.&#8221;. </p>
<p>It depends, of course, on your definition of design. </p>
<p>Implicit in Yongfook&#8217;s argument is <em>his</em> definition of design. He is equating design with <em>making something look good</em>. This is clear from his thesis: </p>
<blockquote><p>&#8220;Stop creating shitty startups that look amazing. A product or service that is indispensably useful yet looks like ass is infinitely more likely to be successful than a product that solves zero problems but looks like a work of art. Stop this cycle of creating beautiful novelties, getting your 15 minutes, then disappearing. Create value.&#8221; </p></blockquote>
<p>&#8220;Look amazing&#8221;, &#8220;looks like ass&#8221;, &#8220;looks like a work of art&#8221;, &#8220;beautiful novelties&#8221;. Each of these terms is about &#8220;looking good&#8221;. So if you agree that design is the act of making something look good, then you&#8217;ll undoubtedly agree with Yongfook&#8217;s piece. </p>
<p>I hear this notion of design every day. Many people seek out design help because they can&#8217;t make something look good on their own…they just haven&#8217;t had practice doing that. But designers secretly know that their role is much more than just making something look good…it&#8217;s solving the right problem and communicating the right message. </p>
<p>And this goes for startups as well. For some reason, Yongfook wants to separate &#8220;value creation&#8221; from &#8220;design&#8221;. But that&#8217;s hard to do&#8230;as design is in part the process of discovering problems and then conceiving of solutions to them. The idea that a founder would go out and &#8220;create value&#8221; without actually designing something along the way doesn&#8217;t make much sense&#8230;in solving the problem they would end up designing something, even if it only be conceptual design of a proposed product. (if they&#8217;re not conceiving of something new then they probably don&#8217;t have a business anyway)</p>
<p>In short, Yongfook&#8217;s dismissal of design as decoration is a long-standing, myopic view of the field. This is not just my opinion. Steve Jobs, in an <a href="http://www.wired.com/gadgets/mac/commentary/cultofmac/2006/10/71956?currentPage=all">interview about the iconic design of the iPod</a>, addresses this notion of design directly:  </p>
<blockquote><p>“Most people make the mistake of thinking design is what it looks like. That’s not what we think design is. It’s not just what it looks like and feels like. Design is how it works.”</p></blockquote>
<p>If you agree with the idea that design is how something works, then you won&#8217;t agree with Yongfook&#8217;s post. Instead, you might insist that learning about what problem to solve in the first place (which Yongfook is adamant about and which I agree with) is actually the first step of design. You cannot create a successful product without first understanding the problem you&#8217;re solving. </p>
<p>Founders who talk to customers are not black swans. There are people who do this all the time&#8230;.UX people in general continually interview, survey, and test with users to make sure that core problems are being addressed and solved. (as much as I&#8217;m a fanboy of Blank and Ries they were not the first people to get out of the office and talk to customers) In a startup you might not have a UX person at the beginning&#8230;but I would recommend hiring one sooner rather than later. Startups who do customer research would benefit greatly from having a UX-minded designer on the team. </p>
<p>Yongfook also separates design from usefulness, suggesting that something can be completely useless but extremely well-designed (and vice-versa). Any designer worth their salt would disagree with this separation and would align usefulness with design success, dismissing the notion that you can have one without the other. They would argue that design only succeeds when people find a product useful, when they adopt it as part of their lives. </p>
<p>The act of design isn&#8217;t reserved for those with the word &#8220;designer&#8221; in their job title. Design is a universal activity that we all participate in&#8230;and it&#8217;s much more than making something look pretty. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/design-is-not-horsepoop/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More on Burying the Sign Up Button</title>
		<link>http://bokardo.com/archives/more-on-burying-the-sign-up-button/</link>
		<comments>http://bokardo.com/archives/more-on-burying-the-sign-up-button/#comments</comments>
		<pubDate>Wed, 07 Dec 2011 16:49:06 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[copywriting]]></category>
		<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[microcopy]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=2023</guid>
		<description><![CDATA[A couple weeks ago I published Why You Should Bury your Sign Up Button and got some really interesting feedback and comments from folks. One of the more interesting bits was a follow-up post by the folks at Zurb who had experienced the exact same phenomenon&#8230;when they took away the &#8220;sign up&#8221; button and instead [...]]]></description>
			<content:encoded><![CDATA[<p>A couple weeks ago I published <a href="http://bokardo.com/archives/why-you-should-bury-your-sign-up-button/">Why You Should Bury your Sign Up Button</a> and got some really interesting feedback and comments from folks. One of the more interesting bits was a follow-up post by the folks at Zurb who had experienced the exact same phenomenon&#8230;when they took away the &#8220;sign up&#8221; button and instead put a &#8220;learn more&#8221; button at the bottom of the page they got a 350% increase in sign ups: <a href="http://www.zurb.com/article/816/why-burying-sign-up-buttons-helps-get-mor">Why Burying Sign Up Buttons Helps Get More Sign Ups</a></p>
<p>Think about how counter-intuitive that is at first glance. You <em>take away</em> the call-to-action that says &#8220;sign up&#8221; and you get <em>more</em> sign ups. But actually it&#8217;s just focusing on what people really want, in the order that they want it, where they happen to be in the <a href="http://bokardo.com/archives/designing-for-the-social-web-the-usage-lifecycle/">usage lifecycle</a>. They want to find out about what you&#8217;re offering first, figure out if it makes sense for them, and <em>then</em> sign up. It&#8217;s a <em>process</em>. Too often we treat a landing page like an immediate decision.  </p>
<p>Cue the analogies to dating and relationships. When you first meet someone you don&#8217;t usually ask them to get into a full-blown relationship (even if that&#8217;s your goal). No, you want to get to know them a little, see what they&#8217;re about, see if they like <a href="http://www.imdb.com/title/tt0087277/">Footloose</a>, and see if you&#8217;re compatible. You want to know that they&#8217;re not crazy or an axe murderer. </p>
<p>Relationships take time, no matter what kind they are. So the next time you are designing a call-to-action, first make it crystal clear but then go beyond clarity and ask: &#8220;Is this the most appropriate time to ask this?&#8221;. Too often timing considerations get lost in our rush to get calls-to-action in front of people. </p>
<p>So yes, <em>timing</em>. In the same way someone would never say &#8220;Hi, I&#8217;m Josh. Do you want to move in together?&#8221; we should be <em>time-appropriate</em> with our design. There is a right time for every message. If I was a religious man I would be quoting Ecclesiastes right now, but I&#8217;ll <a href="http://www.classbrain.com/artmovies/publish/Footloose_atimetodance.shtml">let Ren McCormack do it</a> instead. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/more-on-burying-the-sign-up-button/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Golden Age of Design in Startups</title>
		<link>http://bokardo.com/archives/the-golden-age-of-design-in-startups/</link>
		<comments>http://bokardo.com/archives/the-golden-age-of-design-in-startups/#comments</comments>
		<pubDate>Mon, 05 Dec 2011 10:59:09 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Conferences]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Facebook]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=2007</guid>
		<description><![CDATA[I just returned from Dave McClure&#8217;s excellent Warm Gun Conference, and I haven&#8217;t been this excited to be a designer in a while. The entire event was about design, metrics, and products, and even more importantly the people at the conference were many of the who&#8217;s who in Bay Area design. From what I saw [...]]]></description>
			<content:encoded><![CDATA[<p>I just returned from Dave McClure&#8217;s excellent <a href="http://warmgun.com">Warm Gun Conference</a>, and I haven&#8217;t been this excited to be a designer in a while. The entire event was about design, metrics, and products, and even more importantly the people at the conference were many of the who&#8217;s who in Bay Area design. From what I saw and experienced there I daresay there are signs we&#8217;re entering a golden age of Design. </p>
<p>The evidence: </p>
<p><strong>1. The startups being invested in are designer-led.</strong> Take the new <a href="http://designerfund.com/">Designer Fund</a> that funds startups with designer-founders and helps mentor them. Consider the companies in the banner of their site: YouTube, Tumblr, Android, Slideshare, Feedburner, Flickr, Vimeo, Path, Airbnb&#8230;all founded by designers. I think we&#8217;ll see this continue to be the case. User experience is a huge differentiator in startups right now, with startups like Typekit, Instagram, Lovely, Oink, and others getting investment and doing well. </p>
<p><strong>2. Hot startups want designer co-founders.</strong> I talked with many people who were building startups and their top priority was getting great designers on board. But they didn&#8217;t just want good designers. They wanted <em>designer co-founders</em>, people who could help them from day 1 and be invested in the company. This is a change from the ever-present search for technical co-founders&#8230;designer co-founders are in demand as well. </p>
<p>This makes sense. In a sea of competition…the survivors will be the ones who can communicate most clearly and provide value most quickly. And who specializes in those things more than designers?</p>
<p><strong>3. Startups are being bought for their design talent.</strong> While I was traveling I heard news that <a href="http://blog.gowalla.com/post/13782997303/gowalla-going-to-facebook">Facebook acquired Gowalla</a> and I had to smile. This is an obvious design talent acquisition…Gowalla has one of the most talented groups of designers around and while their service was successful, it was seen to have lost to Foursquare and was looking to reinvent itself. Now, it doesn&#8217;t have to…I&#8217;m sure Facebook has a large roadmap (apparently they&#8217;ll be working on the timeline team) that Josh Williams and company can start designing toward. Couple this with Facebook&#8217;s acquisition of <a href="http://techcrunch.com/2011/06/09/facebook-sofa/">Push Pop Press</a>, <a href="http://mashable.com/2011/06/10/facebook-sofa/">Sofa</a>, and <a href="http://allthingsd.com/20110427/facebook-acqhires-feltron-infographic-creators-company-video-interview/">Daytum</a>, and you see a clear trend here…they&#8217;re pulling in as much design talent as they can. </p>
<p>This also jibes with what I heard from other bay-area startups. I&#8217;ve talked to friends at both Twitter and Zynga and the message is the same…they are 100% focused on design and investing heavily in it (and have been for a couple years now). I&#8217;ve even been asked if I know world-class design teams or agencies who want something new…not because these companies want to work with them but because they want to BUY them…because <em>they can&#8217;t get design talent fast enough by recruiting individuals</em>. Seriously.  </p>
<p>I also met the design recruiter for Groupon who said that they can&#8217;t get enough designers. He was currently fighting against a bit of public pushback b/c of the IPO filing but in general had an amazing growth engine with which to recruit. He could be as aggressive as he wanted in getting designers. </p>
<p>So I&#8217;m not sure what the precursor to all of this was&#8230;perhaps Apple&#8217;s rise to the most valuable tech company in the world on the back of well-designed products? Or maybe the rise of the social networks like Twitter and Facebook who now are poised to be the primary point of communication for the next decade? I don&#8217;t know, but those events probably helped. I also think repeated failure of poorly-designed products must be a part of this&#8230;we&#8217;ve all had those projects in which we knew the design just wasn&#8217;t there and hurt over time. I think most people by now have had an experience like this and want to do anything they can to prevent it from happening again. </p>
<p>All of this holds true for us at <a href="http://www.hubspot.com">HubSpot</a> as well&#8230;we&#8217;re investing heavily in design and front-end engineering for the foreseeable future. We&#8217;ve got a ton of projects in the pipeline, and to build the world-class software we want we&#8217;re going to need thousands of hours of design work to get there. While our events on the East Coast aren&#8217;t quite as big as those in the Valley (yet), our people aren&#8217;t lacking in passion for design.</p>
<p>I remember not too many years ago that designers lamented of not having a &#8220;seat at the table&#8221;. Well, folks, your time has come. Not only do you have a seat at the table…you&#8217;ve got a starring role. There is no better time to be a designer than right now. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/the-golden-age-of-design-in-startups/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why you Should Bury your Sign Up Button</title>
		<link>http://bokardo.com/archives/why-you-should-bury-your-sign-up-button/</link>
		<comments>http://bokardo.com/archives/why-you-should-bury-your-sign-up-button/#comments</comments>
		<pubDate>Fri, 21 Oct 2011 14:26:56 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[Make them Care]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=1991</guid>
		<description><![CDATA[A short while ago I was involved in a project redesigning a home page of a website. I dutifully designed the page in the common fashion, using a bold headline, some bullet points, and a juicy call-to-action button. It was very similar to many of the startup home pages that you might run across every [...]]]></description>
			<content:encoded><![CDATA[<p>A short while ago I was involved in a project redesigning a home page of a website. I dutifully designed the page in the common fashion, using a bold headline, some bullet points, and a juicy call-to-action button. It was very similar to many of the startup home pages that you might run across every day. </p>
<p>The goal of the redesign was to increase conversion on the primary call to action of sign-up. We wanted to double or triple (or more) the number of people who were signing up and trying out the product. </p>
<div class="screenshot"><img src="http://bokardo.com/img/sign-up.png" alt=""/></div>
<p>I knew the redesign was a vast improvement over the existing one, merely because the page better communicated what was going on. Instead of a vague headline that wasn&#8217;t communicating value to readers I used a much more descriptive one that helped orient people immediately to have some idea of what the site does. And the button…well let&#8217;s just say that it was so hot it made you want to click it. </p>
<p>So we launched, and then we looked at the data. Uh Oh. No big increase in conversion, certainly not enough to change the business. The conversion rate had improved about 20%, which is OK, but the rate itself was so low to have very little effect on the company&#8217;s bottom line. </p>
<p>What was wrong? Why wasn&#8217;t there a big improvement in conversion? Why was our click-through so low on what was obviously the primary call-to-action?  Didn&#8217;t we follow all of the visual design rules here? Make headline big and bold. Check. Make a bullet list of important points. Check. Make a beautiful, sexy button that looks like it was born to be clicked. Check. </p>
<p>Why then, were people not clicking the sexy button?  </p>
<p>It&#8217;s at this point when you have to step back and ask yourself: what exactly is design? Is design creating something for creation sake? We certainly had done that, and we had already done as much work as is done on most redesign projects. Most projects would have launched and been done…when redesign is the goal the launch is the end. </p>
<p>But that&#8217;s not what passes as good design these days. Good design is design that works. So to honestly assess the redesign I did I had to admit…this design was still not working. </p>
<p>Damn was that hard to admit. Really, really hard to admit. I hated admitting it because it was an admission that I failed. I&#8217;ve not often admitted that on projects in the past that just didn&#8217;t get the usage that I wanted. In so many cases it was easier to say to myself that what I did was better than what was there before and the work of launching was enough. It is so easy to confuse getting stuff done with doing good work. </p>
<p>Yet, this admission also allowed me to see the problem more clearly. Once I accepted that the redesign still wasn&#8217;t working, I created the opportunity to find out why not. See that interesting little trick I pulled there? Failure is an opportunity to problem solve! We all love to problem solve, right?   </p>
<p>So in hindsight the answer is obvious…people weren&#8217;t clicking &#8220;Sign Up&#8221; because they were not ready to. They saw the button and did not care enough to click it. I could have made it flashing big-ass and red, but still nobody would have clicked on it. </p>
<p>No visual design wizardry at this point would have improved things. No matter how much we tweak the call-to-action, we&#8217;re not going to significantly improve click-through on it. We&#8217;re not fighting an attention war here…we have people&#8217;s attention because they&#8217;re on our website. No, we&#8217;re fighting an emotional war. We need to convince people of the value of what we&#8217;re offering enough so they actually care. They are aware that our big-ass honking button is there…how could they not be? We made it impossible to miss! in fact they&#8217;ve read the text on it that says &#8220;Sign-up for Free&#8221;. They can barely get it out of their peripheral vision&#8230;</p>
<p>No, our visitors can see clearly…they&#8217;re not failing to notice the button. And they can read…they can see what the button says. They&#8217;re also not obstinate…they&#8217;re not doing this just to spite you. </p>
<p>The hard fact is that they <a href="http://oneflightbooks.com"><em>just don&#8217;t care</em></a>. </p>
<p>Or more precisely, they don&#8217;t care <em>yet</em>. They&#8217;re interested, but they do not know enough to care. We have not given them enough of a reason to care. They are not ready to take that step. </p>
<p>So the right answer in this situation is not to give our call-to-action a stronger drop shadow, double its text size, make it fire engine red (#CE1620), or make it blink. No amount of visual design on that button will make people click it more. The right answer is to remove the button altogether and replace it with something that people do want to click. Something they do want to do…the appropriate next step in their lifecycle as a customer. </p>
<p>I call this <em>Designing for the Next Step</em>. And in my next post I will explain what I&#8217;m talking about in much more detail&#8230;</p>
<p><strong>Addendum:</strong> The folks at <a href="http://www.zurb.com/">Zurb</a> have published <a href="http://www.zurb.com/article/816/why-burying-sign-up-buttons-helps-get-mor">an example of a 350% improvement from simply burying the sign-up button</a>. That&#8217;s some serious improvement.  </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/why-you-should-bury-your-sign-up-button/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What our home pages are really saying (a dialog)</title>
		<link>http://bokardo.com/archives/what-our-home-pages-are-really-saying/</link>
		<comments>http://bokardo.com/archives/what-our-home-pages-are-really-saying/#comments</comments>
		<pubDate>Thu, 20 Oct 2011 13:36:52 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[Make them Care]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=1986</guid>
		<description><![CDATA[Often when I&#8217;m designing I try to imagine a screen interaction as a face-to-face dialog between two people. Specifically, I try to imagine that the person visiting or using the screen is trying to have a conversation with a person representing the website or software the screen is part of. Of course, real-life conversation is [...]]]></description>
			<content:encoded><![CDATA[<p>Often when I&#8217;m designing I try to imagine a screen interaction as a face-to-face dialog between two people. Specifically, I try to imagine that the person visiting or using the screen is trying to have a conversation with a person representing the website or software the screen is part of. Of course, real-life conversation is by its nature reactive…we can instantly respond to a direct question and generally structure our responses based on where the conversation is going. When we design, we don&#8217;t have this luxury, and so we are left with designing a one-sided static conversation. This is hard!…and the results are often stilted and not at all like a real human conversation. </p>
<p>In the conversation below I imagine what it would be like to talk to most home pages…you know the ones…with the giant &#8220;Sign Up&#8221; button that commands your attention above all else. </p>
<p>(BTW: the following is an excerpt from my upcoming book <a href="http://oneflightbooks.com">Make them Care!</a>) </p>
<p><em>Setting</em>: The beautifully designed lobby entrance to your company&#8217;s corporate headquarters. </p>
<p><strong>You</strong>: &#8220;Hmm…I just found this place by taking a path that looked interesting. You do software or something?&#8221;</p>
<p><strong>Him</strong> (Salesperson in building lobby): &#8220;We offer amazing Software!&#8221; </p>
<p><strong>You</strong>: &#8220;Ok, what is it?&#8221; </p>
<p><strong>Him</strong>: &#8220;Sign up Now&#8221;</p>
<p><strong>You</strong>: &#8220;Um…what does it do?&#8221; </p>
<p><strong>Him</strong>: &#8220;Sign up Now!&#8221; </p>
<p><strong>You</strong>: &#8220;How does it work?&#8221;</p>
<p><strong>Him</strong>: &#8220;No obligation or credit card necessary!&#8221; </p>
<p><strong>You</strong>: &#8220;I&#8217;m trying to figure out if this thing can work for me.&#8221; </p>
<p><strong>Him</strong>: &#8221; Did I mention it&#8217;s free to sign up?&#8221;</p>
<p><strong>You</strong>: &#8220;Ok, what does it look like?&#8221; </p>
<p><strong>Him</strong>: &#8220;Here&#8217;s a tiny screenshot you can&#8217;t see any detail on. Sign up Now!&#8221; </p>
<p><strong>You</strong>: &#8220;You&#8217;re not answering any of the questions I have.&#8221; </p>
<p><strong>Him</strong>: &#8220;Sign up Now!&#8221; </p>
<p><strong>You</strong>: &#8220;I&#8217;m done here.&#8221; </p>
<p><strong>Him</strong>: &#8220;Sign up Now!&#8221; </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/what-our-home-pages-are-really-saying/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How Steve Changed Things</title>
		<link>http://bokardo.com/archives/how-steve-changed-things/</link>
		<comments>http://bokardo.com/archives/how-steve-changed-things/#comments</comments>
		<pubDate>Sat, 08 Oct 2011 11:45:08 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Apple]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=1975</guid>
		<description><![CDATA[There are many amazing stories and anecdotes being shared about Steve Jobs and his passing this week. Steve had a dramatic effect on industry, introducing the most powerful extension of our brains, the personal computer, to the world and making it accessible to anyone. Not just big business, the traditional focus of technology makers, but [...]]]></description>
			<content:encoded><![CDATA[<p>There are many amazing stories and anecdotes being shared about Steve Jobs and his passing this week. Steve had a dramatic effect on industry, introducing the most powerful extension of our brains, the personal computer, to the world and making it accessible to anyone. Not just big business, the traditional focus of technology makers, but you and me. While Microsoft was busy milking their cash-cow office suite, Apple created simple applications like iTunes and iPhoto so that normal, everyday folks could listen to music and look at photos together. </p>
<p>Apple has had a truly remarkable effect on my life. I have used Apple products for 10 years, since the first iPod came out. A Macbook has been the primary tool I&#8217;ve used continuously for over 8 years&#8230;that&#8217;s every day for 8-12 hours a day for 3,000 days. </p>
<p>So when I sat down and thought about what I would write as a tribute to Steve Jobs, who in my mind is the most brilliant innovator of the modern era, I first thought of his amazing <a href="http://news.stanford.edu/news/2005/june15/jobs-061505.html">2005 Stanford Commencement Speech</a> in which he lays out his philosophy on living. In this speech Steve&#8217;s life comes into focus, his motivations are exposed, and he looks death in the face. What could I possibly say in a blog post that communicates how I feel about the effect he&#8217;s had and continues to have? </p>
<p>But then I remembered a picture I took of my two-year-old daughter that captures just how profoundly Steve changed things. It perfectly embodies Steve&#8217;s vision of computing and what Apple is trying to do: change the world for every man, woman, and child. And given that the words &#8220;iPad&#8221; and &#8220;iPhone&#8221; are now part of my two-year-old&#8217;s everyday language, I would say that though he died much too early at the age of 56, Steve fully succeeded in realizing his vision. </p>
<p>So thank you Steve, and all the people at Apple who do such amazing, life-changing work. </p>
<p><a href="http://bokardo.com/img/daughter-ipad-full.gif"><img src="http://bokardo.com/img/daughter-ipad-800.gif" alt="Steve's vision" style="width:100%;"/></a></p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/how-steve-changed-things/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Five reasons why you should find what you love and double-down on it</title>
		<link>http://bokardo.com/archives/find-what-you-love-and-double-down/</link>
		<comments>http://bokardo.com/archives/find-what-you-love-and-double-down/#comments</comments>
		<pubDate>Wed, 28 Sep 2011 13:43:28 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Advice]]></category>
		<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=1950</guid>
		<description><![CDATA[You know when you meet someone and at first you don&#8217;t really hit it off so well&#8230;you don&#8217;t seem to have much in common? And then, all of a sudden, you hit on a topic you&#8217;re both passionate about and your relationship changes? You immediately lose a sense of time and simply talk and talk [...]]]></description>
			<content:encoded><![CDATA[<p>You know when you meet someone and at first you don&#8217;t really hit it off so well&#8230;you don&#8217;t seem to have much in common? And then, all of a sudden, you hit on a topic you&#8217;re both passionate about and your relationship changes? You immediately lose a sense of time and simply talk and talk and talk because you have a shared interest? </p>
<p>We all have interests like that; we all have something we&#8217;re passionate about. For some people it&#8217;s sports, others politics, others cooking, etc. Everyone has their own thing they love. </p>
<p><strong>So here&#8217;s a challenge:</strong> If you&#8217;re not doing that thing you love for your job, you should quit right now and go figure out a way to make it happen. I&#8217;m serious, you should cut the cord and simply go do what you love. </p>
<p>I know that this is easy to say and hard to do, and it is pretty commonplace advice. But here&#8217;s the thing that I think is usually forgotten when thinking about actually taking the plunge. <strong>When you do what you love, you align your natural interests with your work ethic.</strong> You naturally pour all of yourself into it and you don&#8217;t resent that you&#8217;re working hard. Here are five things I&#8217;ve observed as I&#8217;ve worked as a designer (doing what I love). </p>
<ol>
<li><strong>When you do what you love, you do much better work.</strong><br /> Challenges are merely small hurdles to get over instead of huge mountains to climb. You stick with problems much longer, and you work on problems all the time (at least in your head). Once you get in the flow of this, then you start solving problems faster and faster. </li>
<li><strong>When you do what you love, people notice.</strong><br /> They see your energy and they want to include you. You get a reputation of someone who does that thing because you love to do that thing. You don&#8217;t even have to be good at it to start. People want to work with others who are passionate about what they do. </li>
<li><strong>When you do what you love, work isn&#8217;t work.</strong><br /> This is an interesting phenomenon because you don&#8217;t always realize that it&#8217;s happening. What used to be 8 hours a day at the office is now a dive into doing fun stuff all day that you&#8217;re kinda shocked you get paid for. Work becomes play some of the time. </li>
<li><strong>When you do what you love, you&#8217;re in constant learning mode.</strong><br /> I love this part because I love learning. When you are doing what you love then you naturally want to learn as much as you can. You become like a little kid, diving into new things with abandon. </li>
<li><strong>When you do what you love, you are happier.</strong><br /> That&#8217;s the bottom line, you&#8217;re happier doing work that you enjoy. This is what everyone&#8217;s goal should be. </li>
</ol>
<p>Now you might say &#8220;Well, there is no money in baking cakes&#8221; or &#8220;I can&#8217;t paint pictures for a living&#8221;. Art is a hard one, of course, but there are three bakeries right here in Newburyport whose cakes could be improved upon. There is always room at the top for passionate people who care about what they&#8217;re doing. </p>
<p>You may start off making peanuts compared to what you were making before, and you will probably have to make sacrifices to make this work. But that will change because you&#8217;re going to become really good at this. </p>
<p>It might take a year or two to get up to speed, but that&#8217;s OK. The pain will be worth it because you&#8217;ll be happier. When you do what you love, you&#8217;ll do it more often. But you won&#8217;t mind. In fact, you&#8217;ll find yourself thinking about it when you shouldn&#8217;t be. That&#8217;s a much better problem to have than to want to completely forget your job when you&#8217;re not there!</p>
<p>Now, if you&#8217;re in an OK job right now but you have a plan to get to what you love, then stick with it. You may have to stay in a role that&#8217;s tough for a while, just make sure that you have a plan to move into something else. Talk to your boss and make sure they&#8217;re aware of where you want to go&#8230;if they&#8217;re any good they&#8217;ll help you make it happen because they know that it&#8217;s better for everyone anyway. </p>
<p>The people I admire most are the people doing what they love everyday because there is no separation between work and play. Their life is a constant playground. That&#8217;s what I&#8217;m striving for and I think the path is relatively straight-forward: find what you love and double-down on it.</p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/find-what-you-love-and-double-down/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Redesigned: Facebook Logout Button</title>
		<link>http://bokardo.com/archives/redesigned-facebook-logout-button/</link>
		<comments>http://bokardo.com/archives/redesigned-facebook-logout-button/#comments</comments>
		<pubDate>Tue, 27 Sep 2011 12:16:38 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Interface Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=1931</guid>
		<description><![CDATA[At the very least, interfaces should not lie. They should not deceive the people who use them into thinking something is true when it actually isn&#8217;t. Apparently, Facebook does not agree. On Sunday Nic Cubrilovic posted some troubling news: Logging out of Facebook is not Enough. Facebook doesn&#8217;t actually log you out when you ask [...]]]></description>
			<content:encoded><![CDATA[<p>At the very least, interfaces should not lie. They should not deceive the people who use them into thinking something is true when it actually isn&#8217;t.  </p>
<p>Apparently, Facebook does not agree. On Sunday Nic Cubrilovic posted some troubling news: <a href="http://nikcub.appspot.com/logging-out-of-facebook-is-not-enough">Logging out of Facebook is not Enough</a>. Facebook doesn&#8217;t actually log you out when you ask it to. They pretend to, but they don&#8217;t. Instead, they simply change the status of your logged in session to fool you into thinking you&#8217;re logged out. </p>
<div class="screenshot"><img src="/img/facebook-logout.png" alt=""/> </div>
<p>You don&#8217;t see your friends or profile. You don&#8217;t view your feed. Even if you try to access your profile pages, Facebook will send you to the login screen. Except that you&#8217;re not actually logged out. Every step of the way Facebook knows that it&#8217;s you trying to access those pages. </p>
<p>So, I&#8217;ve designed a more appropriate Facebook logout button&#8230;instead of saying &#8220;Logout&#8221; it now says &#8220;Logout (not really)&#8221;. This is more accurate and better reflects what&#8217;s actually going on. </p>
<p>As an interface designer myself, I know that words matter. I believe that a lot of <a href="http://bokardo.com/archives/interface-design-is-copywriting/">interface design is in fact copywriting</a>. So when I see Facebook knowingly betray their user&#8217;s trust like this it goes against the first rule of interface design: </p>
<p><strong>Clarity above all.</strong></p>
<p>At the very least, interfaces should be clear. People should understand what is going on and what effect their actions are having. In this case people when people click &#8220;Logout&#8221; they think they&#8217;re actually logging out of Facebook, and they think that means their actions are not being recorded, and they are trusting the service to do what it says it&#8217;s doing. </p>
<p>In case you&#8217;re wondering of my Facebook status, I deleted my Facebook account last year because of the <a href="http://bokardo.com/archives/facebook-behaving-badly/">continued pattern of bad behavior</a> from the company&#8230;and no I&#8217;m not 100% certain the account was actually deleted. </p>
<p>So I hope the designers at Facebook might reconsider the design of their logout mechanism. I provide this button design free of charge. </p>
<p>Update: <a href="http://latimesblogs.latimes.com/technology/2011/09/think-you-logged-out-of-facebook-not-really.html">L.A. Times thinks</a> the button is a good idea, too. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/redesigned-facebook-logout-button/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Update on my new book, Make them Care!</title>
		<link>http://bokardo.com/archives/update-on-my-new-book-make-them-care/</link>
		<comments>http://bokardo.com/archives/update-on-my-new-book-make-them-care/#comments</comments>
		<pubDate>Fri, 23 Sep 2011 11:25:29 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Make them Care]]></category>
		<category><![CDATA[microcopy]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=1912</guid>
		<description><![CDATA[Several folks have recently asked me when my new book is coming out&#8230;so here is a quick update. First off, I&#8217;ve completely revamped the book site to better reflect the contents of the book: Official Make them Care! book site Regular readers of Bokardo know that it has been over two years since I announced [...]]]></description>
			<content:encoded><![CDATA[<p>Several folks have recently asked me when my new book is coming out&#8230;so here is a quick update. First off, I&#8217;ve completely revamped the book site to better reflect the contents of the book: </p>
<div style="float:right;width:240px;"><a href="http://oneflightbooks.com"><img src="http://bokardo.com/img/make-them-care-cover.gif" alt=""/></a></div>
<p><a href="http://oneflightbooks.com" alt="One Flight Books: short books for practicing web professionals">Official Make them Care! book site</a></p>
<p>Regular readers of Bokardo know that it has been over two years since I announced Make them Care!. On August 17, 2009 I even <a href="http://bokardo.com/archives/coming-soon-make-them-care-my-new-book/">announced</a> that it was &#8220;coming soon&#8221;. </p>
<p>Well, you could say that I got distracted. Shortly after I wrote that optimistic blog post, I jumped into what would become Performable, a company we sold to HubSpot this past June. (I&#8217;m now the Director of UX at HubSpot). This was certainly a good thing to get distracted by, but it stopped any and all momentum I had writing my book. I would grab a couple hours on a weekend here and there, but life is so busy that I just couldn&#8217;t get any momentum. </p>
<p>This past spring as I was preparing to speak at SXSW I reconsidered the scope of the book, and I worked on what I hope is a renewed, clearer focus for it. I changed the focus away from &#8220;sign up&#8221;, which is important but not the real hurdle that businesses face. I got really excited about the book again, and I started dedicating a little time to it here and there. </p>
<p>I&#8217;m not done yet, I&#8217;m still working on it (mostly on Saturday mornings). I&#8217;m not worried about it taking too long. I&#8217;m going to make it good, the best thing I&#8217;ve ever written. I don&#8217;t really care how long it takes&#8230;my first priority is quality. So I&#8217;m not ready yet to say when the book will be out, but I am telling you that it won&#8217;t be another two years. It will be measured in months. </p>
<p>In the meantime, go check out the new page for the book: <a href="http://oneflightbooks.com" alt="One Flight Books: short books for practicing web professionals">Make them Care!</a>. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/update-on-my-new-book-make-them-care/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How Instagram Stays in Focus</title>
		<link>http://bokardo.com/archives/how-instagram-stays-in-focus/</link>
		<comments>http://bokardo.com/archives/how-instagram-stays-in-focus/#comments</comments>
		<pubDate>Wed, 21 Sep 2011 14:45:41 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[Web Applications]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=1893</guid>
		<description><![CDATA[One of the biggest challenges in designing and building web applications is to find and keep focus: to only build what is necessary and to leave out the rest. So when a company keeps a really tight focus on their core product they should be applauded. Instagram is one of those companies. If you&#8217;re not [...]]]></description>
			<content:encoded><![CDATA[<p>One of the biggest challenges in designing and building web applications is to find and keep focus: to only build what is necessary and to leave out the rest. </p>
<div class="screenshot"><img src="http://bokardo.com/img/instagram.png" alt="" /></div>
<p>So when a company keeps a really tight focus on their core product they should be applauded. <a href="http://instagram.com">Instagram</a> is one of those companies. If you&#8217;re not familiar with the app, Instagram is about as simple as can be: you use it to take pictures, apply filters to them, and share them on social networks. That&#8217;s it. That&#8217;s all the app does. And it has been a wild success&#8230;Instagram is growing like a weed&#8230;they&#8217;re just about to hit 10 million users in about a year. </p>
<p>Instagram has just released <a href="http://blog.instagram.com/post/10444123475/v20">Version 2.0</a> of their popular photo-sharing application and the release notes show a laser focus on the core features and only their core features. Here is what they&#8217;ve improved: speed of filters, added 4 filters, faster tilt-shift, larger images, and optional borders. That&#8217;s it. Those are the core features of the product&#8230;they&#8217;ve essentially taken what they have and sped things up.</p>
<p>In other words, Instagram has not added any new features with this &#8220;largest revamp&#8221; to the product. They&#8217;ve simply improved what they have to make it even easier and faster to share pictures. </p>
<p>So here&#8217;s a simple playbook:</p>
<ol>
<li><strong>Focus on improving what you already have.</strong> Don&#8217;t add new features, improve existing ones. </li>
<li><strong>Make what you have faster.</strong> It can <em>always</em> be faster. Remove delays (like Instagram did by removing filtering delays&#8230;they even now have live filtering)</li>
<li><strong>Improve usability</strong> Instagram also redesigned their already-successful photo taking screen. It would have been easy to skip this&#8230;</li>
<li><strong>Resist the urge to add new features.</strong> Wait until the market demands it or you have real evidence that your business is hurting as a result.</li>
</ol>
<p>Here&#8217;s the thing: What Instagram has done <strong>almost never happens!</strong> It is incredibly rare in the world of web applications to have such tight focus on the core functionality like Instagram has done with their V2 release. The vast majority of releases contains new features that add new capabilities to the product. </p>
<p>To wit: there is an entire vocabulary built around the problem of keeping focus: Feature creep, MVP (minimum viable product), lean startup, (release early, release often). And the problem has only gotten harder in the last few years in which development has sped up significantly. Web application frameworks, Amazon&#8217;s cloud services, and social coding services like Github have made it extremely easy to build faster than ever before. As a result it can be hard to imagine what it looks like to keep focus over time on a very small feature set. </p>
<p>So when a company like Instagram is able to keep extreme focus on only what is necessary they should be applauded and emulated as much as possible. Your users, who are already using your app, will love you for making it even better. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/how-instagram-stays-in-focus/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Important Question: Are your Customers also your Users?</title>
		<link>http://bokardo.com/archives/customers-vs-users/</link>
		<comments>http://bokardo.com/archives/customers-vs-users/#comments</comments>
		<pubDate>Tue, 20 Sep 2011 11:01:04 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Strategy]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=1887</guid>
		<description><![CDATA[For a long time I disliked the terms &#8220;B2B&#8221; and &#8220;B2C&#8221;. They sounded like over-architected corporate terms to me that didn&#8217;t really mean anything. I still think they&#8217;re over-architected corporate terms but I now think that they hint at an important distinction: the difference between selling to customers who don&#8217;t use your product and selling [...]]]></description>
			<content:encoded><![CDATA[<p>For a long time I disliked the terms &#8220;B2B&#8221; and &#8220;B2C&#8221;. They sounded like over-architected corporate terms to me that didn&#8217;t really mean anything. I <em>still</em> think they&#8217;re over-architected corporate terms but I now think that they hint at an important distinction: the difference between selling to customers who don&#8217;t use your product and selling to customers who do. </p>
<p>In B2B businesses sell to other businesses. In B2C businesses sell directly to consumers. This distinction makes all the difference. When you sell to someone who uses your software, you&#8217;re talking to someone who cares about the user experience because it directly affects their future. They might even want to try out your product first. They&#8217;ll want to know what others in their situation did. That&#8217;s why on consumer oriented sites you see free trials&#8230;because someone who is purchasing for their own use wants to know what they&#8217;re getting into.  </p>
<p>When you sell to someone who does not use your software then you have a very different task in front of you. You&#8217;re not talking to someone who cares about user experience because they&#8217;re not the ones who will use your product. They care about making the purchase look like a good idea, so they&#8217;re naturally concerned about features, pricing, and convincing other people. That&#8217;s why on enterprise sites you rarely see free trials and instead see things like whitepapers, webinars, and case studies that someone can use to report to others. </p>
<p>Those two activities are very different: <em>buying</em> and <em>using</em>. When one person does them both, they appear to be one activity and can obscure what&#8217;s really going on. When they are separate, when the customer is not the user, then the difference becomes much more clear. </p>
<p>Therefore, we must design accordingly, depending on who we&#8217;re selling to. This is part of the age-old maxim to know who your audience is and know what they care about. So take a second look&#8230;knowing if your customers are also your users is one of the most important things you can know. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/customers-vs-users/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Netflix in Danger of Ruining their User Experience</title>
		<link>http://bokardo.com/archives/netflix-in-danger-of-ruining-their-user-experience/</link>
		<comments>http://bokardo.com/archives/netflix-in-danger-of-ruining-their-user-experience/#comments</comments>
		<pubDate>Mon, 19 Sep 2011 11:21:24 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[Netflix]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=1877</guid>
		<description><![CDATA[Netflix CEO Reed Hastings wrote a blog post yesterday explaining his company&#8217;s recent decision to split up the streaming and DVD delivery services of the company. An Explanation and Some Reflections The DVD delivery service (the original service) will now be called Qwikster. Yes, that&#8217;s right, Qwikster. The streaming part of the service will continued [...]]]></description>
			<content:encoded><![CDATA[<p>Netflix CEO <a href="http://en.wikipedia.org/wiki/Reed_Hastings">Reed Hastings</a> wrote a blog post yesterday explaining his company&#8217;s recent decision to split up the streaming and DVD delivery services of the company. </p>
<p><a href="http://blog.netflix.com/2011/09/explanation-and-some-reflections.html">An Explanation and Some Reflections</a></p>
<p>The DVD delivery service (the original service) will now be called Qwikster. Yes, that&#8217;s right, Qwikster. The streaming part of the service will continued to be called Netflix. <a href="http://abovethecrowd.com/2011/09/18/understanding-why-netflix-changed-pricing/">One explanation </a> suggests this move was made in response to pressure from Hollywood who wants to charge per user access, not per copy. In other words, no ownership, nothing like owning or renting a DVD. Think Cable TV. The more things change&#8230;the more they stay the same. </p>
<p>Netflix is taking a huge risk here. They&#8217;re changing the user experience of their web apps to model the new company structure, not a structure that is most friendly to people. This is an extremely common problem in user interface design. Netflix is in serious danger of breaking the user experience they are well-known for. </p>
<p>As one commenter complains there will now be two separate movie queues, one on Netflix for streaming and one on Qwikster for DVDs. Hasting&#8217;s response is dismissive: </p>
<blockquote><p>&#8220;We already have two queues. The two &#8220;sites&#8221; are a click between each other, so we think not that much different than two tabs on one site.&#8221;</p>
</blockquote>
<p>Technically, Hastings is right about there already being two queues. But he&#8217;s dead wrong about it being much different. Obviously he&#8217;s never watched people use web applications before. Changing websites is not even close to the same thing as changing tabs. When you change websites you go somewhere different, you get a different UI, you&#8217;re using a different username, and you probably have to log in. You have a different payment system. Different family members to add. Different recommendations to look at. And that&#8217;s just for starters. </p>
<p>When you change tabs you don&#8217;t lose any of that context. You stay in the same place, you just get a different list. </p>
<p>This is a fundamental change in the product, and Hastings just dismisses the concern with a wave of his hand. Not only that, but this is a branding issue as well. When you switch sites you&#8217;re going from Netflix, a brand people know and love, to Qwikster, which sounds like the latest get rich quick startup without a real business plan. </p>
<p>It may be that the split was inevitable, but why not name the DVD service &#8220;Mailflix&#8221; and give people a chance to understand what&#8217;s actually going on? Give them some semi-logical name that actually makes sense? Mailflix for movies in the mail, Netflix for movies on the Internet?</p>
<p>Also, people don&#8217;t think they&#8217;re buying two services right now&#8230;they&#8217;re simply buying Netflix. As another commenter points out: </p>
<blockquote><p>&#8220;You&#8217;re continuing to make a classic mistake: thinking you&#8217;re something different than what everyone believes you are. You&#8217;re not a DVD company and a streaming company: you&#8217;re where I go to watch movies. That&#8217;s it. The future clearly is streaming, but by separating and charging more for access, you&#8217;re wildly less valuable to me. I&#8217;ll likely cancel. You haven&#8217;t listened to customer feedback. You&#8217;re delusional and you&#8217;re lost.&#8221;</p>
</blockquote>
<p>There is one angle where all of this makes sense. Let&#8217;s assume for a moment that Netflix is knowingly trying to kill off its DVD rental service. This is the way to do it&#8230;separate it out completely, give it a ridiculous name, and keep your brand equity with the newer streaming service. This almost makes sense&#8230;except for the fact that the content in Netflix streaming has gotten worse, not better, over time. If they really wanted to focus attention solely on Netflix going forward, they would create a catalog worth watching. Right now the streaming catalog is abysmal, and with movies that can only mean it gets worse over time as you watch the one or two you haven&#8217;t seen yet. </p>
<p>So as a Netflix subscriber who doesn&#8217;t even use the service anymore (outside of my kids watching educational videos) I&#8217;m left wondering&#8230;what is Reed Hastings and Netflix thinking? </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/netflix-in-danger-of-ruining-their-user-experience/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Interface Design is Copywriting</title>
		<link>http://bokardo.com/archives/interface-design-is-copywriting/</link>
		<comments>http://bokardo.com/archives/interface-design-is-copywriting/#comments</comments>
		<pubDate>Sun, 18 Sep 2011 11:30:52 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[copywriting]]></category>
		<category><![CDATA[HubSpot]]></category>
		<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[microcopy]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=1866</guid>
		<description><![CDATA[There is a lot to like in the presentation The Language of Interfaces by Des Traynor, in which he makes several important points about Interface Design. The first is that words mean everything in the interface. Every single word you choose is important, from the call-to-action button to the headline to the words in an [...]]]></description>
			<content:encoded><![CDATA[<p>There is a lot to like in the presentation <a href="http://contrast.ie/blog/the-language-of-interfaces/">The Language of Interfaces</a> by Des Traynor, in which he makes several important points about Interface Design. </p>
<p>The first is that words mean everything in the interface. Every single word you choose is important, from the call-to-action button to the headline to the words in an error message. Each word, if carefully chosen, adds to the experience of the user, making them more confident and sure that they&#8217;re on the right track. When carelessly chosen, each word erodes confidence and adds confusion to an uneven experience. </p>
<p><em>Good design is not an accident</em>. It&#8217;s not something that just happens by someone getting lucky. Sure, once in a while someone stumbles upon a cool <a href="http://bokardo.com/archives/game-mechanics-for-interaction-design-an-interview-with-amy-jo-kim/">core mechanic</a> that happens to work, but to create a solid interface that many people can use and enjoy takes real attention to the details. </p>
<p>The real question is&#8230;what are the details that matter? There are many candidates&#8230;there is technology and social and gaming and psychology and experience and content and fill in the next buzzword please. Everybody has their hobby horse&#8230;in this post I&#8217;m sharing mine. </p>
<p>While I&#8217;ll be the first to say &#8220;Oh&#8230;look a shiny new JQuery widget!&#8221; I humbly submit that there is no single element more important to your interface than the copywriting. There is nothing that makes or breaks a positive experience more than the simple set of words that you choose to communicate with. In a world in which we have to simplify as much as possible, nothing matters more than the small vocabulary you end up with in your final work. </p>
<p>Traynor resurfaces a great post by Jason Fried in which Fried suggests that <a href="http://gettingreal.37signals.com/ch09_Copywriting_is_Interface_Design.php">Copywriting is Interface Design</a>&#8230;I think we should also look at it the other way. <strong>Interface Design is Copywriting</strong>. Designing an interface is largely an exercise in choosing the right words. When you lay out a page, you&#8217;re choosing copy for the headline, subheadline, call-to-action, content area, graphs and analysis areas, error messages. All of these design elements are built out of words. Are you an aspiring wordsmith? I hope so&#8230;because you&#8217;re choosing some very important words! </p>
<p>The best line in Traynor&#8217;s piece is this one: </p>
<p><strong>Nothing says Send Message, like the words “Send Message”.</strong></p>
<p>This simple statement says a lot about the field of Interface Design. So often we don&#8217;t think twice about the words we use, and while we want to write like Hemingway we end up writing something that might place 3rd in a regional high school essay contest. </p>
<p>And, by the way, I don&#8217;t mean to sit on a soapbox here. This is hard stuff&#8230;it&#8217;s hard for every designer and developer I know. Choosing words is the hardest part of my job and I get it wrong before I get it right. The first attempt at any design is almost always wrong&#8230;it&#8217;s only the stubborn people who stick with it, test it, and continually refine who will approach great design.  </p>
<p>Here is an example I&#8217;ve been using lately at <a href="http://jobs.hubspot.com/">HubSpot</a> because it is so easy to see the importance of words in hindsight. For many years the domain setup screen in HubSpot software used the terminology &#8220;Add Domain&#8221; as the primary call-to-action. When you get set up with HubSpot you want to point your domain to the HubSpot servers so that your website (now hosted by HubSpot) continues to work. </p>
<p>However, we recently did some user testing and found that the words &#8220;Add Domain&#8221; stopped people in their tracks. The people using the software in our test said something like &#8220;I have to add a domain&#8230;where do I add it?&#8221; or &#8220;I already have a domain&#8230;why do I need to add one?&#8221;. In their minds they already had a domain&#8230;there was no reason to add a new one! </p>
<p>But the software had that CTA for years. Nobody questioned it because the entire team knew what it meant. It is important to note that no amount of introspection would have caught this! But to a user&#8230;someone who is transitioning from hosting their website somewhere else to hosting it on HubSpot the words were entirely critical to what was going on. </p>
<p>So&#8230;the fix was straight-forward. Change the words from &#8220;Add a Domain&#8221; to &#8220;Connect your Domain&#8221;. Note the subtle yet crucial difference that two words make. You&#8217;re not <em>adding</em> anything&#8230;nothing is <em>new</em> here. Instead, you&#8217;re <em>connecting</em> something that already exists&#8230;a domain that is <em>YOURS</em>. Easy peasy. </p>
<p>Now, multiply this by 1,000 and you might have an idea of how many places in your web application it is crucial to get your words right. Every single headline, every single call-to-action, every single error message, every single bit of <a href="http://bokardo.com/archives/writing-microcopy/">microcopy</a>. All of it. Every word matters. </p>
<p>So if you&#8217;re not already, start thinking of yourself as a copywriter. You already are one anyway. <img src='http://bokardo.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/interface-design-is-copywriting/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>The Process is not the Point</title>
		<link>http://bokardo.com/archives/the-process-and-the-point/</link>
		<comments>http://bokardo.com/archives/the-process-and-the-point/#comments</comments>
		<pubDate>Thu, 11 Aug 2011 12:59:05 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=1850</guid>
		<description><![CDATA[There are two parts to every project&#8230;the Process and the Point. The Process, which gets most of the attention, is the series of steps we go through to do the work. We obsess over the process&#8230;should we do wireframes, mockups, prototypes, or code right in HTML? What deliverables do we need to get buy-in? When [...]]]></description>
			<content:encoded><![CDATA[<p>There are two parts to every project&#8230;the Process and the Point. </p>
<p>The Process, which gets most of the attention, is the series of steps we go through to do the work. We obsess over the process&#8230;should we do wireframes, mockups, prototypes, or code right in HTML? What deliverables do we need to get buy-in? When do we do testing? What kind of testing do we do? Should we do user testing early? Late? When is the best time to get feedback? </p>
<p>We need the process to know what to do next. We need a framework to work with because it helps us get more efficient at what we do. When you&#8217;re user testing, for example, you&#8217;ll go much farther and get there faster if you have a repeatable process in place. You&#8217;ll want a quick way to get users for testing, a quick way to figure out what to test, what tasks to test, and what to do with the results. </p>
<p>While we should constantly tweak our own process, we also discuss it endlessly with others. Are you sure you&#8217;re doing user experience design correctly? Are you designing content first? Are you designing in the browser? Are you using lorem ipsum, for the love of Gods? Are you doing A/B testing? Using personas? I&#8217;m sure yours aren&#8217;t as robust as mine, natch.</p>
<p>And then there is the Point. The problem you&#8217;re trying to solve. The thing that isn&#8217;t part of a process but is the most important thing you need to focus on as a designer. The thing that, if you happen to solve it, makes the process almost irrelevant. Solve the problem and you&#8217;re successful no matter what process you&#8217;ve been using. </p>
<p>The point is often what&#8217;s different in your project&#8230;it&#8217;s the thing that you probably don&#8217;t have a process for yet (if you did it wouldn&#8217;t be a problem!). And you probably can&#8217;t talk about the point anyway because you don&#8217;t want other people to solve it before you (e.g. your competitors).  So we instead talk about the process&#8230; </p>
<p>But we should remember not to confuse the two. The process is valuable&#8230;it&#8217;s a framework for deciding what to do next&#8230;and we need that&#8230;but it&#8217;s merely a means to an end. And whatever you do, don&#8217;t let process details distract you from solving your problem in any way possible. </p>
<p>The Process is important&#8230;but it&#8217;s not the Point. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/the-process-and-the-point/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

