Month: September 2015

Alteryx and Tableau, yin and yang

Many of those who watch the amazing acrobatics in Tableau or other visualization tool find there’s one more spectacle to come: setting up the data — cleaning it, fixing incomplete sets, combining sources, and so on. Only when that’s over can real analysis commence.

Many advanced users still prefer to use a specialized tool for prep. Strong contenders have appeared for graduates of Excel, including Paxata and Trifacta. But it’s Alteryx I finally got a look at not so long ago.

I was curious about Alteryx. It seems to have become the go-to among advanced users of Tableau, which at first seemed odd. To my novice eye, Paxata and Trifacta seem more like Tableau, so why wouldn’t users flock there instead? Based on what I’ve heard from one Tableau super-user I know, Joe Mako, the answer must be in the contrast. Alteryx and Tableau just approach work differently.

Before I talked to Joe, I followed Alteryx chief scientist Dan Putler as he walked through a data analysis challenge. The question: Which of many alumni who have never donated any money are most likely to give some if asked in a new donation drive? A certain public university’s development office would solicit the most likely ones by phone. As if that weren’t enough work, the development staff could make no more than about 10,000 calls per year. Who should they call first? Data on each alumnus included age, area of study, social or familial associations with the university, and a handful of other facts. The answer: the alumnus’s area of study. Putler showed it in a line chart, the results of three of his competing models compared with past experience.

It was an interesting problem, but getting to that answer was most of the fun.

Putler describes Alteryx as a “visual programming framework,” he says, that’s often compared to Visio, the Microsoft diagramming application. Just like in Tableau, its drag and drop interface is friendly to beginners. Unlike Tableau, coding is there for the advanced. A wide range of ready-made possibilities line an upper row of the workspace. Handy documentation has explanations and samples, effective even for those whose ghost-like memory of a statistics class years ago lingers on the edge of awareness.

Also unlike in Tableau, all the details are right out in the open. You see exactly what happens to the data as you do what you will with it.

Putler’s models grow into a diagram that shows exactly what will happen to the data at every step. This is the part of data analysis that resembles detective story, where you sift facts to find the most cogent narrative.

That transparency and control is why Joe Mako prefers Alteryx. Joe is the almost legendary Tableau super-user and volunteer guide. For more than five years, he’s spent hours every week helping even some of the most advanced users figure out how to make Tableau do what they want it to do.

“It’s like having a kitchen,” he says, “and Tableau and Alteryx are your appliances. You can cook without them, but your life in the kitchen is so much better if you have them.” Even better if you use them the way they work best.

“Tableau and Alteryx are wonderful together,” he says. “To me, they’re like yin and yang. They’re both wonderful, but they’re both challenging.”

Tableau’s goal is to make its complexity invisible, which is both good and bad. It powerfully enables the cycle of visual analysis, the uninterrupted flow of questions, insights, and more questions. He says, “No one else comes close.”

But the magic has a flip side. Though the unseen magician almost always guesses correctly what you want to do, it can be fooled by unusually complex work — such as the kind Joe often does. That’s when the magic fails. The computation logic could change without the user’s knowledge or control. A feature known as data densification seems to be one of Joe’s main culprits. (See his video on data densification.)

If Tableau employs an unseen magician, you might say that Alteryx employs a fully visible carpenter. What it does, it does in full view, consistently. Joe says, “It’s the tool you turn to once you need to work with a millions of records and do hard computing and make it a repeatable, self-documenting process instead of a manual, brute-force, hand jammed thing. It lets me codify a thought process.”

Though complex computations can be done without writing code, you can write code if you want to. The user with a sketchy knowledge of some complex predictive logic can open a module with a use case and a description of what it does at input and what comes out on the other end.

Even the icons signify with consistent colors and shapes what each one does. In a series, they reveal at a glance a chain of functions. Joe says, referring to a process he’s constructed, “I see here that I’m pulling the data in, joining it, and I split it out into some groups, and then I put it all back together one piece at a time, precisely how I want it to be pulled back together, and then output it. I get exact control.”

The main downside, he says, is weak interactive visualization. He believes Alteryx simply wasn’t designed for it.

You pick the tool for the job: Tableau to do the visual analysis, and Alteryx to do the tech-side stuff. Joe says, “Together, they’re nirvana.”