<?xml version="1.0" encoding="ISO-8859-1" ?>
<?xml-stylesheet title="XSL_formatting" href="/rssmgr/xsl.xml" type="text/xsl"  media="screen"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">

<channel>
<title>
<![CDATA[Newfangled Employee Blogs]]>
</title>
<link>
http://www.newfangled.com/newfangled_employee_blogs
</link>
<pubDate>
Fri, 20 Nov 2009 16:56:32 -0500
</pubDate>
<lastBuildDate>
Fri, 20 Nov 2009 16:56:32 -0500
</lastBuildDate>
<item>
<title>
<![CDATA[Measuring Sales by Kinds]]>
</title>
<description>
<![CDATA[<p>
<a target="_blank" href="/stuff/contentmgr/files/2/336dfc5fcde6616371b0c1713f9b2359/misc/new_projects_vs_maintenance.jpg"><img width="508" style="border:1px solid #bababa;" src="/stuff/contentmgr/files/2/336dfc5fcde6616371b0c1713f9b2359/misc/new_projects_vs_maintenance.jpg" /></a>
</p>

<p>
Another day, another set of data... I've been investigating what I call "peripheral" data sets in order to get a different perspective on how previously unseen or unmeasured activity affects the overall operation of our company. In my last post, I looked at how our <a target="_self" title="http://www.newfangled.com/visualizing_internal_project_management_communicat" href="/visualizing_internal_project_management_communicat">busyness could be represented  by the volume of communication over our internal project management system</a> from one month to the next. In looking at that picture, I realized that the volume of activity is much more drastically affected by maintenance work for our clients than by new projects. I classify "maintenance" as any work done for an existing client- it's a pretty broad spectrum, but since our new project process is so regimented, the split in categories is pretty realistic as far as our company's day to day experience is concerned. When I noticed that October of 2008 had the highest volume of communication, I wondered what our maintenance sales were that month and how they related to new project sales. Sales data is the easiest information for me to dig up, but I wasn't interested in the particular sales totals as much as the <i>relationship</i> between the numbers.
</p>

<p>
This brings me to the graph you see above. As I said, I wasn't so much interested in how much we sold from one month to the next as I was about the breakdown of sales- how much of it was new business and how much of it was maintenance. So, I determined the <i>percentage</i> of each month's sales total for the past few years that came from new projects and maintenance. For example, the graph above shows that in October, 2008, 37% of the month's sales total came from new  project sales while 63% came from maintenance. No wonder we had so many posts to our project management system that month! As you can tell from glancing at the graph, this is a relatively infrequent occurrence; more often than not, the new project sales account for the majority of the total. When I first plotted the data, I didn't add the percentage values because I was more interested in the general relationship, as well as any trends that might be perceivable from visualizing the data. Again, glancing at the graph seems sufficient to conclude that there are no obvious patterns, nor an obvious trend in any direction (i.e. maintenance percentages trending upward or downward).
</p>

<p>
<b>Averages and Average Averages</b><br />
Then I wondered about averages. The data set covers three years, but it isn't three <i>full</i> years. Additionally, the current year has a couple of extreme cases (January, in which maintenance accounted for only 19% of the sales total, and September, in which new projects accounted for only 2%), so I decided to look only at 2008's average.
</p>

<p>
<img src="/stuff/contentmgr/files/2/336dfc5fcde6616371b0c1713f9b2359/misc/2008_maint_sales_spectrum.jpg" style="border:1px solid #bababa;" />
</p>

<p>
In the chart above, I plotted out a spectrum displaying only the percentages of total sales accounted for by maintenance sales-- the lowest, 24%, came in July of 2008, while the highest, 71%, came in August. Two concurrent months bookending the spectrum seems to clearly show that there isn't a seasonal correlation. But back to averages, the average maintenance sales percentage for 2008 was 41%. What's interesting about this is that 8 months out of 12 were less than or equal to the average, leaving only 4 months in 2008 that exceeded it. If I isolate 2007, the average maintenance percentage for the 7 months plotted is 42%. If I isolate 2010, the average maintenance percentage for the 10 months plotted so far is 38%. These numbers are pretty close together. In fact, only 11 months out of the plotted 29 had maintenance percentages that exceeded 41%, which is a "score" of 40%. Maybe there is some significance to 40%...? 
</p>

<p>
Ultimately, I'd love to see the percentage of maintenance account for more consistently higher amount. I think doing more work for fewer clients is to our and our clients' advantage- it fits in with my motto of what we want to do: Serve fewer clients at a higher level. I believe we'll get there.
</p>

<p>
One last thing: The graph above doesn't show the <i>number</i> of new projects sold on a month to month basis. In 2007, the average was 4.1. In 2008, the average was 4. This year, the average so far is 2.6. To me, that's the kind of decrease I want to see. It means that we're selling fewer projects on a monthly basis this year, but at higher costs each (fewer at a higher level). So, all in all, one more piece of the puzzle...
</p>]]>
</description>
<link>
http://www.newfangled.com/visualizing_web_development_sales_makeup
</link>
<dc:creator>
<![CDATA[Chris]]>
</dc:creator>
<pubDate>
Thu, 19 Nov 2009 14:29:15 -0500
</pubDate>
</item>
<item>
<title>
<![CDATA[Measuring "Busyness"]]>
</title>
<description>
<![CDATA[<p>
<img width="508" style="border:1px solid #bababa;" src="/stuff/contentmgr/files/2/3cbfd40b5036fb40cb2996e760fc748a/misc/project_management_logs.jpg" /></p>

<p>
In my <a href="/visualizing_blogging_activity">last post</a> in what is becoming series on <a href="/visualizing_website_measurement_data">measurement</a>, I started off with my hypothesis that our company is like an ecosystem, "comprised of many areas of <i>unseen</i> activity" in addition to the sort of <i>seen</i> activity you'd expect (sales, individual projects, relationships, etc.). So, in trying to verify my hypothesis, I've been gathering data representing all kinds of unseen and unmeasured activity to see how it relates to the big picture as I've understood it so far. I started with looking at our <a href="/visualizing_blogging_activity">blogging activity</a> over the past three years and noticed that the months where we posted less loosely corresponded to what we tend to think of anecdotally as "busy" times for our company. That made me wonder- how else could I measure "busyness"? Looking at sales data wouldn't quite do it, because those numbers would correspond to the beginning of a project, so the trendline of sales may not match up exactly with that of volume of work over time. However, looking at the volume of communication using our internal project management system might help me discern at trendline for "busyness."
</p>

<p>
<img style="border:1px solid #bababa;margin:0px 20px 20px 0px;" align="left" src="/stuff/contentmgr/files/2/3cbfd40b5036fb40cb2996e760fc748a/misc/proj_search.jpg" />
Unfortunately, there was no simple way to do this. Our system doesn't have reporting tools that would tell me how many logs were completed for a particular period of time. However, since I receive an alert every time a log goes through our system, I realized that I could isolate those messages in my Gmail account and... count them one by one. Actually, I ended up counting them 50 by 50, since that's the page limit in Gmail's search results (see image at left). Needless to say, it took a while, but I did uncover some interesting things.
</p>

<p>
First, let me describe the metrics shown in the graph above. The vertical axis represents the number of individual logs posted by Newfangled employees to our project management system (these might be messages checking in on production progress, updating the task description, asking or answering questions, posting files, etc.). As you might imagine, a project of even minimal complexity would have many such messages, particularly as we have people collaborating on projects who work in separate offices. More obviously, the horizontal axis represents months over the past two years.
</p>

<p>
The first thing I noticed was the dramatic increase between August (1191 logs) and October (3132) of 2008. To put the number in perspective, October's total averages to about 136 logs posted per day (there were 23 business days that month)! That's in addition to all the phone and in-person conversations that occur here each day. In fact, we haven't had a month with that level of communication volume since. I cross referenced this number with our sales from October of 2008, and it turns out that, in addition to the two new projects we signed that month, we also did 57 different new functionality upgrades to existing client sites. That was the highest number of upgrades in one month for the entire year. With that in mind, 3132 project logs makes much more sense. We were busy.
</p>

<p>
<img style="margin:0px 0px 10px 0px;" width="508" src="http://farm3.static.flickr.com/2580/4093673357_c10c7050fe.jpg" /><br />
<small>Here are some Newfanglders. They may not look like it, but some of them were probably communicating using our project management system the moment this picture was taken.</small>
</p>

<p>
However, I then thought to cross reference the lowest month shown, June of 2008, with the sales from that month to see if they were correspondingly lower. While the number was less (3 new projects signed, 43 new functional upgrades), the overall communication volume wasn't proportionate. It should have been a higher number if there was a direct correlation. Especially since the previous month, May of 2008, we'd signed 7 new projects and done 55 functional upgrades. There would certainly be some bleed from May to June in terms of project communication. While October, 2008 is the peak, the numbers tend to level off in the mid-2000's after that, though there is another peak in October, 2009. I don't think sales are the complete explanation for this, but I do have a couple of ideas about other factors that could.
</p>

<p>
The first factor is the number of employees using the system. Between May and October of 2008, we hired 4 new employees- three <a href="/newfangled_web_factory_employees">Project Manager Assistants and one Resourcer</a>. These roles were essential to a new system we'd been establishing to make sure our service remained excellent while the complexity of our work increased. The Project Management teams use this system constantly to communicate and log project progress, and the Resourcer is constantly checking in on every task to watch progress and utilization. No wonder the number jumped so drastically! The other factor helps to explain the pattern, in that we are again seeing a jump this October despite not having a corresponding growth in personnel- that factor is the pre-holidays rush. This happens every year, where existing clients and new prospects are eager to get work completed or scheduled before the holidays and especially the new year. There's something about these calendar landmarks that put the pressure on, not to mention the common need to allocate funds before the end of the financial year.
</p>

<p>This was an interesting exercise. Little by little, measuring these "peripheral" data sets is giving me a much better sense of the big picture.</p>]]>
</description>
<link>
http://www.newfangled.com/visualizing_internal_project_management_communicat
</link>
<dc:creator>
<![CDATA[Chris]]>
</dc:creator>
<pubDate>
Wed, 18 Nov 2009 22:12:15 -0500
</pubDate>
</item>
<item>
<title>
<![CDATA[Benefits of Peer Usability Reviews]]>
</title>
<description>
<![CDATA[<p>As often as possible Newfangled holds professional development sessions for the Project Management teams to focus for an afternoon on a single area of web development. These valuable sessions have allowed us to step out of the workflow and exchange ideas about different aspects of our roles here at Newfangled. During a discussion about web usability I was struck by the variety of my coworkers' impressions about any given site's usability. As project managers we agreed on general practices, but as users, some individual preferences stood out. Sometime after this session my colleague <a target="_blank" href="/katies_blog">Katie Jamison</a> suggested that she and <a target="_blank" href="/jason_adams_newfangled_blog">Jason Adams</a> and I meet weekly to pass around our current prototypes and trade ideas about information architecture and usability.&nbsp; These meetings have proven so valuable that I now consider them a necessary part of every <a target="_blank" href="/planning_for_a_web_development_project">site-building process</a>. In even a fifteen minute review, two new sets of eyes clicking through a <a target="_blank" href="/efficient_website_prototyping">prototype</a> can pinpoint usability issues that those closely involved might miss. It is surprisingly easy for simple efficiencies to be invisible, and since there is not usually time to leave a project and return with an objective eye, usability review sessions are an efficient way to get fresh ideas.</p><p><b>A Recent Example</b></p><p>On a current project for SteriPEN that is now in the <a target="_blank" href="/planning_for_a_web_development_project">whitescreen phase</a>, the client's marketing team and I discussed how to display external links to online retailers that may carry different combinations of SteriPEN products. Before two internal review sessions, on the Product pages, links from sidebar widgets went to a Buy Online page where users could filter the online retailers by the category and product.</p><p><b>Here is a Product page at that stage of the prototype, with Buy Online in the sidebar...</b><br /><br /><img src="/stuff/contentmgr/files/2/1cb9b032cd180ae1f01a520aac0c9223/misc/steripen2.jpg" style="border: 0; vertical-align: middle;" width="500" height="282" /><br /><b><br /></b></p><p><b>...linking to this page, where the correct retailers were to be pre-filtered.</b></p><p><br /><img src="/stuff/contentmgr/files/2/1cb9b032cd180ae1f01a520aac0c9223/misc/steripenbef.jpg" style="border: 0; vertical-align: middle;" width="500" height="361" /><br /><br /></p><p><br /><b>It took a fresh reviewer to suggest pulling the filtered retailer links right into the sidebar of each product page.</b></p><p><br /><img style="vertical-align: middle;" src="/stuff/contentmgr/files/2/1cb9b032cd180ae1f01a520aac0c9223/misc/steripen3_copy.jpg" width="500" height="307" /><br /><br /><br /><b>In a third review</b>, another set of fresh eyes suggested that the retailers maybe should not be placed in the sidebar, since the sidebars could be reserved for more universal callouts rather than the page-specific function of displaying retailers for this individual product. So we placed the retailer links across the bottom of the page.</p><p><img src="/stuff/contentmgr/files/2/1cb9b032cd180ae1f01a520aac0c9223/misc/steripen4.jpg" style="border: 0; vertical-align: middle;" width="500" height="334" /></p><p>It's no news that objective critique can aid any creative process, but I am still amazed by how little time it takes a short review session to produce significant ideas for improvement.</p>]]>
</description>
<link>
http://www.newfangled.com/prototype_usability_testing
</link>
<dc:creator>
<![CDATA[Steve G]]>
</dc:creator>
<pubDate>
Tue, 17 Nov 2009 17:01:31 -0500
</pubDate>
</item>
<item>
<title>
<![CDATA[Three Years of Blogging Activity]]>
</title>
<description>
<![CDATA[<p>
<img width="508" style="border:1px solid #bababa;" src="/stuff/contentmgr/files/2/cb82c80d4e49a81015603bab825201c2/misc/3_years_of_blogging.jpg" />
</p>

<p>
I have a hypothesis that our company is much like an ecosystem--comprised of many areas of <i>unseen</i> activity in addition to the very visible activity. With that in mind, I've been collecting data for the past few weeks that is a bit different from what I might normally look at (i.e. website and financial data). I want to see what unknown connections there might be between what we do intentionally and what we do unintentionally.
</p>

<p>
The graph above, containing one set of data from my "peripheral data collection" of late, shows the number of blog posts we've published since starting the Newfangled blog back in October, 2006. Throughout these three years, we've never had any established quota for publishing frequency, so I wondered what conclusions I might be able to make from looking at post frequency from the beginning until now. One immediate conclusion I can make is that this is not a large enough sample of data to support identifying significant cycles. There are only two full years represented, and the truth of the matter is that our blogging was fairly inconsistent during those three years for pretty discernable reasons. The first is due to population. From 2007 through 2009, we added 9 new employees to our team, all of whom have contributed to the blog. We also lost a few who blogged from time to time. The second is due to a sense of purpose. When we first started, many of our post were culturally oriented, "look-what-I-found" kinds of posts. It wasn't really until July of 2008, when I published a post called <a href="/refining_your_blogging_strategy">Newfangled Blogging 2.0</a> that we really began to focus our efforts. In fact, July of 2008 was a time when we were focusing on <a href="/defining_a_web_content_strategy">defining a web content strategy</a> in earnest, blogging being just one piece. After that, we started to plan our writing- identifying topics we wanted to see covered in the blog, making the frequency more consistent and encouraging more people to write. We've been moderately successful in that; our production schedule does make it a challenge to do all that we want to do. But, we're getting the hang of it.
</p>

<p>
Note, for example, the May-June-July pattern that shows up in 2008 and repeats in 2009. That's an interesting trend. It used to be that summers were a slower time at Newfangled. But since 2007, summers have been the opposite. They've been very, very busy, so I'm not surprised to see the decrease in blogging at the outset of that season. I also wonder if we'll uncover a similar pattern in October-November-December. Time will tell.
</p>]]>
</description>
<link>
http://www.newfangled.com/visualizing_blogging_activity
</link>
<dc:creator>
<![CDATA[Chris]]>
</dc:creator>
<pubDate>
Tue, 17 Nov 2009 20:43:37 -0500
</pubDate>
</item>
<item>
<title>
<![CDATA[Optimize Your Website: Users First, Google Second]]>
</title>
<description>
<![CDATA[<p>The problem many websites have today isn't that their pages aren't optimized, it is that they are difficult to access, read, and take action on. SEO basics are widely known and easy to implement. Developing accurate prospect personas and the information architecture and calls to action that will guide their sessions is more complex--but it is well worth the effort.</p><p>"Optimizing" is an interesting word. It is important to ask the question, "For what, or <i>whom</i>, are we optimizing?" Is the ultimate goal of your site to be Search Engine Optimized, or User Optimized? Oddly enough, most people get stuck on the SEO part of this but don't stop to think about what happens if the SEO actually works and brings great prospects to their site. Your site's success isn't measured in traffic; it is measured in conversions.</p>
<p>We believe that focusing on the actual user experience is the best approach to optimization. If users can get to your site easily, intuitively find the content that they are most interested in, and easily read it, then Google will be able to do the same. The reason that Google has become synonymous with the word search itself is that Google is the best at mimicking human behavior. Since Google reads through web pages and sites like we do, we people consider it to be the best search engine. Makes sense, right?&nbsp;</p><p>We have seen time and time again that Google bait pages aren't great at bringing people in and keeping them. You may get a #1 ranking on Google for a certain phrase, but chances are that few people will actually search for that phrase and most of those that do click through to your Google bait page won't stick around for long once they get to your site. Why? Simple. It is because the page wasn't written for them, it was written for Google. Once they get to the page it just doesn't really seem all that interesting to them, so they bounce.</p><p>Plan your site and write your content for your prospects, make it an educational resource they can't live without, and I assure you that Google will respond in kind.</p>]]>
</description>
<link>
http://www.newfangled.com/optimize_website
</link>
<dc:creator>
<![CDATA[Mark O'Brien]]>
</dc:creator>
<pubDate>
Tue, 17 Nov 2009 09:12:02 -0500
</pubDate>
</item>
<item>
<title>
<![CDATA[Show Me the Data!]]>
</title>
<description>
<![CDATA[<p>
<img style="border:1px solid #bababa;" src="/stuff/contentmgr/files/2/0a2889156e4cbcb9bda9eed3192dadfc/misc/show_me_the_data.jpg" /><br /><br />

If I had to identify one of the biggest themes from the past year at Newfangled, one of them would definitely be measurement. In fact, ever since we <a href="/introducing_resourcing">started a serious resourcing effort</a> back in 2007, we've been learning just how valuable data is to us in general. Having access to real data is necessary to evaluating just about anything--whether it's the performance of a newlsetter campaign, the pages of your website, or even the people at your firm. Without it, you wouldn't be able to answer the questions that really matter: 
</p>

<blockquote>
<i>"What is this worth?" "Is this working?" "What should we change?"</i>
</blockquote>

<p>
Ok, so you should be pretty psyched about data. If you're not yet, I've done you a favor and gathered together nine posts from the past year that are all about data. Don't worry, they're not terribly technical, and each includes a helpful visualization that is created to help communicate the key point concluded from the data collected. Go nuts!
</p>

<p>
<small><i>The list below is ordered from newest to oldest.</i></small>
</p>

<table width="100%" cellspacing="0" cellpadding="0">
<tbody>

<tr>
<td width="33%" valign="top">
<a href="/visualizing_web_development_sales_makeup"><img src="/stuff/contentmgr/files/2/0a2889156e4cbcb9bda9eed3192dadfc/misc/projects_by_kind.jpg" style="border:1px solid #bababa;" /></a><br />
<small><a href="/visualizing_web_development_sales_makeup">3 Years of Sales Data</a></small>
</td>
<td width="33%" valign="top">
<a href="/visualizing_internal_project_management_communicat"><img src="/stuff/contentmgr/files/2/0a2889156e4cbcb9bda9eed3192dadfc/misc/project_management_logs.jpg" style="border:1px solid #bababa;" /></a><br />
<small><a href="http://visualizing_internal_project_management_communicat">2 Years of Communication Data</a></small>
</td>
<td width="33%" valign="top">
<a href="/visualizing_blogging_activity"><img src="/stuff/contentmgr/files/2/0a2889156e4cbcb9bda9eed3192dadfc/misc/blogging_data.jpg" style="border:1px solid #bababa;" /></a><br />
<small><a href="/visualizing_blogging_activity">3 Years of Blogging Data</a></small>
</td>
</tr>

<tr>
<td width="33%" valign="top">
<a href="/measuring_referral_traffic_goal_conversion_rate"><img src="/stuff/contentmgr/files/2/0a2889156e4cbcb9bda9eed3192dadfc/misc/6_months_of_referral_traffic.jpg" style="border:1px solid #bababa;margin:10px 0px 0px 0px;" /></a><br />
<small><a href="/measuring_referral_traffic_goal_conversion_rate">6 Months of Referral Data</a></small>
</td>
<td width="33%" valign="top">
<a href="/evaluating_newsletter_campaign_performance_data"><img src="/stuff/contentmgr/files/2/0a2889156e4cbcb9bda9eed3192dadfc/misc/6_months_of_newsletter_performance.jpg" style="border:1px solid #bababa;margin:10px 0px 0px 0px;" /></a><br />
<small><a href="/evaluating_newsletter_campaign_performance_data">6 Months of Campaign Data</a></small>
</td>
<td width="33%" valign="top">
<a href="/key_google_analytics_metrics"><img src="/stuff/contentmgr/files/2/0a2889156e4cbcb9bda9eed3192dadfc/misc/3_key_metrics.jpg" style="border:1px solid #bababa;margin:10px 0px 0px 0px;" /></a><br />
<small><a href="/key_google_analytics_metrics">Top 3 Analytics Metrics</a></small>
</td>
</tr>

<tr>
<td width="33%" valign="top">
<a href="/example_of_referral_traffic_and_goal_conversions"><img src="/stuff/contentmgr/files/2/0a2889156e4cbcb9bda9eed3192dadfc/misc/on_page_stats.jpg" style="border:1px solid #bababa;margin:10px 0px 0px 0px;" /></a><br />
<small><a href="/example_of_referral_traffic_and_goal_conversions">Impact of Specific Referrals</a></small>
</td>
<td width="33%" valign="top">
<a href="/newsletter_tracking_data"><img src="/stuff/contentmgr/files/2/0a2889156e4cbcb9bda9eed3192dadfc/misc/newsletter_tracking_data_2.jpg" style="border:1px solid #bababa;margin:10px 0px 0px 0px;" /></a><br />
<small><a href="/newsletter_tracking_data">2 Years of Newsletter Data</a></small>
</td>
<td width="33%" valign="top">
<a href="/visualization_of_email_frequency_data"><img src="/stuff/contentmgr/files/2/0a2889156e4cbcb9bda9eed3192dadfc/misc/email_stats.jpg" style="border:1px solid #bababa;margin:10px 0px 0px 0px;" /></a><br />
<small><a href="/visualization_of_email_frequency_data">1 Week's Email Data</a></small>
</td>
</tr>

<tr>
<td width="33%" valign="top">
<a href="/tracking_data_from_email_newsletter_campaign"><img src="/stuff/contentmgr/files/2/0a2889156e4cbcb9bda9eed3192dadfc/misc/newsletter_tracking_data.jpg" style="border:1px solid #bababa;margin:10px 0px 0px 0px;" /></a><br />
<small><a href="/tracking_data_from_email_newsletter_campaign">1 Year of Campaign Tracking Data</a></small>
</td>
<td width="33%" valign="top">
<a href="/newsletter_publication_and_call_to_action_stats"><img src="/stuff/contentmgr/files/2/0a2889156e4cbcb9bda9eed3192dadfc/misc/newsletter_cta_tracking_data.jpg" style="border:1px solid #bababa;margin:10px 0px 0px 0px;" /></a><br />
<small><a href="/newsletter_publication_and_call_to_action_stats">1 Month of CTA Data</a></small>
</td>
<td width="33%" valign="top">
<a href="/graphing_job_resourcing_data"><img src="/stuff/contentmgr/files/2/0a2889156e4cbcb9bda9eed3192dadfc/misc/time_data.jpg" style="border:1px solid #bababa;margin:10px 0px 0px 0px;" /></a><br />
<small><a href="/graphing_job_resourcing_data">1 Day of Timesheet Data</a></small>
</td>
</tr>

</tbody>
</table>]]>
</description>
<link>
http://www.newfangled.com/visualizing_website_measurement_data
</link>
<dc:creator>
<![CDATA[Chris]]>
</dc:creator>
<pubDate>
Mon, 16 Nov 2009 15:25:19 -0500
</pubDate>
</item>
<item>
<title>
<![CDATA[Editing for the Nonprofessional Editor]]>
</title>
<description>
<![CDATA[<p>Everybody at Newfangled has a superpower. Mine is baking pies:<br /><br /><img alt="pie" src="/stuff/contentmgr/files/2/74f3daa750b84c7c224943dfb26eab59/misc/pie.jpg" style="float: left; border: 1px solid #bababa; margin-right: 20px;" height="180" width="240" />But
if I were going to choose something a little more practical (which goes
against the point of a superpower), I would point to my secret identity
as a grammar nerd. Before coming to Newfangled, I majored in English,
taught freshman composition, and tutored in a writing center. Working
at a place where a lot of writing takes place, I end up doing a fair
amount of editing. Chris has recently provided a lot of good <a title="advice" href="/presentation_on_business_writing" id="k08q">advice</a> on <a title="professional" href="/how_to_write_a_newsletter" id="m_rw">professional</a> <a title="writing" href="/best_writing_formats_for_web_content_strategy" id="k4dk">writing</a>; this is my take on another side of the process.<br /><br />The
common understanding of what English majors do tends to involve a lot
of punctuation--"Uh-oh! I better watch my grammar!" was a popular
comment when I used to introduce myself as a writing teacher. I do
happen to be a punctuation fan, but that kind of stuff was actually a
very minor part of any of my previous roles; instead, the writing
program where I taught focused on upper-level concerns like introducing
students to college-level work and teaching them how to revise their
writing. One of the things we stressed was that what many students
thought of as editing--checking the commas, basically--was just the
last, and in some ways the least important, stage of a bigger process.<br /><br />Not
every piece of professional writing you do will involve the same steps
I used to put my freshmen through. But there are three general stages
of revision that will probably come into play in some form for most of
the writing you do. They can be characterized as:<br /><b><br />1. Editing</b><br />At
this stage, the focus should be on the big picture. What are you really
saying? How are you engaging your audience? How is your piece
structured? Until you've got that kind of stuff figured out, it's not
worth getting too hung up on the commas.<br /><br /><b>2. Copyediting<br /></b>Once
you've got the ideas in place and structured the way you want them, you
can start focusing more on the wording. Your draft will probably have
some unclear patches where you weren't sure what you wanted to say
until after you had said it; now that you know, this is the time to
clean it up.<br /><br /><b>3. Proofreading<br /></b>Here's the part where you
make sure everything is ready for presentation. Run spellcheck (but
don't assume it knows everything), and yes, clean up those commas.<br /><br />If
you find yourself asked to help a colleague with some writing--good for
you! You must have gotten a reputation as a grammar nerd yourself. In
that case, one of the most important things I would recommend
(especially if it's the first time this person has enlisted you as an
editor) is taking some time up front to find out where in the revision
process your writer is. Whereas all the students in my composition
classes were supposed to be on the same trajectory, real-world writers
may seek out help at any stage, and that can determine what editing
approach will be effective. If it's early on, and your colleague is
trying to use you as a sounding board for ideas, there's not much point
going through and fixing the spelling; the words are likely to change
several times anyway. In that situation, it may be more helpful for you
to ask questions that help focus the argument, or point out places
where an idea could be developed more. On the other hand, sometimes the
last-minute comma check is exactly what's needed; in those cases,
making structural suggestions may just cause frustration about issues
there isn't really time to address.<br /><br />The editing I do at
Newfangled falls at all points of this range. Most frequently, I'll get
a question along the lines of "How does this sentence look?". I'll say,
"Looks good!" or "Take out the comma," and that's that.</p><p><img style="float: left; margin-right: 20px; border: 1px solid #bababa;" alt="newsletter revsion history" src="/stuff/contentmgr/files/2/74f3daa750b84c7c224943dfb26eab59/misc/newsletter_revision_history.jpg" height="270" width="254" />Less frequently but more consistently, I edit <a title="the Newfangled newsletter" href="/website_topics_for_designers_and_marketers" id="b:hn">the Newfangled newsletter</a>
each month before it goes to press. Several factors make this process
different than a one-off sentence or paragraph correction:<br />-I'm
working with an entire document rather than just an isolated section.
Seeing the big picture gives me the chance to make general structural
suggestions or get a better sense of the overall tone.<br />-I get the
draft a little in advance of the publish date, which makes it possible
to address those kinds of upper-level issues when needed. There's time
to sit down and talk through any points that are unclear.<br />-I'm working with <a title="the same writer" href="/chris_butler_blog" id="be:0">the same writer</a>
every month, which has allowed me to develop a sense of what kinds of
feedback will be useful. For instance, the introduction is often one of
the last things written (which is a very common writing strategy and is
generally the approach I would recommend), so it's usually a key topic
of discussion.<br /><br />Because my background is in teaching rather than
commercial editing, the editing style I've learned focuses heavily on
getting people to develop and express their own ideas. One of my
tendencies as an editor is therefore to want the writer to do the
rewriting, rather than swooping in with a red pen and doing it all
myself. The earlier in the revision process, the stronger that tendency
is. If I find an idea unclear, I'll usually ask questions about it that
lead to a discussion about ways the writer can clarify; if the wording
is unclear in a certain spot, I'll write out an alternate wording or
two but leave it up to the writer to choose which to use; if I see a
misspelling or punctuation error, I'll usually just take care of it.
Again, how appropriate this hands-off style is depends on the
situation. I like that it allows authors to retain a sense of
intellectual ownership over their writing and to know the final product
still feels like their voice. (Ending up with a document that doesn't
sound like me is one of the things I want to avoid when getting my own
writing edited.) On the other hand, it would probably be good for me to
develop more comfort with just jumping in and taking care of everything
when the situation calls for it.<br /><br />What about you--do you
collaborate on writing, either as an author or an editor? If you seek
out editing for your writing, what kinds of responses do you find
helpful? If you tend to be the one doing the editing, how do you
approach the situation?</p>]]>
</description>
<link>
http://www.newfangled.com/editing_professional_writing
</link>
<dc:creator>
<![CDATA[Sarah]]>
</dc:creator>
<pubDate>
Mon, 16 Nov 2009 15:12:02 -0500
</pubDate>
</item>
<item>
<title>
<![CDATA[The History of Our Office]]>
</title>
<description>
<![CDATA[<p>I just read/listened to <a href="/content20107" target="_blank">Sarah's great post</a> about the soundscape of the Newfangled office and got inspired to write down a few things I've recently learned about our historic digs. When we had our last front porch social with BlogAds (our upstairs neighbors) the mayor showed up, and he told me the history of our building. </p><p>&nbsp;</p><center><object height="300" width="400"> <param value="offsite=true&amp;lang=en-us&amp;page_show_url=%2Fphotos%2Fobrienfamilync%2Fsets%2F72157622779246130%2Fshow%2F&amp;page_show_back_url=%2Fphotos%2Fobrienfamilync%2Fsets%2F72157622779246130%2F&amp;set_id=72157622779246130&amp;jump_to=" name="flashvars" /> <param value="http://www.flickr.com/apps/slideshow/show.swf?v=71649" name="movie" /> <param value="true" name="allowFullScreen" /><embed height="300" width="400" flashvars="offsite=true&amp;lang=en-us&amp;page_show_url=%2Fphotos%2Fobrienfamilync%2Fsets%2F72157622779246130%2Fshow%2F&amp;page_show_back_url=%2Fphotos%2Fobrienfamilync%2Fsets%2F72157622779246130%2F&amp;set_id=72157622779246130&amp;jump_to=" allowfullscreen="true" src="http://www.flickr.com/apps/slideshow/show.swf?v=71649" type="application/x-shockwave-flash"></embed></object></center>

<p>Our building was actually the first public building in <a href="http://maps.google.com/maps?hl=en&amp;client=safari&amp;rls=en&amp;q=carrboro&amp;um=1&amp;ie=UTF-8&amp;hq=&amp;hnear=Carrboro,+NC&amp;gl=us&amp;ei=9Hf9Sr6lD43xnQfT6fi8BQ&amp;sa=X&amp;oi=geocode_result&amp;ct=title&amp;resnum=1&amp;ved=0CAoQ8gEwAA" target="_blank">Carrboro</a>. It was built because the train tracks happened to end at this location. They were supposed to continue on a half mile into Chapel Hill, but they ran out of funding so they stopped where they happened to leave off. The original use for the rail line was as a drop-off point for the local farmers to bring their cotton and tobacco. The man that happened to own the few hundred acre farm that abutted the tracks decided to build a building (our glorious office) to hold the offloaded wares overnight. Before long, he decided to outfit the building with the area's first steam engine. This was first used to power a cotton gin and later a grist mill--both of which resided inside the building. At some point between then and now more funding was acquired and today the rail continues on that half mile to a plant that powers UNC. The line is mostly used for coal transport to that plant.</p>]]>
</description>
<link>
http://www.newfangled.com/web_development_office
</link>
<dc:creator>
<![CDATA[Mark O'Brien]]>
</dc:creator>
<pubDate>
Fri, 13 Nov 2009 10:11:48 -0500
</pubDate>
</item>
<item>
<title>
<![CDATA[A Year of Ideas]]>
</title>
<description>
<![CDATA[<p>
<img src="/stuff/contentmgr/files/1/543a239c5a5d35ca1c1828c82af5c609/misc/a_year_of_ideas_sm.jpg" style="border:1px solid #bababa;margin:0px 20px 20px 0px;" align="left" />

Is it preferable to read long format content on a screen or on the printed page? This is a question that I think we're going to be wrestling with as a culture for some time to come. In the meantime our tendency is probably to do much of our day-to-day reading online (I've seen plenty of posts lately declaring all kinds of ridiculous things to the tune of "I don't read books anymore, therefore books must be dead"), though I know there are still plenty of people holding out for actual books. I read quite a bit, both online and in books. In fact, I often bookmark articles that I know I'd be more likely to read if they were in print than I am with them on a screen. This is particularly true of longer content (much of it written by my favorite publications like The Atlantic, The New Yorker, and WIRED). So, after reading a <a target="_blank" href="http://blog.thoughtwax.com/2009/03/instapaper-analogue-edition">post by Emmet Connolly</a>, I began collecting those longer articles and creating printed anthologies of them on Lulu.com. The one pictured above is my third, which I just printed last week. This time, I kept a bookmarks folder of articles that I felt represented the most important ideas I'd encountered in 2009- so I called it "A Year of Ideas."
</p>

<p>
Until I get seduced by the perfect reading device, I'm pretty convinced that there is untapped power and potential in print-on-demand (for example, check out the <a href="http://spectrum.ieee.org/computing/hardware/pushbutton-books" target="_blank">Espresso Book Machine</a>. Russell Davies, the person who, believe it or not, first exposed me to the idea of print-on-demand, <a href="http://russelldavies.typepad.com/planning/2009/11/dconstruct.html" target="_blank">says it perfectly</a>:
</p>

<blockquote>
My favourite example is this: <a target="_blank" href="http://www.flickr.com/photos/thoughtwax/3331917198/">Things I Word Rather Read On Paper</a>. Is it combines what the web does well; publishing, gathering, discovering and curating content (via instapaper) with what print does well; being readable, durable and portable.  
</blockquote>

<p>
As I read that, I realized I should probably put together a post that outlines my process of gathering, discovering and curating content- it's a fairly complicated one when you take into account all the various channels for finding, experiencing and sharing information. But, it is one way of <a href="/learning_how_to_rapidly_process_information">being a human synthesizer</a>- a necessary discipline for people in our industry. For now, though, I wanted to again share the printed side of it- particularly because I'm in awe of how good of a job Lulu.com does. I submitted my files and had my book within several days; the quality of the book itself is very, very good.
</p>

<p>
The image below shows an interior spread of my "A Year of Ideas" book, which includes an image by <a target="_blank" href="http://butdoesitfloat.com/filter/lauris-paulus">Lauris Paulus</a>&nbsp;and an article titled <a target="_blank" href="http://www.cityofsound.com/blog/2008/02/the-street-as-p.html">The Street as Platform</a> by Dan Hill. (<i>Lauris and Dan, don't worry, I'm not selling this book. It's just for me.</i>)
</p>

<p>
<img src="/stuff/contentmgr/files/1/543a239c5a5d35ca1c1828c82af5c609/misc/a_year_of_ideas_int_1.jpg" style="border:1px solid #bababa;margin:0px 0px 0px 0px;" />
</p>

<p>
<br />- - - 
</p>

<p>
Here are the other two books I've created using Lulu.com. The <a href="/creating_a_article_compilation_book_with_lulu_com">book on the left</a> was the first one I created last March. The <a href="/creating_a_book_on_lulu_dot_com">book on the right</a> is the second one I created shortly after in April:
</p>

<p>
<a href="/creating_a_article_compilation_book_with_lulu_com"><img src="/stuff/contentmgr/files/1/543a239c5a5d35ca1c1828c82af5c609/misc/print_on_demand_1.jpg" style="border:1px solid #bababa;margin:0px 20px 0px 0px;" align="left" /></a>

<a href="/creating_a_book_on_lulu_dot_com"><img src="/stuff/contentmgr/files/1/543a239c5a5d35ca1c1828c82af5c609/misc/print_on_demand_2.jpg" style="border:1px solid #bababa;margin:0px 20px 0px 0px;" align="left" /></a>
</p>]]>
</description>
<link>
http://www.newfangled.com/synthesizing_web_content_with_print_on_demand
</link>
<dc:creator>
<![CDATA[Chris]]>
</dc:creator>
<pubDate>
Thu, 12 Nov 2009 17:02:36 -0500
</pubDate>
</item>
<item>
<title>
<![CDATA[Recognizing the Complexity and Value of Transferring Information]]>
</title>
<description>
<![CDATA[<p>
<img style="border:1px solid #bababa;margin:0px 20px 10px 0px;" src="/stuff/contentmgr/files/1/f71f15c00170f6f5bfb1d6c88f363772/misc/nyt_med.jpg" align="left" />

<b>The Problem</b><br />
This is a New York Times newspaper vending box located right near my office in the parking lot of <a target="_blank" href="http://www.jesseescoffee.com/">a wonderful coffee shop called Jessee's</a>. The other day <a target="_blank" href="http://maps.google.com/maps?f=q&amp;source=s_q&amp;hl=en&amp;geocode=&amp;q=jessee%27s+carrboro,+nc&amp;sll=35.930969,-79.029272&amp;sspn=0.012562,0.024934&amp;ie=UTF8&amp;hq=jessee%27s&amp;hnear=Carrboro,+NC&amp;ll=35.91064,-79.066782&amp;spn=0,359.996883&amp;z=19&amp;layer=c&amp;cbll=35.910689,-79.066869&amp;panoid=m43OOrtsQcbj3_qUp_6Ddw&amp;cbp=12,82.19,,0,0.95">I noticed the box</a> and it occurred to me how radically things have changed in terms of how we transfer information in our culture. Consider how a newspaper ends up in a box like this one: Newspapers are bundled after print and available for delivery collection at a distribution center starting at midnight the morning of publication. Drivers pick up their day's delivery and spend the next eight hours depositing them in vending boxes on their route and collecting coins and the unsold papers from the previous day. Considering how most of us consume news information today--instantly and online--this process seems obviously inefficient and antiquated (the boxes can weigh up to 100 pounds and cost $450 each). Needless to say, this kind of business is not long for this world. Here's a quote from a <a target="_blank" href="http://www.cnn.com/2009/US/05/22/newspaper.coin.machines/index.html">CNN article</a> I found on the subject:
</p>

<blockquote>
"It's 5:30 a.m. on a Saturday, and a white delivery truck for the New Jersey Record has just pulled into the parking lot outside the Plaza Diner in Fort Lee, New Jersey. The driver -- Mike, who asked that his last name not be used -- is at one of his 130 stops on an eight-hour shift that began at midnight. Mike's job, which takes less than a couple of minutes per stop, entails filling the coin-operated machine with the day's papers, collecting unsold copies and emptying the machine of its coins. Even though Mike has a full schedule and lots of stops, it doesn't equate to pushing as many papers as he once did. Mike loads 15 copies of the Record into one machine -- and that's a good load, he says. Other locations receive only five to seven copies. He's also tasked with filling machines for USA Today. Though he's been on this job for only two years, Mike has been on the route long enough to know business is down. He says newspapers sell better at train stations than from the street machines he services."
</blockquote>

<p>
<b>The Solution?</b><br />
The image below represents the solution to the inefficiencies of the vending box model. <a target="_blank" href="https://timesreader.nytimes.com/">TimesReader</a> is an application that pulls New York Times content to your computer every day in a more "traditional" reading format than the New York Times website. It also archives up to a week of back "papers" and allows all kinds of unique navigation options. In addition to more content, subscribers get an ad-free interface. For now,though, the website, which provides all New York Times content unrestricted will be the "solution" for people like me. But at some point, The New York Times, and other leading newspapers, will figure out a paid model and the TimesReader will be there to pick it up- particularly if additional devices (such as the rumored Apple tablet) strike deals with newspapers-- see the video with Bill Keller at the end of this post for more on that subject. 
</p>

<p>
<img style="border:1px solid #bababa;margin:0px 0px 5px 0px;" src="/stuff/contentmgr/files/1/f71f15c00170f6f5bfb1d6c88f363772/misc/times_reader.jpg" /><br /><br />

<b>The Real Problem</b><br />
The real problem isn't really the method of delivery. See, the vending box method may seem like an inefficient vestige of the past (which it is, in some respects), but we shouldn't necessarily consider the online solutions as preferable on the basis of perceived simplicity. I think that the contemporary delivery methods are probably dependent upon significantly more complex systems. With the print model, there is one "template" and several delivery methods (homes, businesses, boxes, and particular vendor outlets). With the online model, there are multiple templates (website, emails, unique content channels, advertising, mobile applications, etc.) and the massive conundrum of delivery (from once daily to constant delivery to a multiplicity of formats).
</p>

<p>
<a href="/stuff/contentmgr/files/1/f71f15c00170f6f5bfb1d6c88f363772/misc/circ2.jpg" target="_blank"><img style="border:1px solid #bababa;margin:0px 20px 20px 0px;" src="/stuff/contentmgr/files/1/f71f15c00170f6f5bfb1d6c88f363772/misc/circ2.jpg" width="150" align="left" /></a>

The <i>real</i> problem is regaining a perception of value, which, in part, requires an accurate perception of complexity. I'm not sure how likely that is- it's going to depend upon the unique perspectives of individuals everywhere. (For example, consider the perspective of the vending box delivery driver once that system is phased out.) But that aside, the current climate of content consumption is driven by our expectation that it's all free. 
</p>

<p>
The graph shown to the left (courtesy of <a target="_blank" href="http://www.theawl.com/2009/10/a-graphic-history-of-newspaper-circulation-over-the-last-two-decades">The Awl</a>) highlights an overall diminishing circulation trend among the major U.S. papers (the Boston Globe sank below the 400K mark, which is why it does not appear on the chart). However, the Wall Street Journal appears to be enjoying a healthier reality than the others. Because of the overall decline in circulation, though, advertising is waning and news offices are laying off many journalists (and plenty of other positions integral to the production process). None of this is going to be solved (even by a micropayment scheme) until we recognize the value of the systems required in order to produce this content and act upon that recognition. 
</p>

<p>
<br /><b>The Real Solution</b><br />
So, I don't exactly know what the <i>real</i> solution is, but I do know it has everything to do with perception of value. With newspapers, the value hierarchy begins with the inherent value of the information itself, followed by the value of the thinking behind it-- the writers, editors, producers, etc., followed by the value of the organizational systems, followed by the delivery systems, followed by the value of the corporeal product itself. It's clear what's expendable. I also know that many other industries besides journalism are facing this very same issue right now, including our own. For us, and companies like ours, the value hierarchy is very similar to that of a newspaper. Much of our costs have more to do with planning than implementation, and despite our knowledge that the planning is the foundation of any product, getting the customer to recognize the value of it a challenge. That's why we've spent the majority of the past year highlighting the value and necessity of planning, slowly changing the culture of our small corner of the web. I hope that a similar progression occurs in other industries as well.
</p>

<p>
In the video below, Bill Keller speaks to the digital group at the New York Times, and speaks to many of the topics I've mentioned above-- potential pricing models, new delivery methods, and new technologies to fulfill them...
</p>

<p>
- - -
</p>

<p>
<object width="400" height="293"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=7166514&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" /><embed src="http://vimeo.com/moogaloop.swf?clip_id=7166514&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="400" height="293"></embed></object></p><p>&nbsp;</p><p><a href="http://vimeo.com/7166514">Bill Keller speaks to the digital group at The New York Times</a> from <a href="http://vimeo.com/niemanlab">Nieman Journalism Lab</a> on <a href="http://vimeo.com">Vimeo</a>.</p>]]>
</description>
<link>
http://www.newfangled.com/recognizing_the_complexity_and_value_of_transferri
</link>
<dc:creator>
<![CDATA[Chris]]>
</dc:creator>
<pubDate>
Wed, 11 Nov 2009 09:47:15 -0500
</pubDate>
</item>
</channel>



</rss>