<?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>Gluue</title>
	<atom:link href="http://gluue.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://gluue.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 09 May 2012 17:57:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>What it&#8217;s Like to be a Project Manager.</title>
		<link>http://gluue.com/2012/05/what-its-like-to-be-a-project-manager/</link>
		<comments>http://gluue.com/2012/05/what-its-like-to-be-a-project-manager/#comments</comments>
		<pubDate>Wed, 09 May 2012 17:55:36 +0000</pubDate>
		<dc:creator>Kristin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://gluue.com/?p=2834</guid>
		<description><![CDATA[	Being a PM is like slaving for weeks on a group term paper, and then accidentally deleting the entire thing.

	You get to see a project through from start to finish, influencing nearly every part of it. You get to watch proudly as a mere idea transforms into a great portfolio piece. You put your blood, [...]]]></description>
			<content:encoded><![CDATA[	<p>Being a PM is like slaving for weeks on a group term paper, and then accidentally deleting the entire thing.</p>

	<p>You get to see a project through from start to finish, influencing nearly every part of it. You get to watch proudly as a mere idea transforms into a great portfolio piece. You put your blood, sweat and tears into content creation and development. You get to work with great people to reach the end product. You get to use your skill of turning studio language into something your clients can wrap their brains around. Sometimes you even get to hand deliver the finished product with a big pretty bow on it.</p>

	<p>But when something goes wrong, you&#8217;re the person it <em>always</em> makes sense to blame.</p>

	<p><span id="more-2834"></span></p>

	<p>(Sigh.)</p>

	<p>Regardless of who actually made the mistake, if you&#8217;re the last one to touch it before it goes to a client, you have to take partial responsibility. Sometimes this can make your hard work seem all for naught. After all, your goal was a perfect project, right?</p>

	<p>Adjust your expectations. Take the error in stride, assume the responsibility, and own it. The key to dealing with mistakes as a PM is to grow from and build on them. When you turn ugly red check marks into pretty green plus signs, see it as an opportunity to make your team stronger, and improve your relationship with the client.</p>

	<p>So, being a project manager is really like accidentally deleting that term paper only to find it backed up on your key-ring zip drive. You&#8217;re learning fast…</p>]]></content:encoded>
			<wfw:commentRss>http://gluue.com/2012/05/what-its-like-to-be-a-project-manager/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Want.</title>
		<link>http://gluue.com/2012/05/want/</link>
		<comments>http://gluue.com/2012/05/want/#comments</comments>
		<pubDate>Fri, 04 May 2012 01:45:44 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Ear to the ground]]></category>
		<category><![CDATA[iPad]]></category>

		<guid isPermaLink="false">http://gluue.com/?p=2827</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[]]></content:encoded>
			<wfw:commentRss>http://gluue.com/2012/05/want/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Jumpchart&#8217;s Newest Features!</title>
		<link>http://gluue.com/2012/04/jumpcharts-newest-features/</link>
		<comments>http://gluue.com/2012/04/jumpcharts-newest-features/#comments</comments>
		<pubDate>Wed, 25 Apr 2012 13:21:37 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Jumpchart]]></category>
		<category><![CDATA[mockups]]></category>
		<category><![CDATA[new features]]></category>
		<category><![CDATA[notes]]></category>

		<guid isPermaLink="false">http://gluue.com/?p=2779</guid>
		<description><![CDATA[	It&#8217;s finally time to spill the beans about our latest feature releases. We came up with some improvements that we think will make your life much easier.

	Content and Design Merge in Jumpchart

	Jumpchart has always been about putting content first, and that hasn&#8217;t changed. But now Jumpchart can play an even more active role in your [...]]]></description>
			<content:encoded><![CDATA[	<p>It&#8217;s finally time to spill the beans about our latest feature releases. We came up with some improvements that we think will make your life much easier.</p>

	<p><strong>Content and Design Merge in Jumpchart</strong></p>

	<p><a href="http://gluue.com/wp-content/uploads/2012/04/threadsmock.jpg"><img class="alignleft size-thumbnail wp-image-2805" title="threadsmock" src="http://gluue.com/wp-content/uploads/2012/04/threadsmock-150x150.jpg" alt="" width="150" height="150" /></a>Jumpchart has always been about putting content first, and that hasn&#8217;t changed. But now Jumpchart can play an even more active role in your website project by letting you seamlessly transition into the design phase.</p>

	<p>In the sleek new design section, you can upload mockups to the project, collaborate on them with your clients and team members, and get straightforward approval from the person in charge. We&#8217;re big on tracking revisions, and you can do that here, too. Upload as many versions as it takes to get the job done; switch back to an old version at any time. For more information, check out the support article on <a href="https://core.jumpchart.com/help/article/44/">design mockups.</a></p>

	<p>There&#8217;s something else we thought would make Jumpchart a more well-rounded tool for website planning…</p>

	<p><strong>Store Project Details in Jumpchart.</strong></p>

	<p><a href="http://gluue.com/wp-content/uploads/2012/04/notes.jpg"><img class="alignleft size-thumbnail wp-image-2804" title="notes" src="http://gluue.com/wp-content/uploads/2012/04/notes-150x150.jpg" alt="" width="150" height="150" /></a></p>

	<p>It&#8217;s easy for things to get lost in the e-mail shuffle, but now it&#8217;s even easier to keep track of it <em>all</em>. Passwords, deadlines, launch details, quotes- you name it. If it&#8217;s important to your project, you can store it in the new Notes section of Jumpchart. Never waste time searching your inbox again. All collaborators can comment on the notes, or add notes themselves. Organization has always been important to us, but we took it to the next level with this new feature. To get a deeper idea of what the new Notes section can do for your project, read the related <a href="https://core.jumpchart.com/help/article/41/">support article.</a></p>

	<p>We&#8217;re really proud of the new features we added to Jumpchart. We think they&#8217;re really going to change the way you do your job for the better.</p>]]></content:encoded>
			<wfw:commentRss>http://gluue.com/2012/04/jumpcharts-newest-features/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Writing Toward a Mission. The Call to Action.</title>
		<link>http://gluue.com/2012/04/writing-toward-a-mission-the-call-to-action/</link>
		<comments>http://gluue.com/2012/04/writing-toward-a-mission-the-call-to-action/#comments</comments>
		<pubDate>Fri, 13 Apr 2012 16:13:42 +0000</pubDate>
		<dc:creator>Kristin</dc:creator>
				<category><![CDATA[Paste]]></category>
		<category><![CDATA[call to action]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://gluue.com/?p=2785</guid>
		<description><![CDATA[	As you already know, a lot goes into building a website. There&#8217;s the design, the programming, the implementation… but before all that comes the content. Getting the content wrong could mean quite a bit of backtracking later on, and I think we can all agree backtracking = evil. So while you&#8217;re busy not taking one [...]]]></description>
			<content:encoded><![CDATA[	<p>As you already know, a lot goes into building a website. There&#8217;s the design, the programming, the implementation… but before all that comes the content. Getting the content wrong could mean quite a bit of backtracking later on, and I think we can all agree backtracking = evil. So while you&#8217;re busy <em>not</em> taking one step forward and two steps back, make sure you don&#8217;t forget perhaps the most important element of your copy- the thing that will get readers to do what you want them to do.</p>

	<p>It&#8217;s a crucial (and largely underrated) part of writing website content: the call to action.</p>

	<p><strong>What&#8217;s the Point?</strong><br />
When users visit your site, they&#8217;re either looking for something specific (which is why you make your navigation incredibly user-friendly- so they can get in and get out.) or they&#8217;re interested in learning more about your company/product. Either way, what they don&#8217;t want is to reach the end of a page and think &#8220;Okay, what do I do now?&#8221;<br />
<span id="more-2785"></span></p>

	<p>Calls to action help increase conversions on your end, but they also make the visitor feel more confident about getting what they want out of your site. For example, let&#8217;s say you have a website for your party planning business. The visitor just read a page about the most important steps of party planning. You need to make it easy for them to take the next step. Give them a reason to spend a few more minutes on your site by guiding them through the process of learning, and then taking action. It&#8217;s as simple as including a sentence like this to your page. &#8220;Interested in how we can help plan your party? Schedule a consultation here!&#8221; Then link to your contact page which clearly provides the information they&#8217;ll need to get a hold of you, or link directly to the online form where they can submit their information and wait for you to get a hold of them. Easy, easy easy.</p>

	<p><strong>Internal and External Calls to Action.</strong><br />
There are ways to track what your users are doing online through various forms of analytics. That being said, you can vary your call to action. Maybe you want the visitor to simply click to the next page to read more about the topic. Or maybe your goal is persuade them to fill out an online quote form.</p>

	<p>I like to distinguish these by whether or not the action taken will happen internally (read more!) or extend outside the site (Fill out this form for more information. We&#8217;ll be in touch soon!). If your site is content heavy, it&#8217;s beneficial to have these tidbits infused throughout the content on each page.</p>

	<p><strong>Working a Call to Action into Your Site.</strong><br />
There are a million and a half tips out there telling you how to write a strongly worded, effective call to action that will get visitors to drop what they&#8217;re doing and buy your product. But you know as well as I do that a call to action can be much more than persuading someone to <em>buy</em> something. The &#8220;Action&#8221; can in fact be anything. It can be big and loud, or it can be subtle and helpful. Both can be good choices depending on the context! First and foremost, you have to decide exactly what you want your visitors to do.</p>

	<p><strong>The Action, and How to Implement it.</strong><br />
Here are some examples of how to put into action the action you want your uses to take.<br />
<strong>Action</strong>: Call the office for more information<br />
<strong>Make it Happen</strong>: Link to the contact page, and/or list the phone number right there in the text.<br />
<strong>Example</strong>: &#8220;Talk to an expert today!&#8221; &#8220;Call us!&#8221; &#8220;For more information, please call or e-mail us.&#8221;</p>

	<p><strong>Action</strong>: Fill out the contact form so someone can get in touch with you.<br />
<strong>Make it Happen</strong>:  Link right to the form. Make it as easy as possible for the user.<br />
<strong>Example</strong>: &#8220;Fill out the form below for more information- we&#8217;ll be in touch soon!&#8221;</p>

	<p><strong>Action</strong>: Schedule an appointment<br />
<strong>Make it Happen</strong>: Link to the page where the user can either schedule online, or call someone direct to get it set up.<br />
<strong>Example</strong>: &#8220;To schedule an appointment, give us a call or fill out the form here.&#8221;</p>

	<p><strong>Action</strong>: Read more<br />
<strong>Make it Happen</strong>: Post a compelling snippet of the content on one page, and include a link to the rest of the content via a &#8220;Read more&#8221; link.<br />
<strong>Example</strong>: &#8220;Read the rest of the story here.&#8221;</p>

	<p>A good call to action can generate measurable <span class="caps">ROI</span> one way or another, so working it into your website is not only easy, but <em>necessary</em>.</p>]]></content:encoded>
			<wfw:commentRss>http://gluue.com/2012/04/writing-toward-a-mission-the-call-to-action/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Effective Naming of Pages.</title>
		<link>http://gluue.com/2012/04/effective-naming-of-pages/</link>
		<comments>http://gluue.com/2012/04/effective-naming-of-pages/#comments</comments>
		<pubDate>Thu, 12 Apr 2012 15:00:04 +0000</pubDate>
		<dc:creator>Kristin</dc:creator>
				<category><![CDATA[Ear to the ground]]></category>
		<category><![CDATA[naming pages]]></category>

		<guid isPermaLink="false">http://gluue.com/?p=2770</guid>
		<description><![CDATA[	&#8220;The biggest mistake I observe when it comes to information architecture is in the naming of pages and sections. The problem manifests itself in three ways:

	Use of jargon: Every industry and company has its jargon. Web design is certainly no exception with more acronyms than you can shake a stick at. The problem is that [...]]]></description>
			<content:encoded><![CDATA[	<p>&#8220;The biggest mistake I observe when it comes to information architecture is in the naming of pages and sections. The problem manifests itself in three ways:<br />
<ul>
	<li>Use of jargon: Every industry and company has its jargon. Web design is certainly no exception with more acronyms than you can shake a stick at. The problem is that you can never assume your users will know all the acronyms. They maybe new to the sector or use a slightly different variation of your companies terminology. The names of your sections and pages should be free of jargon and where possible, product names that the users will not have previously encountered. Page and section titles should be descriptive of their content in the plainest language possible.</li>
	<li>Long names: Although naming should be descriptive they should also be short. Ideally all menu items should be one or two words long. The idea is that users should be able to quickly scan down the list of pages available and identify the one most likely to have content they need.</li>
	<li>Inconsistent naming: Be careful that the way you refer to pages does not change depending on which section you are in. Every link to a page should be referred to in the same way. Where a page title needs to be longer than the wording used in menu items make sure it mirrors it closely. Inconsistent naming can cause confusion and doubt in users making them unsure if they have previously viewed a particular page.&#8221;</li><br />
</ul><br />
<a href="http://boagworld.com/usability/common-mistakes-of-site-structure/">Read more here.</a></p>]]></content:encoded>
			<wfw:commentRss>http://gluue.com/2012/04/effective-naming-of-pages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>An All Day Meeting.</title>
		<link>http://gluue.com/2012/04/an-all-day-meeting/</link>
		<comments>http://gluue.com/2012/04/an-all-day-meeting/#comments</comments>
		<pubDate>Tue, 10 Apr 2012 19:27:40 +0000</pubDate>
		<dc:creator>Kristin</dc:creator>
				<category><![CDATA[Paste]]></category>
		<category><![CDATA[meetings]]></category>

		<guid isPermaLink="false">http://gluue.com/?p=2766</guid>
		<description><![CDATA[	A lot of people in this world think meetings are evil. I tend to be one of those people, actually. But let me clarify- it&#8217;s meetings that take 3 hours to accomplish what could have been knocked out in 30 minutes that get under my skin.

	I have a deep appreciation for group communication. People working [...]]]></description>
			<content:encoded><![CDATA[	<p>A lot of people in this world think meetings are evil. I tend to be one of those people, actually. But let me clarify- it&#8217;s meetings that take 3 hours to accomplish what could have been knocked out in 30 minutes that get under my skin.</p>

	<p>I have a deep appreciation for group communication. People working together, touching base frequently, actively collaborating and working toward the best possible result. There&#8217;s nothing negative about that.</p>

	<p>I just think there are ways to go about it that don&#8217;t require half a day&#8217;s attention. Frequent e-mails showing progress, phone calls to touch base, and some occasional face time is nice! And I like to think our clients agree. After all, once we&#8217;ve determined we&#8217;re all on the same page, don&#8217;t they want us spending more time <em>working</em> on their project than <em>talking</em> about it?</p>]]></content:encoded>
			<wfw:commentRss>http://gluue.com/2012/04/an-all-day-meeting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;Life is Not Just a Sequence of Waiting for Things To Be Done.</title>
		<link>http://gluue.com/2012/04/life-is-not-just-a-sequence-of-waiting-for-things-to-be-done/</link>
		<comments>http://gluue.com/2012/04/life-is-not-just-a-sequence-of-waiting-for-things-to-be-done/#comments</comments>
		<pubDate>Mon, 09 Apr 2012 16:56:15 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Ear to the ground]]></category>

		<guid isPermaLink="false">http://gluue.com/?p=2761</guid>
		<description><![CDATA[	]]></description>
			<content:encoded><![CDATA[	<p><iframe width="400" height="233" src="http://www.youtube.com/embed/RYlCVwxoL_g" frameborder="0" allowfullscreen></iframe></p>]]></content:encoded>
			<wfw:commentRss>http://gluue.com/2012/04/life-is-not-just-a-sequence-of-waiting-for-things-to-be-done/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Father of Video Games</title>
		<link>http://gluue.com/2012/03/father-of-video-games/</link>
		<comments>http://gluue.com/2012/03/father-of-video-games/#comments</comments>
		<pubDate>Mon, 26 Mar 2012 16:45:04 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Ear to the ground]]></category>

		<guid isPermaLink="false">http://gluue.com/?p=2757</guid>
		<description><![CDATA[	Cool guy.

	Inventor Portrait: Ralph Baer from David Friedman on Vimeo.]]></description>
			<content:encoded><![CDATA[	<p>Cool guy.</p>

	<p><iframe src="http://player.vimeo.com/video/37870722?title=0&amp;byline=0&amp;portrait=0" width="350" height="197" frameborder="0" webkitAllowFullScreen mozallowfullscreen allowFullScreen></iframe><p><a href="http://vimeo.com/37870722">Inventor Portrait: Ralph Baer</a> from <a href="http://vimeo.com/davidfriedman">David Friedman</a> on <a href="http://vimeo.com">Vimeo</a>.</p></p>]]></content:encoded>
			<wfw:commentRss>http://gluue.com/2012/03/father-of-video-games/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Small Ideas</title>
		<link>http://gluue.com/2012/03/small-ideas/</link>
		<comments>http://gluue.com/2012/03/small-ideas/#comments</comments>
		<pubDate>Thu, 15 Mar 2012 16:30:01 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[free ideas]]></category>

		<guid isPermaLink="false">http://gluue.com/?p=2747</guid>
		<description><![CDATA[	]]></description>
			<content:encoded><![CDATA[	<p><iframe width="400" height="233" src="http://www.youtube.com/embed/F8UFGu2M2gM" frameborder="0" allowfullscreen></iframe></p>]]></content:encoded>
			<wfw:commentRss>http://gluue.com/2012/03/small-ideas/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Inventing on Principle.</title>
		<link>http://gluue.com/2012/02/inventing-on-principle/</link>
		<comments>http://gluue.com/2012/02/inventing-on-principle/#comments</comments>
		<pubDate>Wed, 15 Feb 2012 15:35:05 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[free ideas]]></category>
		<category><![CDATA[interfaces]]></category>

		<guid isPermaLink="false">http://gluue.com/?p=2744</guid>
		<description><![CDATA[	Bret Victor &#8211; Inventing on Principle from CUSEC on Vimeo.

	via http://waxy.org/links/]]></description>
			<content:encoded><![CDATA[	<p><iframe src="http://player.vimeo.com/video/36579366?byline=0" width="400" height="225" frameborder="0" webkitAllowFullScreen mozallowfullscreen allowFullScreen></iframe><p><a href="http://vimeo.com/36579366">Bret Victor &#8211; Inventing on Principle</a> from <a href="http://vimeo.com/cusec">CUSEC</a> on <a href="http://vimeo.com">Vimeo</a>.</p></p>

	<p>via <a href="http://waxy.org/links/">http://waxy.org/links/</a></p>]]></content:encoded>
			<wfw:commentRss>http://gluue.com/2012/02/inventing-on-principle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

