Wednesday, May 7, 2008
See Data, Feel Data, Touch Data...for free?
Meanwhile, Google may also be seeking to make a dent in the area of data visualization. Building on last year's acquisition of Gapminder's Trendanalyzer, Google released a data visualization API, essentially a platform to create interesting displays based on structured data stored in Google Docs.
Initially, there's simply a "cool" factor at work here - "If I could get that salary list, I could post a piles-of-money gadget around the office!" But are there competitive implications? It's interesting that for as many years as it's taken for real on-line competition for Office to emerge, there could be a viable alternative in the much younger data visualization space much sooner.
There are so many questions - What are Google's long-term intentions in this space? Will it be a drag for the leading BI vendors, or will it help popularize the concept and "raise all boats"? Will Google's experience in search engines mean we can expect it to lead the way with unstructured data visualization?
Saturday, May 3, 2008
Lowering the Bar for Data Visualization
So what does the watch actually do?
“With no display for the hours, minutes or seconds, the Day&Night offers a new way of measuring time, splitting the universe of time into two fundamentally opposing sections: day versus night.”
Day versus night, huh? And it sells out for an unbelievable price?
I'm going to start working on a new dashboard project, directed at CEOs of multi-billion dollar firms.
It won't have KPI's, trends, links or navigation; all it will do is flash two words - either "MAKING MONEY" or "LOSING MONEY".
Next I'll develop a separate version to sell sports teams - a new scoreboard that flashes only whether the home team is "WINNING," "LOSING" OR "TIED".
Monday, April 28, 2008
What Gets in the Way of Good Analytics?
Today at Bank Systems and Technology, there’s an article on the increasing importance of analytics to the banking industry. The story is fairly typical in the genre – “we used to manage by gut, but better information about our customers can help us in so many ways!”
What caught my attention was that quite a few of the contributed quotes came from places on the org chart that just don't exist at most organizations – the “Director of Statistics and Modeling” and the “Department of Insight and Innovation” to name two. These references were threaded alongside a frequent comparison of “mature” analytics areas, such as credit card predictive modeling and “growing” areas, such as customer attrition modeling. This might suggest that organizations who create a dedicated function related to analytics and related disciplines are more successful at spreading the competency internally than those organizations that leave it to chance. This is certainly the position put forth by Thomas Davenport in Competing on Analytics, and is certainly intuitive in some respects.
It’s easy to envision a success story for such a group – evangelizing the power of analytics, introducing new skills to functions without a historical strength in analysis, etc. But what are the likely barriers and points of failure? How can an organization considering such an investment get ahead of the curve and mitigate the risk?
I’d speculate there are a handful of key reasons for struggle or failure:
- Lack of a starting point / quick win “pilot” - Perhaps it is difficult for a Center of Excellence-type structure to get off the ground without one demonstrated benefit within the first year or so
- Insufficient data trail - For businesses or domains without a solid trail of transactional information, it might be tougher to get started (there goes my idea for a chain of cash-only restaurants with no POS system)
- Lack of data architecture / infrastructure investment - If a new analytics team’s first report includes a request for $5 million just to organize the data, rough roads may be ahead
- Active resistance to the scientific approach - If a CEO is commonly heard to say “you guys think too much,” is that an organization likely to be hospitable to analytics?
What do you think is the biggest barrier? One I didn’t identify? What are the keys to success in building an organization's overall competency in analytics?
Thursday, April 17, 2008
Politics: There's No "I" in "DIG"
What do sports, politics and DIG have in common? Well, of course, it’s prediction markets. There’s Protrade, and Tradesports and the Iowa Electronic Markets and, well,
In the last few years, some individuals and organizations have begun to make a dent in this space; notably among them Get Out the Vote: How to Increase Voter Turnout by a couple of Yale professors who base their recommendations on actual research. More recently, Brendan Nyhan at Duke reports on his blog the founding of “The Analyst Institute,” which states as its mission “for all voter contact to be informed by evidence-based best practices. To ensure that the progressive community becomes more effective with every election, we facilitate and support organizations in building evaluation into their election plans.”
It’s not as if there isn’t incentive to win, and it’s not as if there’s a lack of interested funding. So why is politics behind the curve on data and analytics? Is there a rational (or irrational) belief that politics need to be managed by gut? Or are there structural reasons? Or am I mistaken in thinking politics is late to the game, and that McCain is hiding the next Billy Beane somewhere on the Straight Talk Express?
Wednesday, April 9, 2008
In the Mood
Consider this an open thread to share book and article recommendations related to data, analytics or enterprise 2.0. The poster with the most compelling suggestion will...be treated to their choice of a soft drink or adult beverage at the Green Valley Ranch by legendary DIG conference chair Pete “Memphis Ruined My Week” Graham.
Tuesday, April 1, 2008
Opening Day (Part 2)
To help me get ready for the upcoming baseball season, I recently purchased the 2008 Baseball Prospectus, an annual almanac of analysis and predictions from the folks who brought us 21st century metrics like VORP (Value Over Replacement-level Player) and BABIP (Batting Average on Balls In Play).
- Boil the frog slowly – If On-Base Percentage really correlates better with runs scored than batting average, well, who am I to argue? And if that's true, then maybe I ought to listen to some of your other ideas...
- Myth-busting – Some assertions have been controversial (e.g. “There’s no such thing as a clutch player”), but maybe they’re plausible and interesting enough to get attention
- Case studies – Michael Lewis’ best-seller Moneyball and the 2004 and 2007 Boston Red Sox (World Series winners) have shined a public light on organizations that succeeded with analytics-friendly leadership
- Audience evolution – People in general have better quantitative reasoning skills than they did, say, 20 years ago, and so are more open to evidence-based insights
Here’s my question, and it’s not about baseball: In your organization and mine, a major barrier to extracting value from analytics is a rejection of the methods and implications from (for lack of a better term) the “old school” crowd. What’s the best way to make the case for analytics in your organization? Take on a single cherished nugget of conventional wisdom and prove it wrong? Or is that too risky? Is it better to plug along cautiously, incrementally adding some objectivity and trickling new metrics into the soup until the organization is ready? Or is it the Moneyball approach – find one manager willing to try the Kool-Aid and make something happen?
Opening Day (Part 1): Roger Clemens is Innocent
I’m excited to join such a distinguished group of bloggers, and proud to reveal a new analytic insight in my first post.
It seems to be the consensus among baseball fans that Roger Clemens used performance enhancing drugs in the latter stages of his Hall of Fame career. Accusers support their claims by referring to his apparent improvement when he left the Boston Red Sox for the Toronto Blue Jays before the 1997 season, right before his age-34 season. But advanced analytics tell a different story altogether.
Using some new functionality in the latest version of SAS, I created two new metrics. One is something I call Adjusted Prevented Runs (In League). Basically, it controls for a handful of factors not addressed in the pitching metrics most favored by sabermetricians today and in one number tells you how effective a starting pitcher is, relative to the rest of the league, in keeping the opposing team from scoring. I call the second metric Factored Outs Over League, because in terms of pitching performance, while keeping opposition runs down is the ultimate goal, the way to achieve it is by getting outs. It’s like a pitcher’s version of On Base Percentage.