<?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>Undercurrent &#187; tools</title>
	<atom:link href="http://www.undercurrent.com/post/tag/tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.undercurrent.com</link>
	<description>Undercurrent is a digital strategy firm. We apply a digital worldview to the challenges and ambitions of complex organizations.</description>
	<lastBuildDate>Sat, 18 May 2013 23:46: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>Building Strategically: A Manifesto for Successful Implementation</title>
		<link>http://www.undercurrent.com/post/building-strategically-a-manifesto-for-successful-implementation/</link>
		<comments>http://www.undercurrent.com/post/building-strategically-a-manifesto-for-successful-implementation/#comments</comments>
		<pubDate>Tue, 12 Jun 2012 19:55:01 +0000</pubDate>
		<dc:creator>Joanna Beltowska</dc:creator>
				<category><![CDATA[Production Notes]]></category>
		<category><![CDATA[strategy]]></category>
		<category><![CDATA[agencies]]></category>
		<category><![CDATA[competitive advantage]]></category>
		<category><![CDATA[digital strategy]]></category>
		<category><![CDATA[orchestration]]></category>
		<category><![CDATA[production]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[tools]]></category>

		<guid isPermaLink="false">http://undercurrent.com/?p=2872</guid>
		<description><![CDATA[During the planning and execution phases of a digital product, service or system, there’s a non-trivial amount of decisions to be made that have long-bearing consequences for the ultimate success of the project, as well as for the ease of its future iterations and additions. Many of these decisions have to do with choosing how [...]]]></description>
			<content:encoded><![CDATA[<p>During the planning and execution phases of a digital product, service or system, there’s a non-trivial amount of decisions to be made that have long-bearing consequences for the ultimate success of the project, as well as for the ease of its future iterations and additions. Many of these decisions have to do with choosing how and where you’ll ultimately invest a good amount of your budget; the money ear-marked for technical execution.</p>
<p><span id="more-2872"></span></p>
<p>If you’re on the marketing or planning side, and are wondering how this at all applies to you, you should read the first part of this two-part series on <a href="http://undercurrent.com/post/where-digital-strategy-planning-and-practice-overlap/">how digital strategy translates into digital execution</a>. In the short term, this is about building things, something marketing traditionally isn’t concerned with. But in the long term, this is really about money and making smart business decisions. Building strategically means that you’re building competitive advantage by creating better digital experiences that last longer and are more adaptive to changing consumer needs and market conditions.</p>
<p>Because of our vantage point as digital strategy consultants, we get to see a lot of companies right at this crossroads – facing seemingly small decisions whose full context and consequences are not entirely defined, and at a risk of cornering themselves down the road because of it. Our hope is that that this list will help to shed some light on a few of these treacherous decision points.</p>
<p>It is by no means an exhaustive or definite list – attempting to pen a comprehensive collection of generally applicable, yet sufficiently directional, guidelines for applying strategy to the implementation of digital systems would be a Sisyphean task. In fact, <strong>we welcome any and all suggestions for edits and additions. </strong></p>
<p>&nbsp;</p>
<h2></h2>
<h2><span style="text-decoration: underline"><strong>A MANIFESTO FOR SUCCESSFUL IMPLEMENTATION</strong></span></h2>
<h2></h2>
<h2><strong>DESIGN FOR FUTURE NEEDS AND TECHNOLOGY</strong></h2>
<p><strong>1. Build for current and future web standards</strong></p>
<ul>
<li><em>It&#8217;ll keep your solution sustainable.</em> Platforms and technologies that don’t fall under common web guidelines and standards (like the HTML5 predecessor Adobe Flash) are at a risk of being phased out and abandoned by the design and development communities as their popularity wanes. They are met with less support and maintenance and incur higher costs as developers and agencies charge more for longer and more complex production cycles. We’re not absolutist here; there are times when older and less buzzed-about technologies are the appropriate tool for the job. Their application however relies on <a href="http://en.wikipedia.org/wiki/Coupling_(computer_programming)">attributing little dependence</a> to them, in accordance with sound system design principles.</li>
</ul>
<ul>
<li><em>It&#8217;ll make your solution recombinant and adaptive.</em> Building with standards in mind will leave you with something that plays nicely with other Internet things, such as API:s, the communication interfaces of other Internet <a href="http://instagr.am/developer/">platforms</a> <a href="https://dev.twitter.com/">and</a> <a href="https://developer.spotify.com/technologies/web-api/">services</a>). More importantly, products designed for web standards can also be used by the most number of people in the long run as consumers upgrade to modern, standard compliant, digital devices and web browsers.</li>
</ul>
<p><strong>2. Build for tomorrow</strong></p>
<ul>
<li><em>Your business might have changed by the time you&#8217;re done.</em> Implementation can easily take up to six months or a year &#8211; you&#8217;ll be better off planning ahead (just make sure you&#8217;re being reasonable) and designing for the needs you anticipate at that point in time. Does it seem like mobile will account for a significant share in traffic by the end of the year? Strongly consider designing your digital execution to be accessible via mobile devices – even though no one else is doing this (yet).</li>
</ul>
<blockquote><p>Building strategically means that you’re building competitive advantage by creating better digital experiences that last longer and are more adaptive to changing consumer needs and market conditions.</p></blockquote>
<p><strong>3. Design for scaleability</strong></p>
<ul>
<li><em>It&#8217;ll enable you to minimize growing pains.</em> Make sure you’re not constraining future growth by anticipating what is required to scale your product and its associated operations. Prepare a parallel path of production to ease a future switch between platforms or technologies. If you&#8217;re a small brand who is only getting started with eCommerce, you&#8217;ll do just fine investing in a light and externally hosted turnkey storefront. If your new initiative proves successful, you can start planning for an upgrade to an enterprise solution and know that the transition will be relatively easy. Cloud computing services and cloud-based products are great for this, because they generally charge only for what you need and consume.</li>
</ul>
<p><strong><br />
</strong></p>
<h2>DON&#8217;T BE AFRAID TO START FROM SCRATCH</h2>
<p><strong></strong><strong>1. Don’t compromise your future because of previous investments</strong></p>
<ul>
<li><em>Avoid sunk cost fallacy</em>. This is one of the most treacherous aspects of investing in digital tools and services, because it is so difficult to realize and acknowledge. Defending previous investments is a natural instinct; when we remember the effort and emotion we put into creating something, we&#8217;re hesitant to throw it to the side, even though it might have outlived its usefulness. In fact, <a href="http://youarenotsosmart.com/2011/03/25/the-sunk-cost-fallacy/">as psychologists Kahneman and Tversky proved</a>, the more of ourselves we invest into something, the harder it becomes to abandon; loss has a more powerful effect on our minds than potential gain. But poor, previous, investments can hamper progress, leaving the field open for competitors to speed ahead.</li>
</ul>
<ul>
<li>&#8230;<em>But beware of incurring <a href="http://en.wikipedia.org/wiki/Technical_debt">Technical Debt</a>. </em>This is a fairly advanced concept which we won’t explore further in this piece. In short, technical debt describes the impeding consequences of rushing into new investments before completing necessary preceding work. It’s an idea that is crucial for any organization maintaining its own codebase to be familiar with.</li>
</ul>
<p><strong>2. Adapt solutions for your needs; don&#8217;t adapt your needs around available solutions</strong></p>
<ul>
<li><em>What works for others may not work for you. </em>Every business is unique. Your starting point should be your very own set of needs and capabilities. Evaluate prospective solutions against that.</li>
</ul>
<ul>
<li><em>Avoid swiss army knives. </em>They&#8217;re the most dazzling alternative – all of those cool features! – but do you really need all of that stuff? Do you have the knowledge and resources to maintain a more complex solution than what your actual needs call for? 360-degree solutions are the equivalent of doorman buildings; they come with common areas, lobbies and a lobby attendants, gyms, live-in supers, and the doorman, of course. A non-trivial amount of your rent is going towards covering all of these fancy things – but how often will you really use them? Figure out what you need your investment to accomplish, then find someone to help you either build or give you advice on what to buy that is exactly that and nothing more.</li>
</ul>
<p><strong>3. Open Source FTW</strong></p>
<ul>
<li><em>The sky is the limit. </em>With the explosion of open source technologies, platforms and services, there&#8217;s no longer any excuse to default to buying licensed out-of-the-box solutions anymore. WordPress for instance is an incredibly versatile web platform that is free. By compromising to handle custom development and dedicated support yourself (or hiring a partner to help you), you&#8217;re getting all of that versatility for free, without crowding your platform with features you don&#8217;t need. WordPress, and open solutions like it, are like Mr. Potato heads: they provide a well-defined, functional core solution that can be enhanced by innumerable add-ons, provided by a huge and vibrant online community of designers and developers.</li>
</ul>
<p><strong>4. Don’t outsource control</strong></p>
<ul>
<li><em>Think twice about licensing solutions. </em>Licensing a product or service might sound like a good idea, but you could find yourself in a situation down the road where the vendor&#8217;s maintenance isn’t on track with your business needs or with your category standard. You&#8217;ll be effectively tied to the grace and capability of your vendor for the remainder of your contract. You might also become blindsided to problems that your vendor is having, because you&#8217;re in a relationship with them and have already invested a significant amount of money (see “1. Don&#8217;t compromise your future because of previous investments”).</li>
</ul>
<p><strong><br />
</strong></p>
<h2>PARTNERS, NOT VENDORS</h2>
<p><strong></strong><strong>Digital Production is Collaborative.</strong></p>
<ul>
<li><em>Avoid &#8220;Shiny Object Fallacy&#8221;.</em> Our last piece of advice is perhaps our most important: Do your best to find a trustworthy, capable partner to help you realize your vision. Undercurrent Production Director Matthew Carlin addresses this topic expertly in a <a href="http://undercurrent.com/post/partners-not-vendors-a-digital-production-manifesto/">separate blog post</a>.</li>
</ul>
<p>&nbsp;</p>
<p><em>This post was written by strategists Joanna Beltowska (<a href="https://twitter.com/#!/jbeltowska">@jbeltowska)</a> and Vladimir Pick (<a href="https://twitter.com/#!/vladimirpick">@vladimirpick</a>) who both come from a background of software and web development. </em></p>
<p><em><br />
</em></p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.undercurrent.com/post/building-strategically-a-manifesto-for-successful-implementation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Numblr: Designing A Tumblr Analytics Platform For All</title>
		<link>http://www.undercurrent.com/post/numblr-designing-a-tumblr-analytics-platform-for-all/</link>
		<comments>http://www.undercurrent.com/post/numblr-designing-a-tumblr-analytics-platform-for-all/#comments</comments>
		<pubDate>Wed, 09 May 2012 15:26:24 +0000</pubDate>
		<dc:creator>Derrick Bradley</dc:creator>
				<category><![CDATA[Dispatches]]></category>
		<category><![CDATA[metrics]]></category>
		<category><![CDATA[analytics]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[production]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[tumblr]]></category>

		<guid isPermaLink="false">http://undercurrent.com/?p=2555</guid>
		<description><![CDATA[A few weeks back I was trying to work out how to analyze a Tumblr’s performance – a long-standing issue for everyone, particularly within the fashion industry. Short of cataloging every note and post by hand, there isn’t any tool out there that solves for this problem and so a few days ago I, along [...]]]></description>
			<content:encoded><![CDATA[<p>A few weeks back I was trying to work out how to analyze a Tumblr’s performance – a long-standing issue for everyone, particularly within the fashion industry. Short of cataloging every note and post by hand, there isn’t any tool out there that solves for this problem and so a few days ago I, along with my colleague Vladimir Pick, set out to build our own. It’s called <a title="Numblr, A Tumblr Analytics Tool" href="http://tumblr.undercurrent.com" target="_blank">Numblr</a>. It was conceived, launched, and in use by others in four days. What follows is a reflection on our process.<span id="more-2555"></span></p>
<h2><strong>Fewer Feedback Loops</strong></h2>
<p>We didn&#8217;t ask for any input during the first iteration of this project. Few people in the office knew it was being created, unless they happen to peer over our desks. Working alone allowed us to build momentum, move fast, and stay focussed and excited on the initial vision we crafted. We were working on <a title="Do The Least You Need To Succeed" href="http://undercurrent.com/post/do-the-least-you-need-to-succeed/" target="_blank">creating a minimum viable project</a>; had we invited feedback early on, a ton of solid ideas would have came our way, but with them, a ton of meetings to toil over what feedback we&#8217;d accept and what the timelines were for implementing them. <a title="Your Digital Worldview Doesnt Need An App" href="http://undercurrent.com/post/your-digital-worldview-doesnt-need-an-app/" target="_blank">We had already decided to launch first, iterate, and accept feedback later</a>. The lesson here is don&#8217;t try to build v2 when v1 will do, especially in low-risk environments.</p>
<h2><strong>Small Victories</strong></h2>
<p>By keeping the entire operation lean and only making small, incremental changes to the tool, everything started to feel like a small victory. Added a new line of CSS? Win. Informal, but frequent meetings no longer than a couple minutes? Win. Revised the structure of a multi-dimensional array? Win. With only small pockets of time to work on this project, we were forced to be focussed on clear outputs. This made small achievements appear as clear victories, meaning every incremental change increased our momentum and drove the project forward.</p>
<h2><strong>Define Boundaries You&#8217;re Comfortable Working In</strong></h2>
<p>Identifying a specific problem to solve for and finding the right people to solve for it is key to a quick success. We never explicitly outlined boundaries when it came to our roles on the project, but given our familiarity with each other, and pre-existing working relationships, we didn&#8217;t have to. We knew what our strong suits were and played to our strengths without needing to discuss it. That might sound obvious, but as team size grows and varying degrees of expertise start to overlap, selecting the right person to champion a specific role gets tricky.</p>
<p>Beyond roles, the boundaries of the project were defined by the data provided by Tumblr&#8217;s API and the narrative we were trying to craft. Having used the platform for a few years, and having poked around the API once or twice beforehand, it took little time to decide which metrics we could accurately depict, which ones we couldn&#8217;t, and how sophisticated we could make our visualization of them for a v1 launch.</p>
<h2><strong>Use The Right Existing Assets</strong></h2>
<p>Existing assets can help you move fast, but they’re only helpful if you understand them well enough. We used Twitter&#8217;s Bootstrap framework, for example, because it&#8217;s well documented and we had previous experience with it when we built <a href="http://mecemaker.com/">M.E.C.E. Maker</a>, another Undercurrent project. The same wasn&#8217;t true for the charts we wanted to make, though. Despite the dozens of charting libraries out there, we could&#8217;t find one that we could quickly learn the ins and outs of, so we built ours from scratch. As a result, making changes to them is easy-peasy.</p>
<p>This project was only born because of the mission and freedom we&#8217;re given at Undercurrent to explore the internet and create new knowledge. Without it, we wouldn&#8217;t know as much as we do, nor have the time to dedicate to a project like this. Come <a href="http://tumblr.undercurrent.com/">check out Numblr</a> and give us your feedback. It&#8217;s buggy, but who gives a shit.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.undercurrent.com/post/numblr-designing-a-tumblr-analytics-platform-for-all/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Is Your Measurement Strategy Broken?</title>
		<link>http://www.undercurrent.com/post/is-your-measurement-strategy-broken/</link>
		<comments>http://www.undercurrent.com/post/is-your-measurement-strategy-broken/#comments</comments>
		<pubDate>Wed, 08 Feb 2012 21:00:12 +0000</pubDate>
		<dc:creator>Derrick Bradley</dc:creator>
				<category><![CDATA[Dispatches]]></category>
		<category><![CDATA[strategy]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[social media]]></category>
		<category><![CDATA[tools]]></category>

		<guid isPermaLink="false">http://undercurrent.com/?p=636</guid>
		<description><![CDATA[Most social media monitoring tools aren&#8217;t designed for a specific brand; they&#8217;re designed for every brand. This distinction imposes limits on their ability to deliver the contextual, personalized analysis brands should look for when evaluating their social performance. Measurement needs to be more than just monitoring; it has to be part of your strategy. Even a cursory [...]]]></description>
			<content:encoded><![CDATA[<p>Most social media monitoring tools aren&#8217;t designed for a specific brand; they&#8217;re designed for every brand. This distinction imposes limits on their ability to deliver the contextual, personalized analysis brands should look for when evaluating their social performance. <strong>Measurement needs to be more than just monitoring; </strong>it has to be part of your strategy.</p>
<p>Even a cursory glance at many of the most popular tools –such as Radian6, Sysomos, Lithium– show a focus on volume and activity as metrics for success. If your page, wall, or feed is seeing a flurry of activity, you&#8217;re winning. If you have more followers than the other dude, you&#8217;re winning. It&#8217;s no wonder so many brands focus on volume as a valuable metric for success.</p>
<p><span id="more-636"></span></p>
<p>These tools hope to help brands monitor their performance, but they all struggle to account for the objectives a brand is trying to solve for. None provide a range of metrics that are capable of assessing performance in truly meaningful ways &#8211; <strong>measuring where and how digital executions are succeeding or failing</strong> and providing insight into the appropriate next steps.</p>
<p>Imagine if you were VP of Customer Experience for a large hotel. It is hardly a stretch to realize that tailored metrics detailing the average time it took to reply to customer inquiries would be useful in explaining, in part, your performance across digital platforms and the value that brings to the business. To help understand how you stack up against your competitors, this (and other) metrics could then be indexed and benchmarked against data points accessible to anyone who knows where to look for them. To top it off, you’d probably want a notification pushed to your community manager&#8217;s iPhone if the response rate dropped below a set performance threshold, so they can respond appropriately. <strong>Tailoring and matching the metrics to your business objectives and measurement strategy provides much more actionable insights than measuring for volume alone.</strong></p>
<p>At scale, requests for insight like this become increasingly difficult for general-purpose social media monitoring tools to deliver upon. While great for research, general-purpose measurement tools are focussed on high-level reporting, rather than deep analysis. As a result, most who rely on them alone end up with a muddied analysis of their performance, chock-full of false positives.</p>
<p>Recognizing that social media monitoring tools aren’t delivering the right kind of value often leads to a discussion about rolling out your own tools – not something everyone is equipped to do. It can be challenging enough to design your own data mining tools, let alone retain someone who can do something useful with the data, but doing so can pay dividends. Even if you’re not ready to consider building something from the ground up, here are three questions to help you assess whether you’re set up to successfully measure your online performance.</p>
<ol>
<li>Is your measurement framework connected to meaningful data sets, where the output is a cogent, <strong>action-oriented analysis</strong> that helps inform the decisions you&#8217;re making?</li>
<li>Does the social media monitoring tool you’ve chosen allow you to <strong>plug in your own data sets</strong> (static or dynamic) for a richer, complete picture of your performance?</li>
<li>Does your level of analysis extend beyond the reports generated by these monitoring tools? They are a great start, but leave out a level of insight that’s only obtainable through a customized approach accompanied by a quality data set.</li>
</ol>
<p>What has your business been doing to measure its performance online? Could you clearly articulate the pieces of your strategy?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.undercurrent.com/post/is-your-measurement-strategy-broken/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tools vs. Content</title>
		<link>http://www.undercurrent.com/post/tools-vs-content/</link>
		<comments>http://www.undercurrent.com/post/tools-vs-content/#comments</comments>
		<pubDate>Tue, 29 Nov 2011 10:52:51 +0000</pubDate>
		<dc:creator>Matt Daniels</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[agencies]]></category>
		<category><![CDATA[brands]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[tools]]></category>

		<guid isPermaLink="false">http://staging.undercurrent.com/?p=224</guid>
		<description><![CDATA[Creating tools is attractive because of their potential – they scale, develop into platforms people use, and garner regular attention (hopefully). But brands aren’t set up to create tools effectively and efficiently. At the end of the day, they still create content. And too many brand-created tools and platforms will die a slow death rather [...]]]></description>
			<content:encoded><![CDATA[<p>Creating tools is attractive because of their potential – they scale, develop into platforms people use, and garner regular attention (hopefully). But brands aren’t set up to create tools effectively and efficiently. At the end of the day, they still create content. And too many brand-created tools and platforms will die a slow death rather than compel people to engage with them. Perhaps, but brands should consider creating tools not <em>as </em>content, but <em>to create </em>content.</p>
<p>Read more here – <a href="http://www.mdaniels.com/tools-vs-content/">http://www.mdaniels.com/tools-vs-content/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.undercurrent.com/post/tools-vs-content/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
