Focus and Priorities vs. Turf

When dealing with complex issues that spread across functional lines, a senior executive focusing on the issue can being important focus and coordination to the effort.

But too often, people are paying more attention to the politics of Turf instead of the value of that cross-organization emphasis.

I started thinking about this after reading a piece by Jonathan Martin of Politico. He may be right about Obama’s strategy. He believes he’s bringing power in closer to him and taking authority away from Cabinet positions. For example:

“Czar” Carol Browner will head up Obama’s fight on global warming, where once his energy and environmental chiefs might have stepped in.

[From West Wing on steroids in Obama W.H. – Jonathan Martin – Politico.com]

But the spread of authority on some issues, such as global warming, is exactly the problem that needs to be fixed. These problems need focus and it helps to have someone focusing on the issue and actively figuring out how to bring together the disparate objectives throughout the administration.

The same applies to any organization. This approach can be great for everyone involved. But infighting and turf battles do happen.

What’s the key? How does it all come together? What is it that really makes the difference?

Scobleizer — Tech geek blogger » Blog Archive Seagate learns important PR lesson: keep the customers happy! «

Robert Scoble posted details of this week’s blow-up over failing drives and censored forum posts:

Seagate (maker of hard drives and storage devices) has been getting slammed on forums and blogs the past couple of days. Partly because they had a bad batch of hard drives and didn’t properly recognize or fix the problem quickly. Partly because they removed a few anti-Seagate threads from its forums.

[From Scobleizer — Tech geek blogger » Blog Archive Seagate learns important PR lesson: keep the customers happy! «]

This one is going in my file for great examples. It’s surprising how often you’ve got to walk companies through this logic.

Ross Mayfield’s Weblog: Service and the Fifty Percent Rule

This week, Ross Mayfield makes an interesting point about the level of service experience at the Apple Store. It’s a brilliant post and poses some great follow-on questions, but the thing I liked most was this point about support knowledge:

But I think Apple gets something more than the value of customer experience. According to the Consortium of Service Innovation, there is an iceberg effect for product knowledge. 90% of conversations about supporting products never touch the company. Only 10% touch the call center. And 1% of this service and product quality knowledge are assimilated.

Sometimes this distribution is purposeful. Support is viewed as a cost center. Time to resolution (which we’ve decreased by as much as 30%) often trumps customer satisfaction or capturing knowledge. Worst practices are often employed to incent contact center reps to avoid contact.

The problem is far worse with multi-vendor support. Multi-vendor issues take 3-4 times longer to resolve. So almost all vendors explicitly do not support these issues at all. There is some promise in Vendor Relationship Management, or communities that address systemic needs through the demand side supplying itself, but only the beginning of promise.

[From Ross Mayfield’s Weblog: Service and the Fifty Percent Rule]

How is your performance? Do you even measure knowledge creation rates? Do you know how many of your support center cases are already solved in the knowledge base, but customers aren’t finding it?

Perhaps more importantly, have you moved past “call avoidance” to embrace Customer Engagement the way Apple has in the Apple Store?

FriendFeed, value, and … on Gillmor Gang

The May 30th Gillmor Gang is all about FriendFeed and it’s one of the best I’ve heard.

http://gillmorgang.techcrunch.com/2008/05/31/gillmor-gang-053008/

Why FriendFeed Matters

Bret Taylor of FriendFeed makes the point that different people use different tools, and that’s one of the reasons he created FriendFeed. He says: “The union of all of your friend’s one or two services is a really diverse set of information and a really diverse array of services.”

For me, this is the key point. I shouldn’t have to use the same tool as my friends in order to see their photos, videos, favorite music or movies, recommended news articles or podcasts. The key is in how usable my view into all this information can be.

Following the conversation

Today we can search, but when the conversation is flying, I really want to see “who else is talking about this”. Within that view, I may want to be able to limit it to what my friends are saying, or maybe what their friends are saying, or just see the whole conversation.

This is not a trivial problem. The conversation isn’t a single thread; it doesn’t start from a single place. So bringing it all together in a coherent way is not easy. I shouldn’t have to be an expert at crafting a search string in order to find and follow the conversation. That search complexity should be hidden – It needs to be a usable, intuitive interface that lets me focus on the content, on the conversation.

Segmentation of content

I’m not very interested in Robert Scoble’s twitter feed or his shows on Qik, but I’m very interested in his events list on Upcoming, shared items from Google Reader and his detailed posts on technology. Can FriendFeed be the place where I follow just the parts of Scoble’s prodigious output that interests me? Can this kind of fussy control be provided without making the user experience so dense that it drives away users?

Take a Listen

The Gillmor Gang today covered all these questions and more. It was a fascinating hour, and the FriendFeed team handled it all thoughtfully and with great insight.

Hugh McLeod says “Being a nucleus is the money shot” for FriendFeed, and I think he’s right. The FriendFeed team seems poised to really make it work.

Why the Open will win

Why the Open will win

If only my friends who have accounts in the same service can see my photos or favorite music or restaurants, then I will put less energy into participating in that service. But with a mesh of services connected by common syndication formats and open APIs (Application Programming Interfaces), my friends and I can share and converse amongst ourselves or with the connected world, independent of which tools we use.

For all the services using this open model, this network of tools brings audience. People who share photos, recommend an interesting article, or podcast, or coming event will pull more people into the conversation – a conversation tied to the open mesh of tools.

Any company that sticks to a silo strategy will fail. Instead of the silo communities locking in their users, they will be locked out of the conversation.