<?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>The Phuse</title>
	<atom:link href="http://thephuse.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://thephuse.com</link>
	<description></description>
	<lastBuildDate>Mon, 14 May 2012 15:00:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Build Responsive Websites Faster with Sass</title>
		<link>http://thephuse.com/development/build-responsive-websites-faster-with-sass/</link>
		<comments>http://thephuse.com/development/build-responsive-websites-faster-with-sass/#comments</comments>
		<pubDate>Mon, 14 May 2012 15:00:40 +0000</pubDate>
		<dc:creator>Tamera Mitchell</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[box-sizing]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[css3]]></category>
		<category><![CDATA[dev]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[html]]></category>
		<category><![CDATA[html5]]></category>
		<category><![CDATA[options]]></category>
		<category><![CDATA[responsive]]></category>
		<category><![CDATA[responsive design]]></category>
		<category><![CDATA[Sass]]></category>
		<category><![CDATA[sites]]></category>
		<category><![CDATA[websites]]></category>

		<guid isPermaLink="false">http://thephuse.com/?p=985</guid>
		<description><![CDATA[With new CSS box-sizing options and the latest version of Sass, developers can build responsive web sites much easier now, with a combination of a few new tools at our disposal.]]></description>
			<content:encoded><![CDATA[<p>Responsive web design has been a hot topic with web developers ever since Ethan Marcotte <a href="http://www.alistapart.com/articles/responsive-web-design/">introduced the method</a>. It&#8217;s a really great way to build one site that is usable across many devices, but it takes a lot of work with math for truly flexible designs, and managing extra css rules for media queries can be a pain.</p>
<p>That was the case until recently. <strong>With new CSS box-sizing options and the latest version of Sass, developers can build responsive web sites much easier now, with a combination of a few new tools at our disposal.</strong></p>
<h2 id="border-boxandsass3.2">Border-box and Sass 3.2</h2>
<p>Like any developer, I&#8217;ve spent more time than I like to admit working on issues with the <a href="https://developer.mozilla.org/en/CSS/box_model">css box model</a>. It can be really frustrating to adjust a bunch of container sizes just to change the padding on one element.</p>
<p>The new css rule
<pre><code class="css">box-sizing: border-box</code></pre>
<p> makes our jobs a lot easier. It changes the css box model so that containers don’t expand with padding and border width adjustments. This rule is new to CSS3 and is compatible with Firefox, Chrome, Opera, and IE8+ (with <a href="http://html5please.us/#box-sizing">an available polyfill</a> for IE6 and IE7). If you aren&#8217;t familiar with the border-box rule, you&#8217;ll want to read the articles by <a href="http://paulirish.com/2012/box-sizing-border-box-ftw/">Paul Irish</a> and <a href="http://css-tricks.com/box-sizing/">CSS-Tricks</a> on using it. Border-box especially shines when it comes to grids.</p>
<p>Another tool that really helps developers create sites easier and quicker is Sass. Sass is CSS, but much smarter; it adds the ability to use nesting, variables, and reuse snippets of code called mixing. If you haven&#8217;t used Sass yet, The Sass Way has a <a href="http://thesassway.com/beginner/getting-started-with-sass-and-compass">getting started guide</a>. Sass 3.2 introduces even more smart tools especially for use with responsive web design. At this time 3.2 is the &#8216;bleeding edge&#8217; version, so you&#8217;ll need to install it with this line:</p>
<pre><code class="css">gem install sass --pre
</code></pre>
<h2 id="asimplesasslayout">A simple Sass layout</h2>
<p>Here is an example of responsive design using variables and a few simple equations to do the math for you.</p>
<p><a href="https://github.com/thephuse/Circuits/tree/master/sass-site">Source</a></p>
<p><a href="http://circuits.thephuse.com/sass-site">Demo</a></p>
<p>The example is a typical blog post: we have a large column for the article next to a smaller column for relevant information, a header on top and a footer at the bottom. But rather than choose the widths of the columns directly, we implemented a Sass mixin and some variables for a simple custom grid.</p>
<pre><code class="css">$columns: 12;
$max-page-width: 1200; /* Even though we mean 1200 pixels, we leave out 'px' so that the mixing below can perform calculations on it. */
$column-width: $max-page-width/$columns;
$column-padding: 1rem;

@mixin column($amount, $context: $max-page-width, $padding: $column-padding) {
width: percentage(($column-width * $amount) / $max-page-width);
padding: $padding;
}
</code></pre>
<p>Our variables at the top describe the grid; we have 12 columns of 100px each, with 1 relative em of padding. The column mixin lets you choose the amount of columns you want and optional context and padding amounts, then performs the standard target / context = result formula on it.</p>
<p>So that our padding won&#8217;t break our grid, add box-sizing to every element:</p>
<pre><code class="css">* { -moz-box-sizing: border-box; -webkit-box-sizing: border-box; box-sizing: border-box; }
</code></pre>
<p>Now we can assign width to our article, figure, and aside elements:</p>
<pre><code class="css">#content {
    float: left;
    @include column(8);

    figure {
        @include column(5, $padding: 0);
        min-width: 240px;
        margin: 0 0 1rem 1rem;
        float: right;
    }
}
aside {
    float: left;
    @include column(4);
}
</code></pre>
<p><a href="http://thephuse.com/cms/wp-content/uploads/2012/05/desktopview1.jpg"><img src="http://thephuse.com/cms/wp-content/uploads/2012/05/desktopview1.jpg" alt="" title="Desktop View" width="624" height="403" class="alignnone size-full wp-image-1008" /></a></p>
<h2 id="addingbreakpoints">Adding Breakpoints</h2>
<p>Our page looks good now, at least on large screens. Rather than jump in right away and add a lot of media queries at standard breakpoints, we’re going to put in breakpoints based on our content. In other words, at points where our layout breaks, we&#8217;re going to adjust it with a media query based rule.</p>
<p>When we resize the window, it&#8217;s clear that around 800px window width, our article text is really getting squeezed by the image. This is a good spot to put in a breakpoint. Try it out for yourself by grabbing the corner of your browser window and shrinking it. </p>
<p>We can use another Sass mixin to make it easy:</p>
<pre><code class="css">@mixin breakpoint($size) {
 @media only screen and (max-width: $size) { @content; }
}</code></pre>
<p>Now we can include the mixin to stack and resize our columns:</p>
<pre><code class="css">#content {
    float: left;
    @include column(8);

    @include breakpoint(770px) {
        clear: left;
        @include column(12);
    }

aside {
    float: left;
    @include column(4);

    @include breakpoint(770px) {
        clear: left;
        @include column(12);
    }
}
</code></pre>
<p><a href="http://thephuse.com/cms/wp-content/uploads/2012/05/tabletview1.jpg"><img src="http://thephuse.com/cms/wp-content/uploads/2012/05/tabletview1.jpg" alt="" title="Tablet View" width="368" height="437" class="alignnone size-full wp-image-1010" /></a></p>
<p>We could take it a step further and use variables for the width; The Sass Way goes into more detail on <a href="http://thesassway.com/intermediate/responsive-web-design-in-sass-using-media-queries-in-sass-32">this and other Sass 3.2 features</a>.</p>
<p>More testing by resizing the browser gives us another breakpoint at 600px &#8211; we&#8217;ll drop the article text below the image here.</p>
<pre><code class="css">    @include breakpoint(600px) {
        min-width: 280px;
        margin: 0 auto;
        float: none;
    }
</code></pre>
<p><a href="http://thephuse.com/cms/wp-content/uploads/2012/05/phoneview1.jpg"><img src="http://thephuse.com/cms/wp-content/uploads/2012/05/phoneview1.jpg" alt="" title="Phone View" width="189" height="440" class="alignnone size-full wp-image-1009" /></a></p>
<p>Now, our site looks good at any browser width. The best part, though, is that using the Sass mixins and variables means that you can adjust the layout quite easily as you build and adjust a site design.</p>
<h2 id="goingforward">Going Forward</h2>
<p>While this is just a simple example, I hope it will help you cut down on the amount of time it takes to build your next responsive site!</p>
<p>Do you build responsive websites? What tools and methods do you use to streamline your work?</p>
]]></content:encoded>
			<wfw:commentRss>http://thephuse.com/development/build-responsive-websites-faster-with-sass/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Brief Matter</title>
		<link>http://thephuse.com/content-strategy/a-brief-matter/</link>
		<comments>http://thephuse.com/content-strategy/a-brief-matter/#comments</comments>
		<pubDate>Tue, 08 May 2012 16:57:35 +0000</pubDate>
		<dc:creator>Matt Herron</dc:creator>
				<category><![CDATA[Content Strategy]]></category>
		<category><![CDATA[brief]]></category>
		<category><![CDATA[client]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[copy]]></category>
		<category><![CDATA[copywriting]]></category>
		<category><![CDATA[creative]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[interview]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[project]]></category>
		<category><![CDATA[services]]></category>
		<category><![CDATA[strategy]]></category>
		<category><![CDATA[web]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://thephuse.com/?p=942</guid>
		<description><![CDATA[Content strategy starts where all client projects start: with the brief.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.flickr.com/photos/48778414@N04/6105873569/"><img class="size-full wp-image-977 alignnone" title="Compass and Binoculars" src="http://thephuse.com/cms/wp-content/uploads/2012/05/compass-binoculars600.jpg" alt="" width="600" height="250" /></a></p>
<p>Content strategy starts where all client projects start: <strong>with the brief</strong>.</p>
<h2>Content and Strategy</h2>
<p>Enough has been said over the past few years about <a title="Content-tious Strategy" href="http://www.alistapart.com/articles/contenttiousstrategy/">what</a> <a title="Content Strategy: The Rude Awakening" href="http://jointhecarnival.posterous.com/content-strategy-the-rude-awakening">content</a> <a title="Tinker, Tailor, Content Strategist" href="http://www.alistapart.com/articles/tinker-tailor-content-strategist/">strategy</a> <a title="The Complete Beginner's Guide to Content Strategy" href="http://www.uxbooth.com/blog/complete-beginners-guide-to-content-strategy/">is</a>. That song is so overplayed even the radio won’t touch it.</p>
<p>However, tradition demands we have a working definition to proceed, so we’ll go with a broad one from <em>A List Apart</em> <a title="The Discipline of Content Strategy" href="http://www.alistapart.com/articles/thedisciplineofcontentstrategy/ ">article by Kristina Halverson</a>:</p>
<blockquote><p>“Content strategy plans for the creation, publication, and governance of useful, usable content.”</p></blockquote>
<p>I also think that we all know by now that <strong>content is more than just copywriting</strong>. Web content today also includes videos and images, external files (like PDFs), contact forms, buttons (and other calls to action), maps, data tables, infographics, as well as the copy—titles, slogans, about pages, etc.</p>
<p>According to Halverson, it&#8217;s all about planning. A brief is a “useful, usable” way of putting it all down on paper (or .pdf). The content brief is a document that outlines all of the content (<a title="What Is Content Strategy" href="http://allday.cc/blog/what-is-content-strategy/ ">in context</a>).</p>
<h2>What Lucky Sap Gets The Job?</h2>
<p>Who, specifically, should take lead on the content brief? Anyone that can listen and take notes will do. Whether they’re a copywriter, content strategist, project manager, designer, developer, whatever.</p>
<p>Can you type? Then you&#8217;re good to go. Thorough, organized, communicative, good with words, thinks of the big picture: these are also good qualities to look for.</p>
<p>In any case, a brief isn&#8217;t built by one person. Projects have many <a title="Understanding Organizational Stakeholders for Design Success" href="http://www.boxesandarrows.com/view/understanding_organizational_stakeholders_for_design_success ">stakeholders</a>. A copywriter may put together the rough draft or write revisions, but it’s the whole team&#8217;s job to put the brief together in collaboration with a client.</p>
<p>Clients have input from multiple stakeholders in their own company, too, so be careful not to leave anyone out of the decision making process.</p>
<h2>What Goes Into a Good Content Brief?</h2>
<p>A brief must take into account <strong>everything</strong> on the project.</p>
<p>The brief should cover all of it: not only what the client’s goals are, but what tone of voice they prefer, what the timeframe looks like, what content should be on the site, what should be left out, how the content fits into the context of the design, editorial strategy, who is going to add new content, and whether or not they need formatting guidelines to follow.</p>
<p>A good brief is a vital source of information for everyone involved in a project. Designers, copywriters, and even developers should be able to refer to it while they work.</p>
<p><strong>Special note to designers and developers:</strong> a content brief is especially useful with clients who underestimate the work involved on a particularly complex project.</p>
<h2>A Brief Example</h2>
<p>This is the basic brief I use for website design projects. I often find myself adding new sections, quotes from clients (copy pasted from emails), and scribbling notes in the margins. If you don&#8217;t have to alter the brief to the context of the project, you&#8217;re probably missing something.*</p>
<ul>
<li><strong>Basic Details</strong></li>
<ol>
<li>Company Name</li>
<li>Contact Name</li>
<li>Project Start Date</li>
<li>Projected Finish Date</li>
<li>Will this be part of a larger communication or stand-alone?</li>
</ol>
<li><strong>Overview</strong></li>
<ol>
<li>What is the client expecting of the project?</li>
<li>Define the goals of the project.</li>
<li>What is the background and context for communication?</li>
</ol>
<li><strong>Background and Raw Material</strong></li>
<ol>
<li>What material has the client produced before? How did it perform?</li>
<li>How does this campaign fit in with other communications produced by the client?</li>
<li>What images, videos, copy, and other material has already been created?</li>
<li>What images, videos, copy, etc. is missing?</li>
</ol>
<li><strong>Target Audience</strong></li>
<ol>
<li>Who are we trying to reach? Why? How?</li>
<li>What mediums are we using to reach the users?</li>
<li>What is their profile? Do we need to develop <a title="Personas: Putting The Focus Back On The User" href="http://www.uxbooth.com/blog/personas-putting-the-focus-back-on-the-user/">personas</a>?</li>
<li>What do they think about the client?</li>
<li>What’s going on in the marketplace? How crowded is it?</li>
</ol>
<li><strong>The Core Message</strong></li>
<ol>
<li>What is the single, compelling message that must be communicated?</li>
<li>What supporting evidence is there to back up the claims being made?</li>
</ol>
<li><strong>The Unique Selling Point</strong></li>
<ol>
<li>What benefit does the core message provide to the audience?</li>
<li>What makes this different and compelling in the marketplace?</li>
<li>Why should the reader bother to read the copy and respond at all?</li>
</ol>
<li><strong>Creative Direction</strong></li>
<ol>
<li>How should the finished work look and feel?</li>
<li>Is there a brand style that must be adhered to?</li>
<li>Are there examples of similar work that can be used as a guide?</li>
<li>What’s the appropriate tone of voice?</li>
</ol>
</ul>
<p>After you’ve completed the brief, be sure to clear it with all stakeholders involved in the project. Each person may have their own perspective to add. The more people involved, the more comprehensive the brief will become.</p>
<p>The trickiest part of a good content brief is making sure that it covers all the angles. If it doesn’t cover everything, it may fall short or even fail entirely. Deadlines get missed, budgets run out, people get stressed out, and suddenly you’re drinking twelve cups of coffee a day, working weekends, or pulling a frantic all nighter.</p>
<p>Nobody wants that.</p>
<h2>The Interview Process</h2>
<p>When you’re taking the brief, you want to get into the mindset of an interviewer.</p>
<p>The person taking the brief has to ask the right kind of questions. Since there are usually multiple stakeholders involved in a project, be sure to talk to all of them. Interview them relentlessly. Ask the dumb questions. Be persistent. A bad assumption will cause you more work in the end, whereas a dumb question wastes a few minutes of time at most.</p>
<p>Also, don’t be afraid to call back and clarify. A good interviewer is thorough and goes back a second time if they feel like something is missing.</p>
<h2>Tweak It As You Go Along</h2>
<p>If someone realizes that the content brief is missing something—whether it’s a paragraph or a page or something bigger—the brief should be updated. If it’s a major change, be sure to notify your team! Nothing says waste of time like writing content that’s already been cut.</p>
<h2>Discussion</h2>
<p>Do you use content briefs in your projects? What kinds of questions do you ask your clients? Is there any place where content briefs fall short?</p>
<p><em style="font-size: 70%;">*Disclaimer: this brief outline is based off one from <a title="Buy the book at Amazon" href="http://www.amazon.com/Copywriting-Successful-Writing-Advertising-Marketing/dp/1856695689/ref=sr_1_8?ie=UTF8&amp;qid=1336083561&amp;sr=8-8 ">Copywriting: Successful Writing for Design, Advertising, and Marketing</a>. If you like and use the outline, we recommend that you buy the book. Especially if you’re interested in copywriting. It is an indispensable resource.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://thephuse.com/content-strategy/a-brief-matter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How The Phuse Hires</title>
		<link>http://thephuse.com/business/how-the-phuse-hires/</link>
		<comments>http://thephuse.com/business/how-the-phuse-hires/#comments</comments>
		<pubDate>Mon, 30 Apr 2012 15:00:28 +0000</pubDate>
		<dc:creator>James Costa</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[company]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[hire]]></category>
		<category><![CDATA[hiring]]></category>
		<category><![CDATA[hr]]></category>
		<category><![CDATA[human resources]]></category>
		<category><![CDATA[people]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://thephuse.com/?p=928</guid>
		<description><![CDATA[Interviewing and hiring people over the past year has solidified a process that goes beyond a standard interview procedure to make sure that the people we hire are a good fit for our company, and nobody’s time is wasted in the process.]]></description>
			<content:encoded><![CDATA[<p><div id="attachment_929" class="wp-caption alignright" style="width: 510px"><a href="http://www.flickr.com/photos/61565435@N03/6915259795/"><img src="http://thephuse.com/cms/wp-content/uploads/2012/04/hire-me-or-else.jpg" alt="" title="Hire me or else!" width="500" height="375" class="size-full wp-image-929" /></a><p class="wp-caption-text">Hire me or else! Illustration by Daniel Ferenčak</p></div><br />
Hiring is scary for a small business. Not only can it be tough to find someone who can handle the workload you need covered, but finding someone who can be a seamless extension of your business and maintain consistency with your level of work is even more difficult.</p>
<p>We have a high standard of design and development, and our clients come to us not only knowing that we’ll get the job done, but that we’ll do it well and exceed their wildest expectations. So when our business started growing and we had to hire more people, we knew that we had big shoes to fill.</p>
<p>Interviewing and hiring people over the past year has solidified a process that goes beyond a standard interview procedure to make sure that the people we hire are a good fit for our company, and nobody’s time is wasted in the process.</p>
<p>This process has been shaped and formed with the help of many others who are pros at the hiring process and have learned things the hard way like us. We hope you can use our hiring process to improve your own and find people who are a good fit for yourself, your company, and your clients.</p>
<h2>Why Do People Use Your Product or Service?</h2>
<p>Start by considering why people use your product or service. Do you serve a need that isn’t being met by anyone else? When clients think of your company, what do they think? Write down all those things and any brand promises that you have.</p>
<p>Next, if you’ve hired someone before that has been a success, think of <strong>why you hired them</strong>. Look at the emails/communications you initially had with them, and remind yourself of why you brought them in. Were they friendly and showed they read any listings you put out or about your company in general? Did they show excitement about the position and working with you?</p>
<p>Once you have all of these things written down, you know what kind of person you’re looking for. Everything in terms of skills and position requirements should only be figured out after this.</p>
<h2>The Listing (Details are Important)</h2>
<p>One thing we’ve learned about putting together awesome listings is writing out the responsibilities of the position that you’re hiring for, talking about your team and company, and mentioning what the new hire will be getting (pay, benefits, etc) in return for their work.</p>
<p>But more importantly than this, make sure you’re specific about all of the above &#8211; if you’re looking for a designer, are you looking for someone who has a specific style/designs in specific media (web, print, brand)?. If you’re looking for a developer, are you looking for someone who can take PSDs and bring them to life, or someone who can develop fully functional backends with a specific language (e.g. PHP, Ruby, etc)?</p>
<h2>Applications</h2>
<p>We’ve tried both forms for people to fill out and emails for people to apply, and there are definitely benefits to both. While forms can help make sure you get information you want and serve as a pre-interview, emails are our preferred method because it allows people to copy and paste messages and serves as an open conversation that shows how that person communicates.</p>
<p>Regardless, this is the part where you make the first cut of applicants. There are a few things we look for that tell us <strong>the person won’t be a good fit</strong>:</p>
<ul>
<li>They copy and paste a generic message they’re sending to every listing.</li>
<li>They use improper spelling or grammar (communication is really important to us).</li>
<li>They don’t have what we’re looking for in terms of skills or experience.</li>
<li>They give us something we didn’t ask for.</li>
<li>They don’t give us something we <em>did</em> ask for.</li>
</ul>
<p>However, if the person is a good fit:</p>
<ul>
<li>They send us a personalized message that tells us why they want to work with us and why they think we’re awesome.</li>
<li>They communicate clearly and sound excited about the position and opportunity.</li>
<li>They give us what we ask for and omit any irrelevant information.</li>
</ul>
<p>For every 25 applicants we generally get only 1 or 2 that fits the bill. Expect those kind of odds in your hiring process because good people are hard to find!<br />
Before the Interview</p>
<p>Once we’ve got the application and think that the person might be a good fit, we email them back and schedule a time to talk about the position and what it will be like working with us. At this point, we look for two things <strong>before the interview even happens</strong>:</p>
<ul>
<li>How long does it take them to respond?</li>
<li>Do they still seem excited and the same person as in the other email now that you’re communicating with them?</li>
<li>Are they on time for the interview? Is it easy to schedule an interview with them? (If they seem too busy, they probably have their priorities mixed up!)</li>
</ul>
<p>If they don’t do the above, raise your warning flags. In some situations we won’t even bother with getting them on the phone for an interview if getting ahold of them is too difficult because that’s a sure sign that working with them will be difficult as well.</p>
<h2>The Interview</h2>
<p>Ask anyone who works with us or has been interviewed to work with us &#8211; I’m terrible in interviews. I tend to talk more than I listen, and run out of questions to ask. To make sure that I’m on track and don’t get nervous (yes, interviewers get nervous, too), I have a list of points that I know I need to get through. Everything from questions to things I need to mention are written down so that the interview goes smooth. Sure, questions come up that aren’t written down, but in case I run out of things to ask about, I always have something to fall back on.</p>
<p>The way we do our interviews, we need an hour with the applicant to figure out whether or not they’re a fit. Not all interviews go the full hour, but blocking out that much time is important. <strong>We break down interviews like this</strong>:</p>
<ul>
<li>15 minutes &#8211; Screening</li>
<li>15-30 minutes &#8211; Questions and finding out about the applicant</li>
<li>15 minutes &#8211; Talking about The Phuse, why we’re awesome, answering questions, and talking about next steps</li>
</ul>
<h3>Screening</h3>
<p>This is the one part of our interview process that I think changed everything. Some companies screen interviewees before an interview is even set up, but we decided that we’d do it at the beginning of the interview. At this stage we talk candidly about the position, how much the position pays, what we offer in terms of other benefits, and the responsibilities of the person.</p>
<p>We also give the interviewee a chance to answer initial questions and hang up if they didn’t realize what they were getting into. This part of the process has knocked out a few applicants because the pay is too low for them or they don’t feel comfortable with any of the responsibilities.</p>
<p>If they’re good with everything we’ve thrown at them, we let them talk!</p>
<h3>Let Them Talk</h3>
<p>Since at this point I’ve likely talked for a good 75% of the time, I ask the applicant to talk about their experiences, how they got into what they’re doing now from the point they left high school (or sooner if they started sooner) to present day. During this part of the interview I tell them I’m going to be extremely quiet while taking notes to let them talk, and will ask them questions afterwards.</p>
<p>This is the closest thing we do to asking for resumes. I personally dread reading resumes, and think that hearing people talk about their previous positions and education helps me learn a lot more about them. I get to hear about positions they liked versus ones they didn’t like, how long they generally stay at companies, and what sort of responsibilities they had.</p>
<p>During this time, I’ll be writing down what I think of them &#8211; are they excited about certain positions more than others? Do I have questions about specific positions? You might also write down a scale for different criteria based on things you’re looking for that you’ll continually rate to see if they’re a good fit.</p>
<p>Afterwards, I’ll ask questions specific about the positions and about the position at hand, and most of the time it’ll be about things right off of the application. Do they know how to do X? How would they do Y? How do they feel about doing Z?</p>
<p><strong>I’m generally looking for:</strong></p>
<ul>
<li>Someone who is genuine and shows excitement and interest</li>
<li>Someone who knows what they’re talking about</li>
<li>Someone who Doesn’t half-ass answers to questions</li>
<li>Someone who can maintain a conversation and seems like an interesting person</li>
</ul>
<h3>Talk about the company and position</h3>
<p>Once I’m comfortable with everything that I’ve asked and have been told, I’ll generally talk about The Phuse. How did we start? Why are we shaped the way we are? Why do we do things the way we do? Who are our clients? All of this gives the interviewee a chance to take a break, listen, and form any questions they might have about the company (which is a really good sign).</p>
<h2>What’s Next?</h2>
<p>Once we’ve got everything for the interview wrapped up, we’ll talk about what happens next. For different positions, we have different ways of doing things. Generally, though, we’ll assign a small project not for any clients in particular to see how they do. For this “test”, we ask the applicant to only work <em>one hour</em>. We give a complete brief, and tell them exactly what we’re looking for.</p>
<h3>Here are some project tests that you can use to evaluate potential employees:</h3>
<p>For <strong>developers</strong>, the test is generally on an application page we’ve already done. We tell them to look at it and figure out how they’d develop certain technical components of it, and then let them hack away for the rest of the hour. Through this we find out:</p>
<ul>
<li>How they analyze things and if they know how to get the job done</li>
<li>How much they get done</li>
<li>The quality of the work they get done</li>
<li>How they communicate what they’d like to get done and how long they budget for it to be completed</li>
<li>What deadline they set for themselves and if they meet it</li>
</ul>
<p>For <strong>designers</strong>, we give a wireframe to work off of or a simple brief with things that need to be done, and let them have at it. Again, we’re looking at:</p>
<ul>
<li>How they analyze any problems in the design</li>
<li>How they follow the brief and style/brand guides</li>
<li>How much they get done</li>
<li>The quality of the work they get done</li>
<li>How they communicate their decisions</li>
<li>What deadline they set for themselves and if they meet it</li>
</ul>
<p>None of this work is for any current clients and the work is just to see how they do, but we do pay for the hour regardless, at the rate they’d like to be paid.</p>
<p>If everything checks out and other members of the team are happy with the product, we’ll ask them on their first project with us. During this part of the process, we’ll do the same thing &#8211; we’ll make sure they deliver on time, deliver what they say they’re going to, and make sure the quality is up to par. Again we assess things and decide whether or not it’s a good fit &#8211; if not, we don’t show anything to the client, don’t charge the client, and move on.</p>
<h2>How Do You Hire?</h2>
<p>These are the processes that have helped us find people that are a good fit for our team. It’s important to be thorough in the interviewing process, and to test applicants on a project before we agree to any sort of contract. That gives us a chance to test each other out (both employer and employee) and decide if we’re a good fit for each other.</p>
<p>What works for you when you hire new employees? Do you interview extensively or let the work speak for itself? How hard is it to find a good fit for your company? Share your stories with us in the comments!</p>
]]></content:encoded>
			<wfw:commentRss>http://thephuse.com/business/how-the-phuse-hires/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>So You&#8217;ve Got a Great Idea for a Website. Now What?</title>
		<link>http://thephuse.com/business/so-youve-got-a-great-idea-for-a-website-now-what/</link>
		<comments>http://thephuse.com/business/so-youve-got-a-great-idea-for-a-website-now-what/#comments</comments>
		<pubDate>Tue, 24 Apr 2012 16:00:59 +0000</pubDate>
		<dc:creator>Matt Herron</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Content Strategy]]></category>
		<category><![CDATA[Design and Usability]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[build]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[entrepreneur]]></category>
		<category><![CDATA[great idea]]></category>
		<category><![CDATA[help]]></category>
		<category><![CDATA[hire]]></category>
		<category><![CDATA[how]]></category>
		<category><![CDATA[idea]]></category>
		<category><![CDATA[portfolio]]></category>
		<category><![CDATA[site]]></category>
		<category><![CDATA[tips]]></category>
		<category><![CDATA[tricks]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[web app]]></category>
		<category><![CDATA[website]]></category>
		<category><![CDATA[when]]></category>
		<category><![CDATA[where]]></category>
		<category><![CDATA[who]]></category>

		<guid isPermaLink="false">http://thephuse.com/?p=913</guid>
		<description><![CDATA[The best way to take your idea from conception to completion, and make sure your site gets built as close as possible to the way you envisioned it, is to know exactly what you’re getting yourself into.]]></description>
			<content:encoded><![CDATA[<p><div id="attachment_919" class="wp-caption alignright" style="width: 650px"><a href="http://www.flickr.com/photos/27954776@N04/3168683736/"><img src="http://thephuse.com/cms/wp-content/uploads/2012/04/lightbulb.jpg" alt="Lightbulb!" title="Lightbulb!" width="640" height="428" class="size-full wp-image-919" /></a><p class="wp-caption-text">What the inside of your head looks like when you get a bright idea.</p></div>Have you ever had a great idea for a website? Have you ever been at a loss as to how to build it? Is it even a good idea in the first place? Who should you hire to build it?</p>
<p>It&#8217;s one thing to have an <em>idea</em> for a site. Turning that idea into an elegant, functional and user-friendly website is another monster entirely.</p>
<p>The best way to take your idea from conception to completion, and make sure your site gets built as close as possible to the way you envisioned it, is to know exactly what you’re getting yourself into.</p>
<h2>1. Determine What It Is</h2>
<div id="attachment_920" class="wp-caption alignright" style="width: 437px"><a href="http://www.flickr.com/photos/96726028@N00/2211431161/"><img src="http://thephuse.com/cms/wp-content/uploads/2012/04/questionmark.jpeg" alt="Question Mark!" title="Question Mark!" width="427" height="640" class="size-full wp-image-920" /></a><p class="wp-caption-text">The obstacle to avoid.</p></div>
<p><em>The point at which “It’s a website” isn’t good enough anymore.</em></p>
<p>Start by making sure that the idea you have in mind really is a website.</p>
<p>Some good questions to ask yourself include:</p>
<ul>
<li>How is building a website going to benefit my business? My art? Myself?</li>
<li>Is the internet a medium where my idea can thrive? (Hint: not if it’s a 500 page novel!)</li>
<li>Is my idea original? (If you don’t know, research it!)</li>
<li>Will people use the site?</li>
</ul>
<p>In case you hadn’t noticed, there’s a lot of crap on the internet. It’s mostly crap, in fact. If I had to estimate the amount of crap on the internet like a jar of jelly beans, I’d say that 95% of websites on the internet are worthless crap. And that’s me being generous.</p>
<p>Another common misconception: “I need a website!” We’ve all heard this from clients, and when web tinkerers ask their clients questions like “Why?” and “What’s going on it?” and “What will it say?” they often get a blank stare in response. Don&#8217;t be that person.</p>
<h2>2. Outline the Goals</h2>
<p><em>Where’s the finish line?</em></p>
<p>Every project has a desired outcome. Once you figure out what the website <em>is</em>, you have to <strong>figure out what it’s going to accomplish</strong>. Ask yourself a few more questions:</p>
<ul>
<li>What actions will users be performing on the site?</li>
<li>How often will users be visiting?</li>
<li>Do I need a blog or other regularly updated content?</li>
<li>Do I want to sell products on the site?</li>
</ul>
<p>These are the kinds of questions we ask clients in our <a href="http://phuse.wufoo.com/forms/project-questionnaire/" title="The Phuse Project Questionnaire">project questionnaire</a>. They help us evaluate exactly what our clients need out of their website, what the end goals are, and what needs to be built. That should help get you started.</p>
<p>Don’t reinvent the wheel. Trying to compete with a behemoth like Amazon by creating an eCommerce site without any unique spin on it is a sure path to failure. Not that you can&#8217;t compete with them: but know what you&#8217;re up against.</p>
<p>Also, if your idea can be built off an existing platform, then let that platform do the legwork for you. It will save you lots of time, money, and headaches. A lot of app ideas start that way. Facebook apps, for example, are built off of an existing platform and they have <a href="https://developers.facebook.com/blog/post/2012/02/15/early-success-stories--timeline-apps-and-open-graph/" title="Facebook App Success">seen a lot of success</a>.</p>
<p><a href="http://mashable.com/2011/06/02/website-flowchart/" title="Website Flowchart">This flowchart is also a savvy litmus test for your website idea.</a></p>
<h2>3. Figure Out How It&#8217;s Going To Be Built</h2>
<p><em>Learn what tools you need and define the scope of the project.</em></p>
<p><strong>Tools</strong></p>
<p>Website vary greatly in the amount of time, effort, and money it takes to build them. </p>
<p>A photography portfolio is on the lower end of the time/effort/money scale, for example. They are not typically too complex, and the web has been around long enough that <a href="http://webdesignledger.com/tools/10-best-content-management-systems-for-designers" title="10 Best Content Management Systems for Designers">free, customizable content management systems</a> are available in abundance that are adequate to get the job done. Same with blogs. You can use an existing platform (like <a href="http://www.tumblr.com/" title="Tumblr">Tumblr</a> or <a href="http://www.blogger.com" title="Blogger">Blogger</a>), or you can download <a href="http://wordpress.com/" title="Wordpress">WordPress</a> and install it on your own server.</p>
<p>Not every website is so easy to create. Web apps are more complex and costly due to the necessity for back-end development (read: complex programming for customized functionality). eCommerce sites can be a massive drain on time and budgets simply because of their sheer size. Adding all the products, descriptions, a checkout system, user login, a settings panel, etc., and keeping everything up-to-date requires a lot of time and manpower.</p>
<p><strong>Scope</strong></p>
<p>If you don&#8217;t know enough to figure out the scope of your project yourself, <a href="http://phuse.wufoo.com/forms/project-questionnaire/" title="The Phuse Project Questionnaire">ask an experienced web design/development company (like us!) for an estimate</a>. They have enough experience to estimate cost and time accurately.</p>
<p>Underestimating what it takes to build a website is a very common pitfall with uninitiated entrepreneurs, and can become a point of contention if these issues are not cleared up early in the project.</p>
<p>Web Style Guide has <a href="http://webstyleguide.com/wsg3/1-process/8-project-charter.html" title="Project Charter">a great article on scope, risk assessment, budget, and much more</a>.</p>
<h2>4. Find Someone to Build It</h2>
<p><em>Do it yourself? — or hire a pro?</em></p>
<p>Now that you know what kind of website you want to build and how much work it will take to build it, you have to decide whether you&#8217;re going to build it yourself or hire someone to build it for you.</p>
<p>If you are comfortable with computers, and the idea is pretty simple (a blog, for example), then you might well be able to do it yourself. But there is a lot to learn if you&#8217;ve never tried building a website before. Even with all the free, customizable software out there, delving into the coding side of things can be extremely frustrating for first-timers. Let alone metrics and marketing, social media, and professionally tailored design.</p>
<p>Learning these skills takes time and you may be better off investing some money to have a group of professionals build it for you.</p>
<p>This is especially true with web applications, which are notoriously more complex than your standard website. For these you often need a design and a development team.</p>
<h2>5. Find The Time and Money to Build It</h2>
<p><em>… and come prepared!</em></p>
<p><strong>Money Costs</strong></p>
<p>Whether you do it yourself or hire someone to build it, everything costs time and money. For those that don&#8217;t know, hosting typically charges per month, and domain names charge per year. Web development companies either charge hourly or a flat fee for the whole project; there are benefits and drawbacks to both ways that we won’t go into right now.</p>
<p>Website projects cost anywhere from $500 to $50,000+. It would be impossible to list all the different possibilities. If you aren’t sure, crunch the numbers yourself or (once again) get a professional estimate.</p>
<p><strong>Time Costs</strong></p>
<p>Even if you decide to use all free software (i.e. a wordpress blog with a free theme), and do it all yourself, time is money, and the time you invest into building the site is time that could be spent creating content or marketing it.</p>
<p>Which brings us to another point: make sure you have valuable content ready before you launch the site. That means investing time and effort.</p>
<p>There is nothing more wasteful in the web design business than a pretty site with zero content value. Think Traffic has <a href="http://thinktraffic.net/write-epic-shit" title="Write Epic Shit">an excellent article on the value of epic content</a> with specific examples from successful websites.</p>
<h2>6. Make Sure You&#8217;ve Got The Follow Through</h2>
<p><em>Follow through is everything.</em></p>
<p>The biggest killer of good website ideas is a lack of follow through. Make sure—before you start—that you have the nerve to see it through. Overnight successes are the exception, not the rule. Sometimes new brands and products stagnant for years before they find success. But then, that’s true about many things in life, and if you’re really serious about your idea, you already knew that.</p>
<p>Once the site is built, your job is far from over! The type of follow up depends largely on what type of site you’re running. With a blog, for example, nearly all of the time and effort are put in after the site launches. Content continually needs to be added. </p>
<p>If you built a portfolio, it’s important to keep it updated and relevant. Last year <a href="http://googleblog.blogspot.de/2011/11/giving-you-fresher-more-recent-search.html " title="Giving you fresher, more recent search results">Google added a relevancy factor to its search rankings</a>. The idea is that people want to find fresh, relevant content.</p>
<p>Cameron Kellogg also has <a href="http://www.globalrhetoric.com/2011/09/17/follow-through/ " title="Follow Through">some good advice about follow through from a business standpoint</a>.</p>
<h2>Final Words</h2>
<p>If you’re still not sure whether your website idea is worth pursuing, <a href="http://phuse.wufoo.com/forms/project-questionnaire/" title="The Phuse Project Questionnaire">ask us</a>! We love hearing about new ideas, and who knows, maybe we’re just the people you need to build it for you.</p>
<p>There are a million opportunities out there for a successful website, whether it’s a business or a blog. Yours may be the next big thing. </p>
<p>What now?</p>
]]></content:encoded>
			<wfw:commentRss>http://thephuse.com/business/so-youve-got-a-great-idea-for-a-website-now-what/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Long-term, Sustainable Business Models and The Lessons We’ve Learned</title>
		<link>http://thephuse.com/business/long-term-sustainable-business-models-and-the-lessons-weve-learned/</link>
		<comments>http://thephuse.com/business/long-term-sustainable-business-models-and-the-lessons-weve-learned/#comments</comments>
		<pubDate>Thu, 19 Apr 2012 15:10:33 +0000</pubDate>
		<dc:creator>James Costa</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[clients]]></category>
		<category><![CDATA[customers]]></category>
		<category><![CDATA[expand]]></category>
		<category><![CDATA[grow]]></category>
		<category><![CDATA[growth]]></category>
		<category><![CDATA[happy]]></category>
		<category><![CDATA[investment]]></category>
		<category><![CDATA[labor of love]]></category>
		<category><![CDATA[long-term]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[sustainable]]></category>

		<guid isPermaLink="false">http://thephuse.com/?p=903</guid>
		<description><![CDATA[Learning to balance our business without sacrificing the quality of work and customer service that makes our clients happy is a journey. Here are some lessons that we’ve learned along the way.]]></description>
			<content:encoded><![CDATA[<p><div id="attachment_906" class="wp-caption alignright" style="width: 384px"><a href="http://www.flickr.com/photos/jason-samfield/4929948998/lightbox/"><img src="http://thephuse.com/cms/wp-content/uploads/2012/04/sapling-growth.jpg" alt="" title="The Model of Growth" width="374" height="500" class="size-full wp-image-906" /></a><p class="wp-caption-text">The model of growth. Requires tender love and care at all times. Don't forget to water.</p></div>Running a business is an investment. For The Phuse, the investment has often been more than monetary. Our work is a labor of love. It’s not just about making money, but creating quality products and making our clients happy.</p>
<p>But for us, part of making our clients happy is being able to fulfill their needs. While we’ve managed to make our clients happy for years, we’ve realized that it’s time to put the gears in motion and grow with our clients. As their needs expand, our ability to meet those needs must grow as well.</p>
<p><strong>Learning to balance our business without sacrificing the quality of work and customer service that makes our clients happy is a journey.</strong> Here are some lessons that we’ve learned along the way.</p>
<h2>The Fork in the Road</h2>
<p>The Phuse has always been a small business, and we pride ourselves on intimacy with our clients and with our team members. But we’re at a crucial point where the decision needs to be made as to whether the business grows, or stays the same size. <strong>We’ve chosen to grow.</strong></p>
<p>Not being well-versed in the theories of business management, I started looking around for some good advice, and a friend of mine (<a href="http://www.seebq.com/">Charles</a>) told me about a program he’s involved in that really changed the shape of his Ruby on Rails development shop, Highgroove.</p>
<p>The program is called <a href="http://accelerator.eonetwork.org/" title="Entrepreneur's Organization Accelerator">The Entrepreneur’s Organization Accelerator</a> and it allows businesses of roughly the same size (making $250,000 to $1,000,000 in sales each year) to meet on a frequent basis to figure out how to solve problems they’re having (with a bit of great networking as well). Each group is a small packet of specifically-chosen people who are at about the same place in their business.</p>
<p>The program encourages participants to move up to the Entrepreneur’s Organization (at which point the business is making over $1,000,000 per year). In the U.S., a staggering 95% of businesses never cross this threshold.</p>
<p>Getting referred to the program by Charles landed me a screening interview which got me excited (and a little nervous) about what’s next. The decision to join the EOA is a big one that means we’re committing to <em>growing</em> the business.</p>
<p>It’s a tough decision, but one that we believe will benefit The Phuse in the long run.</p>
<h2>A Stereotype: Entrepreneurs Are Only Interested in Making Money</h2>
<p>There’s a really dirty stereotype that says that Entrepreneurs are more interested in exit plans than they are about building long-lasting and sustainable businesses. They don’t want a good business model, they want a big paycheck and to be able to wash their hands afterwards.</p>
<p>Of course, not all entrepreneurs think like this and they get a bad rap because of it. But The Phuse is not like that. It has never been about the exit strategy. The businesses we want to create offers <em>careers</em>, not <em>jobs</em>; that means a long-term strategy.</p>
<p>I also hate being called an entrepreneur because for me it’s never been about making money. It’s always been about making quality products that our clients love. So the thought of trying to make <em>more</em> money still seems strange to me.</p>
<h2>Money is the Food of a Healthy Business</h2>
<p>However, part of running a successful and healthy business <em>is</em> about making money. We have bills to pay, and the expenses we have even as a virtual shop (bank fees, currency exchange fees, on top of normal operating expenses most businesses have) increase with every hire we make.</p>
<p>We want a stable environment for our team where we’re not jumping between heavy loads of projects and dead-zones where there’s no client work to handle. An unsteady workload makes it harder for us to pay our bills, and even harder to grow at the rate we want to grow at.</p>
<p>Last month we brought on Jessica to help us out with sustaining a consistent load throughout the year. Then we realized we couldn’t handle all of the development work we had, so we had to bring on Tamera to help Jenna out with development. Now we’re at a point where we could still stand to hire another developer as well as another designer to help the team to meet its demands. The cycle never ends as we try to strike a healthy balance while our company grows.</p>
<p>That balance is important for a long-term business model, and every effort is being made to find that sweet spot as we expand. We want our business to be healthy and our people (employees and clients!) to be happy, and if we can get the money flow figured out the rest will be easy, and we can focus on doing what we love.</p>
<h2>Taking Things to the Next Level</h2>
<p>I’ve always been about taking things to the next level with myself personally and professionally. When I realized there were people out there better that I was at Javascript and more complex development, I recruited people that had those skills. When I realized there were people whose styles of design I wanted to tap into, we brought them on.</p>
<p>To this day we continue to hire people with better experiences and different skills to take our entire team to the next level with what we could offer our clients. We’re very picky with who we bring on our team, and we want to make sure we offer things to awesome people who want to be on it so that it makes sense for them and for us.</p>
<p><strong>Growing our business is also about taking things to the next level.</strong> Every change we make to the business is aimed at the same end result: a long-lasting, sustainable business model.</p>
<h2>Looking Forward</h2>
<p>I’ve been meaning to write this article for a good part of the last year. Looking back since that year, The Phuse has doubled in revenue and quadrupled in how many resources (team members) we need to get through all the work we have in a week. This is a blessing to me because I get to live my dream every day while I help other people live theirs.</p>
<p>But what does that say about next year? Or, better yet, five years from now?</p>
<p>We’re not interested in investors or getting outside funding, and it’s not about selling out or exit strategies. I’m not interested in taking myself out of the business that I’ve put blood, sweat, and tears into. Far from it.</p>
<p>Learning what we have the last two years about running the business we’ve built today, we want to grow our business, not only for ourselves but for our clients too. There are enormous benefits to growing so that we can grow <em>with</em> them and make sure we always have available resources to help them with their projects.</p>
<p>At various points throughout the last two years we’ve had to move around resources to make things work from a project planning perspective. We don’t like that, and we’re doing everything in our power to give us more flexibility.</p>
<p>We want to make sure that there’s a consistency from our end so that our clients can rest comfortably knowing that the people working on their projects are so familiar with the project and the client that they don’t even have to ask questions. This also gives us the ability to offer better benefits to our team to keep on quality team members. <strong>Keeping quality team members is just another quality that a sustainable business looking at long-term goals can offer.</strong></p>
<h2>Growing the Business and Growing as People</h2>
<p>In growing we know there’s going to be a lot we need to learn, and we know the experiences from clients and the Entrepreneur’s Organization will be valuable in expanding a business in a way that won’t affect any aspect of it negatively, from service quality to cost and beyond.</p>
<p>Writing things down always makes it official for me. It means looking at the idea square in the face and saying “I can do this”. <strong>The key to expanding The Phuse will be in keeping things simple, and keeping people around that inspire and motivate us on a daily basis.</strong> Those people make our dreams a reality every day.</p>
<p>We&#8217;re extremely excited about this new chapter in The Phuse. This doesn’t mean any changes to what we’ve been committed to (awesome customer service for our clients, a killer environment to work in for our team), but a realization that if we want to keep being able to offer this to our growing clients, we need to grow too.</p>
]]></content:encoded>
			<wfw:commentRss>http://thephuse.com/business/long-term-sustainable-business-models-and-the-lessons-weve-learned/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How Working Remotely Works for Us</title>
		<link>http://thephuse.com/business/how-working-remotely-works-for-us/</link>
		<comments>http://thephuse.com/business/how-working-remotely-works-for-us/#comments</comments>
		<pubDate>Tue, 03 Apr 2012 13:56:52 +0000</pubDate>
		<dc:creator>Matt Herron</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[basecamp]]></category>
		<category><![CDATA[empathy]]></category>
		<category><![CDATA[follow the sun]]></category>
		<category><![CDATA[harvard business review]]></category>
		<category><![CDATA[hours]]></category>
		<category><![CDATA[location]]></category>
		<category><![CDATA[negativity]]></category>
		<category><![CDATA[pace]]></category>
		<category><![CDATA[remote]]></category>
		<category><![CDATA[remotely]]></category>
		<category><![CDATA[scheduling]]></category>
		<category><![CDATA[studio]]></category>
		<category><![CDATA[time zones]]></category>
		<category><![CDATA[work]]></category>
		<category><![CDATA[working]]></category>

		<guid isPermaLink="false">http://thephuse.com/?p=896</guid>
		<description><![CDATA[Four excellent reasons why our team excels despite our vast differences in location. A team working remotely can be just as effective—or more so—than a team that works out of the same studio.]]></description>
			<content:encoded><![CDATA[<div id="attachment_898" class="wp-caption alignright" style="width: 510px"><a href="http://www.flickr.com/photos/60364452@N00/297992956/"><img class="size-full wp-image-898" title="Time Zone Clocks" src="http://thephuse.com/cms/wp-content/uploads/2012/04/timeZoneClocks.jpg" alt="" width="500" height="375" /></a><p class="wp-caption-text">We have to keep track of time differences, but it&#39;s often to our benefit.</p></div>
<p>As you may already know, all of the awesome people employed by The Phuse work remotely.</p>
<p>Our team is separated by oceans, mountain ranges, country borders, and time zones. And despite the generally accepted misgivings about working remotely, we&#8217;ve managed to build a company on it.</p>
<p>We would even say that a team working remotely can be just as effective—or more so—than a team that works out of the same studio.</p>
<p>Apart from <a href="../../business/30-hours-are-better-than-40/">our flexible schedules and thirty hour work weeks</a>, we&#8217;ve come up with a few more reasons why working remotely is beneficial to our team.</p>
<h2>1. Work at your own pace, set your own hours</h2>
<p>Our work is task and goal oriented. With people located all over the world, that&#8217;s the best way we&#8217;ve found to keep projects on task. Our team members can work whenever they want to. The only caveat we have is that they have to meet their deadlines.</p>
<p>Of course, this process only works if tasks are completed on time and to spec, so before you give people the kind of freedom that a task-oriented work process allows, make sure you can rely on them, or be prepared to pick up the slack.</p>
<h2>2. Negativity is contagious</h2>
<p>The biggest benefit to working in a studio is that you are surrounded by like-minded creative people all day long. You can feed off their energy. However, you can also be hindered by their negativity.</p>
<p><a href="http://www.uxbooth.com/blog/invisible-armor-protecting-your-empathy-at-work/">If you are an empath, there are ways to get around it</a>. But none better than working where you want, when you want (see #1). It&#8217;s easy to close Skype and focus when you work from home.</p>
<p>On the flip side, sometimes working alone gets lonely. That&#8217;s why we communicate frequently with our teammates, have weekly motivational meetings, send loads of emails, advocate coffee breaks on Skype, and condone off-topic conversations when deadlines aren&#8217;t looming.</p>
<h2>3. Shrewd scheduling, and following the sun</h2>
<p>It didn&#8217;t happen on purpose, at first. But as it turns out our lead designers for the past few months have been located in UK while our coders are in the US and Canada. That gives the design team a head start of at least six hours. Our day is extended and we can actually get more work done in a day than any team that works out of the same studio.</p>
<p>The Harvard Business Review blogged about how <a href="http://blogs.hbr.org/cs/2012/03/how_virtual_teams_can_outperfo.html">Virtual Teams Can Outperform Traditional Teams</a> recently, and when we read that article we were pleasantly surprised to find that were were already following most of their advice.</p>
<h2>4. We handpick our team</h2>
<p>This method wasn&#8217;t allowed in gym class when choosing kickball teams, but in the real world cherry picking the best talent from the crowd is not only allowed but encouraged.</p>
<p>A bigger company may be able to find talent in different parts of the world and relocate them, but with limited resources we are very grateful that the internet allows us to collaborate with people in vastly different locations without forcing anyone to leave their favorite internet hotspot.</p>
<p>We have chosen the best applicants from all over the world because they&#8217;re good at what they do, and not because they live near us.</p>
<p>We aren&#8217;t limited by location. We surpass it.</p>
<p><center>*    *    *</center>Not quite convinced? Still need another reason to work remotely? The new Basecamp came out a few weeks ago and has <a href="http://37signals.com/svn/posts/3145-hows-the-new-basecamp-doing-so-far">recorded multiple milestones marking the improved product&#8217;s success</a>. With project management software of this caliber, who needs an office anyways?</p>
]]></content:encoded>
			<wfw:commentRss>http://thephuse.com/business/how-working-remotely-works-for-us/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Professionalism as a State of Mind</title>
		<link>http://thephuse.com/writing-tips/professionalism-as-a-state-of-mind/</link>
		<comments>http://thephuse.com/writing-tips/professionalism-as-a-state-of-mind/#comments</comments>
		<pubDate>Tue, 27 Mar 2012 13:34:59 +0000</pubDate>
		<dc:creator>Matt Herron</dc:creator>
				<category><![CDATA[Productivity]]></category>
		<category><![CDATA[Resources]]></category>
		<category><![CDATA[Writing Tips]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[creating]]></category>
		<category><![CDATA[creative]]></category>
		<category><![CDATA[designing]]></category>
		<category><![CDATA[failure]]></category>
		<category><![CDATA[freezing up]]></category>
		<category><![CDATA[getting things done]]></category>
		<category><![CDATA[out of love]]></category>
		<category><![CDATA[professionalism]]></category>
		<category><![CDATA[success]]></category>
		<category><![CDATA[work]]></category>
		<category><![CDATA[working]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://thephuse.com/?p=889</guid>
		<description><![CDATA[Getting too close to your work can get in the way of actually <em>doing</em> your work. Acting like a pro is the solution.]]></description>
			<content:encoded><![CDATA[<div id="attachment_890" class="wp-caption alignright" style="width: 370px"><a href="http://thephuse.com/cms/wp-content/uploads/2012/03/300spartanphalanx.jpg"><img src="http://thephuse.com/cms/wp-content/uploads/2012/03/300spartanphalanx.jpg" alt="Spartan warriors were pros." title="300spartanphalanx" width="360" height="237" class="size-full wp-image-890" /></a><p class="wp-caption-text">The Spartan warriors were professionals and they acted like it.</p></div>
<p>Getting too close to your work can get in the way of actually <em>doing</em> your work.</p>
<p>Have you ever given up on a project even though the end was in sight? Have you ever had a brilliant idea that you never tried to execute because the idea of failure was too intimidating? Maybe you’re still telling yourself that you’ll write that novel—”one day”.</p>
<p>Wouldn’t it be nice not to have to deal with all that negativity? The solution is simple: adopt the attitude of a professional.</p>
<p>Getting too close won’t be a problem ever again.</p>
<h2>Professional Distance</h2>
<p>Last week, when we were talking about <a href="http://thephuse.com/business/why-you-should-throw-away-the-best-idea-you-ever-had/">throwing your best ideas in the trash</a>, I characterized the problem of getting too close as a light so bright it blinds you, and that&#8217;s often how it seems from a first-person perspective.</p>
<p>If you&#8217;re too close to a project, and you care too much about its success or failure, it can blind you, freeze you up, or make you give up entirely.</p>
<p>That&#8217;s why throwing your ideas away works, because treating your ideas as if they can be discarded keeps them at an appropriate professional distance.</p>
<h2>Pressfield&#8217;s <em>The War of Art</em></h2>
<p><a href="http://thephuse.com/cms/wp-content/uploads/2012/03/war-of-art.png"><img src="http://thephuse.com/cms/wp-content/uploads/2012/03/war-of-art.png" alt="Cover, Pressfield&#039;s The War of Art" title="The War of Art" width="462" height="725" class="alignright size-full wp-image-891" /></a><br />
Keeping your work at a distance is one way to tell the professional from the amateur in any job, whether it&#8217;s writing, designing, coding, or running a business.</p>
<p>In <a href="http://www.stevenpressfield.com/the-war-of-art/"><em>The War of Art</em></a>, Steven Pressfield explains how adopting the attitude of a professional is advantageous, and how it keeps you in the game:</p>
<blockquote><p>
&#8220;The professional, though he accepts money, does his work out of love. He has to love it. Otherwise he wouldn&#8217;t devote his life to it of his own free will.</p>
<p>The professional has learned, however, that too much love can be a bad thing. Too much love can make him choke. The seeming detachment of the professional, the cold-blooded character to his demeanor, is a compensating device to keep him from loving the game so much that he freezes in action. Playing for money, or adopting the attitude of one who plays for money, lowers the fever.&#8221;</p></blockquote>
<p>You can love your work and still act like a pro. Not only is acting like a professional a buffer between you and the ruination of failure, but it&#8217;s a buffer between you and your work that makes it easier to get things done, too.</p>
<p>Among other things, Pressfield writes that a professional also:</p>
<ul>
<li>Shows up every day.</li>
<li>Shows up no matter what.</li>
<li>Is committed over the long haul.</li>
<li>Plays for stakes that are high and real.</li>
<li>Has a sense of humor about his job.</li>
</ul>
<div align="center">*    *    *</div>
<p>For a full explanation of Resistance, the force that keeps us from doing our work, and Pressfield&#8217;s professional solution, we highly recommend you pick up a copy of <a href="http://www.stevenpressfield.com/the-war-of-art/"><em>The War of Art</em></a>.</p>
<p>We get nothing from you clicking that link and buying the book. You, however, will have just acquired one of those rare and elusive gifts that keeps on giving.</p>
]]></content:encoded>
			<wfw:commentRss>http://thephuse.com/writing-tips/professionalism-as-a-state-of-mind/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Value of Appreciation</title>
		<link>http://thephuse.com/business/the-value-of-appreciation/</link>
		<comments>http://thephuse.com/business/the-value-of-appreciation/#comments</comments>
		<pubDate>Mon, 19 Mar 2012 16:00:51 +0000</pubDate>
		<dc:creator>James Costa</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Productivity]]></category>
		<category><![CDATA[advice]]></category>
		<category><![CDATA[appreciation]]></category>
		<category><![CDATA[awesome]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[clients]]></category>
		<category><![CDATA[coworkers]]></category>
		<category><![CDATA[deadlines]]></category>
		<category><![CDATA[good and bad]]></category>
		<category><![CDATA[late nights]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[teamwork]]></category>
		<category><![CDATA[timelines]]></category>
		<category><![CDATA[value]]></category>

		<guid isPermaLink="false">http://thephuse.com/?p=883</guid>
		<description><![CDATA[If it weren’t for our amazing clients, our team wouldn’t be able to afford to do what we all love to do for a living. It’s pretty clear just sitting in on our team chats and meetings with clients that the appreciation goes both ways. It wasn’t until recently, however, that I realized how important it really is to feel appreciated when times are tough.]]></description>
			<content:encoded><![CDATA[<p>We’re lucky to have awesome relationships with our clients, and since we’re pretty picky with who we work with in the first place, we’re always very appreciative of one another.</p>
<p>If it weren’t for our amazing clients, our team wouldn’t be able to afford to do what we all love to do for a living. It’s pretty clear just sitting in on our team chats and meetings with clients that the appreciation goes both ways. It wasn’t until recently, however, that I realized how important it really is to feel appreciated when times are tough.</p>
<h2>Positivity Is Contagious</h2>
<p><a href="http://www.flickr.com/photos/71419691@N00/2394514059/"><img src="http://thephuse.com/cms/wp-content/uploads/2012/03/fabulous-high-five.jpg" alt="&quot;Fabulous&quot; High Five" title="&quot;Fabulous&quot; High Five" width="425" height="640" class="alignright size-full wp-image-885" /></a>I’d like to think I’m a pretty nice guy. I’ve been known to overuse phrases like “awesome”, “thank you”, and “you’re the best” during the day when talking to my team or to clients to thank them for pulling together awesome work (see? I did it again), or just being plain awesome (this is getting a little sickening), since I can’t physically give them high fives.</p>
<p>So when clients tell us that one of the best decisions they made in running with their idea was working with us, the whole team gets all bubbly inside. Knowing how <em>that</em> feels makes me remember that it’s my responsibility to pass it on to others because <em>positivity is contagious</em>.</p>
<p>But positivity <em>isn’t only for the good times</em>. It’s even more important when times are tough. When projects aren’t going well, or something is behind, or there’s a big bug that someone is trying to fix—it’s incredibly important to show appreciation then as well.</p>
<h2>Appreciated Also Means Motivated</h2>
<p>Last weekend I was working on a project with a pretty tight timeline. One of our regular clients needed some help meeting a deadline, and I had to put a whole weekend into getting everything together in time for the launch.</p>
<p>Throughout the entire process the client kept good tabs on who was where and who was doing what through calls and IMs. He also kept a running list of things that needed to be done. Not only that, but he was incredibly patient as well. That’s the kind of appreciation we’re looking to achieve, and it helped us meet our tight deadline.</p>
<p>For example, at some point on Sunday (read: the day we needed to launch) I decided to take a nap, as I was ready to throw a fist through my cinema display. Not thinking I’d actually fall asleep, I woke up to a phone call some 3 hours later from the client leaving a <em>hilarious</em> voicemail telling me (in a much more profane way) to “wake up and get back to work”. That he said it in a way that made me laugh, and that made me feel appreciated, was all it took for me to get back to work.</p>
<p>Every call we had was filled with jokes, stories, and endless appreciation for the work I was doing, and for pulling together to the timeline we committed to and for changing my weekend’s plans including staying up until 6AM to get everything done.</p>
<p>Every time I got stressed out during the timeframe—running into bugs, losing focus, or finding more things that needed to be changed—I could laugh it off because I had that bubbly feeling in my stomach, knowing that the over-and-above work I was doing to meet the deadline was appreciated by the client.</p>
<h2>Lessons in Management</h2>
<p>So what does this mean for how you manage a team? Don’t lose that positivity. When <em>you</em> start stressing out, you’re only <em>adding</em> to the stress your team has. Be unnecessarily apologetic. Be happy that they’re hacking away. And help whenever you can to make sure they’re focusing on the hard stuff.</p>
<p>Burn out is a real thing. It’s <em>not</em> fun, and you don’t want your team burning out in the midst of a tight deadline. So make sure you show them you care through the good <em>and</em> the bad!</p>
<p>What do you do to show your team that they’re appreciated?</p>
]]></content:encoded>
			<wfw:commentRss>http://thephuse.com/business/the-value-of-appreciation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why You Should Throw Away The Best Idea You Ever Had</title>
		<link>http://thephuse.com/business/why-you-should-throw-away-the-best-idea-you-ever-had/</link>
		<comments>http://thephuse.com/business/why-you-should-throw-away-the-best-idea-you-ever-had/#comments</comments>
		<pubDate>Thu, 15 Mar 2012 16:00:31 +0000</pubDate>
		<dc:creator>Matt Herron</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Writing Tips]]></category>
		<category><![CDATA[advice]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[creativity]]></category>
		<category><![CDATA[good]]></category>
		<category><![CDATA[great]]></category>
		<category><![CDATA[idea generation]]></category>
		<category><![CDATA[ideas]]></category>
		<category><![CDATA[inspiration]]></category>
		<category><![CDATA[liberating]]></category>
		<category><![CDATA[techniques]]></category>
		<category><![CDATA[tips]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://thephuse.com/?p=878</guid>
		<description><![CDATA[Matt discusses how throwing away the best idea you ever had is the litmus test of a truly good idea, and how good ideas can be blinding.]]></description>
			<content:encoded><![CDATA[<p><a href="http://thephuse.com/cms/wp-content/uploads/2012/03/davincishelicopter.jpg"><img class="alignright size-full wp-image-879" title="Da Vinci's Helicopter" src="http://thephuse.com/cms/wp-content/uploads/2012/03/davincishelicopter.jpg" alt="Da Vinci's Helicopter" width="364" height="504" /></a>You&#8217;re laying in bed, and an idea hits you. It&#8217;s formless at first, abstract, but it might just be the best idea you&#8217;ve ever had. Brilliant. Truly awesome. Shining like the sun.</p>
<p>You write it down, and early the next day get to work fleshing it out. It&#8217;s no longer formless now. Whether it&#8217;s an idea for a business or a website or a blog, at this point it seems to have real-world potential.</p>
<p>Excellent. Now take the best idea you ever had and toss it in the trash.</p>
<h2>Crazy Say What?</h2>
<p>You&#8217;re probably wondering if I&#8217;ve lost my mind. &#8220;Throw away the best idea I ever had?&#8221; you ask yourself. &#8220;Is he serious?&#8221;</p>
<p>Don&#8217;t jump to conclusions. First, we need to understand how ideas work.</p>
<h2>The Litmus Test</h2>
<p>See the thing about good ideas is that you can&#8217;t kill them. You can throw them away, sure. But if the idea is truly good, it will always come back to nag at the edge of your mind.</p>
<p>For example, novelists don&#8217;t write books about the first idea that comes to mind, even if it is the best idea they&#8217;ve ever had. They write books on the idea that won&#8217;t leave them alone. Oftentimes, these ideas have been nagging at them for years, growing inside their minds, until eventually it takes all their will power NOT to write about it.</p>
<p>Throwing your best idea away isn&#8217;t crazy. It&#8217;s the litmus test of a good idea. Throw it away so you can put it to the test. If It&#8217;s truly a good idea, it will come back even stronger than before.</p>
<h2>Good Ideas Can Be Blinding</h2>
<p>One problem with a good idea is that sometimes it seems so good that you can&#8217;t see beyond it. The light is just too bright.</p>
<p>Throwing away your idea will give you the chance to look at it from a professional distance, to evaluate it with the analytical part of your mind instead of with the passion of your gut. Many a good idea has been ruined because of a lack of professional distance.</p>
<p>If your idea really is the best idea you&#8217;ve ever had, that won&#8217;t change when it comes back to you later and you&#8217;re able to treat it like a pro treats his ideas. It will still be the best idea you&#8217;ve ever had. The difference is that now you&#8217;ll know what to do with it.</p>
<h2>Ideas Are Liberating</h2>
<p>Human beings with ideas are some of the most inspired, happy people that ever lived. But ideas only matter if you can turn them into reality. Da Vinci&#8217;s helicopter was only an idea at first. And it was only an idea for a long, long time. What made it great was that it was turned from a drawing into a physically reality. Someone actually built a helicopter, and it could fly! How liberating.</p>
<p>So take your ideas and throw them away. The good ones will come back. The rest will stay in the garbage where they belong.</p>
<p>And when the good ones come back, make them real. Don&#8217;t let them waste away in a notebook at the bottom of a desk drawer. Build them, write them, show them to the world.</p>
]]></content:encoded>
			<wfw:commentRss>http://thephuse.com/business/why-you-should-throw-away-the-best-idea-you-ever-had/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Lorem Ipsum Is a Crutch!</title>
		<link>http://thephuse.com/design-and-usability/lorem-ipsum-is-a-crutch/</link>
		<comments>http://thephuse.com/design-and-usability/lorem-ipsum-is-a-crutch/#comments</comments>
		<pubDate>Mon, 05 Mar 2012 17:00:43 +0000</pubDate>
		<dc:creator>Matt Herron</dc:creator>
				<category><![CDATA[Content Strategy]]></category>
		<category><![CDATA[Design and Usability]]></category>
		<category><![CDATA[Writing Tips]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[content precedes design]]></category>
		<category><![CDATA[content strategy]]></category>
		<category><![CDATA[copywriting]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[lorem ipsum]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://thephuse.com/?p=807</guid>
		<description><![CDATA[Lorem ipsum, the faux-latin text that means nothing and is used liberally and with little regard by designers to fill space in lieu of actual content, is a crutch.]]></description>
			<content:encoded><![CDATA[<p><a href="http://thephuse.com/cms/wp-content/uploads/2012/03/lorem-ipsum.jpg"><img src="http://thephuse.com/cms/wp-content/uploads/2012/03/lorem-ipsum.jpg" alt="" title="lorem-ipsum" width="503" height="350" class="alignright size-full wp-image-810" /></a>Lorem ipsum, the faux-latin text that means nothing and is used liberally and with little regard by designers to fill space in lieu of actual content, is a crutch.</p>
<p>You don&#8217;t need it. In fact, you shouldn&#8217;t use it at all. Next time you are mocking up a design filled with lorem ipsum text, slap yourself in the face and do this instead:</p>
<p><em>Write the content first.</em></p>
<h2>Content Precedes Design</h2>
<blockquote><p>&#8220;Content precedes design. Design in the absence of content is not design, it&#8217;s decoration.&#8221;<br /><a href="https://twitter.com/#!/zeldman/statuses/804159148" title="Tweet">Jeffrey Zeldman</a></p></blockquote>
<p>That quote is nearly four years old. Why do designers still use lorem ipsum text? Have they ignored even the sagely advice of the wise Zeldman?</p>
<p>Trust me, you don&#8217;t need lorem ipsum text. In fact, your design will always benefit from having content to work with early in the design process. As early as possible.</p>
<p>Sometimes things don&#8217;t work out that way. Your copywriter is on vacation or you&#8217;re in a pinch. Or maybe you fly solo. Are you a freelancer who does everything from wireframes to design to coding to maintenance by yourself? The client didn&#8217;t give you any copy? What then?</p>
<h2>You Make Something Up</h2>
<p>You&#8217;re a professional. It&#8217;s easy.</p>
<p>Method number one, steal it. Say you&#8217;re making a website for a business: don&#8217;t they have brochures? Company newsletters? Hell, e-mail signatures? Anything will do, pick and choose until it looks like you&#8217;ve got enough to work with.</p>
<p>If there&#8217;s no old material to work with, write your own. Anyone can write. It doesn&#8217;t have to be perfect yet, just enough to cover the basic message. Again, just enough to work with. Your clients can give you more later when you show them what’s missing.</p>
<h2>Working with a Team</h2>
<p>If you’re working with a team, the planning stage has often begun before the content gets written. At The Phuse, for example, sometimes our designers use Lorem Ipsum text in the wireframes. That’s acceptable because it’s still the planning stage, and it’s not the designer’s job to write the content. We want them to focus on what they’re best at.</p>
<p>The copywriter is then responsible to make sure the designer has content to work with by the time the planning stage is done. It’s important for a copywriter or content strategist to work closely with the design team to make sure that no lorem ipsum text resurfaces in the design. And if it does, that content gets written immediately to replace it.</p>
<h2>Practice Makes Process</h2>
<p>As you practice, you&#8217;ll get a feel for how long copy will be, or how much space to leave for a thumbnail.</p>
<p>In short, you’ll develop a process.</p>
<p>There are some basics. Headlines should stay on one line when possible. Make the text easy to read. Leave enough room for all the content. Have plans for moving elements around to fit whatever content your client wants to add in later.</p>
<p>Each project is different because the content is different. But remember: “content precedes design.”</p>
<h2>The Magazine Method</h2>
<blockquote><p>&#8220;There are cases where designers need never consider writing a single word themselves.&#8221;<br /><a href="http://designshack.net/articles/business-articles/the-importance-of-copywriting-in-web-design" title="Design Shack article">Joshua Johnson at DesignShack</a></p></blockquote>
<p>In magazines, advertising, and other large agencies, there are often separate design and copywriting departments. The writers deliver content to the designers which ensures that the designers can focus on their job and not get distracted or delayed by issues such as wording, semantics, grammar, etc.</p>
<p>Over time, these departments get better at working with each other. Eventually, one would hope they operate like two parts of one unit.</p>
<p>Obviously bigger companies have the resources to allow for this kind of work, whereas if you&#8217;re a freelancer you may not be able to afford it. If monetary constraints allow, consider hiring a writer who will trade you his skills for portfolio pieces, or an old friend who has a flair with words. Marketing and English students are frequently as happy to get the work (and at a cheaper price) than seasoned copywriting vets.</p>
<h2>This Sounds Hard</h2>
<p>It is. That’s still no excuse for lazy design that doesn&#8217;t take into account the essential role content plays in the design of a website, advertisement, press release, newsletter, etc.</p>
<p>Stay away from lorem ipsum text and you will be able to focus on the function of your design as well as the form. It’s not just text and images filling your page. It&#8217;s content. Get the picture?</p>
<p>Tell us: what do you do to ensure that content is ready to roll before the design? What are some common pitfalls and how do you get around them?</p>
]]></content:encoded>
			<wfw:commentRss>http://thephuse.com/design-and-usability/lorem-ipsum-is-a-crutch/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 0.383 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-05-17 06:10:10 -->

