Tag Archive for Adobe

FAQ

Eight months ago, on this blog, I described with excitement my decision to leave Adobe and join ESPN as an analytics manager. At the time, I knew that I was embarking on a tremendous learning experience, and I thought I even knew how everything would go. Sports, analytics, and New England; how could I lose? Call it a youthful sense of invincibility, if you will.

Well, as of this past Monday, I have rejoined Adobe, and I am thrilled, excited, and grateful for the entire turn of events. The Adobe Digital Marketing Summit took place this past week in Salt Lake City, and as I wandered the halls of the Salt Palace among colleagues, customers, and industry folks, a few things happened.

First, I felt like I was home, immediately. Second, I answered a barrage of questions about the past eight months. I took mental note of these questions and I’m going to answer them here, in good old FAQ form. So here we go.

FREQUENTLY ASKED QUESTIONS ABOUT BEN’S RETURN TO ADOBE

Q: So. . . what happened?

A: This is actually a tremendously complicated question, but I will simplify it by saying that once I started at ESPN, I quickly started to realize that making software is what gets me out of bed in the morning. When one of the engineers at Adobe asked me this question, I told him that I was sure he could go be a fantastic analyst, but he probably wouldn’t enjoy it—he needs to be programming and solving problems using code. That’s just in his DNA. I certainly could have stuck it out—and, in fact, tried to stick it out—but it wasn’t for me. If I needed to spend this time in order to learn that lesson, I can’t say that it wasn’t worth it. I’ve got a strong sense of direction for the foreseeable future, and that’s valuable.

Q: How were the people at ESPN?

A: They were great, and I consider many of them friends. In fact, I saw them at Summit and it wasn’t weird. . . well, it wasn’t too weird, at least. I’m so grateful that they gave me a chance. They’re brilliant and they are doing cutting-edge things with digital analytics. If you ever have a chance to them talk about cross-platform analysis, as my former VP Dave Coletti did at eMetrics NYC last October, you will know what I mean.

Q: What will you be doing at Adobe?

A: I’m returning to the Product Management team, working on analytics products—SiteCatalyst and more. When I originally joined that team almost two years ago, I wrote that I felt like a minor-league baseball player getting the call-up to the majors to play with his heroes. I still feel that way, and am excited to be part of such a bright and talented group. It seems that Adobe’s recent acquisitions have only added to the brainpower and passion. I hope that I now bring at least a little bit of unique insight having been an analytics practitioner for most of the past year.

Q: Are you staying in Connecticut, or moving back to Utah?

A: Actually, we have really enjoyed our time in Connecticut. The area is beautiful and our neighborhood is full of kids who want to play with our daughters almost constantly. But we still own our home in Utah, and rented in Connecticut, and it’s time to get back to the family and friends that we’ve missed so badly. But we had a great quality of life in both Utah and Connecticut. We will definitely miss Connecticut and hope to visit our friends there in the future.

Q: Why did you go back to Adobe?

A: First, as I mentioned above, I need to be in tech/software. That’s a given. Second, I believe in what Adobe is doing in digital marketing and I want to be a part of it. Third, there is a reason that Adobe consistently appears on Fortune’s “top places to work” list. It really is a fantastic company in too many ways to list here, but I especially love the way Adobe trusts its employees and values input from all over the organization. At least, that has been my experience, and I hope it will be again.

In 2011, Good Changes Take Time

This is not an Omniture-versus-Google Analytics post. This is not a Google Analytics-bashing post.

This is a post in which I defend a decision that I helped (in some tiny way) to make when I was a Product Manager on the SiteCatalyst team at Adobe.

In 2011, businesses rely heavily on their web analytics data. Analytics may not be where we’d like to see it yet, but it certainly has come a long way over the past decade. And the more critical this data becomes, the more resistant customers will be to uncomfortable change.

SiteCatalyst 15 introduced major changes to the Omniture platform. This brought some great features with it: segmentation, breakdowns on all conversion variables, Processing Rules, etc. But it also introduced change. Specifically, it affected the way that SiteCatalyst determined the number of visits to customers’ sites/apps. In most implementations, it was a minor change, but in some cases it was noticeable in client data. (You can read all about these changes here.)

Because this platform change potentially affected things like year-over-year comparisons and conversion rate, some of our customers weren’t comfortable making the change to the new platform right away. They told us that they wanted some time to understand the new platform and its effects on their business.

As I explained on Eric Peterson’s epic (and awesome) Google+ thread last week:

The feedback that we got on this was that it was significantly painful for many users to have that change occur, but that they acknowledged the improvement. So, if you’re Adobe, do you make the change and alienate some users, or do you hold off and alienate other users?

Alyson Murphy echoed this thought:

Can you really expect Omniture to implement a major paradigm shift without alienating a ton of customers? People love their comparison data. Look at how difficult it is for some companies to shift to SiteCatalyst 15. If a relatively small change compared to what you are suggesting causes that much pain, a huge paradigm shift isn’t going to go over too well with many of their clients.

The day Alyson and I made these comments, Google announced in a blog post that it had also changed the way it calculates Visits. Now, any new traffic source encountered by a user (paid search, natural search, affiliate, social media, etc.) would instantiate a new visit/session. The reaction from customers in the blog comments has been. . . interesting:

I am see weird stuff bounce rate up 50% time on site down 75% this happened from 11th August. on most visits it count each page viewed as a new visit.

Good Grief, less then a 1% change!
“Based on our research” I would love to know how you conducted this research.

I am seeing 20% increase in visits, I thought I had finally broken free of Panda!

How I am supposed to evaluate these new metrics on steroids vs my previous metrics?

My average time on site has fallen from 7+ minutes to 12 seconds. Each visitor seems to visit the same page 6 times causing my bounce rate to be ridiculous.

I think that this update is an example of someone fixing something that wasn’t broken. Now analytics is useless.

The update makes my data virtually useless. It makes no sense.

Over the weekend, I feel that around. half of my visits are returning visitors, and the same guest may have seen the same item up to 10 times. In return, my bouncerate sky-high.

It is a vital part to have a website to have a reliable analysis program, but GA is certainly not very reliable right now, and in my case the data produced now are completely useless.

I think Google Analytics is a great tool. I use it. I use it from time to time on this blog and others, and I like it. This isn’t a complaint about Google Analytics. It is a statement about the way an upgrade which may actually be a very good thing (in terms of helping customers understand their customers and improve conversion) was handled in two different cases. I’m sure someone could explain why that last poster’s average time spent dropped precipitously, and why the new data is more accurate or more actionable.

But that’s not the point.

Conclusion? In 2011, you CANNOT just slap platform changes into your analytics platform, call it good, and expect businesses to adjust on the fly.

When I joined the Product Management team at Adobe in May 2010, we were in the midst of having this conversation with users. On one hand, it was disappointing to hear that so many felt that their users and their businesses needed time—in some cases, at companies with hundreds of users, a lot of time—to prepare for platform changes that everyone agreed were exciting. On the other, it was great to know that SiteCatalyst was that critical to various business processes even outside of the analytics team. But it’s really hard to explain to an executive why conversion rate suddenly dropped by 5% because your analytics tool changed. That’s what required time.

I’m proud that we listened to these customers and that we both a.) released a product with significant platform improvements and b.) created a system that allowed users to prepare before having these changes dropped on their plates. Is the SiteCatalyst 15 upgrade process perfect? Certainly not. But, as I mentioned above, there are considerations beyond simply the need to prepare for a change in visit calculations, and I know for a fact that Adobe continues to adapt and optimize the upgrade process.

(Also, in all fairness, Omniture has been fairly accused to making changes on the fly in the past. For example, in 2006, a SiteCatalyst point release corrected the way that search engines were identified, updating the platform to use both referring domain and referrer query string for improved accuracy. Like I said, this isn’t a tool-versus-tool argument. It’s an observation about the importance of data.)

One more thing: Anyone who tells you that only the analyst matters is fooling you. Anyone who tells you that your analytics tool only needs to serve the analyst is living in a dream world. That may have been true in 2005, but that is not how the real world works in 2011. People all over the business need data. Yeah, sometimes it’s just a perfunctory year-over-year visits comparison. Does it improve on-site conversion? Maybe not. But it matters somewhere else, to someone. Probably to someone who can influence the success of analytics in the business. Analysts had few problems with the platform changes that SiteCatalyst 15 brought, but they knew that, in order for them to succeed and to be trusted to help guide the business, their users needed to know what is going on in SiteCatalyst and not to have metrics changing unexpectedly.

So, when people say, “How come Omniture hasn’t delivered the kitchen sink yet?” remember that this isn’t a fantasy world where wholesale changes can slide right into the businesses painlessly. Google’s platform change proved that, as did the feedback we got from customers at Adobe.

The move

(I thought this post would be easier to write.)

I don’t want to bury the lead, so I’ll just say it: At the end of this week, I will be leaving my post as Product Manager on the SiteCatalyst team at Adobe and taking a position as Manager of Research Analytics for ESPN. I’m tremendously excited, although I will miss many people, places, and things that my family and I have come to love during our time here in Utah, and specifically at Omniture/Adobe.

(Fortunately, the world is a lot smaller than it used to be. I’m still going to pester you, Jeff Jordan. I’m keeping your number in my phone. You’ve been warned. Oh, and Ambria? I’ll be giving out your e-mail address to everyone who wants to participate in one of your beta tests.)

The past five years at Omniture (now Adobe) have been an honor. I feel it’s important to mention that there is probably one company on the planet that could wrestle me away from Adobe at this time, and that is ESPN. In case my blog hasn’t made it clear already, I’m a sports nut who loves analytics and grew up in New England. ESPN combines all three of those things. (Plus, Bristol is only two hours from Fenway Park.) The point is that I am not making this move out of frustration, disenchantment, or fear about the future.

I don’t want anyone to think otherwise for even half a second.

My greatest concern is that people in the #omniture community that I helped build on Twitter will jump to foolhardy conclusions. That’s the downside of having been one of public faces of a brand on social media—when you leave, it never looks good. I know this because I’ve been in the “rush-to-judgment” camp before. For example, I wondered about Comcast when Frank Eliason left last year. How could Comcast have lost Frank? Things must be really bad for him over there.

How could Omniture have lost Ben? They didn’t. ESPN won me. There’s a huge difference.

I’m looking forward to writing often here as I begin to explore life as a daily practitioner of analytics. I performed analysis frequently as a Product Manager (and previously) at Adobe—as I hope you’d assume, we do use SiteCatalyst heavily to analyze and optimize SiteCatalyst—but I also spent a lot of time on other things. Fortunately, I’ve been taught well by mentors too numerous to name, and I hope to do them proud.

You can expect plenty of continued involvement in the analytics community, as well. In fact, I hope that I can participate in new and exciting ways, now that I won’t be a “second-class citizen” (as described—correctly, I think—by Jennifer Day on Emer Kirrane’s blog). On this site, I’m hoping to continue to write posts similar to those I’ve been publishing on the Omniture blog since 2009, discussing implementation, analysis, and more, as well as whatever else I decide is worth writing.

So, there you have it. If you’re ever in the Bristol, CT area, please drop me a line.