<?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>Mako Metrics</title>
	<atom:link href="http://makometrics.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://makometrics.com</link>
	<description>Exploring data with Lyza and Tableau</description>
	<lastBuildDate>Thu, 22 Oct 2009 05:35:15 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Tableau and Lyza Together</title>
		<link>http://makometrics.com/tableau-and-lyza-together/</link>
		<comments>http://makometrics.com/tableau-and-lyza-together/#comments</comments>
		<pubDate>Thu, 02 Jul 2009 03:00:54 +0000</pubDate>
		<dc:creator>Joe Mako</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://makometrics.com/?p=12</guid>
		<description><![CDATA[I have struggled for years to turn raw data into useful information. The two primary challenges I face are preparing data to be analyzed, and actually analyzing it.]]></description>
			<content:encoded><![CDATA[<p>I have struggled for years to turn raw data into useful information. The two primary challenges I face are preparing data to be analyzed, and actually analyzing it. I first heard about <a href="http://www.tableausoftware.com/">Tableau</a> in September of 2008 via <a href="http://flowingdata.com/">FlowingData</a>, when they <a title="FlowingData Welcomes Tableau Software" href="http://flowingdata.com/2008/09/18/flowingdata-welcomes-tableau-software/">became a sponsor of the blog</a>. I downloaded <a href="http://www.tableausoftware.com/products/trial">their trial</a>, watched some of their <a href="http://www.tableausoftware.com/learning/training/ondemand">on-demand training videos</a>, and was blown away by how easy it seemed to allow someone to look at data from many different viewpoints quickly, and their <a href="http://www.tableausoftware.com/learning/examples">examples</a> are <a href="http://www.tableausoftware.com/learning/training/ondemand/amazingthings">amazing</a>. When I first tried using it with my data, I had difficulty getting the results I was looking for; Tableau&#8217;s approach to data was very different from what I was familiar with. After attending a few of their <a href="http://www.tableausoftware.com/learning/training">live training sessions</a>, I finally grasped the concept of structured data. As I began participating in the <a href="http://www.tableausoftware.com/community/forums">Tableau User Forums</a> and reading everything I could get my hands on about quantitative analysis best practices, I took to Tableau&#8217;s philosophy, the &#8220;<a href="http://www.tableausoftware.com/videos/zen">The Zen of Visual Analysis</a>&#8221; and the &#8220;cycle of visual analysis&#8221; described as &#8220;the iterative process of asking questions, creating pictures, discovering new hypothesis, and foraging for data&#8221;, like a duck to water.</p>
<p><a href="http://www.juiceanalytics.com/">Juice Analytics</a> has a series of posts on the &#8220;5 Phases of Data Analytics Maturation&#8221; (<a href="http://www.juiceanalytics.com/writing/5-phases-data-analytics-maturation-part-1/">Part 1</a> &amp; <a href="http://www.juiceanalytics.com/writing/data-analytics-maturation-part-2/">Part 2</a>), there they describe the most developed as: &#8220;Good information tools are just like an experienced safari guide.&#8221; I feel Tableau lets me experience my data with exploration. When I open Tableau, I am preparing to go on a safari into my data with Tableau as my guide.</p>
<p>After working with Tableau, a question remained for me, how do I best prepare data for Tableau? Depending on how source data is structured, I have varying degrees of flexibility. Different types of graphs can either be available or can produce different visualizations depending on the structure of the source data. I feel Tableau works best with raw data, where each row is a distinct event or data point. Many data sets that cross my path are pre-aggregated into a crosstab tables, and this type of data structure has limited flexibility. Tableau published an Excel Add-In, <a href="http://www.tableausoftware.com/forum/using-excel-crosstab-data-source.">found on their forum</a>, that un-pivots tables in Excel. It is a useful tool, and has saved me a countless amount of time in preparing data for Tableau. Another situation is Tableau aggregates data to one level of detail per worksheet. If I wanted to show a yearly aggregate and a monthly aggregate at the same time from a per-event data set, I would have to use a dashboard. This does not limit my ability to analyze the data, but there are times when I would like to show both on the same sheet.</p>
<p><a href="http://www.lyzasoft.com/">Lyza</a> is my solution for aggregating data at multiple levels and additional data preparation tasks. With Lyza, I can use different types of data sources (Tableau can join data sources of the same type, and multiple sheets in Excel very easily), and perform a series of simple queries to accomplish a complex task. By connecting Lyza to my data first, I feel that I have no limits in visualizing the story in Tableau. I can see Lyza&#8217;s goal to be a one-stop-shop for connecting to data, reshaping and visualization, while currently, the charting capabilities of Lyza are still maturing.</p>
<p>Lyza takes the process of querying data, and turns it into four simple possible steps. Each available step is intuitive and a joy to use. Like Tableau is my guide in visual analysis, Lyza is my guide in preparing data. I don&#8217;t remember when I first heard of Lyza, likely via their <a href="http://www.twitter.com/lyzasoft">Twitter account</a>, but I delayed trying it out because I did not immediately see how it could help me in my process flow with data. I tried out another application some time later with a complex user interface and was obviously over kill for my needs, but it worked with data in a series of queries, and it reminded me of Lyza. So I downloaded a <a href="http://www.lyzasoft.com/try.php">trial of Lyza</a>, and after watching a <a href="http://www.lyzasoft.com/analyze.php">short video</a>, I was up and running with my data. On my first day of using Lyza, I recreated a process in less than an hour; it previously took me a day of programming to originally develop. Instead of writing SQL and code from scratch, I was dragging and dropping with joy. Working with data in Lyza is like grocery shopping for me, I pick what I want and what flavor I want it in, I enjoy the selection of different variations of each data point available to me, and all I have to do is pick it up, drop it, and I&#8217;ve got it. Taking this analogy further, working with data in Tableau is like cooking a meal or a great looking desert (ah, the joy of cooking) with the items I picked out in Lyza. As I am cooking up a great visualization, if I realize I need some other data point, I go back to Lyza and drop it into the data set I have Tableau connected to, and voilà, I&#8217;m visualizing data as easy as pie (but hardly ever a pie chart).</p>
<p>The initial thing that I had to learn about Lyza was their use of color and what each meant. Once I did, their use of color became a great asset in easily seeing how things are set, where they came from, are going, and what can be done. I have made some massive series of steps, and when I find that I did something wrong along the way; Lyza provides two things that ease the process of finding out what I did. First there is the visual flow chart of parent and child steps, and second, there is a way to trace where columns of data came from, by reverse. Because each query step in Lyza is simple, I find myself creating patterns of steps to accomplish results. The act of splitting a complex query into its most basic parts is not an issue because this provides me a more elemental view of how my data is flowing, and makes it easier to troubleshoot and change.</p>
<p>With Lyza, I feel that I have complete flexibility in reshaping my data any way I want. Lyza has a <a href="http://www.lyzasoft.com/support/question.php?ID=115&amp;catID=19">previous function</a> and <a href="http://www.lyzasoft.com/support/category.php?catID=20">summary functions</a> that are really powerful, I will go into detail on these in a future post, and it is truly amazing how quickly Lyza allows me to get my data shaped the way I want it.</p>
<p>Both of these applications have allowed me to accomplish things that I previously deemed too complex to be done with a reasonable amount of time and effort, into tasks that are a joy and easy.</p>
<p>Thank you for reading, and I hope you return, or add the <a href="http://makometrics.com/feed/">feed</a> to your RSS reader, for future posts as I explore data with <a href="http://www.lyzasoft.com/">Lyza</a> and <a href="http://www.tableausoftware.com/">Tableau</a> together.</p>
<p><em>Disclaimer: as of this post publish data, I had no ties with Tableau, and a referral agreement with Lyza. I received no compensation for this article.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://makometrics.com/tableau-and-lyza-together/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
