Rating:

Straight from the Horse's Mouth with Livia Labate and Austin Govella











iTunes     Download    Del.icio.us     Pod-safe music generously provided by Sonic Blue

banda_headphones_sm.gif Christina Wodtke traveled with microphone to the IA Summit in Las Vegas this year and sat down with some of the most interesting and accomplished information archictects and designers in all the land. Bill Wetherell recorded those five conversations, and now B&A is proud to bring them to you. Thanks to AOL for sponsoring these podcasts.

Christina talks with Livia Labate and Austin Govella about the UX practice in Comcast and how they have created an environment where they are treated as colleagues rather than a service organization.

We discuss…

Big IA vs. Little IA
Livia describes “Little IA” as the bottom-up approach to projects looking at the structure and organization of content. While “Big IA” is about acquiring user and business needs and then converging these, taking content and structure into account.

Defining the damn thing
Does the role define the person or does the person define the role? Austin believes that job titles are not relevant any more. What matters is learning from other professionals to improve upon a product or create a new solution to an old problem.

Ying Yang
The need for “specialization” and the need for “collaboration” in business is a big challenge. These two important yet distinct elements are rarely looked at in harmony.

What is IA all about…besides “herding cats?”
Livia defines this process through their mission statement: “Balancing user needs and business goals to create a framework in creating positive user experience”. This helps them define the boundaries of Information Architecture.

Looking through the Looking Glass
Austin suggests reading business publications thereby changing the words you use to sell ideas to different members of the corporation. Dress code also impacts the kinds of conversations you have with the client. Know who you are presenting too, and dress the part.

Describing Value
Austin discusses the importance of talking to business leaders about design choices in their own language. For example, “this move will decrease our acquisition rate”...”decrease our ability to convert people”...”decrease our referrals.” In essence, know your audience and speak their language.

Secrets to Success
Christina sums up this conversation beautifully, ”...learn the language, lose the agenda, be a resource, and dress better!”

Rate This Story

Register or log in to rate
 
Share on Facebook

Readers' Comments (4)

Michael Beavers's avatar

Michael Beavers

69 Reputation points

Posted 2007/06/05 @ 14:09PM with

Nice and tidy interview, Christina. Excellent information for putting IAs in businesspeoples’ shoes—and clothes.

Matthew  Doty's avatar

Matthew Doty

1 Reputation points

Posted 2007/06/11 @ 13:05PM with

Great interview! Very practical and informative… and brief. Great “ROI” for the 18 minutes it takes to listen to it.

Adam Polansky's avatar

Adam Polansky

55 Reputation points

Posted 2007/06/12 @ 07:39AM with

Well done. It’s a difficult reality that the needs of the business don’t always run true with what would empirically inform UX efforts.

It’s the ability to manage those relationships – the compromises and the understanding of others goals, that moves projects into production. Yes, you might have to hold your nose as you identify ad space in your wireframe but you pick your battles. The consessions you make on one item result in the latitude to take a risk elsewhere.

Hopefully, over time, you can influence business owners to see and belive that usable products DO generate more revenue and DO save costs!

Henrik Arndt's avatar

Henrik Arndt

3 Reputation points

Posted 2007/06/14 @ 02:45AM with

What information architects demand of a good website they should do themselves: Structuring and presenting information in the language and style of their target group (the client) and not insist on their own language and structure. If business people can understand what they get for their money, they pay for information architecture.

Great interview.