<?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>Atomic Interactive Blog &#187; Denise Armentrout</title>
	<atom:link href="http://atomicinteractive.com/blog/author/denise/feed/" rel="self" type="application/rss+xml" />
	<link>http://atomicinteractive.com/blog</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Thu, 02 Sep 2010 18:25:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Moving Forward, Looking Back</title>
		<link>http://atomicinteractive.com/blog/moving-forward-looking-back/</link>
		<comments>http://atomicinteractive.com/blog/moving-forward-looking-back/#comments</comments>
		<pubDate>Thu, 13 May 2010 21:12:42 +0000</pubDate>
		<dc:creator>Denise Armentrout</dc:creator>
				<category><![CDATA[culture]]></category>
		<category><![CDATA[project management]]></category>

		<guid isPermaLink="false">http://atomicinteractive.com/blog/?p=349</guid>
		<description><![CDATA[One of the things I love about working at Atomic Interactive is that every project gives me a chance to learn something new.&#160;That&#8217;s because the culture here is not about hanging on to old processes just because &#8220;that&#8217;s how we&#8217;ve always done things.&#8221; Instead, it&#8217;s about being open to new ideas and expanding our minds!
For [...]]]></description>
			<content:encoded><![CDATA[<p>One of the things I love about working at Atomic Interactive is that every project gives me a chance to learn something new.&nbsp;That&#8217;s because the culture here is not about hanging on to old processes just because &#8220;that&#8217;s how we&#8217;ve always done things.&#8221; Instead, it&#8217;s about being open to new ideas and expanding our minds!</p>
<p>For me, a key part of that is going back after a project has been completed to analyze what we could have done better. Maybe we could have worked more efficiently, or used a different tool. Maybe we could have communicated more clearly with the client – or even within our own team.</p>
<p>Mind you, this review isn&#8217;t about finger-pointing. It&#8217;s all about understanding that, no matter how good we are, there&#8217;s always something we can improve upon. (As a dear friend of mine used to say, &#8220;the biggest room in the world is room for improvement.&#8221;) That&#8217;s especially true in the interactive environment where new technologies pop up daily. It&#8217;s our job to try them out – and if they&#8217;re promising, becoming familiar with them and adding them to our toolbox. </p>
<p>Sometimes being innovative means rejecting new technology. As Atomic&#8217;s project manager, I&#8217;ve started organizing all our project information in binders. Yes, I mean an ugly, old-school, three-ring binder. Of course, we use an online project management system, too – but sometimes it&#8217;s easier to grab a binder and head to the desk of a designers or a developer with site maps, wire frames or other information in hand. Hey, if a tool helps us work more efficiently, we&#8217;ll use it. Even if it&#8217;s not flashy or new.</p>
<p>On the other hand, if I discover that a tool is not working, I&#8217;m not afraid to pitch it. Sometimes you can get stuck trying to tweak a process to death – when what you really need to do is scrap it entirely and start fresh. </p>
<p>So if you see me bent over my notebook long after a project is completed, you&#8217;ll know what I&#8217;m doing. Revisiting the project one last time and refining the process that works best for Team Atomic and our customers.</p>
]]></content:encoded>
			<wfw:commentRss>http://atomicinteractive.com/blog/moving-forward-looking-back/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing scope changes</title>
		<link>http://atomicinteractive.com/blog/managing-scope-changes/</link>
		<comments>http://atomicinteractive.com/blog/managing-scope-changes/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 02:26:49 +0000</pubDate>
		<dc:creator>Denise Armentrout</dc:creator>
				<category><![CDATA[interactive design]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://atomicinteractive.com/blog/?p=207</guid>
		<description><![CDATA[As Atomic&#8217;s project manager, my job is to plan our projects and keep them on track.  Sounds easy enough &#8230; maybe even boring. But there&#8217;s one little thing that keeps my job challenging.
Changes.
Scope changes. Schedule changes. Software changes. You name it, I&#8217;ve seen it. In fact, it seems to me that no matter how [...]]]></description>
			<content:encoded><![CDATA[<p>As Atomic&#8217;s project manager, my job is to plan our projects and keep them on track.  Sounds easy enough &#8230; maybe even boring. But there&#8217;s one little thing that keeps my job challenging.</p>
<p>Changes.</p>
<p>Scope changes. Schedule changes. Software changes. You name it, I&#8217;ve seen it. In fact, it seems to me that no matter how carefully a project is planned, some level of changes are inevitable. That&#8217;s just what happens when a creative concept evolves into a reality. </p>
<p>So instead of closing my eyes and hoping that changes won&#8217;t happen, I&#8217;m always ready for them. Here are some of the strategies I use to keep our projects on track in the face of the unexpected. </p>
<ul>
<li>
		<strong>Talk openly about the impact of 	changes.</strong> Sometimes a client thinks of a new requirement or new 	idea partway through a project. We can always accommodate these 	requests, but it&#8217;s my job to make sure the client understands 	exactly how those changes would affect schedule and budget. That way 	the client can make an informed decision on whether to implement the 	changes or stick with the original plan.
	</li>
<li>
		<strong>Be honest about delays.</strong> Every now and then, it takes us longer to execute a task than we 	thought it would. (Yes, it&#8217;s true – we do make mistakes!) In 	those situations, I always let our clients know right away that we 	need to bump our schedule back a couple of day. Clients appreciate 	this honesty, and it helps them to better plan their review cycles 	accordingly.
	</li>
<li>
		<strong>Constantly monitor and adjust 	milestones.</strong> If we miss a milestone in our project schedule, we 	don&#8217;t just throw up our hands and say, “well, we&#8217;re sunk now.” 	Instead, I constantly readjust project milestones as needed. If we 	get behind on a deadline, I find out if we can expedite subsequent 	ones. And, if needed, I crack the whip and get our team really 	cranking to help us meet a deadline.
	</li>
</ul>
<p>Of course, in my fondest dreams, all projects tick along perfectly, with every milestone met to the minute. I&#8217;ll keep hoping for that &#8230; but in the meantime, when changes come along, I&#8217;ll be ready for them.</p>
]]></content:encoded>
			<wfw:commentRss>http://atomicinteractive.com/blog/managing-scope-changes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What’s Up with Wireframes?</title>
		<link>http://atomicinteractive.com/blog/what%e2%80%99s-up-with-wireframes/</link>
		<comments>http://atomicinteractive.com/blog/what%e2%80%99s-up-with-wireframes/#comments</comments>
		<pubDate>Thu, 15 Oct 2009 01:03:10 +0000</pubDate>
		<dc:creator>Denise Armentrout</dc:creator>
				<category><![CDATA[interactive design]]></category>
		<category><![CDATA[marketing strategy]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://atomicinteractive.com/blog/?p=146</guid>
		<description><![CDATA[We mentioned in our previous blog entry that we’re a little bit obsessive about project planning. And we admit it—we are. But that’s because we’ve seen too many web projects derailed because of poor planning, or no planning. And that’s not what we want for our customers.
So we take planning and project management seriously. One [...]]]></description>
			<content:encoded><![CDATA[<p>We mentioned in our previous blog entry that we’re a little bit obsessive about project planning. And we admit it—we are. But that’s because we’ve seen too many web projects derailed because of poor planning, or no planning. And that’s not what we want for our customers.</p>
<p>So we take planning and project management seriously. One critical step in those efforts is creating a wireframe for any new website.</p>
<p>What’s a wireframe? A wireframe is very simple design that lays out the essential elements that go on each of your web pages. A wireframe for a common webpage, for example, might include placeholders for a header, navigation, body copy, an image, a search function, a “call to action” box, and “contact us” information.</p>
<p>It would look something like this:</p>
<p><img src="http://www.atomicinteractive.com/blog/wp-content/uploads/2009/twitter-mockup.png" alt="" /></p>
<p>Why are wireframes so important?</p>
<ul>
<li><strong>Wireframes save time</strong> because they give web designers clear direction on what needs to go on each page of the site. With a creative brief in one hand and an approved wireframe in the other, a designer  begin developing a great visual image for your site – without having to worry that he might be leaving a critical functionality off of one of the pages. Too many web projects jump straight from creating a sitemap to beginning design, without creating a wireframe in between—and too much information falls in the gap in between.</li>
<li><strong>Wireframes also save money</strong> because the basic elements of the site have been determined and approved before the creative design process ever begins. So there’s much less chance that a design will have to be torn apart and done over—which can drive costs up quickly.</li>
</ul>
<p>Even though we’re a newfangled interactive firm, I guess we believe in the old-fashioned principle of “doing things right the first time.” We know that’s the right thing for our customers.</p>
<p>Want to learn more about wireframes and Atomic’s project management strategy? <a href="http://www.atomicinteractive.com/contact/">Contact us</a> anytime.</p>
]]></content:encoded>
			<wfw:commentRss>http://atomicinteractive.com/blog/what%e2%80%99s-up-with-wireframes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
